Relocating a backend service

Based on the expected workload for particular services, you can relocate active backend services from the Data hub or a Generic Service Container to another Generic Service Container.

Deciding when to relocate a backend service

Consider the following deployment scenarios for deciding when to move an active backened 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 to optimize isolation and allow the Data API to use more memory. For example, a Data Hub running simultaneous instances of the Auto Forecasting 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 Auto Forecasting Service to ensure optimal performance of the service, you can relocate Auto Forecasting Service from the Data Hub to a  Service Container, to optimize isolation and to allow Auto Forecasting Service to use more memory. Similarly, you can choose to relocate other services that you do not want to share Data Hub resources with.

Relocating a backend service

  1. Navigate to Administration > SYSTEM > Status. The page contains hosts and their components.

  2. Depending on the component from where you want to relocate a backend service, click the Data hub or the Service Container component.
  3. Click the backend service to be relocated. The service details page is displayed.
  4. In the Relocate Service window, select the destination Service Container where you want to relocate the service and click Move
    The selected backend service is moved to the destination Service Container.


    After you click Move, the source and destination Service Containers are shut down and restarted, and their services are unavailable for some time. Services resume after the relocation is complete.

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 Service Container and Remote ETL services:

ServiceClient reconfiguration steps
Service ContainerRegister the BCM Provider with the new URL, and set the port to number 8380.
Remote ETLs

There are two scenarios:

  • Relocating the Data API to a Generic Service Container on the same computer: Port change is transparent for the remote ETL.
  • Relocating Data API to a Generic Service Container on another computer: Perform the following steps:
    • If there is a firewall/NAT between the Remote ETL and TrueSight Capacity Optimization Application Server: Reconfigure the NAT to point to the new machine.
    • Edit the Data API External Backend Service URL property from the Data Hub tab under Administration > System > Global configuration and Save your settings. All components including the Remote ETLs are notified of the change.

Note: BMC recommends you not to relocate the Data API service while ETL processes are running, this might result in loss of data.

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


  1. Tushar Vedak

    CLM (Cloud Life-Cycle Management) is deprecated and dropped from TSCO 11.3 so kindly use different active backened service name for an "example", instead of CAPA as this is not in used now.

    Sep 07, 2020 09:24
    1. Bharati Poddar

      Thanks for bringing this to our notice, Tushar. 

      The topic is updated to remove references of CAPA.

      Oct 05, 2020 05:55