Transcript CTG at DIB

CTG at DIB
CICS Transaction Gateway at Dexia Insurance Belgium
GSE CICS-DB2 11/10/2007
Rainbow ICT Services
Peter Christensen
CTG at DIB
• Mainframe environment
–
–
–
–
–
–
–
• Decentral on INTEL
–
–
–
–
–
Z/OS 1.7
DB2 7.0
CICS TS 2.3
MQ Series
RACF
OPC
3 LPAR:
Virtualization: VMWARE
CITRIX
WAS 5.1
JAVA 1.4 & 1.6
CTG 6.0.1
LPAR
Mips
ENV DB2 CICS
PROD
505
1
3
8
DVLP
TEST
380
5
13
55
INST
36
1
1
6
CTG at DIB
•
CICS Transaction Gateway
IBM CICS Transaction Gateway provides secure, easy access from Web browsers and network computers
to CICS applications, using standard Internet protocols in a range of configurations.
• Gateway Deamon
Supports communication between client (eg Browser) and CTG server 
manages connections = connection thread(s)
• Client deamon
Supports communication between CTG server and CICS Servers  manages
ECI-requests = worker thread(s)
CTG at DIB
•
Platforms
– Z/OS Sysplex
– LINUX
– UNIX
– WINDOWS
•
Connection protocols
– TCPIP (CICS 2.1)
– TCP62
– SNA
CTG at DIB
•
ECI (External call interface)
– Calling a CICS program in a CICS server
– Commarea based (EXEC CICS LINK)
•
EPI (External presentation interface)
– Installs and deletes virtual IBM 3270 terminals
– Supports ATI (Automatic Transaction Initiation)
•
ESI (External security interface)
– Accesses userid data in CICS External Security Manager
– Setting default security management
CTG at DIB
•
ECI request
– Commarea
– LUW control
– LUW Identifier
– Programname
– Userid
– Password
– CICS server
– Tpnname
– Tranname
Java Coding:
String IPadr = "tcp://" + IPaddress;
jg = new JavaGateway(IPadr,port);
ECIRequest req = new CIRequest(ECIRequest.ECI_SYNC,
connectionID,
uid,
pwd,
programma,
transid,
commarea,
80,
ECIRequest.ECI_NO_EXTEND,
ECIRequest.ECI_LUW_NEW);
jg.flow(req);
jg.close();
CTG at DIB
•
Programming Languages
– JAVA
– JCA (J2EE Communication Architecture)
– C , C++ and COBOL
– COM
CTG at DIB
Applications: Local Mode – Remote Mode
CTG at DIB
•
Gateway Configuration
CTG at DIB
•
Client Configuration
CTG at DIB
•
CICS TCPIP Service Definition
OBJECT CHARACTERISTICS
CEDA View TCpipservice( TXPA
TCpipservice
: TXPA
GROup
: DVVTCPPA
DEscription
:
Urm
:
POrtnumber
: 03611
STatus
: Open
PROtocol
: Eci
TRansaction
: CIEP
Backlog
: 00100
TSqprefix
:
Ipaddress
: ANY
SOcketclose
: No
SECURITY
SSl
: No
Certificate
:
(Mixed Case)
PRIvacy
:
AUthenticate
:
ATtachsec
: Verify
DNS CONNECTION BALANCING
DNsgroup
:
GRPcritical
: No
•
CICS RELEASE = 0630
)
1-65535
Open | Closed
Iiop | Http | Eci
0-32767
No | 0-240000 (HHMMSS)
Yes | No | Clientauth
Notsupported | Required | Supported
No | Basic | Certificate | AUTORegister
| AUTOMatic | ASserted
Local | Verify
No | Yes
CTG at DIB
Scheme for Production
DIBIS Client
- DIBIS Appl (CITRIX)
- IE with DC4ASF (WAS)
Z/OS 1.7
dvvlapmf.dvsys.dv.be
DVSPCTGXX
NLB-Cluster
Heartbeat
TCP/IP
DVSPCTG01
Host1
(Server – Livingstone)
Port#: 2006
DVCTGPRD
CICSPA
(C-NAME to DVSPCTGXX)
172.25.20.20
Port#: 3611
DVSPCTG02
Host2
Heartbeat
(VMware – Livingstone)
Port#: 2006
Claint:
Heartbeat
- IE with E-mail (WAS)
CICSP2
Task Server
Port#: 3392
CTG at DIB
NUMBERS:
•
•
•
•
PROD
PROD office hours
DVLP/TEST
Stress/Performance
215.000/day
25.000/hour
70.000/day
120.000/hour
•
AVERAGE RESP END-TO-END
– Includes CIEP + Mirror Trans
– minimal functionality in CICS
– LAN
13 ms
• CPU on INTEL-server
• STORAGE on INTEL-SEREVR
< 5%
< 400 MB
CTG at DIB
•
MS Network Load Balancing
– Advantages
• No additional cost
• Simple setup – dynamic configuration
• Allows by server failure to route IP-traffic to other servers defined in
the cluster
– Disadvantages
• Is limited to detection of unavailability of IP-stack  Application
failure is not detected
– Heartbeat
• Checks on a timely base the availability of application, via callout
infrastructure intervention on NLB cluster can be triggered
– Management: NLB Manager
• Activated via command prompt
• Create Cluster
• Add – Remove hosts
• Start – Stop – DrainStop hosts
• Activate logging
CTG at DIB
•
MS Network Load Balancing (continued)
CTG at DIB
•
Evaluation at DIB
– Availability: High
– Scalable: High
– Implementation: Easy
 no incidents in 2 years
 limits are not met yet
 basic architecture
 simple installation
 simple configuration
 No operational issues
•
TO DO
– Implemenation of SSL
– Reporting
– Performance – Tracing
•
References
– IBM CICS Transaction Gateway version 6.0.1