10.1.1 Single Connection and Multiple Links
As shown in the following figure, one Tuxedo client calls a remote service, which maps to a CICS DPL program. The DPL program runs in two CICS regions – CICSA and CICSB. Meanwhile, two GWSNAX/CRM pairs are configured to avoid any single point of failure. Each CRM connects to both CICS regions.
Figure 10-1 Outbound Call (Single Connection and Multiple Links)
In this scenario, the load balancing / failover can be accomplished via following four paths:
toupclt -> SNAX1 -> CRM12205 -> CICSA -> TOUPDPLS
toupclt -> SNAX1 -> CRM12205 -> CICSB -> TOUPDPLS
toupclt -> SNAX2 -> CRM12206 -> CICSA -> TOUPDPLS
toupclt -> SNAX2 -> CRM12206 -> CICSB -> TOUPDPLSThe following table lists all the configurations required for making outbound calls of single connection and multiple links.
Table 10-1 Configurations for Single Connection and Multiple Links (Outbound)
| Machine | Component | Resource | Resource |
|---|---|---|---|
TUXEDO
|
UBBCONFIG |
*GROUPS
|
2 groups for 2 GWSNAX servers
|
*SERVERS
|
2 GWADM/GWSNAX pairs
|
||
DMCONFIG |
*DM_LOCAL
|
2 local domains: SNAX1, SNAX2 |
|
*DM_REMOTE
|
4 remote domains: CICSA1, CICSB1, CICSA2, CICSB2 |
||
*DM_SNACRM
|
2 CRMs: CRM1, CRM2 |
||
*DM_SNALINKS
|
4 LINKs: CICSA1, CICSB2, CICSA2, CICSB2 |
||
*DM_IMPORT
|
4 remote homonymous services as 2X2 LACCESSPOINT /RACCESSPOINT combinations: DPLS | ||
| MAINFRAME | VTAM list | Major node | 2 APPC LUs (for two CRMs) |
| CICSA | Resource | 2 CONNECTION/SESSION pairs for two LUs
|
|
| 1 PROGRAM for DPLS | |||
| CICSB | Resource | 2 CONNECTION/SESSION pairs for two LUs
|
|
| 1 PROGRAM for DPLS |