8.2 Managing Scenario Migration Utility

Use the Scenario Migration Utility to migrate scenarios, datasets, networks, and associated metadata from the development environment to the production environment.

To provide a list of scenarios, datasets, or networks, you edit the scnros.cfg, dataset.cfg, or the network.cfg files prior to scenario extraction or loading.

The Scenario Migration Utility creates and migrates the following metadata files:

• Scenarios: The <scenario catalog identifier>.<scenario id>.xml file contains scenario metadata for core Behavior Detection tables. It also may contain scenario metadata for optional tables.
• Datasets: The <dataset idDS>.xml file contains dataset metadata for core Behavior Detection tables.
• Networks: The <network>NW.xml file contains network metadata for core Behavior Detection tables.

  Note:

  When the Scenario Migration Utility extracts these files, you can version-control them or store them in the Oracle client’s archival system.

To help avoid accidental loading of a scenario into the incorrect environment, the Scenario Migration utility enables you to name your source and target environments. On extract, you can specify the environment name to which you plan to load the scenario. If you attempt to load it to a different environment, the system displays a warning prompt.

This section covers the following topics:

• Logs
• Using the Scenario Migration Utility
• Scenario Migration Best Practices

Logs

The Scenario Migration Utility produces two log files (See Sample install.cfg File): load.log and extract.log. These files reside in the following location: <OFSAAI Installed Directory>/database/db_tools/logs