01.01.2013 Views

CICS Transaction Gateway V5 The WebSphere ... - IBM Redbooks

CICS Transaction Gateway V5 The WebSphere ... - IBM Redbooks

CICS Transaction Gateway V5 The WebSphere ... - IBM Redbooks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

10.2.1 J2EE Server configuration files<br />

A J2EE Server instance utilizes several different configuration files. <strong>The</strong> key files<br />

are as follows:<br />

current.env Current environment variables<br />

jvm.properties JVM properties settings<br />

webcontainer.conf Web container configuration<br />

For our J2EE Server instance, these files were located in the directory:<br />

/<strong>WebSphere</strong>C1/CB390/controlinfo/envfile/WTSCPLX1/C1OASR2A/<br />

In Example 10-1 we show the content of our jvm.properties file for our J2EE<br />

Server instance. <strong>The</strong>se settings were created from the settings input using the<br />

Administration application. After changes are activated using the Administration<br />

application, the settings are written to the jvm.properties file.<br />

Example 10-1 jvm.properties for J2EE Server instance<br />

com.ibm.ws390.wc.config.filename=/<strong>WebSphere</strong>C1/CB390/controlinfo/envfile/<br />

WTSCPLX1/C1OASR2A/webcontainer.conf<br />

com.ibm.ws390.trace.settings=/<strong>WebSphere</strong>C1/CB390/controlinfo/envfile/WTSCPLX1/<br />

C1OASR2A/trace.dat<br />

com.ibm.ws390.server.classloadermode=1<br />

In Example 10-2, we show the content of our current.env file for our J2EE Server<br />

instance C1OASR2A. <strong>The</strong>se settings were created from the settings input using<br />

the Administration application. After changes are activated using the<br />

Administration application, the settings are written to the current.env file.<br />

Example 10-2 current.env for J2EE Server instance<br />

# ENVIRONMENT FILE FROM CONVERSATION 20.6. 10:24<br />

#----------------------------------------------<br />

CLASSPATH=/usr/lpp/<strong>WebSphere</strong>/lib/ws390srt.jar:/usr/lpp/<strong>WebSphere</strong>/lib/xerces.jar<br />

:/usr/lpp/<strong>WebSphere</strong>/lib/waswebc.jar:/usr/lpp/WebSphe re/lib/bboaxrt.jar:<br />

/usr/lpp/db2/db2710/classes/db2j2classes.zip:/usr/lpp/<strong>WebSphere</strong>/lib/<br />

waswebccp.jar:/usr/lpp/ctg500/ctg/deployable/cicseciRRS.jar:/usr/lpp/ctg500/ctg<br />

/deployable/cicsframe.jar:/usr/lpp/ctg500/ctg/deployable/ctgserver.jar:/usr/lpp<br />

/ctg500/ctg/deployable/ctgclient.jar:<br />

JVM_LOGFILE=/tmp/C1OASR2.jvm.log<br />

BBOC_HTTP_PORT=80<br />

BBOC_HTTP_LISTEN_IP_ADDRESS=9.12.6.29<br />

LIBPATH=/usr/lpp/db2/db2710/lib:/usr/lpp/java/<strong>IBM</strong>/J1.3/bin:/usr/lpp/java/<strong>IBM</strong>/<br />

J1.3/bin/classic:/usr/lpp/<strong>WebSphere</strong>/lib:/usr/lpp/ctg500/ctg/deployable<br />

MAX_SRS=5<br />

DFHJVPIPE=WASCTG<br />

TRACEBUFFLOC=SYSPRINT<br />

Chapter 10. <strong>CICS</strong> TG and <strong>WebSphere</strong> Application Server for z/OS 245

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!