Starting the Runtime to Historical data movement service

The deployment archives DS_Runtime_setup and DS_Datamart_setup contains executable scripts that can be used to start 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 start scripts for new Capture and Apply component instances have been packaged.

Note: You can consolidate the scripts to starting the data movement service. For more information about consolidating scripts refer to Consolidating start and stop scripts.
However, the instructions below can be used even if no consolidation has been performed. To start the Runtime to Historical 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 Runtime database.
    If you have already consolidated all Capture component instance start 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 start 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 start scripts for new Capture component instances. To identify all relevant start 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 Runtime_to_Historical\source subdirectory and locate all StartCapture_<number>scripts.
    3. Repeat above steps for each deployment of this business measures model.
  2. Start Capture component instances.
    The identified Capture component instances must be started on the machine hosting the Runtime database. If the start scripts have been consolidated, launch the consolidated start script. If no consolidation has been performed, you need to execute each one of the start scripts that you identified in the previous step. The scripts should not be launched simultaneously, because the Capture utility initialization could otherwise fail. However, it does not matter in which order the start scripts are being launched. Authorization requirements, the user id that starts the Capture component instances should hold:
    • Database Administration Authority (DBADM) authority on the Runtime database.
    • Write access to the directory referenced by the CAPTURE_PATH parameter in the start scripts.
    • Read access to the file referenced by the optional parameter PWDFILE in the start scripts
  3. Identify all Apply component instances that have been assigned to the business measures model in the Historical database.
    If you have already consolidated all Apply component instance start 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. Apply component instance start 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 start scripts for new Apply component instances. To identify all relevant start 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 Runtime_to_Historical\targetsubdirectory and locate all StartApply_<number> scripts.
    3. Repeat above steps for each deployment of this business measures model.
  4. Start Apply instances.
    The identified Apply component instances should be started on the machine hosting the Historical database. If the start scripts have been consolidated, launch the consolidated start script. If no consolidation has been performed, you need to execute each one of the start scripts that you identified in the previous step. The scripts should not be launched simultaneously, because the Apply utility initialization could otherwise fail. However, it does not matter in which order the start scripts are being launched. Authorization requirements, the user id that starts the Apply component instances must have:
    • SELECT/INSERT/UPDATE/DELETE privileges for the associated Capture component instance control tables in the Runtime database
    • SELECT privileges for the associated Capture component instance work tables in the Runtime database.
    • SELECT/INSERT/UPDATE/DELETE privileges for the associated replication staging tables in the Historical database.
    • SELECT/INSERT/UPDATE/DELETE privileges for the Apply component instance control tables in the Historical database.
    • Write access to the directory referenced by the APPLY_PATHparameter in the start scripts.
    • Read access to the file referenced by the optional parameter PWDFILE in the start scripts
  5. Verify that each one of the Capture and Apply component instances started successfully.

Copyright IBM Corporation 2005, 2006. All Rights Reserved.