To simplify the process of starting and stopping a data movement
service, you can consolidate the generated start and stop scripts and invoke
them through master scripts.
Because the Capture and Apply components have to be run on the system
where the databases are located, consolidation options vary depending on the
topology used. Regardless of how the scripts are consolidated, to prevent
initialization errors, you need to ensure that no two component instances
are launched simultaneously.
Although you can start or stop each Capture or Apply Component instance
separately, it is convenient to consolidate the content of all component instance
start and stop scripts so that only one script is needed to start or stop
the data movement service for a single business measures model.
You can consolidate scripts by:
- Identifying the Capture component instances start
and stop scripts for the source database.
- Creating Capture master start and stop scripts that invoke the
Capture component instances start and stop scripts for the source database.
- Identifying the Apply component instances start and stop scripts
for the target database.
- Creating Capture master start and stop scripts that invoke the
Capture component instances start and stop scripts for the target database.
As a result of this consolidation, only four start (or stop) scripts
need to be executed to start or stop the data movement services for a business measures model.
You can consolidate
further if there is no need to start or stop the two data movement services
separately. In this case, only three start and stop scripts are necessary:
- A script starts (stops) all Capture Component instances in the State database.
- A script starts (stops) all Capture Component instances and Apply Components
in the Runtime database.
- A script starts (stops) all Apply Components in the Historical database.
If all three databases reside on one system, these three consolidated
scripts can be further consolidated to just a single script that starts or
stops all Capture and Apply Component instances.
There is a case where consolidation is required of the start and
stop scripts for a data movement service that has been created by different
deployments. During the initial deployment of a data movement service, start
and stop scripts for all business measures groups are created. Subsequent
deployments that are a result of changes to the business measures model do
not contain start and stop scripts for existing business measures groups.
Instead only start and stop scripts for new business measures groups will
be made available. You need to manually update previously created consolidated
start and stop scripts.
The following example illustrates this case:
An initial data-movement-service deployment for a business measures model FinanceModel contains
three business measures groups. Three Capture start and stop scripts have
been created for the State database. Subsequently, the model is updated and
a new business measure added. Only one Capture start and stop script for the
new business measures group will be created during deployment. Four Capture
start and stop scripts need to be run to enable the data movement service.