1. Marketing Installation and Administration Guide
  2. Prepare to Run the Siebel Segmentation Migration Utility

Prepare to Run the Siebel Segmentation Migration Utility

Before running the Siebel Segmentation Migration Utility, you need to do some work to prepare for it:

Here are the preparation steps:

Locate the .zip File

Locate the delivered mktg-seg-migration.zip package in the Siebel Server bin directory. For example, <Siebel_Server_Root>/siebsrvr/bin.

Extract the .zip Package

Extract the migration utility .zip file:

  1. Extract the mktg-seg-migration.zip file into the working location for the migration run.

    • Linux/macOS:

      unzip <migration_application_zip> -d <target_directory>

    • Windows PowerShell:

      Expand-Archive -Path <migration_application_zip> -DestinationPath <target_directory>

  2. Confirm that the package folder has been created successfully. The extracted folder is used in the subsequent configuration and execution steps.

Review the Package Contents

Review the package contents to ensure the correct files are present:

  1. Open the extracted migration utility folder and verify that the expected runtime files are present.

  2. Use these details:

    File Description
    run-mktg-seg-migration.sh Linux, Unix, or macOS wrapper script
    run-mktg-seg-migration.bat Windows wrapper script
    lib/mktg-seg-migration.jar Migration utility executable
    config/application.properties Main configuration file
    config/logback.xml Logging configuration
    README.md Package usage guide

  3. Verify that the wrapper script, configuration file, executable JAR, and logging configuration are present before running the migration utility.

    Important: The wrapper script, configuration file, executable JAR, and logging configuration are required before running the migration utility.

Configure the Wrapper Script

Configure the wrapper script by updating the environment-specific parameters in the wrapper script:

  1. Open the wrapper script for the operating system where the migration utility will run.
    • Linux, Unix, or macOS:

      run-mktg-seg-migration.sh

    • Windows:

      run-mktg-seg-migration.bat

  2. Use these settings:

    Setting Description
    JAVA_HOME_PATH Java 21 JRE or JDK home directory
    TRUSTSTORE_PATH Path to the truststore prepared in the Certificate Truststore section
    TRUSTSTORE_PASSWORD Truststore password
    TRUSTSTORE_TYPE Truststore type, such as JKS
    LOG_DIR Directory where application and audit logs are written
    APP_LOG_LEVEL migration utility log verbosity
    ROOT_LOG_LEVEL Fallback log level for dependency and framework logging
    MAX_FILE_SIZE Log rollover threshold
    EXTRA_JAVA_OPTS Optional JVM options, such as heap settings
Note: Don't add Siebel or OAS passwords to the wrapper script. The migration utility prompts for those passwords at runtime.

Configure the Properties File

Configure config/application.properties before running the migration utility:

Open config/application.properties and enter the required Siebel, OAS, and RPD XML values.

Here are the properties:

Property Required Description
siebel.api.url Yes Siebel API endpoint
siebel.api.username Yes Siebel user
oas.api.url Yes OAS endpoint
oas.api.username Yes OAS user
rpd.xml.path Yes Path to the RPD XML prepared in the Prerequisites section
oas.session.timeout No OAS session timeout in seconds
migration.threads.count No Worker thread count
siebel.campaign.searchspec No Optional Siebel campaign filter
Note: Don't store Siebel or OAS passwords in this file. The migration utility prompts for both passwords at runtime.

Review the Campaign State Before Migration

Before running the migration utility, open the campaign in Siebel Marketing and confirm the source segmentation artifact is still associated with the campaign.

  • In the Segments/Lists view, the campaign should show the existing Segment or List artifact that will be migrated.

  • In the Allocation view, confirm that the campaign allocation is still associated with the Segment or List artifact.

  • The Analyses/Lists view in the L4 menu should not contain any records before migration.

Next step: Run the Segmentation Migration Utility and Review the Results