Using the JDBC Server

Using the Java Client on Any Platform › Using the JDBC Server

Using the JDBC Server

The JDBC server can be used as a command line application to support web servers running on platforms other than Windows and z/OS. The JDBC server application is provided as a Java archive file, and is actually the same file used by the JDBC server service on z/OS. Because the native code has not been ported to all platforms, certain limitations apply:

The service wrapper is not supported. Start and stop the JDBC server by running the JVM, specifying the main class file. It can be run as a background process.
The configuration file is not supported. Instead, specify options in the properties file or on the command line.
The native log file is not supported, but trace information can be written to stdout or a file specified in the properties file. Log messages are sent to stderr instead of the syslog daemon.
The native SQL client is not supported. Connections are routed to CA IDMS using a remote JDBC server running on Windows, z/OS, or directly to CA IDMS r16 SP2 or later which is treated as a remote server.

To use the JDBC server as a command line application

Extract the JDBC server Java archive file, idmsjsrv.jar, on the client machine. For example, on UNIX, assuming you have copied the archive to the /classes directory:
```
cd /classes
tar -xovf idmsjdbc.tar idmsjsrv.jar
```
Update the CLASSPATH environment variable to point to the JDBC server directory and Java archive file. For example:
```
set CLASSPATH=/classes:/classes/idmsjsrv.jar:$CLASSPATH
```
Start the JDBC server with a command similar to:
```
java ca.idms.proxy.ProxyMain start -h host 1>out 2>err &
```
The parameters are as follows:

host

Specifies the DNS name or TCP/IP address of the Windows or z/OS machine where the native JDBC server is running, or for CA IDMS r16 SP2 or later, the DNS name or TCP/IP address associated with the TCPIP line of the IDMS system.

out

Specifies the name of the trace file, and err specifies the name of the log file.
Stop the JDBC server with:
```
java ca.idms.proxy.ProxyMain stop
```

Options equivalent to those specified in the configuration file on z/OS or using the ODBC Administrator on Windows are specified in the properties file or on the command line:

Options	Description
-?	Prints this information
-h host	Host listener name or IP address
-p port	Host listener IP port
-q count	Host listener queue length
-r host	Remote host name or IP address
-s port	Remote IP port
-c	Enables control by remote client
-e encoding	Overrides platform encoding
-u	Specifies Unicode fallback encoding
-w seconds	Client wait timeout interval
-t seconds	Server reply timeout interval
-b seconds	Socket blocking timeout interval
-v [level]	Syslog message level (level = 10 if not specified)
-l level	Trace log message level
-d option [option]	Enables debugging with the following trace options, where option can be: trace—debug tracing native—native trace snap—object display buffer—native buffer display object—native object display
-k	Enables SSL client support
-a	Requires SSL client certificate
-y	Enables SSL to remote JDBC Server or CA IDMS r16 SP2 or later
-i class [class]	Includes class in trace
-x class [class]	Excludes class from trace

Note: For detailed information about these options, see the appendices "Configuration File Information" and "Properties File Information."