8.4.1 Configuring the Scenario Migration Utility

To configure the Scenario Migration Utility, navigate to <OFSAAI Installed Directory>/database/db_tools/mantas_cfg/install.cfg. The install.cfg file contains common configuration information that Scenario Migration and other utilities require for processing.

Sample install.cfg File for Scenario Migration

This section provides sample information from the install.cfg file that is specific to this utility.

################ SCENARIO MIGRATION CONFIGURATION #######################
#### GENERAL SCENARIO MIGRATION SETTINGS

#Specify the flags for whether scoring rules and wrapper datasets must be extracted or loaded
score.include=N
wrapper.include=N

#Specify the Use Code for the scenario. Possible values are 'BRK' or 'EXP'
load.scnro.use=BRK

#If custom patterns exist for a product scenario, set to 'Y' when loading a scenario hotfix.
#This should normally be set to 'N'.
load.ignore.custom.patterns=N

#Specify the full path of depfile and name of fixfile used for extraction and loading
#Note : fixfile need not be specified in case of loading
sm.depfile=/scratch/ofsaaapp/OFSBD 8.0.2/OFSBD 8.0.2_B06/BDP62_B06/database/db_tools/mantas_cfg/dep.cfg

sm.release=5.7.1

#### EXTRACT

# Specify the database details for extraction
extract.database.username=${utils.database.username}
extract.database.password=${utils.database.password}

# Specify the case schema name for both extraction and load .
caseschema.schema.owner=ATOMIC

# Specify the jdbc driver details for connecting to the source database
extract.conn.driver=${database.driverName}
extract.conn.url=jdbc:oracle:thin:@ofss220074.in.oracle.com:1521:Ti1O11L56
#Source System Id
extract.system.id=
# Specify the schema names for Extract
extract.schema.mantas=${schema.mantas.owner}
extract.schema.case=ATOMIC
extract.schema.business=${schema.business.owner}
extract.schema.market=${schema.market.owner}
extract.user.miner=${load.user.miner}
extract.miner.password=${utils.miner.password}

# File Paths for Extract

#Specify the full path in which to place extracted scenarios
extract.dirname=/scratch/ofsaaapp/OFSBD 8.0.2/OFSBD 8.0.2_B06/BDP62_B06/database/db_tools/data

#Specify the full path of the directory where the backups for the extracted scripts would be maintained
extract.backup.dir=/scratch/ofsaaapp/OFSBD 8.0.2/OFSBD 8.0.2_B06/BDP62_B06/database/db_tools/data/temp

#Controls whether jobs and thresholds are constrained to IDs in the product range (product.id.range.min
# through product.id.range.max). Values are Y and N. If the range is not restricted, you can use range.check
# to fail the extract if there are values outside the product range.
extract.product.range.only=N
extract.product.range.check=N

#### LOAD

# Specify the jdbc driver details for connecting to the target database
load.conn.driver=${database.driverName}
load.conn.url=${utils.database.urlName}

#Target System ID
load.system.id=Ti1O11L56

# Specify the schema names for Load
load.schema.mantas=${schema.mantas.owner}
load.schema.case=ATOMIC
load.schema.business=${schema.business.owner}
load.schema.market=${schema.market.owner}
load.user.miner=${utils.miner.user}
load.miner.password=${utils.miner.password}

#Directory where scenario migration files reside for loading
load.dirname=/scratch/ofsaaapp/OFSBD 8.0.2/OFSBD 8.0.2_B06/BDP62_B06/database/db_tools/data

# Specify whether threshold can be updated
load.threshold.update=Y

# Specify whether or not to verify the target environment on load
verify.target.system=N

Note:

In the install.cfg file, entries are in the form Property1=${Property2}. That is, the value for Property1 is the value that processing assigns to Property2. As such, if you change Property2’s value, Property1’s value also changes.

Configuring the Environment

To configure the environment for scenario migration, modify the parameters that the sample <OFSAAI Installed Directory>/database/db_tools/mantas_cfg/install.cfg shows. The tables in the following sections describe the parameters specific to the Scenario Migration Utility.