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

More documents

Recommendations

Info

International Technical Support Organization CICS Transaction Gateway V5 The WebSphere Connector for CICS August 2002 SG24-6133-01
Page 1: CICS Transaction Gateway V5 The Web
Page 5 and 6: Contents Notices . . . . . . . . .
Page 7 and 8: 6.2.1 ECI to CICS TG for z/OS (EXCI
Page 9 and 10: Appendix B. Sample applications . .
Page 11 and 12: Notices This information was develo
Page 13 and 14: Preface The CICS® Transaction Gate
Page 15 and 16: Richard Johnson, Robert Jerrom, Kat
Page 17 and 18: Summary of changes This section des
Page 19 and 20: Part 1 Introduction Part 1 In this
Page 21 and 22: Chapter 1. CICS Transaction Gateway
Page 23 and 24: 1.1.1 Client daemon The CICS TG Cli
Page 25 and 26: 1.1.2 Gateway daemon The Gateway da
Page 27 and 28: 1.1.3 Configuration Tool The Config
Page 29 and 30: 1.2 CICS TG: Interfaces All the pri
Page 31 and 32: ► The Common Connector Framework
Page 33 and 34: Part 2 Configuring CICS connections
Page 35 and 36: Chapter 2. APPC connections to CICS
Page 37 and 38: 2.1.1 Software checklist We used th
Page 39 and 40: 2.2 APPC connections in CICS To def
Page 41 and 42: CONNECTION Specifies the name of th
Page 43 and 44: OVERTYPE TO MODIFY CICS RELEASE = 0
Page 45 and 46: MODETAB Is the name of the VTAM log
Page 47 and 48: ► Configure a Transaction Program
Page 49 and 50: Testing the configuration After we
Page 51 and 52: 7. Started the Client daemon connec
Page 53 and 54:
2.6 Problem determination 2.6.1 Tip
Page 55 and 56:
CICSCLI /S=SCSCPJA1 /D=9999 /M=ALL
Page 57 and 58:
3 Chapter 3. TCP62 connections to C
Page 59 and 60:
Static LU names We simplified our c
Page 61 and 62:
3.2 APPC connections in CICS From a
Page 63 and 64:
Example 3-1 Content of ESA.SYS1.VTA
Page 65 and 66:
► Partner LU name 4.5 The fully q
Page 67 and 68:
The IP address mask should be set t
Page 69 and 70:
Note: Although using this technique
Page 71 and 72:
Figure 3-5 ScanPort utility 3. Star
Page 73 and 74:
Page 75 and 76:
information that you got from the c
Page 77 and 78:
IST171I ACTIVE SESSIONS = 000000000
Page 79 and 80:
3.5.2 Tracing SNA sense data can be
Page 81 and 82:
Source User Address: 0000001d MPTN
Page 83 and 84:
Chapter 4. EXCI connections to CICS
Page 85 and 86:
4.1.1 Software checklist We used th
Page 87 and 88:
Note that when a single CICS TG for
Page 89 and 90:
The key parameters in the SESSIONS
Page 91 and 92:
► SURROGCHK Defaults to YES, mean
Page 93 and 94:
Page 95 and 96:
View the connection definition To v
Page 97 and 98:
View status of EXCI calls To view t
Page 99 and 100:
5 Chapter 5. TCP/IP connections to
Page 101 and 102:
Windows 2000 CTG TCP/IP Figure 5-2
Page 103 and 104:
z/OS TCP/IP definitions The TCP/IP
Page 105 and 106:
5.3 TCP/IP definitions for the CICS
Page 107 and 108:
1. We checked basic IP connectivity
Page 109 and 110:
CICS TS For problem determination w
Page 111 and 112:
Example 5-8 tracert command C:\>tra
Page 113 and 114:
Figure 5-10 STAT report selection s
Page 115 and 116:
5.4.2 Tracing This occurs if an EPI
Page 117 and 118:
6 Chapter 6. CICS TG security scena
Page 119 and 120:
Surrogate user security CICS perfor
Page 121 and 122:
In Table 6-1 we document the user I
Page 123 and 124:
► Update access to the RACF FACIL
Page 125 and 126:
CONNECTION and SESSIONS definitions
Page 127 and 128:
Configure the flowed user ID Becaus
Page 129 and 130:
EciB1 is written so that it will in
Page 131 and 132:
CICS region configuration We used t
Page 133 and 134:
1. SC62PJA1 -CICSTS 2.2 AT SC66 2.
Page 135 and 136:
Therefore, when writing an EPI appl
Page 137 and 138:
OVERTYPE TO MODIFY CICS RELEASE = 0
Page 139 and 140:
Sign on to the CICS terminal This r
Page 141 and 142:
In contrast, Example 6-8 shows the
Page 143 and 144:
Verifying EPI signon incapable secu
Page 145 and 146:
useful in problem determination. Th
Page 147 and 148:
► Errno 163 JNI trace entry CCL68
Page 149 and 150:
Part 3 Gateway daemon scenarios Par
Page 151 and 152:
Chapter 7. TCP connections to the G
Page 153 and 154:
Page 155 and 156:
Example 7-1 Using FTP to send the z
Page 157 and 158:
the su command to switch users to t
Page 159 and 160:
Tip: When running ctginstall under
Page 161 and 162:
Tip: The contents of a JAR or zip f
Page 163 and 164:
There are two methods of defining a
Page 165 and 166:
Example 7-5 TCP protocol handler SE
Page 167 and 168:
Yes Use the setting for this variab
Page 169 and 170:
► AUTH_USERID_PASSWORD This opera
Page 171 and 172:
7.2.2 Defining CICS TG configuratio
Page 173 and 174:
CICS TG thread usage The Gateway da
Page 175 and 176:
Restriction: If your Gateway daemon
Page 177 and 178:
1. We started the CICS TG on z/OS a
Page 179 and 180:
Once the file was created, we went
Page 181 and 182:
Hex: 20202020202020203173742072756e
Page 183 and 184:
CICS TG on Windows, UNIX, or OS/2.
Page 185 and 186:
EZA0463I PING: Ping #1 response too
Page 187 and 188:
► You are upgrading to a new vers
Page 189 and 190:
incorrect CTG_RRMNAME (CCL.IBM.CTG5
Page 191 and 192:
Figure 7-9 Formatting the Gateway d
Page 193 and 194:
We see the output: CTGCtrl - CTG Co
Page 195 and 196:
Example 7-27 CICS TG for z/OS TCPAd
Page 197 and 198:
Tip: In CICS TG for z/OS V5.0 the E
Page 199 and 200:
CETR CICS Trace Control Facility PJ
Page 201 and 202:
.... EX 1000 XCPRH ENTRY - DPL TO P
Page 203 and 204:
Chapter 8. SSL connections to the G
Page 205 and 206:
Page 207 and 208:
management tool ctgikey, which uses
Page 209 and 210:
8.2.1 Configuring the server certif
Page 211 and 212:
MIIBLDCB1wIBADByMQswCQYDVQQGEwJVUzE
Page 213 and 214:
genkey Generates a key pair and wra
Page 215 and 216:
Figure 8-3 iKeyman initial window 3
Page 217 and 218:
Tip: We found that iKeyman does not
Page 219 and 220:
Tip: We found it difficult to tell
Page 221 and 222:
8.3 Testing the configuration To te
Page 223 and 224:
The message CCL8402I also indicated
Page 225 and 226:
CICS Servers Defined: 1. SCSCPJA1 -
Page 227 and 228:
► If the keystore is not in the l
Page 229 and 230:
8.4.2 Tracing Testing JSSE under z/
Page 231 and 232:
Chapter 9. TCP connections to the G
Page 233 and 234:
9.1.2 Definitions checklist The def
Page 235 and 236:
User (vmlinux1.itso.ibm.com:(none))
Page 237 and 238:
Example 9-8 Using the rpm command t
Page 239 and 240:
We clicked No on the TaskGuide? win
Page 241 and 242:
2. We defined our configuration usi
Page 243 and 244:
After we installed and configured t
Page 245 and 246:
Reply from 9.12.6.98: bytes=32 time
Page 247 and 248:
Compiling and using EciB1 In the ab
Page 249 and 250:
Gateway daemon trace Gateway daemon
Page 251 and 252:
Gateway daemon JNI trace Gateway da
Page 253 and 254:
Part 4 WebSphere scenarios Part 4 I
Page 255 and 256:
10 Chapter 10. CICS TG and WebSpher
Page 257 and 258:
10.1.1 Software checklist For this
Page 259 and 260:
HTTP Web browser TCP/IP Port: 99 Po
Page 261 and 262:
CTGTesterCCI The CTGTesterCCI enter
Page 263 and 264:
10.2.1 J2EE Server configuration fi
Page 265 and 266:
Tip: Environment variables can be s
Page 267 and 268:
2. This will display the Login wind
Page 269 and 270:
all the CICS regions with which you
Page 271 and 272:
chmod ugo+x libCTGJNI.so Defining c
Page 273 and 274:
a. Add the following JAR files in t
Page 275 and 276:
Figure 10-12 J2EE resource instance
Page 277 and 278:
2. Under the applications folder, t
Page 279 and 280:
- Look for the following message to
Page 281 and 282:
and does not affect our application
Page 283 and 284:
Deploying CTGTesterECI The installa
Page 285 and 286:
Since there is no definition of our
Page 287 and 288:
► http://wtsc66oe.itso.ibm.com:80
Page 289 and 290:
Figure 10-21 CTGTesterECI response
Page 291 and 292:
We clicked Submit and received the
Page 293 and 294:
If you are running the HTTP Server
Page 295 and 296:
Once the request had successfully e
Page 297 and 298:
Since we are using a session bean i
Page 299 and 300:
the J2EE resource (the ECI resource
Page 301 and 302:
J2EE resource adapter trace Resourc
Page 303 and 304:
For further details on tracing J2EE
Page 305 and 306:
To activate J2EE Server tracing, we
Page 307 and 308:
Chapter 11. CICS TG and WebSphere A
Page 309 and 310:
The flow of control through the ent
Page 311 and 312:
11.1.2 Definitions checklist Before
Page 313 and 314:
Default resources We expanded the c
Page 315 and 316:
Configure a connection factory Ever
Page 317 and 318:
Figure 11-8 Administrative console
Page 319 and 320:
Figure 11-10 Selecting Virtual Host
Page 321 and 322:
Figure 11-12 Default server configu
Page 323 and 324:
3. Click Next three times to displa
Page 325 and 326:
6. Click the Select Resource button
Page 327 and 328:
11.3 Testing the configuration 11.3
Page 329 and 330:
parameters were set up to cause the
Page 331 and 332:
Results with J2EE application Next
Page 333 and 334:
Figure 11-26 CTGTesterCCI enterpris
Page 335 and 336:
Figure 11-28 CTGTesterCCI resource
Page 337 and 338:
WebSphere logs Log files provide in
Page 339 and 340:
11.4.2 Tracing Example 11-2 Output
Page 341 and 342:
Figure 11-32 Connection factory tra
Page 343 and 344:
Figure 11-34 Defining the JNI trace
Page 345 and 346:
Part 5 Appendixes Part 5 In this se
Page 347 and 348:
Appendix A. DFHCNV and CICS data co
Page 349 and 350:
The name of the mirror transaction
Page 351 and 352:
Web Browser 1047 (an extended 037 E
Page 353 and 354:
EPI applications Web Browser For EP
Page 355 and 356:
Appendix B. Sample applications B I
Page 357 and 358:
4. The CICS TG Java classes return
Page 359 and 360:
import javax.servlet.http.HttpServl
Page 361 and 362:
public void init(ServletConfig sc)
Page 363 and 364:
We also use the mechanism for passi
Page 365 and 366:
The next section of code deals with
Page 367 and 368:
The results page outputs the COMMAR
Page 369 and 370:
Figure B-14 CTGTesterECI Web deploy
Page 371 and 372:
Figure B-16 CTGTesterECIWeb propert
Page 373 and 374:
The CTGTesterCCI application The CT
Page 375 and 376:
As an alternative to using Applicat
Page 377 and 378:
public class CTGTesterCCIServlet ex
Page 379 and 380:
public void processRequest(HttpServ
Page 381 and 382:
encoded string can be obtained by i
Page 383 and 384:
package itso.cics.eci.j2ee.testercc
Page 385 and 386:
The other method in our servlet is
Page 387 and 388:
public ResultsBean execute( String
Page 389 and 390:
create a record for use jsr = new J
Page 391 and 392:
try { eciConn = (Connection) cf.get
Page 393 and 394:
set CCI trace switch (trace) { case
Page 395 and 396:
The page then includes our common J
Page 397 and 398:
Figure B-46 CTGTesterCCI Web deploy
Page 399 and 400:
WEB-INF, right-click ibm-web-bnd.xm
Page 401 and 402:
Figure B-50 CTGTesterCCI bean trans
Page 403 and 404:
To show what the resource reference
Page 405 and 406:
specifies. The href attribute point
Page 407 and 408:
Appendix C. Additional material Thi
Page 409 and 410:
Importing CTGTesterECI into WebSphe
Page 411 and 412:
The CTGTesterECIWeb application sho
Page 413 and 414:
Figure C-5 WebSphere Studio server
Page 415 and 416:
4. Expand CTGTesterCCIEJB -> ejbMod
Page 417 and 418:
Figure C-9 WebSphere Studio Classpa
Page 419 and 420:
In order to flow a request to CICS,
Page 421 and 422:
Figure C-13 Server configuration wi
Page 423 and 424:
Abbreviations and acronyms AOR appl
Page 425 and 426:
Related publications IBM Redbooks O
Page 427 and 428:
IBM Redbooks collections Redbooks a
Page 429 and 430:
Index Symbols %%CLIENT%% 274, 280,
Page 431 and 432:
deploying to WebSphere for Windows
Page 433 and 434:
link user ID 100, 277 Linux, CICS T
Page 435 and 436:
TRACEBUFFLOC variable, WebSphere fo
Page 437:
(0.5” spine) 0.475”0.875” 250
show all

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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?