Previous Topic: Performing Post-Installation TasksNext Topic: Deploying Administration Console

CA RiskMinder Windows Installation Guide › Deploying RiskMinder On a Single System › Performing Post-Installation Tasks › Running Database Scripts

Running Database Scripts

Important! Before you run the scripts that are discussed in this section, ensure that you are logged in as the same database user that you created in the section, "Configuring Database Server".

RiskMinder is shipped with scripts that are required to create necessary tables in the RiskMinder database. To run the required database scripts:

  1. Navigate to the following directory: 
    <install_location>\Arcot Systems\dbscripts\
  2. Based on the database that you are using, navigate to one of the following subdirectories:
  3. Irrespective of whether you have a single database for reports and transactions, or a separate database for reports, run the scripts in the following order:
    1. arcot-db-config-for-common-2.0.sql

      Important! If you have installed CA AuthMinder 7.1, do not run arcot-db-config-for-common-2.0.sql because you have already run it while installing CA AuthMinder 7.1.

    2. arcot-db-config-for-riskfort-3.1.sql
    3. (Optional, only if you must create the 3D Secure Channel) arcot-db-config-for-3dsecure-3.1.sql

Verifying the Database Setup

After you run the required database scripts, verify that the RiskMinder schemas were seeded correctly. To do so:

  1. Log in to the RiskMinder database as the user who installed the database.

    Note: If you are following the upgrade path, then log in to the database as the user who upgraded the database.

  2. Run the following query: 
    SELECT SERVERNAME, VERSION FROM ARRFSERVERS;

    You must see the following output as a result of the preceding query:

    SERVERNAME                   VERSION
-------------------------  ----------------
RiskFort                     3.1
RiskFortCaseManagement       3.1
  3. Log out of the database console.

Preparing Your Application Server

Two components of RiskMinder, User Data Service (UDS) and Administration Console, are web-based and can be deployed on any of the following supported application servers:

Before you deploy the WAR files for these web applications on the application server of your choice, copy the files that are required by UDS and Administration Console to the appropriate location on your application server. This section walks you through the steps to copy the required crypto files to your application server and to deploy the WAR files of these web applications:

Step 1: Setting Java Home

Before you deploy the WAR files for UDS and Administration Console on the application server of your choice, ensure that you set the JAVA_HOME environment variable. This JAVA_HOME must be your application server JAVA_HOME.

In addition, %JAVA_HOME%\bin\ must be added to the PATH variable. If you fail to do so, then Administration Console, UDS, and other JDK-dependent components may fail to start.

Step 2: Copying Database Access Files to Your Application Server

UDS and Administration Console use the following files to access the RiskMinder database securely:

As a result, these files must be copied to the appropriate location on the application server where you have deployed these RiskMinder components. The following subsections provide information about copying these files for:

Apache Tomcat

To copy the files that are required for database access:

  1. Copy arcot-crypto-util.jar to <Tomcat_JAVA_HOME>\jre\lib\ext\.

    Here, <Tomcat_JAVA_HOME> represents the JAVA_HOME used by your Apache Tomcat instance.

  2. Copy ArcotAccessKeyProvider.dll to <Tomcat_JAVA_HOME>\jre\bin\.
  3. Restart the application server.

IBM WebSphere

To copy the files that are required for database access:

  1. Log in to WebSphere Administration Console.
  2. Click Environment, and then click Shared Libraries.
    1. From the Scope drop-down, select a valid visibility scope. The scope must include the target server or node on which the application is deployed.
    2. Click New.
    3. Enter the Name, for example, ArcotJNI.
    4. Specify the Classpath.

      This path must point to the location where the arcot-crypto-util.jar file is present and must also include the file name. For example, C:\Program Files\Arcot Systems\java\lib\arcot-crypto-util.jar.

    5. Enter the JNI Library path.

      This path must point to the location where the ArcotAccessKeyProvider.dll file is present.

  3. Click Apply to save the changes.
  4. Configure the server-level class loaders.
    1. Click Servers, and then click Application Servers.
    2. Under Application Servers, access the settings page of the server for which the configuration must be performed.
    3. Click Java and Process Management and then click Class Loader.
    4. Click New.
    5. Select default Classes loaded with parent class loader first and click OK.
    6. Click the auto-generated Class Loader ID.
    7. On the class loader Configuration page, click Shared Library References.
    8. Click Add, select ArcotJNI, and then click Apply.
    9. Save the changes.
  5. Copy ArcotAccessKeyProvider.dll to <WebSphere_JAVA_HOME>\jre\bin\.

    Here, <WebSphere_JAVA_HOME> represents the JAVA_HOME used by your IBM WebSphere instance.

  6. Restart the application server.

Oracle WebLogic

To copy the files that are required for database access:

  1. Copy ArcotAccessKeyProvider.dll to <WebLogic_JAVA_HOME>\jre\bin\.

    Here, <Weblogic_JAVA_HOME> represents the JAVA_HOME used by your Oracle WebLogic instance.

  2. Copy arcot-crypto-util.jar to <WebLogic_JAVA_HOME>\jre\lib\ext\.

    Note: Ensure that you use the appropriate <JAVA_HOME> used by WebLogic.

  3. Log in to WebLogic Administration Console.
  4. Navigate to Deployments.
  5. Enable the Lock and Edit option.
  6. Click Install and navigate to the directory that contains the arcot-crypto-util.jar file.
  7. Click Next to open the Application Installation Assistant.
  8. Click Next to display the Summary page.
  9. Click Finish.
  10. Activate the changes.
  11. Restart the application server.

JBoss Application Server

To copy the files that are required for database access:

  1. Copy ArcotAccessKeyProvider.dll to <JBoss_JAVA_HOME>\jre\bin\.

    Here, <JBoss_JAVA_HOME> represents the JAVA_HOME used by your JBoss Application Server instance.

  2. Copy arcot-crypto-util.jar to <JBoss_JAVA_HOME>\jre\lib\ext\.
  3. Restart the application server.
Step 3: Copying JDBC JAR Files to Your Application Server

RiskMinder requires the following JDBC JAR files for the supported databases:

The following subsections walk you through the steps for copying the JDBC JAR required for your database to one of the following application servers:

Apache Tomcat

To copy the required JDBC JAR file:

  1. Navigate to the location where you have downloaded the <Database_JAR> file.
  2. Copy the <Database_JAR> file to the following directory:
  3. Restart the server.

IBM WebSphere

To copy the required JDBC JAR file:

  1. Log in to the WebSphere Administration Console.
  2. Click Environment, and then click Shared Libraries.
    1. From the Scope list, select a valid visibility scope. The scope must include the target server or node on which the application is deployed.
    2. Click New.
    3. Enter the Name, say, JDBCJAR.
    4. Specify the Classpath.

      Important! This path must point to the location where the <Database_JAR> file is present and must include the file name.

    5. Click Apply to save the changes that were made.
  3. Configure server-level class loaders.
    1. Click Servers, and then click Application Servers.
    2. Under Application Servers, access the settings page of the server for which the configuration is performed.
    3. Click Java and Process Management, and then click Class Loader.
    4. Click New.
    5. Select default Classes loaded with parent class loader first and click OK.
    6. Click the auto-generated Class Loader ID.
    7. In the class loader Configuration page, click Shared Library References.
    8. Click Add, select JDBCJAR, and then click Apply.
    9. Save the changes that were made.
  4. Restart the application server.

Oracle WebLogic

Note: If you are using Oracle database, then do not perform the configurations that are mentioned in this section, because WebLogic supports Oracle database by default.

To copy the required JDBC JAR file in the case of Microsoft SQL Server:

  1. Copy the <Database_JAR> file to <Weblogic_JAVA_HOME>\lib\ext\.

    Here, <WebLogic_JAVA_HOME> represents the JAVA_HOME used by your Oracle WebLogic instance.

  2. Log in to the WebLogic Administration Console.
  3. Navigate to Deployments.
  4. Enable the Lock and Edit option.
  5. Click Install and navigate to the directory that contains the required <Database_JAR> file.
  6. Click Next to display the Application Installation Assistant page.
  7. Click Next to display the Summary page.
  8. Click Finish.
  9. Activate the changes.
  10. Restart the application server.

JBoss Application Server

To copy the required JDBC JAR file:

  1. Copy the JDBC JAR file to the following location on the JBOSS installation directory: 
    <JBOSS_HOME>\server\default\lib\
  2. Restart the application server.
Step 4: (Mandatory for Oracle WebLogic 10.1) Creating Enterprise Archive Files

Most enterprise Application Servers (such as WebSphere and Weblogic) enable you to bundle the related Java ARchive (JAR) or Web ARchive (WAR) files from one vendor (say, CA) to a single enterprise application (or archive). As a result, all the related JARs or WARs can be deployed together, and can be loaded by a class loader. This archive also contains an application.xml file, which is generated automatically and describes how to deploy each bundled module.

By default, WAR files are provided to deploy UDS and Administration Console. However if necessary, you can also change the format of these files to Enterprise ARchive (EAR) and then deploy the EAR files.

As discussed in the following subsections, you can either generate separate EAR files for both UDS and Administration Console, or you can generate a single EAR file that contains both web archives.

Generating Separate EAR Files

To create a separate EAR file each for UDS and Administration Console:

  1. Open the Command Prompt window.
  2. Navigate to the <install_location>\Arcot Systems\tools\common\bundlemanager\ directory.
  3. To create the EAR file, run the following command: 
    java -jar bundle-manager.jar -ear <filename.ear> -warList <filename.war>

    The preceding command generates individual EAR files that are available at:

    <install_location>\Arcot Systems\java\webapps\

Generating a Single EAR File

To create a single EAR file that contains UDS and Administration Console Web archives:

  1. Open the Command Prompt window.
  2. Navigate to the <install_location>\Arcot Systems\tools\common\bundlemanager\ directory.
  3. To create the EAR file, run the following command: 
    java -jar bundle-manager.jar -ear <filename.ear> -warList arcotadmin.war arcotuds.war

    The preceding command generates a single EAR file that is available at:

    <install_location>\Arcot Systems\java\webapps\