Red Hat JBoss Core Services Collection FAQ

Updated

  • Who is entitled to Core Services?
    All entitled users of JBoss Middleware products, with the exception of users exclusively entitled to JBoss Web Server, are entitled to all Core Services Collection components. JWS users are entitled to use the Core Services HTTP Server, as that distribution is shared across the Core Services and JWS entitlements.

  • What are the components in Core Services?
    As of May 2016, the Core Services Collection includes Red Hat Single Sign-On, Apache HTTP, JBoss Operations Network, Apache Jsvc, and web server connectors for IIS and iPlanet.

  • What are the supported configurations for the core services?
    The supported configurations for each core services component are listed on this page.

  • Can I run an unlimited amount of core services in production?
    No, Core Services provides an entitlement model that limits the number of processor cores that can be used in production by core services components.

  • How many cores can I run core services components on?
    You can run up to an equal number of cores of core services components equal to your product entitlement. For example, if you have a 64 core subscription of EAP, you can run the core services components on an additional 64 processor cores.

  • Can I split my pool of core service entitlements across multiple services?
    Yes. If you have 64 cores of core services available, you can split them into any distribution that total 64 or less. For example, you can run 32 cores of Apache HTTP, 16 cores of Red Hat Single Sign On, and 16 cores of JBoss Operations Network.

  • Does Core Services have a defined lifecycle?
    The Core Services Collection does not have a lifecycle, but each component in the collection has a lifecycle of it's own. Each component has a lifecycle that has been selected based upon several characteristics of the component including its maturity and the frequency of major version updates. The lifecycles can be found on the Red Hat JBoss Middleware Product Update and Support Policy page.

  • How is maintenance provided for the core services?
    Each core service component will receive maintenance in accordance with its lifecycle phase according to the Red Hat JBoss Middleware Product Update and Support Policy page. The maintenance releases are not coordinated with product maintenance releases but rather produced to optimally support the component itself.

  • Does my Core Services entitlement apply to OpenShift?
    No. Red Hat Single Sign On is the only Core Services component available on OpenShift, and it is included in the OpenShift entitlement. A Core Services entitlement is not required and use of Red Hat SSO will not count against your Core Services entitlement if you do have one.

  • How does Core Services entitlements work with Red Hat Middleware bundles (Red Hat Runtimes, Red Hat Integration, Red Hat Process Automation)?
    Just as with individual products, customers can run an equal number of cores of Core Services along with the core entitlements from the Bundles. For example, a customer who purchases 16-cores of Red Hat Integration gets two production-SLA entitlements:

    • 16-cores of any combination of Integration or Runtimes products - Fuse, AMQ, 3scale, EAP, RHOAR, JWS, Data Grid
    • 16-cores of "Core Services" - which includes RH-SSO and other components
Article Type