Deploying a Replication Model

To deploy a replication model, provide property values for each replication component. RMA verifies the database configuration and provides the ability to generate scripts to correct the database configuration, if necessary.

  1. In the SAP Replication Management Agent Designer window, right-click the highlighted AgentContainer and select Deploy a Model.
    The Replication Model Deployment wizard appears in a separate window.
  2. (Optional) If you have a previously saved replication model properties file, click Load, browse through your local directory, select the file, and click Open.
  3. Select a primary database to use for replication from the list, and specify its required configuration information.
    (Oracle only) In the data change interface combo box, select either the XStream or LogMiner. If you select LogMiner, you have the option to provide the archive directory. Otherwise, this field is disabled as it is not applicable to replication using XStream.
    (Optional) Click Save to store the information for later use.
    Note: When you make changes to the loaded properties file, clicking Save also store those changes.
  4. Click Next.
    RMA verifies the source database configuration. If you select Oracle, RMA detects if Data Vault is in use with the database and verifies Data Vault privileges.
  5. If the verification fails, select either:
    Option Description
    Automatically create users and configure the database
    1. (Oracle only) In the pop-up dialog, enter the Data Vault admin credentials.
      Note: This credentials are only used during configuration correction, and are not retained when the correction is complete.
    2. Enter the DBA user and password.
    3. (Optional. Oracle only) Select As SYSDBA check box to execute the autoconfiguration or verification as SYSDBA.
    4. Click Configure.
    5. (Optional) Click Reverify with DBA.
    Note: Some configuration tasks can only be performed manually. The tasks vary depending on the database type.
    Manually create users and configure the database
    1. Click View Scripts.

      The Database Configuration Scripts window appears.

    2. Use the scripts provided in each tab as your guide to configure the database and/or create the required user.
    3. (Optional) Click either:
      • Save Script – to save script to a file for later use. Or,
      • Copy Script – to copy script to the clipboard.
    4. Edit the scripts based on the required configuration, and run them using the command line.
    5. When the configuration is done, close the Database Configuration Scripts window, and click Reverify in the deployment wizard.
      Note: The Next button is disabled until verification passes.
  6. Click Next.
  7. Specify all the required configuration information for the replicate database.
    (Optional) Click Save to store the information for later use.
  8. Click Next.
    RMA verifies the replicate database configuration. If it does not pass the verification, you are provided with options similiar to step 5 to correct the database configuration.
  9. Specify all the required configuration information for the Replication Agent.
    (Optional) Click Save to store the information for later use.
  10. Click Next.
  11. Specify all the required configuration information for the SAP Replication Server.
    (Optional) Click Save to store the information for later use.
  12. Click Next.
  13. Review the Replication Model Summary.
    (Optional) Click Save to store the summary of replication model.
  14. Click Deploy.
After a successful deployment, the replication model is visible in the Agent Servers pane. To see it, expand the AgentContainer.

If the deployment does not complete successfully, you see an error message in the deployment progress window. The information in this window may help you fix the problem. The Agent Container log also has useful information regarding the errors.

Additionally, if deployment fails, a suspect model may remain deployed to the AgentContainer. This allows you to diagnose the failure. When the cause of the error is determined, undeploy the suspect model. A suspect model entities are displayed in the Server tree with red X icons.