Administering Backend Services
This topic explains how to view a list of all configured Generic Service Containers along with their with status, and relocate active backend services to Generic Service Containers in TrueSight Capacity Optimization. For information about the various backend services available, see Viewing backend services.
Information
To have a successful integration between TrueSight Operations Management and TrueSight Capacity Optimization, the following backend services of the Application Server must run on the same generic service container or Data Hub:
- API Providers - Agent Data service
API Providers - Data Provider service
API Providers - Search service
If you decide to relocate a backend service, you must relocate all three of them to the new container, re-register the TrueSight Capacity Optimizationcomponent, and enter the port value according to the current container (Data Hub - 8280, Service Container - 8380). For more information about service containers, see Managing Service Containers.
For more information, refer to the following sections:
Relocating a backend service
To learn how to relocate a backend service from one Generic Service Container to another, perform the following task:
Navigate to Administration > COMPONENTS > Backend Services. The page contains an Active Services table that displays the following information:
Column Description Icon Hyper-linked icon depicting the type of service. Name Hyper-linked name of the active backend service. Service Container The type of Service Container – Data Hub or Generic Service Container – that the active backend service in the corresponding row is configured on. Status Displays whether the status of the service is OK or NOT OK. Message Displays whether the service is OK (running) or SLEEPING. Last update Time stamp of when the service was last updated on. Show log Click Show Log 
to view a log for the corresponding backend service. The Log table contains the following information:- Timestamp: Time stamp of when the service was last updated on.
- Type: Type of logged information.
- Message: The actual message that was logged in the service log.
You can also click the following buttons in the Log table of the service to:
- Refresh: Click to refresh the Log table with current data for the service.
- Download log: Click to download the log file to your machine as a .log text file.
- Click the hyper-linked icon or name of the active backened service that you want to relocate.
Under the active backend service details page, click Relocate to display the Relocate Service dialog box. The following figure shows an example of the Relocate Service dialog box.
The Relocate button is displayed only for backend services that can be relocated to another Generic Service Container.
From the dialog box, select a Destination Service Container from the list, to relocate the selected service.
Important
After you click Move in the next step, both Service Containers involved – the one that was containing the service before the move (source), and the destination service container – are shut down and restarted, and their services are unavailable for some time. After the relocation is complete, Services will be available again.
- Click Move to relocate the selected service.
The following figure shows an example of the Backend Services page displaying the Active services table.
Backend Services page
Adding a Generic Service Container
A Generic Service Container is automatically installed (added) to BMC TrueSight Capacity Optimization when you choose to install either the Web, Data Hub or Primary Scheduler Application Server features.
The product Installer automatically configures all Application Server machines with a Generic Service Container, including those running the Data Hub. Any machine that you are installing either the Web, Data Hub or Primary Scheduler features on, will automatically have the Generic Service Container feature configured on it.
After relocating a backend service
After you relocate an active backend service from one Generic Service Container to another, the concerned clients should be reconfigured to use the right port. The following table elicits basic guidelines for CAPA and Remote ETL services:
| Service | Client reconfiguration steps |
|---|---|
| CAPA | Register the BCM Provider with the new URL, and set the port to number 8380. |
| Remote ETLs | There are two scenarios:
Note: BMC recommends you not to relocate the Data API service while ETL processes are running, this might result in loss of data. |
Administration tasks for Generic Service Containers
The following table lists important information about Service Containers.
| Generic Service Container property | Value/Command/Description |
|---|---|
Installation folder | <CPIT_Base>/servicecontainer |
Log files | Reside in the /log subfolder. |
| To manually start/stop | Use the following commands:
The start command will start the Service Container only if it has a service assigned to it. If there is no service to run, the Service Container will remain tuned off and a 'No active services to run' message will be returned. This also ensures that the Service Container is started only if needed. |
| Type of process | A Generic Service Container is a Java/Tomcat process. |
| To detect the process from the shell prompt | Type the
|
| To force a restart | You can use the |
Comments