CA Risk Authentication Windows Installation Guide › How to Deploy CA Risk Authentication on a Single System › How to Prepare an Application Server › Copy Database Access Files to Application Server

Copy Database Access Files to Application Server

UDS and Administration Console use the following files to access the CA Risk Authentication database securely:

• arcot-crypto-util.jar available at:

  <install_location>\Arcot Systems\java\lib\
  

• ArcotAccessKeyProvider.dll available at:

  <install_location>\Arcot Systems\native\win\<32bit-or-64bit>\
  

As a result, copy these files to the appropriate location on the application server where you have deployed the CA Risk Authentication components. The following subsections provide information about copying these files for:

Apache Tomcat

Follow these steps:

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

   <Tomcat_JAVA_HOME>

   Specifies 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

Follow these steps:

1. Log in to WebSphere Administration Console.
2. Click Environment, and click Shared Libraries.
   1. From the Scope drop-down, select a valid visibility scope. Include the target server or node on which the application is deployed.
   2. Click New.
   3. Enter the Name.

      Example: ArcotJNI.

   4. Enter 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.

      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.
4. Configure the server-level class loaders.
   1. Navigate to Servers, Server Types, WebSphere Application Servers.
   2. Under Application Servers, access the settings page of the server.
   3. Click Java and Process Management. 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. Click Shared Library References.
   8. Click Add and select ArcotJNI. 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

Follow these steps:

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

   Here, <Weblogic_JAVA_HOME> represents the JAVA_HOME used by the 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. Navigate to the directory that contains the arcot-crypto-util.jar file.
7. Click Next.
8. Click Next to display the Summary page.
9. Click Finish.
10. Activate the changes.
11. Restart the application server.

JBoss Application Server

Follow these steps:

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. Create a folder structure as <JBOSS_HOME>\modules\advauth-admin-libs\main\ and copy the following JARs from <ARCOT_HOME>\java\lib to this folder:
   • arcot-crypto-util.jar.
   • bcprov-jdk15-146.jar
3. Create a file with the name module.xml in the same folder location (<JBOSS_HOME>\modules\advauth-admin-libs\main) with the following codes:

   <?xml version="1.0" encoding="UTF-8"?>
   <module xmlns="urn:jboss:module:1.1" name="advauth-admin-libs">
   <resources>
   <resource-root path="arcot-crypto-util.jar"/> 
   <resource-root path="bcprov-jdk15-146.jar"/> 
   </resources>
       <dependencies>
           <module name="javax.api"/>
       </dependencies>
   	              </module>
   

4. Restart the application server.