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.

324 <strong>CICS</strong> <strong>Transaction</strong> <strong>Gateway</strong> <strong>V5</strong><br />

Figure 11-33 Defining the Java system properties for the default server<br />

To activate any changes to the default server or a connection factory, the default<br />

server must be restarted. To do this, expand <strong>WebSphere</strong> Administrative<br />

Domain -> Nodes -> node name -> Application Servers. Right-click Default<br />

Server. Stop the server if it is running, then select Start to restart the default<br />

server. <strong>The</strong> connection factory trace output will now go to standard error, so it will<br />

appear in the <strong>WebSphere</strong> standard error log.<br />

JNI trace<br />

<strong>CICS</strong> TG JNI trace is produced when using a local <strong>CICS</strong> TG, and is controlled<br />

with the Java system property gateway.T.setJNITFile. <strong>The</strong> property value<br />

specifies the file name where the JNI trace is output. This must be set on the<br />

application server. To do this, perform the following steps:<br />

1. From the <strong>WebSphere</strong> administrative console, expand <strong>WebSphere</strong><br />

Administrative Domain -> Nodes -> node name -> Application Servers.<br />

Click Default Server.<br />

2. Click the JVM Settings tab.<br />

3. In the System Properties section of the JVM Settings tab, click the Add<br />

button. In the Name field enter gateway.T.setJNITFile. In the Value field<br />

enter C:\<strong>WebSphere</strong>\AppServer\logs\ctgjni.trc and then click Apply.<br />

<strong>The</strong> completed window should now look as shown in Figure 11-34.

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

Saved successfully!

Ooh no, something went wrong!