Stopping the State to Runtime data movement service

The process of stopping the Runtime to Historical Data Movement Service is very similar to the process of starting it. The deployment archives DS_State_setup and DS_Runtime_setup contain executable scripts that can be used to stop the Capture and Apply component instances for the Runtime to Historical Data Movement Service.

If the archive was created as a result of a change to the business measures model, only stop scripts for new Capture and Apply component instances have been packaged.
Note: It is recommended to consolidate the scripts prior to stopping the data movement service. For more information about replication scripts consolidation, refer to Consolidating start and stop scripts.
However, the instructions below can be used even if no consolidation has been performed.
To stop the State to Runtime Data Movement Service for a given business measures model:
  1. Identify all Capture component instances that have been assigned to the business measures model in the State database. If you have already consolidated all Capture component instance stop scripts, nothing needs to be done. Proceed with the next step. If you have not consolidated the scripts yet (and do not wish to consolidate them) you need to identify all capture component instances that have ever been created for this business measures model. The Capture component instance stop scripts are automatically generated the first time schema generation is performed for a business measures model. Subsequent schema generations (e.g. after you have updated the business measures model) only generate stop scripts for new Capture component instances. To identify all relevant stop scripts you will have to repeat the following steps for each deployment that you have performed for this business measures model.
    1. Navigate to the directory where you performed a deployment for this model
    2. Navigate to the State_to_Runtime\source subdirectory and locate all StopCapture_<number> scripts.
    3. Repeat above steps for each deployment of this business measures model.
  2. Stop Capture component instances. The identified Capture component instances must be stopped on the machine hosting the State database. If the stop scripts have been consolidated, launch the consolidated stop script. If no consolidation has been performed, you need to execute each one of the stop scripts that you identified in the previous step. The order in which the stop scripts are being launched does not matter.
    Note: The stop scripts work asynchronously and occasionally, there may be a delay between when a stop command is issued and when the capture component stops. This is due to the fact that the Capture component instance is finishing up a transaction prior to stopping.
  3. Identify all Apply component instances that have been assigned to the business measures model in the Runtime database. If you have already consolidated all Apply component instance stop scripts, nothing needs to be done. Proceed with the next step. If you have not consolidated the scripts yet (and do not wish to consolidate them) you need to identify all Apply component instances that have ever been created for this business measures model. The Apply component instance stop scripts are automatically generated the first time schema generation is performed for a business measures model. Subsequent schema generations (e.g. after you have updated the business measures model) only generate stop scripts for new Apply component instances. To identify all relevant stop scripts you will have to repeat the following steps for each deployment that you have performed for this business measures model:
    1. Navigate to the directory where you performed a deployment for this model.
    2. navigate to the State_to_Runtime\target subdirectory and locate all StopApply_<number> scripts.
    3. Repeat above steps for each deployment of this business measures model.
  4. Stop Apply component instances.
    The identified Apply component instances should be stopped on the machine hosting the Runtime database. If the stop scripts have been consolidated, launch the consolidated stop script. If no consolidation has been performed, you need to execute each one of the stop scripts that you identified in the previous step. The stop scripts can be launched in any order.
    Note: The stop scripts work asynchronously and occasionally, there may be a delay between when a stop command is issued and when the apply component stops. This is due to the fact that the Capture component instance is finishing up one or more transactions prior to stopping.
Related concepts
Data movement services
Related tasks
Starting the State to Runtime data movement service

Copyright IBM Corporation 2005. All Rights Reserved.