8.4.1.3 Configuring Scenario Load

This topic describes scenario load parameters.

Table 8-10 Scenario Load Parameters

Parameter Description
load.conn.driver Database connection driver that the utility is to use (oracle.jdbc.driver.OracleDriver).
load.conn.url Database connection string that the Scenario Migration Utility is to use.
load.ignore.custom.patterns=N When set to N, custom patterns will not be ignored. This mode should be used when migrating scenarios between environments within the client's environment. If a custom pattern is not in the loaded XML file, then it will be deactivated.

When set to Y, any custom patterns will be ignored by the load process, and should continue to operate.

load.schema.mantas ATOMIC schema owner in the database in which loading of the scenario occurs (ATOMIC).
load.schema.business ATOMIC schema owner in the database in which loading of the scenario occurs (ATOMIC).
load.schema.market ATOMIC schema owner in the database in which loading of the scenario occurs (ATOMIC).
load.user.miner ATOMIC schema owner in the database in which loading of the scenario occurs (ATOMIC).
load.miner.password Password for the above user.
load.threshold.update Threshold values from the incoming scenario.
  • Selecting N retains the threshold values from the target environment.
  • Selecting Y updates thresholds in the target environment to values from the incoming file.
load.system.id Name that is assigned to the system into which this instance of Scenario Migration loads metadata. The system compares the value for this setting to the target system in the metadata file.
load.dirname Directory from which the system loads scenario, network, and dataset XML files.
verify.target.system Check target name upon loading metadata files.
  • Setting to N prevents Scenario Migration from checking the load.system.id against the target system specified whenthe scenario, network or dataset was extracted.
  • Setting to Y enables this check. If the target in theXML file does not match the setting for load.system.id or the target is present in XML file but the load.system.id is blank then the system prompts you for an appropriate action. You can then continue with load or abandon the load, and you can apply the same answer to all other files in the session of Scenario Migration or allow the utility to continue prompting on each XML file that has a mismatch.