Administration Guide › Accessing Collected Events with ODBC and JDBC › Example: Preparing to Use ODBC and JDBC Clients with Crystal Reports › Edit the Crystal Reports Configuration File › JDBC URL Considerations

JDBC URL Considerations

When using the JDBC client to access event data stored in CA Enterprise Log Manager, 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 Enterprise Log Manager.

//IP Address:Port;

Names the IP address that represents the CA Enterprise Log Manager 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 Enterprise Log Manager 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 Enterprise Log Manager 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 Enterprise Log Manager 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 Enterprise Log Manager 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