1. Database Upgrade Guide for DB2 for z/OS
  2. Incremental Migration from Development to Production Environment Without Using Siebel Migration

Incremental Migration from Development to Production Environment Without Using Siebel Migration

Typically if either source (development) or target (production) environment is not in a Repository Upgraded state, then migration execution is performed in synchronous mode. You can migrate asynchronously only if both environments are in a Repository Upgraded state. However, if you want to avoid synchronous migration altogether, you can manually apply any repository and schema changes to target environments that are not in a Repository Upgraded state by completing the steps in this procedure.

Note: A Repository Upgraded state means that the environment (repository and schema) has been upgraded to Siebel 18.8 Update or later release of Siebel CRM.
Caution: It is recommended that you back up your target database before starting to migrate repository or data using Siebel Migration.

To migrate incrementally from a development (source) to a production (target) environment without using the Siebel Migration Application

Note: If your Runtime Repository Data Service or Incremental Runtime Repository Data Service migration plan does not include the non-mandatory Schema Service, then you must migrate any schema changes before executing the plan. If you want to move the schema changes separately, then ignore Step 2 and Step 5 in this procedure.

  1. Generate a watermark for the target environment:

    1. Start the target application. For example, Siebel Call Center or any other employee facing application.

    2. Navigate to the Administration - Business Service screen, then the Simulator view.

    3. Click New (the plus (+) icon) to create a new Business Service record with the following values:

      Service Name Method Name

      Migration Incremental Runtime Repository Data Service

      GetWatermark

    4. Click Run.

    5. In the Output Arguments applet, copy the value in the Property Value field for the watermark Property Name.

      Save the value in a text file because you will need it in Step 3.

  2. Export the schema from the source environment:

    1. Start the source application. For example, Siebel Call Center or any other employee facing application.

    2. Navigate to the Administration - Business Service screen, then the Simulator view.

    3. Click New (the plus (+) icon) to create a new Business Service record with the following values:

      Service Name Method Name

      Migration Schema Service

      Export

    4. Create a new record in the Inputs Arguments list applet:

      • Click the multiple select button in the Property Name field, and then click the plus (+) icon on the Property Set Properties applet that appears.

      • Enter the following values in the Property Name and Value fields, and then click Save.

        Property Name Value

        migrationid

        schema_export

      • Click OK to close the Property Set Properties applet.

    5. Click Run.

    6. In the Output Arguments applet, copy the value in the Property Value field for the trackingid Property Name.

      Save the value in a text file because you will need it in Step 5.

    7. Make sure that the ddldict process is running.

      To do this, use Task Manager on Windows or the ps command on UNIX.

  3. Export the Incremental Runtime Repository from the source environment:

    1. Start the source application.

    2. Navigate to the Administration - Business Service screen, then the Simulator view.

    3. Click New (the plus (+) icon) to create a new Business Service record with the following values:

      Service Name Method Name

      Migration Incremental Runtime Repository Data Service

      Export

    4. Create a new record in the Inputs Arguments list applet:

      • Click the multiple select button in the Property Name field, and then click the plus (+) icon on the Property Set Properties applet that appears.

      • Enter the following values in the Property Name and Value fields, and then click Save:

        Property Name Value

        migrationid

        repo_export

      • Click the plus (+) icon in Property Set Properties applet again, enter the following values in the Property Name and Value fields, and then click Save.

        Property Name Value

        watermark

        Paste the value that you saved from the Property Value field in the Output Arguments applet in Step 1 into this field.

      • Click OK to close the Property Set Properties applet.

    5. Click Run.

    6. In the Output Arguments applet, copy the value in the Property Value field for the trackingid Property Name.

      Save the value in a text file because you will need it in Step 6.

    7. Make sure that the repimexp process is running.

      To do this, use Task Manager on Windows or the ps command on UNIX.

  4. Ensure that the Schema Export and Incremental Runtime Repository Export from the source environment is complete:

    • At regular intervals, check that the ddldict and repimexp processes are running, until they complete.

    • Verify the logs for ddldict and repimexp. The logs for these utilities are stored in the following locations:

      <FS_PATH>\migration\schema_export\log for Schema Export

      <FS_PATH>\migration\repo_export\log for Incremental RR

    • You must wait until these two processes (ddldict and repimexp) are complete.

  5. Import the (source) Schema to the target environment:

    1. Copy the schema_export folder from <FS_PATH>\migration\ on the source machine.

    2. Paste the schema_export folder into the <FS_PATH>\migration path on the target machine.

    3. Start the target application. For example: Siebel Call Center or any other employee facing application.

    4. Navigate to the Administration - Business Service screen, then the Simulator view.

    5. Click New (the plus (+) icon) to create a new Business Service record with the following values:

      Service Name Method Name

      Migration Schema Service

      Import

    6. Create a new record in the Inputs Arguments list applet:

      • Click the multiple select button in the Property Name field, and then click the plus (+) icon on the Property Set Properties applet that appears.

      • Enter the following values in the Property Name and Value fields, and then click Save:

        Property Name Value

        migrationid

        schema_export

      • Click the plus (+) icon in Property Set Properties applet again, enter the following values in the Property Name and Value fields, and then click Save.

        Property Name Value

        filename

        Paste the value that you saved from the Property Value field in the Output Arguments applet in Step 2 into this field.

      • Click the plus (+) icon in Property Set Properties applet again, enter the following values in the Property Name and Value fields, and then click Save.

        Property Name Value

        username

        <Target Database Schema User Name>

        Note: The database schema user name is in plain text format. Contact your Siebel administrator if you do not know what the database schema user name is for the target environment.

      • Click the plus (+) icon in Property Set Properties applet again, enter the following values in the Property Name and Value fields, and then click Save.

        Property Name Value

        password

        <Target Database Schema Password>

        Note: The database schema password must be in Base 64 encoded format. Contact your Siebel administrator if you do not know what the database schema password is for the target environment.

      • Click OK to close the Property Set Properties applet.

    7. Click Run.

    8. Make sure that the ddlimp process is running in the target environment.

      To do this, use Task Manager on Windows or the ps command on UNIX.

    9. Wait until the ddlimp process completes successfully.

      Verify the log located in the <FS_PATH>\migration\schema_export\log folder on the Target machine.

  6. Import the (source) Incremental Runtime Repository to the target environment:

    Note: Perform this task only if the previous step completes successfully.

    1. Copy the repo_export folder from <FS_PATH>\migration\ on the source machine.

    2. Paste the repo_export folder into the <FS_PATH>\migration path on the target machine.

    3. Start the target application.

    4. Navigate to the Administration - Business Service screen, then the Simulator view.

    5. Click New (the plus (+) icon) to create a new Business Service record with the following values:

      Service Name Method Name

      Migration Incremental Runtime Repository Data Service

      Import

    6. Create a new record in the Inputs Arguments list applet:

      • Click the multiple select button in the Property Name field, and then click the plus (+) icon on the Property Set Properties applet that appears.

      • Enter the following values in the Property Name and Value fields, and then click Save:

        Property Name Value

        migrationid

        repo_export

      • Click the plus (+) icon in Property Set Properties applet again, enter the following values in the Property Name and Value fields, and then click Save.

        Property Name Value

        filename

        Paste the value that you saved from the Property Value field in Output Arguments applet in Step 3 into this field.

      • Click OK to close the Property Set Properties applet.

    7. Click Run.

    8. Make sure that the process repimexp is running in the target environment.

      To do this, use Task Manager on Windows or the ps command on UNIX.

    9. Wait until the repimexp process completes successfully.

      Verify the log located in the <FS_PATH>\migration\repo_export\log folder on the Target machine.

After you complete the steps in this procedure, the environment is ready for asynchronous migration.