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
- Navigate to Administration > SYSTEM > Status. The page contains hosts and their components.
- Depending on the component from where you want to relocate a backend service, click the Data hub or the Service Container component.
- Click the backend service to be relocated. The service details page is displayed.
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 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: