Jboss Enterprise Application Platform

What is Jboss Enterprise Application Platform:

•Based on the deployment data collected the main Jboss middleware application deployed in Adecco’s estate is Jboss Enterprise Application Platform (Jboss EAP).

•Jboss EAP is one of the markets leading open source platform for java applications deployed in enterprise environments.

•The platform offers powerful management and automation helping to increase developers productivity.

Licensing Jboss Enterprise Application Platform: 

Licensed via number of physical processor cores for example deploying Red Hat Middleware on two four core processors would count as 8 cores.

•A Red Hat subscription is required for each and every instance or installation of a Jboss product. However Jboss is licensed via cores.

•Jboss Subscriptions are sold in increments of 16 or 64 processors cores.

Licensing Jboss Enterprise Application Platform in physical deployments:

•Licensed via number of physical processor cores for example deploying Red Hat Middle ware on two four core processors would count as 8 cores.

•When Red Hat Jboss middleware is deployed on a physical server using OS partitioning, only the total number of physical cores assigned to the OS partitioning containing Jboss Middleware is counted.

•For example: an eight-core physical server is partitioned into two equal partitions, each allocated four processor cores. A Red Hat Jboss middleware product is deployed to only one of these partitions and on the cores allocated to the partition containing Red Hat Jboss middleware are counted.

Licensing Jboss Enterprise Application Platform in virtual deployments:

•Licensed via number of virtual cores for example deploying Red Hat Middleware on 14 core VM would count as a subscription requirement 14 cores.

Licensing Jboss Enterprise Application Platform in physical deployments when partitioning: 

When Red Hat Jboss middleware is deployed on a physical server using OS partitioning, only the total number of physical cores assigned to the OS partitioning containing Jboss Middleware is counted.

For example: an eight-core physical server is partitioned into two equal partitions, each allocated four   processor cores. A Red Hat Jboss middleware product is deployed to only one of these partitions and on   the cores allocated to the partition containing Red Hat Jboss middleware are counted.

Jboss Middleware SLAs

•Jboss Middleware subscriptions are offered with a choice of either Standard or Premium SLAs.

•Standard SLAs provide coverage in normal business hours whilst premium SLAs are 24/7, different SLA types can be mixed and matched across any type of environment.

Other information:

•When allocating core subscriptions production, test, hot disaster recover/failover cores are counted however cold disaster recovery cores are not counted.

•Subscribers to any individual Jboss middleware products have access too all of the products in the Jboss middleware portfolio for development use this is provided to 25 users with every 16 cores of a Jboss Middleware product under subscription.