JDBC Driver Implementation and Configuration › DriverManager › JDBC URL Format for a DriverManager Connection

JDBC URL Format for a DriverManager Connection

A URL is used to locate a resource on the Internet; it can be thought of as an address. A URL always begins with a protocol followed by a colon, such as http: or ftp: and the rest of the string is defined by the protocol. In keeping with the Internet orientation of Java, JDBC URLs are used to identify databases. The JDBC specification defines conventions for the format of JDBC URLs. Each JDBC driver defines the actual format of the URLs that it recognizes. The general format of a JDBC URL is as follows:

jdbc:<subprotocol>:<subname>

Protocol in a JDBC URL is always jdbc. The <subprotocol> and <subname> variables are defined by the JDBC driver. The subprotocol for the CA Datacom JDBC driver is datacom. The subname for the CA Datacom JDBC driver defines the type of connection and the connection parameters

The CA Datacom JDBC driver recognizes three URLs with <subprotocol> datacom. The subname for the CA Datacom JDBC driver defines the type of connection and the connection parameters.

The CA Datacom Server JDBC driver URL general syntax is as follows:

jdbc:datacom:/<subname>

Specifies the format used to make a Type 2 JDBC driver connection. The CA Datacom JDBC driver calls the Proprietary Interface directly. It does not use the proxy. This connection can be made from Windows or USS environments, only. The <subname> consists of keyword/value pairs for the connection properties, as shown in the following example.

jdbc:datacom:/ServerName=,SystemID=,ApplicationID=,UserID=,Password=.
NewPassword=,HostName=,HostPort=,ConnectType=.TransTable=

jdbc:datacom://<proxyname>:<proxyport>/<subsubname>

Specifies the format used to make a Type 3 JDBC driver connection. The CA Datacom JDBC driver calls the JDBC Proxy which in turn invokes the Proprietary Interface to communicate with the CA Datacom Server mainframe region . This is typically used when a Java applet or application is deployed on a platform where the Proprietary Interface is not supported, such as Linux or UNIX.

<proxyname>

Specifies the IP address or DNS name of the Windows box or USS LPAR where JDBC Proxy is deployed.

<proxyport>

Specifies the IP port that was specified as the JDBC Proxy listener.

<subsubname>

Consists of the keyword or value pairs for the connection properties as shown in the following:

jdbc:datacom://<proxyname>:<proxyport>/ServerName=,SystemID=,ApplicationID=,
UserID=,Password=.NewPassword=,HostName=,HostPort=,ConnectType=.TransTable=

jdbc:datacom://<hostname>:<hostport>/<subsubname>

Specifies the format used to make a Type 4 JDBC driver connection (z/OS only). The CA Datacom JDBC driver calls the CA Datacom Server mainframe component directly using its TCP/IP listener port. The Type 4 JDBC driver connection requires the native TCP/IP interface. PROTOCOL=BOTH must be specified in the CA Datacom Server mainframe component startup parameters.

<hostname>

Specifies the IP address or DNS name of the LPAR where CA Datacom Server mainframe component resides.

<hostport>

Specifies the IP listener port of the CA Datacom Server mainframe component startup parameter, TCPIP_PORT= .

<subsubname>

Consists of the keyword or value pairs for the connection properties as shown in the following:

Note: ServerName, SystemID, ApplicationID and ConnectType properties are irrelevant because the connection is made based on the hostport.

jdbc:datacom://<hostname>:<hostport>/UserID=,Password=.NewPassword=,TransTable=

For the previous URL samples, the properties are the same as those seen in the cadatacom.properties file.