Managing Service Containers

Service Container is a component of TrueSight Capacity Optimization architecture that can run backend services. It provides you with the ability to isolate backend services to improve their resilience and workload balancing. More than one Service Container can be defined.

Service containers and backend services

Some backend services that run in the Data Hub component are relocatable, that is, they can run either in the Data Hub, or in a Service Container. In terms of implementation, a Generic Service Container is an additional (but separate) instance of an Apache Tomcat Application Server, and is deployed alongside the TrueSight Capacity Optimization Data Hub on the primary application server. However, a secondary application server machine (if available) might also run a Generic Service Container.

The Generic Service Container component is part of and resides on the the Application Server computer. By default it is not turned on, but relocating a backend service to a Service Container automatically turns it on.

Whether or not to relocate services is a decision that must be made based on the expected workload for particular services. For more information on relocation guidelines, see Guidelines for relocating backend services to Service Containers.

For more information, refer to the following sections:

Types of Service Containers

TrueSight Capacity Optimization offers the following types of Service Containers:

  • Data Hub: Available in versions of TrueSight Capacity Optimization prior to 10.0.00. It can host any backend service.
  • Generic Service Container: Capable of hosting selected backend services, such as CAPA, Data API, by the process of Relocation. All backend services cannot be relocated to the Generic Service Container.

Status of Generic Service Containers

A Generic Service Container is installed on every TrueSight Capacity Optimization Application Server, but it is inactive by default, and all backend services are running in the Data Hub. You can activate a Generic Service Container from the Console, however, it automatically starts when a backend service is relocated to the Generic Service Container. Relocation of an active backend service moves it to another Generic Service Container. 

The product Installer automatically configures all Application Server machines with a Generic Service Container, including the one running the Data Hub. Any machine that you are installing either the Web Server, Data Hub or Primary Scheduler features on, will automatically have the Generic Service Container feature configured on it.

Deciding when to relocate a backend service

Consider the following deployment scenarios for deciding when to move an active backend service from the Data Hub to a Generic Service Container.

  • In a deployment that has a relatively large Remote ETL load: You can relocate the Data API to a Generic Service Container from the Console to optimize isolation and allow the Data API to use more memory. For example, a Data Hub running simultaneous instances of the CAPA service and a Remote ETL could encounter (over)load problems.
  • In a deployment with a relatively large Data Hub load: If you need to isolate CAPA to ensure optimal performance of the service, you can relocate CAPA through the Console from the Data Hub to a Generic Service Container, to optimize isolation and allow CAPA to use more memory. Similarly, you can choose to relocate other services that you do not want to share Data Hub resources with. 

Viewing configured service containers in the Console 

To view a list and the status of all configured Generic Service Containers in the Console, navigate to Administration > COMPONENTS > Service Containers. The Service Containers page is displayed. It contains a Service Containers table that displays the following information.

Even if a configured Service Container is installed on the machine, it need not necessarily be “active”.

Service Containers table: Description of columns

IdInternal ID of the Generic Service Container.

Hyper-linked name of the Generic Service Container. Click this link to view whether this Generic Service Container is Active or Inactive.

Note: A Generic Service Container is automatically activated whenever there is at least one backend service that has been relocated to it. It is deactivated automatically when there is no backend service running on it.

DescriptionA brief description of the Generic Service Container.
TypeThe type of Service Container, whether a Data Hub or a Generic Service Container.
Host nameName of the host the Generic Service Container is configured and resides on.
StatusStatus of the service container
Edit this service containerClick Edit this service container to edit the name and description of this Generic Service Container.

The following image shows an example of the Service Containers page displaying a list of all configured Generic Service Containers. 

Service Containers page

Where to go from here

For information on relocating an active backend service to a Generic Service Container from the Console, see Administering Backend Services.

Was this page helpful? Yes No Submitting... Thank you