Deploying data movement services

Before the State to Runtime and Runtime to Historical data movement service can be deployed, the dynamic database tables should be created. Any error occurs while executing dynamic database tables creation scripts will result in problems during the data movement service deployment.

During schema generation, up to three compressed (ZIP files or JAR files) archives (named DS_State_setup, DS_Runtime_setup and DS_Datamart_setup) containing data movement service setup files will be created. The three archives will always be created the first time schema generation is performed for a business measures model. Subsequent generations, e.g. after a business measures model has been modified, can create zero, one, two or three new archives. An archive will only be created if a change in the existing replication environment is necessary to accommodate business measures model changes. The data movement service deployment archives are located in the directory that was specified in the Schema Generator Admin console configuration under the "general" tab.

Deployment of a data movement service involves creation and configuration of database objects in the source database (from where data is moved) as well as database objects in the target database (to where data is moved).
  • DS_State_setup contains the deployment script for the source database setup of the State to Runtime data movement service.
  • DS_Runtime_setup contains the deployment script for the target database setup of the State to Runtime data movement service and the deployment script for the source database setup of the Runtime to Historical data movement service.
  • DS_Datamart_setup contains the deployment script for the target database setup of the Runtime to Historical data movement service.
  1. Deploy the State to Runtime data movement service:
    1. Determine on which machine you will be deploying the source artifacts for State to Runtime data movement service. In most cases this is the machine hosting the state database.
    2. Create a working directory on that machine and copy (or transfer if the machine is remote) the generated DS_State_setup archive to that directory. You must choose a path with a length of 100 characters or less due to operating system dependent path length restrictions.
    3. Extract the archive (in a .zip file on Windows® and in a .jar file on UNIX®) into the working directory.
    4. During deployment, a variety of DB2® utilities will be used to create and configure database objects. To use those tools, the database environment must be set up. On Microsoft® Windows you can do that by opening a DB2 command window. On UNIX make sure that the appropriate environment variables are set.
    5. Navigate to the directory into which you extracted the DS_State_setup archive.
    6. Execute State_to_Runtime_setup_source.bat (the extension is .sh on UNIX) and follow the prompts. The script will display status messages indicating whether a certain command: succeeded, generated a warning or failed.
    7. Inspect the generated log fileState_to_Runtime_setup_source.logfor any warning or error messages. Do not proceed if any error messages are being displayed.
    8. Backup the work directory. IBM® support may use its content for troubleshooting.
    9. Determine on which machine you will be deploying the target artifacts for State to Runtime data movement service. In most cases this is the machine hosting the Runtime database.
    10. Create a working directory on that machine and copy (or transfer if the machine is remote) the generated DS_Runtime_setup archive to that directory. You must choose a path with a length of 100 characters or less due to operating system dependent path length restrictions.
    11. Extract the archive (in a .zip file on Windows and in a .jar file on UNIX) into the working directory.
    12. During deployment, a variety of DB2 utilities will be used to create and configure database objects. To use those tools, the database environment must be set up. On Microsoft Windows you can do that by opening a DB2 command window. On UNIX make sure that the appropriate environment variables are set.
    13. Navigate to the directory into which you extracted the DS_Runtime_setuparchive.
    14. Execute State_to_Runtime_setup_target.bat (the extension is .sh on UNIX) and follow the prompts. The script will display status messages indicating whether a certain command succeeded, generated a warning or failed.
    15. Inspect the generated log file State_to_Runtime_setup_source.log for any warning or error messages. Do not proceed if any error messages are being displayed.
    16. Backup the work directory. IBM support may use its content for troubleshooting.
    17. If no problems were reported, the State to Runtime data movement service has been set up.
  2. Deploy the Runtime to Historical data movement service:
    1. Determine on which machine you will be deploying the source artifacts for the Runtime to Historical data movement service. In most cases this is the machine hosting the Runtime database. If you've deployed the target artifacts for the State to Runtime data movement service on the same machine, you can proceed with step e below because the necessary deployment files have already been extracted.
    2. If deployment is performed on a machine other than the machine hosting the Runtime database, create a working directory on that machine and copy (or transfer if the machine is remote) the generated DS_Runtime_setup archive to that directory. You must choose a path with a length of 100 characters or less due to operating system dependent path length restrictions.
    3. Extract the archive (in a .zip file on Windows and in a .jar file on UNIX) into the working directory.
    4. During deployment, a variety of DB2 utilities will be used to create and configure database objects. To use those tools, the database environment must be set up. On Microsoft Windows you can do that by opening a DB2 command window. On UNIX make sure that the appropriate environment variables are set.
    5. Navigate to the directory into which you extracted the DS_Runtime_setup archive.
    6. Execute Runtime_to_Historical_setup_source.bat (the extension is .sh on UNIX) and follow the prompts. The script will display status messages indicating whether a certain command succeeded, generated a warning or failed.
    7. Inspect the generated log file Runtime_to_Historical_setup_source.log for any warning or error messages. Do not proceed if any error messages are being displayed.
    8. Backup the work directory. IBM support may use its content for trouble shooting.
    9. Determine on which machine you will be deploying the target artifacts for the Runtime to Historical data movement service. In most cases this is the machine hosting the Historical database.
    10. Create a working directory on that machine and copy (or transfer if the machine is remote) the generated DS_Datamart_setup archive to that directory. You must choose a path with a length of 100 characters or less due to operating system dependent path length restrictions.
    11. Extract the archive (in a .zip file on Windows and in a .jar file on UNIX) into the working directory.
    12. During deployment, a variety of DB2 utilities will be used to create and configure database objects. To use those tools, the database environment must be set up. On Microsoft Windows you can do that by opening a DB2 command window. On UNIX make sure that the appropriate environment variables are set.
    13. Navigate to the directory into which you extracted the DS_Runtime_setup archive.
    14. ExecuteRuntime_to_Historical_setup_target.bat (the extension is .sh on UNIX) and follow the prompts. The script will display status messages indicating whether a certain command succeeded, generated a warning or failed.
    15. Inspect the generated log file State_to_Runtime_setup_source.log for any warning or error messages. Do not proceed if any error messages are being displayed.
    16. Backup the work directory. IBM support may use its content for troubleshooting.
    17. If no problems were reported, the Runtime to Historical data movement service has been set up for this business measures model.

Copyright IBM Corporation 2005, 2006. All Rights Reserved.