Previous Topic: Copy Database Access Files to the Application ServerNext Topic: Step 4: Create Enterprise Archive File


Copy JDBC JARs to the Application Server

CA Advanced Authentication, UDS, and Sample Application, which are the Java-dependent components of CA Strong Authentication, need JDBC JAR files to connect to the database. Copy these files to the application server.

Note: Before proceeding with the steps mentioned in the following subsections, ensure that you have downloaded the JDBC JARs, see chapter, "Preparing for Installation" for more information about supported JDBC JARs.

The following sections 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 JDBC JAR file to the Apache Tomcat installation directory:

  1. Navigate to the location where you have downloaded the JDBC JAR file.
  2. Copy the JDBC JAR file and paste it in the following directory:

    Alternatively, add the path that contains the JDBC JAR file to the Classpath environment variable.

  3. Restart Apache Tomcat.

IBM WebSphere

To copy the JDBC JAR file to the IBM WebSphere:

  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/node on which the application is deployed.
    2. Click New.
    3. Enter the Name, for example, JDBCJAR.
    4. Specify the Classpath. This path must point to the location where the JDBC JAR file is present and must also include the file name.
    5. Click Apply to save the changes.
  3. Configure server-level class loaders.

    Note: You can either create a class loader or use the one that you created while performing the procedure described in Step 2: Copying Database Access Files to Your Application Server.

    1. Navigate Servers, Server Types, WebSphere 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. Select default Classes loaded with parent class loader first and click OK.
    5. Click the auto-generated Class Loader ID.
    6. In the class loader Configuration page, click Shared Library References.
    7. Click Add, select JDBCJAR and then click Apply.
    8. Save the changes.
  4. Restart IBM WebSphere.

Oracle WebLogic

To copy the JDBC JAR file to Oracle WebLogic Server:

Note: If you are using Oracle Database, then you need not perform the configuration described in this section because Oracle WebLogic Server supports Oracle Database by default.

  1. Copy the JDBC JAR file to the following directory:
    <JAVA_HOME used by Oracle WebLogic instance>/jre/lib/ext directory.
    
  2. Log in to 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 JDBC JAR file.
  6. Click Next.

    The Application Installation Assistant screen appears.

  7. Click Next.

    The Summary page appears.

  8. Click Finish.
  9. Activate the changes.
  10. Restart Oracle WebLogic Server.

JBoss Application Server

Follow these steps:

  1. Download the required JAR from any source, and then navigate to the location where you have downloaded it..
  2. Create a folder structure as <JBOSS_HOME>\modules\advauth-jdbc-driver\main\ and copy JDBC Jar file in this folder location.
  3. Create a file as ‘module.xml’ in the same location (<JBOSS_HOME>\modules\advauth-jdbc-driver\main\) with the following codes:
    <?xml version="1.0" encoding="UTF-8"?>
    <module xmlns="urn:jboss:module:1.1" name="advauth-jdbc-driver">
    <resources>
    <resource-root path="<JDBC Jar Name>"/>
    </resources>
        <dependencies>
            <module name="javax.api"/>
    <module name="javax.transaction.api"/>
        </dependencies>
    </module>
    

    Note: Edit the tag ‘<JDBC Jar Name>’with JDBC Jar file name.

    Example: sqljdbc.jar

Restart the application server.