Database replication scripts

The Schema Generator generates replication scripts that are used to handle the replication from the State to the Runtime database and from the Runtime to the Historical database.

The purpose of the replication services is to provide an infrastructure that copies business measures model events data stored in the State database to the Runtime database and from the Runtime database to the Historical database. This infrastructure is dynamically built during the deployment phase of the business measures model. The Schema Generator creates the replication scripts. These scripts, once deployed on the systems hosting the State, Runtime, and Historical Databases, provide the services necessary to move the data from one database to another. The general activity flow can be described as follows:

To enable the Schema Generator to create the required replication scripts, the DBA must configure the replication operation through the State to Runtime and Runtime to Historical pages in the Schema Generation Configuration panel before generating the scripts. The defined configuration parameters can be changed later. For more information about changing data movement service configuration parameters, refer to Configuring the Schema Generator.The most important parameter is the replication population interval, which determine the time period in minutes between two replication cycles. This interval is determined according to the required frequency of updating the information in runtime. This time period must be defined for the replication between State to Runtime databases and between Runtime to Historical databases. The default replication interval for the State to Runtime database replication is 10 minutes, while the default replication interval for the Runtime to Historical database replication is 24 hours.

Subsequent changes to the business measures model have an impact on the generated replication scripts and can lead to a re-creation and redeployment of previously generated scripts. The Schema Generator maintains the mapping among State, Runtime, and Historical database tables; it generates the required replication scripts. A new mapping is created, reflecting the latest state of the databases. A user will have to go through a series of activities before starting replication services. The basic activity flow is:
  1. Configure replication parameters through WebSphere® Business Monitor administrative console
  2. Generate replication scripts using information derived from the Schema Generator and other sources
  3. Optional. Customize generated replication scripts
  4. Deploy replication scripts.
  5. Start replication services
Related concepts
Database replication
Related tasks
State to Runtime databases replication
Runtime to Historical databases replication

Copyright IBM Corporation 2005, 2006. All Rights Reserved.