Prerequisites to Using the Siebel Segmentation Migration Utility

Before configuring the Siebel Segmentation Migration Utility, ensure that you've done the prerequisites:

• Import Certificates into a Truststore
• Prepare the OAS Repository Metadata File
• Enable Dynamic IO for Siebel REST Access
• Prepare the Repository File and Convert It to XML

Import Certificates into a Truststore

Import both Siebel and OAS certificate chains into one shared truststore, for example migration-truststore.jks, and point TRUSTSTORE_PATH to that file.

Windows example:

keytool -importcert -alias siebel -file C:\path\to\siebel.cer
                -keystore C:\path\to\migration-truststore.jks -storepass <pwd> -noprompt
              keytool -importcert -alias oas    -file C:\path\to\oas.cer    -keystore
              C:\path\to\migration-truststore.jks -storepass <pwd> -noprompt
        

Linux example:

keytool -importcert -alias siebel -file /path/to/siebel.cer
                -keystore /path/to/migration-truststore.jks -storepass '<pwd>' -noprompt keytool -importcert
                -alias oas    -file /path/to/oas.cer    -keystore /path/to/migration-truststore.jks
                -storepass '<pwd>' -noprompt 

Also see: The keytool Command

Prepare the OAS Repository Metadata File

Before configuring the segmentation migration utility, prepare the OAS repository metadata file. The segmentation migration utility uses this file to identify target levels and qualifying-key columns, such as ROW_ID.

See Managing Metadata Repositories for Oracle Analytics Server for more information.

Enable Dynamic IO for Siebel REST Access

Enable Dynamic IO for Siebel REST access and grant REST access to these business objects:

• Marketing Segment
• Mktg List Format

See Supporting RESTful Access to Siebel Business Objects Dynamically for more details.

Prepare the Repository File and Convert It to XML

If the Oracle BI Repository File (RPD) file isn't already available, download the active OAS repository file using Oracle's downloadrpd command.

The command is run through datamodel.sh on Linux or datamodel.cmd on Windows.

Use the target OAS or OBIEE RPD that contains the Siebel Marketing segmentation metadata. Siebel's segmentation migration utility doesn't migrate or remodel the RPD. It reads and filters the metadata required to generate the migrated Analysis and Analysis Collection artifacts, including target levels and qualifying-key columns such as ROW_ID.

If the target OAS or OBIEE repository already contains customer-configured Marketing metadata, prepare the XML from that active repository so that the segmentation migration utility can use the deployed metadata during migration.

After the RPD file is available, convert it to XML with Oracle's biserverxmlgen utility:

biserverxmlgen -M -R <rpd_path> -O <output_xml_path>

Important: Oracle recommends prompting for repository and user passwords instead of placing passwords directly in scripts or command-line history.

The parent directory for the generated XML file must be writable. During preprocessing, the segmentation migration utility generates a sibling YAML file beside the XML file and uses that generated file during migration.

References

Topic	Oracle Reference
Download deployed RPD	Download Repository Command
Generate XML from RPD	About the Oracle BI Server XML API