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.

the J2EE resource (the ECI resource adapter). Using Server or Role would<br />

cause either the Server’s user ID or EJB role security to be used.<br />

► ThreadID<br />

This parameter is set on the EJB deployment descriptor in the +ThreadID tab<br />

by selecting Set OS Thread Identity to RunAS Identity for the methods in<br />

the home and remote interface. <strong>The</strong> default is for the value not to be set. It<br />

controls the operating system identity on the thread of execution and allows<br />

the security context of the thread to be switched to that of the caller itself. If<br />

set for a J2EE/EJB application using the ECI resource adapter, this will<br />

change the link user ID for the EXCI request to be the flowed user ID rather<br />

than the user ID of the J2EE Server.<br />

► Res-Auth<br />

This parameter controls whether the container or application component will<br />

determine the user ID. This defaults to container and this is what we used,<br />

since this will honor the settings for ThreadID and RunAS. If Res-Auth is set<br />

to application then the user ID and password are taken from the values<br />

specified in the getConnection() method.<br />

10.4 Problem determination<br />

In this section, we document useful information we learned while configuring this<br />

scenario and further information on problem determination and tracing.<br />

10.4.1 Tips and utilities<br />

In this section, you will find commands and utilities to use in debugging problems<br />

with your configuration. You will also find some additional information about<br />

topics discussed in this chapter.<br />

<strong>WebSphere</strong> logs<br />

<strong>WebSphere</strong> Application Server uses the MVS Logger to store its log data, and<br />

therefore for setup you need to define policies to the MVS Logger for this<br />

purpose. In order to access and read this log information, you need to have<br />

access to a sample CLIST called BBORBLOG, which is supplied on the<br />

SBBOEXEC data set, which can be run using the following command:<br />

EXEC 'BBO66.SBBOEXEC(BBORBLOG)' 'WAS.SC66.ERROR.LOG'<br />

Where WAS.SC66.ERROR.LOG is the name of the MVS Logger logstream definition<br />

containing the log data. A sample of the type of information you might find when<br />

you enter this command is shown in Example 10-7.<br />

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

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

Saved successfully!

Ooh no, something went wrong!