Java commands: Starting a Java client for OLT and Distributed Debugger enablement
java_g -debug
-Dcom.ibm.CORBA.requestTimeout=0 -Dcom.ibm.CORBA.BootstrapHost=<BootstrapHostname>
-Dcom.ibm.CORBA.EnableApplicationOLT=true
-Dcom.ibm.CORBA.OLTApplicationHost=<OLT_Server_Host>
-Dcom.ibm.CORBA.OLTApplicationPort=<OLT_Server_Port>
-DOLTClient=true
-classpath <path\YourAppJarFile>;<path\somojor.zip>;<path\dertrjrt.jar>;
%CLASSPATH% AppName
Variation for AIX:
- Replace %CLASSPATH% with $CLASSPATH
where:
- <BootstrapHostname> is your fully qualified server application
host name (only needed if System Manager is running on a different host). This
specification is applicable only for WebSphere Application Server, Enterprise Edition.
- <OLT_Server_Host> is the fully qualified name or TCP/IP
address of the machine running your OLT server.
- <OLT_Server_Port> is the port where the OLT server
listens for connecting OLT clients. The default is 2102.
- <path\YourAppJarFile> is the fully qualified path to you
client application JAR file.
- <path\somojor.zip> is only required when debugging a Component
Broker client. It should be set as follows: /usr/lpp/CBConnector/lib/somojor.zip on
AIX, /opt/CBConnector/lib/somojor.zip on Solaris, and
x:\WebSphere\AppServer\lib\somojor.zip on Windows NT/2000.
- <path\dertrjrt.jar> = x:\WebSphere\AppServer\lib\dertrjrt.jar
on Windows NT/2000; /usr/WebSphere/AppServer/lib/dertrjrt.jar on AIX;
/opt/WebSphere/AppServer/lib/dertrjrt.jar on Solaris, /opt/IBMcbc/lib/dertrjrt.jar on
OS/390.
- AppName is the fully qualified path to your program.
Note:
- To eliminate out-of-memory errors, add the string -mx75m -ms30m -oss75m to
the Java command arguments. For example:
. . .
-classpath . . . %CLASSPATH%
-mx75m -ms30m -oss75m
AppName
The values 75, 30, and 75 in the above -mx75m -ms30m -oss75m example are
just sample values; they are not recommended values.
A Windows NT/2000 client environment requires these memory settings in the command.
- When running your debugger remotely and the source files reside on the machine where you
are running the debugger user interface, set DER_DBG_PATH environment variable to include
your source files.
For the Java 2 platform:
java -Xdebug -Xnoagent
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=<JVM_port>
-Djava.compiler=NONE
-Xbootclasspath/a:"<WebSphere_jdk>\lib\tools.jar;<WebSphere>\lib\derdbpw.jar"
-Denv.class.path=%DEBUG_CP%
-classpath "<path\YourAppJarFile>;<WebSphere>\lib\dertrjrt.jar;%CLASSPATH%"
-Dcom.ibm.debug.jdwpport=<JVM_port>
-Dcom.ibm.CORBA.EnableApplicationOLT=true
-Dcom.ibm.CORBA.requestTimeout=0
-Dcom.ibm.CORBA.OLTApplicationHost=<OLT_Server_Host>
-Dcom.ibm.CORBA.OLTApplicationPort=<OLT_Server_Port>
-DOLTClient=true AppName
Variation for AIX:
- Replace %CLASSPATH% with $CLASSPATH
where:
- <BootstrapHostname> is your fully qualified server application host
name (only needed if System Manager is running on a different host). This specification is
applicable only for WebSphere Application Server, Enterprise Edition.
- %DEBUG_CP% has the location of the Java source code.
- <WebSphere_jdk> is the where the WebSphere JDK is
installed, for example, c:\WebSphere\AppServer\java.
- <WebSphere> is the where the WebSphere AppServer is
installed.
- <OLT_Server_Host> is the fully qualified name or TCP/IP address
of the machine running your OLT server
- <OLT_Server_Port> is the port where the OLT server listens for
connecting OLT clients. The default is 2102.
- <path\YourAppJarFile> is the fully qualified path to you
client application JAR file.
- <JVM_port> is the port for the JVM. It is a free port
number.
- AppName is the fully qualified path to your program.
Note:
- To eliminate out-of-memory errors, add the string -mx75m -ms30m -oss75m to
the Java command arguments. For example:
. . .
-classpath . . . %CLASSPATH%
-mx75m -ms30m -oss75m
AppName
The values 75, 30, and 75 in the above -mx75m -ms30m -oss75m example are
just sample values; they are not recommended values.
A Windows NT/2000 client environment requires these memory settings in the command.
- When running your debugger remotely and the source files reside on the machine where you
are running the debugger user interface, set DER_DBG_PATH environment variable to include
your source files.
java -Xdebug -Xnoagent
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=<JVM_port>
-Djava.compiler=NONE
-Xbootclasspath/a:"<WebSphere_jdk>\lib\tools.jar;"
-Denv.class.path=%DEBUG_CP%
-classpath "<path\YourAppJarFile>;<WebSphere>\lib\dertrjrt.jar;%CLASSPATH%"
-Dcom.ibm.debug.jdwpport=<JVM_port>
-Dcom.ibm.CORBA.EnableApplicationOLT=true
-Dcom.ibm.CORBA.requestTimeout=0
-Dcom.ibm.CORBA.OLTApplicationHost=<OLT_Server_Host>
-Dcom.ibm.CORBA.OLTApplicationPort=<OLT_Server_Port>
-DOLTClient=true AppName
Variation for AIX:
- Replace %CLASSPATH% with $CLASSPATH
where:
- <WebSphere_jdk> is the where the WebSphere JDK is
installed, for example, c:\WebSphere\AppServer\java.
- %DEBUG_CP% has the location of the Java source code.
- <WebSphere> is the where the WebSphere AppServer is
installed.
- <path\YourAppJarFile> is the fully qualified path to you
client application JAR file.
- <OLT_Server_Host> is the fully qualified name or TCP/IP
address of the machine running your OLT server
- <OLT_Server_Port> is the port where the OLT server
listens for connecting OLT clients. The default is 2102.
- <JVM_port> is the port for the JVM. It is a free port
number.
- AppName is the fully qualified path to your program.
Note: When running your debugger remotely and the source files reside on the
machine where you are running the debugger user interface, set DER_DBG_PATH environment
variable to include your source files.

Debugging a Java client

Java commands for tracing and debugging