Implementation Guide › Installing CA User Activity Reporting Module › Installing the JDBC Client

Installing the JDBC Client

The JDBC client provides JDBC access through any Java-enabled applet, application, or application server. It delivers high-performance point-to-point and n-tier access to data sources. The client is optimized for the Java environment, allowing you to incorporate Java technology and extend the functionality and performance of your existing system.

The JDBC client runs on 32-bit and 64-bit platforms. No changes are required to existing applications to enable them to run on 64-bit platforms.

Installing the JDBC client involves the following steps:

1. Ensure that a web application server with connection pool configuration capabilities is installed and running.
2. Obtain the license key for the JDBC client driver.
3. Install the JDBC client.
4. Configure the connection to the database using your web application server's connection pool management functions.
5. Test the connection to the database.

JDBC Client Prerequisites

JDBC access to the event log store is available only CA User Activity Reporting Module r12.1 and later releases. You can install the JDBC client on Windows and UNIX systems.

Users of this feature must belong to a CA User Activity Reporting Module user group that has the dataaccess privilege in the Default Data Access Policy (in the CALM access policies).

For a JDBC client, the following prerequisites apply:

• You must have administrator privileges to install the JDBC client on a Windows server.
• Verify that the ODBC Server configuration window shows that the Enable Service check box is selected (enabled)
• You must have rights to create files in the directory where you want to install the client on UNIX and Linux systems.
• For applications running under the J2SE v 1.4.2.x, set your database connections programmatically, as defined in a specific application.
• For applications running under J2EE 1.4.2.x and later versions, use a web application server such as Oracle WebLogic or Red Hat JBoss to configure connection pool management.

See the CA User Activity Reporting Module Support Certification Matrix on http://www.ca.com/Support for details on the specific platforms supported for use with the ODBC and JDBC feature.

Install the JDBC Client on Windows Systems

Use this procedure to install the JDBC client driver on a Windows system.

To install the JDBC driver

1. Locate the following two .jar files in the Application DVD or installation image, in the directory CA/ELM/JDBC:

   LMjc.jar
   LMssl14.jar
   

2. Copy the .jar files to the desired directory on the destination server and make a note of the location.

Install the JDBC Client on UNIX Systems

Use this procedure to install the JDBC client driver on a UNIX system.

To install the JDBC driver

1. Locate the following two .jar files in the Application DVD or installation image, in the directory CA/ELM/JDBC:

   LMjc.jar
   LMssl14.jar
   

2. Copy the .jar files to the desired directory on the destination server and make a note of the location.
3. Execute the following (or similar) command manually from the installation directory after installing the JDBC client for JDBC on UNIX:

   chmod -R ugo+x file_location
   

   The value for file_location is the directory where you installed the JDBC client. This step enables you to execute shell scripts supplied with the installed client.

JDBC Connection Parameters

Various applications require certain connection parameters to use the JDBC client driver. The usual parameters include the following:

• Connection string or connection URL
• Class name

The JDBC connection string (URL) is in the following format:

jdbc:ca-elm://[CA-ELM_host_name]:[ODBC/JDBCport];ServerDataSource=Default;

The JDBC driver class name is:

com.ca.jdbc.openaccess.OpenAccessDriver

JDBC URL Considerations

When using the JDBC client to access event data stored in CA User Activity Reporting Module, you need both the JDBC Classpath and a JDBC URL. The JDBC Classpath names the driver JAR file locations. The JDBC URL defines the parameters the classes in the JARs use when they load.

The following is a complete, sample JDBC URL:

jdbc:ca-elm://127.0.0.1:17002;encrypted=1;ServerDataSource=Default;CustomProperties=(querytimeout=600;queryfederated=true;queryfetchrows=1000;offsetmins=0;suppressNoncriticalErrors=false)

The following descriptions explain the URL components:

jdbc.ca-elm:

Defines the protocol:subprotocol string that designates the JDBC driver provided with CA User Activity Reporting Module.

//IP Address:Port;

Names the IP address that represents the CA User Activity Reporting Module server whose data you want to access. The port number is the port to use for the communications, and must match the setting in the CA User Activity Reporting Module ODBC Service configuration panel. If the ports do not match, the connection attempt fails.

encrypted=0|1;

Determines whether SSL encryption is used for the communications between the JDBC client and the CA User Activity Reporting Module server. The default value is 0, not encrypted, and does not require specification in the URL. Setting encrypted=1 turns encryption on. Set the connection to encryption explicitly. In addition, this setting must match what you configure in the CA User Activity Reporting Module ODBC Service dialog or the connection attempt fails.

ServerDataSource=Default

Specifies the name of the data source. Set this value to Default for access to the CA User Activity Reporting Module event log store.

CustomProperties=(x;y;z)

These properties are the same as the ODBC custom properties. If you do not specify them explicitly, the default values shown in the example URL apply.

More information

ODBC Data Source Considerations