Securing the data movement service database schema

By default, the enable data movement service schema (DMS) script contains the required grant statements to secure the data movement service, but the grant statements are commented out. Uncomment the grant statements and run the enable data movement service script to implement the grant statements for a higher level of security.

Before you begin

Stop the monitor model.

Procedure

  1. Export the enable DMS script using the following steps.
  2. In the WebSphere® Application Server administrative console, click Applications > Monitor Models.
  3. Click the version of the model for which you want to enable data movement service.
  4. Click Enable Data Movement Service.
  5. Click Export Enable DMS Script.
  6. Save the file. This procedure produces a script that you can run manually using a command prompt. You can run this script later or from a remote location.

    After data movement service has been enabled it will be in a suspended state for the model version. Data is not copied to the reporting tables or pruned from the operational tables until the data movement service is activated for the model version. Activate the data movement service by using the Resume Data movement service option.

  7. Navigate to the directory that contains the exported script, which is a DDL file.
  8. Edit the EnableDMS_ModelName.ddl file, removing the comment indicators for each GRANT statement and allowing the statements to be implemented in the next step by replacing the string "--GRANT STMT--" with "". Grant statements required for IBM® Business Monitor are commented out.
  9. Run the create script using the EnableDMS_ModelName.ddl file.
    On DB2®, in the DB2 command window, enter the following command:
    db2 -td@ -vf EnableDMS_ModelName.ddl
    On Oracle, enter the following command:
    sqlplus dbadmin/dbpassword@orcl @EnableDMS_ModelName.ddl
    On Microsoft SQL Server, enter the following command:
    sqlcmd -U <userid> -P <password> -e -i EnableDMS_ModelName.ddl

    where

    ModelName is the name of the model.

  10. Stop and start the monitor model so that the monitor model application picks up the new database tables.