Tomitribe Subscription Guide

Tomitribe’s support subscription is more than just a support plan; it’s peace of mind that your deployment is running at optimal performance and with very little, if any, downtime.. Your direct connection with Tomitribe’s developers and founding contributors of the Apache TomEE Open Source project means you’re getting expert advice and support from the best.

Subscription Guidelines

Deployment Type

Tomitribe support subscription accounts for both physical and virtual deployment type with the flexibility of selecting the support plan with the least core count as defined.

Virtual Deployments
  • When using virtualization software, only instances assigned to run TomEE will be counted.
  • Example: A server with four quad-core CPU (16 physical cores) is virtualized and assigns two quad-core CPU to run TomEE; this would count as eight TomEE cores.
Physical Deployments
  • When deploying TomEE directly on physical servers, without virtualization software, the total number of processor cores on the server will be counted.
  • Example: Two servers with two dual-core CPUs (4-cores/server, 8 physical cores total) would count as eight TomEE cores.
Partitioned Physical Deployments
  • When deploying TomEE directly on physical servers, without virtualization software and is partitioned, the total number of processor cores on the partition running on TomEE will be counted
  • Example: A server with four quad-core CPU (16 physical cores per server), partitioned equally in two and only one partition is assigned to run TomEE; this would count as eight TomEE cores

Processor Core Allocation by Environment Types

Processor core allocation for support applies to production, QA, testing, staging and hot disaster recovery environments of virtual and physical deployments. The number of cores counted is an aggregate of either physical or virtual cores for these environments combined.

Production Environment: Live Production Servers
  • This environment will be defined by virtual or physical deployment type and the core count will be counted according to the deployment type definition
  • To receive support, an active and valid production support subscription is required
Non-production Environments: Testing, Quality Assurance (QA), User Acceptance Testing (UAT), Staging, Hot/Cold Disaster Recovery, and Development
  • Non-production environments are voluntary and require support only at the discretion of the customer
  • To receive support, an active and valid support subscription is required naming each supported Non-production environment
  • Each environment will be defined by virtual or physical deployment type and the core count will be counted according to the deployment type definition

Learn more about the
Tomitribe Community Partnership Program

Tomitribe’s Community Partnership Program is an innovative rewards-based program that pays you back for supporting the community.

Like what you see and have some questions?

Get in touch with us