Installing Scenario Manager

7.3 Installing Scenario Manager

This section provides the general steps to install the OFS BD Scenario Manager software, along with a reference to the specific section and page where the tasks are explained.

Installing the Scenario Manager involves the following procedures:

Verifying the Pre-installation Requirements
Installing the Scenario Manager on Workstation

Verifying the Pre-installation Requirements

Before you install the OFSBD Scenario Manager on the Windows workstation, verify the following information:

Verifying Prerequisite Third-Party Software Installation
Verifying Values for the Scenario Manager Installation Program

Note:
Install and configure the OFS BD application completely before you install the Scenario Manager software.

Verifying Prerequisite Third-Party Software Installation

Before installing the OFS BD Scenario Manager, verify that the third-party software defined in the following table is installed and configured on the workstation.

Table 7-2 Prerequisite Third-Party Software Products for the Scenario Manager Workstation

Component	Product	Version	Vendor
Operating System	Windows 7 and above	-	Microsoft
Java (32-bit)	JRE, Standard Edition with HotSpot	1.8 and above	Sun

Verifying Values for the Scenario Manager Installation Program

To prepare for the OFS BD Scenario Manager installation program’s requests for information, use the pre-installation checklist in the following table to verify the database connection information, provide the user and owner names to the Scenario Manager Installation Program.

Table 7-3 Scenario Manager Pre-installation Checklist

Item	Description	Example Value	Your Value
OFS BD Installation Directory	Directory on the workstation where you want to install the Scenario Manager.	C:\Oracle Scenario Manager	Microsoft
Database Client	Oracle Client 11g Release 2 (11.2.0.3.0+) - 64 bit Oracle Client 12c Release 1 (12.1.0.1.0+) - 64 bit Oracle Database Client & Server - Enterprise Edition 19.3+	N/A	N/A
Service Name/SID	Service Name/ SID for the instance. This is often the same as the database name.	ORA_PROD	Sun
KDD Schema Database Owner	KDD Schema Database owner's name.	Value for kdd_ schema_owner	-
Alert Management Schema Database Owner Name	Mantas Schema Database owner's name.	Value for mantas_ schema_owner	-
Database server name	Name of the server that the database resides on.	prod_server	-
KDD Miner User Name	KDD Miner user's name.	Value for tools_user	-
Operating System	Windows 7 and above.	-	Microsoft
Java (32-bit)	JRE, Standard Edition with HotSpot.	1.8 and above	Sun
JRE Home	Directory name of your JRE 1.7 server installation.	C:\apps\jre1.7	-
Maximum Java Virtual Machine Memory	Usage Maximum amount of Java Virtual Machine (JVM) memory available for the Scenario Manager.	64	-
Program Group Name	Name of the Windows Program Group where you want to install the Scenario Manager.	Financial Crime and Compliance Management Scenario Manager	-
JAVA_TOOL_OPTIONS	System environmental variable need to add a new param.	Dos.name=Windows 7	-

Installing the Scenario Manager on Workstation

The OFS BD Scenario Manager Installation program installs the Scenario Manager using a series of screens that prompt you for the information relevant to local installation and interface with the other subsystems of the OFS BD application.

Note:

You can cancel the installation from any screen in the installation program. For more information, see Cancelling the Scenario Manager Installation Program.

To start the OFS BD Scenario Manager installation, follow these steps:

Copy the ScenarioManager.exe file from OFS_BD_PACK/OFS_BD/bin to the windows machine.
Scenario Manager installation with Java version jre1.8.0_60 and above generates the error Windows Error 2 Occurred While Loading the Java VM. Follow the below steps to address this error:
1. Open the Command Prompt and navigate to the location of the installer CD C:\Users\”YourUsername”\Downloads.
2. Once in the location of the Installer, execute the command:
```
ScenarioManager.exe -i GUI LAX_VM "C:\Program Files (x86)\Java\jre1.8.0_291\bin\java.exe"
```
  Note:
  The JRE file (jre1.8.0_291) referred to above must be the version available in the local setup.
Enter the Oracle database connection string for Oracle Mantas. In most cases, this is the same as the Oracle database instance. For example: jdbc:oracle:thin:@hostname:port ID:service name/ Service ID.
For the Oracle Mantas database, enter the atomic schema as username for the following:
1. KDD schema database owner
2. FIRM schema database owner
3. KDD miner
When prompted for Java Runtime Environment Home, click Next.
Make below changes in kddstart.bat at C:\opt\Oracle_Mantas_Platform\behavior_detection\toolkit\bin\kddstart.bat
Changes to be made in kddstart.bat are listed below:
- Set ‘set KDD_HOME=C:\opt\Oracle_Mantas_Platform\behavior_detection’
- Set ‘set JAVA_HOME="C:\Program Files (x86)\Java\jre1.8.0_291"’
  
  Note:
  The JRE file (jre1.8.0_291) referred to above must be the version available in the local setup.
- Set ‘SET ORACLE_JAR=%LIBDIR%\ojdbc7.jar’.
  Note:
  - Set the latest ojdbc.jar file value in ORACLE_JAR. ojdbc6.jar is unable to connect with 19c.
  - If the Scenario Manager tool does not have the latest jar files, copy the required .jar files from ##FIC_HOME/ficweb/ WEB_INF/lib ## and place them at <INSTALLED_DIRECTORY\Oracle_Mantas_Platform\behavior_ detection\toolkit\lib\.
Make below changes in install.cfg at C:\opt\Oracle_Mantas_Platform\behavior_detection\toolkit\mantas_cfg\inst all.cfg
Changes to be made in install.cfg are listed below:
Enter the Correct jdbc details. For example: com.mantas.toolkit.database.url=jdbc:oracle:thin:@whf00qjy.in.oracle.co m:1521:Ti41O12L74
Set mantas.jvm.maximum.size=256 or mantas.jvm.maximum.size=1000
Copy and paste these two files (common.dtd and pattern.dtd) from C:\Oracle_Mantas_Platform\behavior_detection\toolkit\xml to C:\Oracle_Mantas_Platform\behavior_detection\toolkit\bin.
Launch the Scenario Manager.
C:\opt\Oracle_Mantas_Platform\behavior_detection\toolkit\bin\kddstart.bat
Note:

If the Command window does not come up when kddstart.bat is clicked, then follow the below steps. This may happen due to an issue with the DB connection.
1. Check set JAVA_HOME="C:\Program Files (x86)\Java\jre1.8.0_291" in the kddstart.bat file and confirm that the provided path exists in the local.
2. Check that the Schema name is correct in the install.cfg file.
3. In install.cfg, the JDBC url must have separator as : or /. If the kddstart.bat does not work with : as a separator then change the separator to /.
For example: com.mantas.toolkit.database.url=jdbc:oracle:thin:@whf00qjy.in.oracle.com:1521/Ti41O12L74 or

com.mantas.toolkit.database.url=jdbc:oracle:thin:@whf00qjy.in.oracle.com:1521:Ti41O12L74.