Addressing OLTP Solutions with CICS: The Transaction Server ... - Ibm

More documents

Recommendations

Info

Figure 37. CICS SM Component Distribution 120 CICS for AIX as the Transaction Server Management node: The GUI, SMappl, WLMAppl-SMappl, global cache, and EIB are located on the dedicated management node. DSOM is installed on this node to facilitate communication between the GUI and the SMappl as well as between the WLMAppl and the SMappl. Managed node: Each of the managed nodes contains systems to be managed, DSOM, and a resource controller. Additionally, one of the managed nodes contains a workload cache manager and a workload management client. These workload management components are present because one of the managed systems is using workload management for dynamic transaction routing and DPL requests to the other managed systems. The management node that does not have the workload management components installed has no need to perform workload management. DSOM is installed on the managed nodes to facilitate communication between the resource controllers and the SMappl. The resource controller communicates with the agent transaction in the managed system through UNIX sockets and a datagram protocol. The workload management components communicate with each other through UNIX sockets and a datagram protocol. Communication between the workload cache manager and the WLMAppl on the management node is also achieved through UNIX sockets and a datagram protocol over TCP/IP as the communication is now intermachine.
Client node: The client node contains a CICS client, a workload management client, a local cache, and a workload management cache manager. DSOM is not installed on the client node as there is no need to communicate with the other CICS SM components that use DSOM, namely, the GUI, SMappl, and WLMAppl-SMappl interface. The workload management client is called by the CICS client to route the client request. It does this based on information held in the local cache. The workload management cache manager manages the local cache, updating it when updates are received from the WLMAppl or requesting data from the WLMAppl when a routing request is made for a program or transaction that is not present in the local cache. 8.5 Workload Management Considerations 8.5.1 Maximizing the Benefit In this section we look more closely at three aspects of workload management. First we examine the sort of configurations that are required to improve the value that can be obtained from introducing workload management. Second we look the reference system that is used with workload management in order to rank the size of different processors in a CICS configuration. Third we look at the workload management algorithm. Workload management is most effective when there are a number of CICS systems from which to choose. There is little point in implementing workload management with a single CICS system, unless you are planning to subsequently expand, as there is only the one system to which to route. Static routing would be just as effective in such a case. 8.5.1.1 Combining Resources The ideal approach for workload management is to have one (or more) applications available with each CICS system on its own machine. It may be that you choose to adopt this approach for only your most critical applications. There could be significant value, however, in combining several less obvious candidates for workload management and the machines on which they run. The aim is to provide one common type of CICS system that contains all of the resources required to run each of the applications. This common CICS system is then reproduced on multiple systems. Workload management is used to distribute the incoming work over the systems that can process the work. Such an approach can provide benefits to each of the applications as the combined machine resources are now available for the applications. Such an environment cannot proceed without the use of effective workload management. The availability of CICS SM workload management now enables you to adapt in the distributed transaction processing world. Consider the case shown in Figure 38 on page 122. Chapter 8. Using CICS System Manager for AIX 121
Page 1:
Addressing OLTP Solutions with CICS
Page 4 and 5:
Take Note! Before using this inform
Page 6 and 7:
iv CICS for AIX as the Transaction
Page 8 and 9:
9.4 Security Issues on the Internet
Page 10 and 11:
viii CICS for AIX as the Transactio
Page 12 and 13:
x CICS for AIX as the Transaction S
Page 14 and 15:
xii CICS for AIX as the Transaction
Page 16 and 17:
The Team That Wrote This Redbook xi
Page 18 and 19:
xvi CICS for AIX as the Transaction
Page 20 and 21:
2 CICS for AIX as the Transaction S
Page 22 and 23:
1.2 Complex OLTP Business Environme
Page 24 and 25:
Figure 2. OLTP Complex for XYZ Insu
Page 26 and 27:
By using common application program
Page 28 and 29:
1.5 OLTP Market 10 CICS for AIX as
Page 30 and 31:
Figure 5. OLTP Market Segmentation
Page 32 and 33:
14 CICS for AIX as the Transaction
Page 34 and 35:
2.1 IBM Software Servers 2.1.1 Lotu
Page 36 and 37:
2.2.1 CICS Clients V1.1.0 A Transac
Page 38 and 39:
2.2.4 CICS Internet Gateway for AIX
Page 40 and 41:
3.1 Services CICS for AIX is a very
Page 42 and 43:
3.1.2 CICS API 24 CICS for AIX as t
Page 44 and 45:
3.1.3.1 Terminal Users and CICS Reg
Page 46 and 47:
3.2 Implementation 3.2.1 Components
Page 48 and 49:
3.2.2 Processes 3.2.1.3 Application
Page 50 and 51:
3.3.1 DCE RPC 3.3.2 TCP/IP 32 CICS
Page 52 and 53:
Figure 9. Interconnection Using Enc
Page 54 and 55:
connect to a PPC Gateway server mac
Page 56 and 57:
Figure 12. Interconnection Using TC
Page 58 and 59:
3.4.3 Configuration 3.4.4 Managing
Page 60 and 61:
3.4.6 Intersystem Communication CIC
Page 62 and 63:
3.4.8 Data Location 44 CICS for AIX
Page 64 and 65:
3.4.11 Operations plan to cope with
Page 66 and 67:
3.5 Summary 48 CICS for AIX as the
Page 68 and 69:
Figure 13. Application Server Model
Page 70 and 71:
4.2.1 CICS External Call Interface
Page 72 and 73:
By means of mapping files, you can
Page 74 and 75:
4.3 Versions 56 CICS for AIX as the
Page 76 and 77:
4.4 Sample Network Configurations 4
Page 78 and 79:
4.5.1 CICS Client for OS/2 60 CICS
Page 80 and 81:
4.5.2 CICS Client for DOS 62 CICS f
Page 82 and 83:
4.5.5 CICS Client for AIX CICS Clie
Page 84 and 85:
Page 86 and 87:
4.6 Summary 68 CICS for AIX as the
Page 88 and 89: 5.1.1 DCE Threads 5.1.2 Remote Proc
Page 90 and 91: The GDS is based on the CCITT X.500
Page 92 and 93: egion or server it is looking for.
Page 94 and 95: 76 CICS for AIX as the Transaction
Page 96 and 97: 6.1.2 Encina Toolkit Server Core 6.
Page 100 and 101: is also necessary to use native AIX
Page 104 and 105: 7.1 X/Open XA Interface 7.1.1 X/Ope
Page 108 and 109: Communication between the transacti
Page 112 and 113: 7.2.2 Single-Phase and Two-Phase co
Page 116 and 117: Figure 28. Switching Access among D
Page 120 and 121: Figure 30. CICS Access to Remote DB
Page 122 and 123: emote DRDA database. Information ab
Page 124 and 125: As the COMMAREA has an allowable ma
Page 126 and 127: 7.5 Summary 108 CICS for AIX as the
Page 130 and 131: 8.2 Workload Management 112 CICS fo
Page 134 and 135: 8.4.2 System Management Application
Page 136 and 137: Figure 36. The CICS SM GUI 8.4.6 Di
Page 140 and 141: Figure 38. Combining Resources 122
Page 142 and 143: 8.5.2 The Reference System 124 CICS
Page 146 and 147: 8.6 Planning Considerations for CIC
Page 152 and 153: 9.1 Some Terminology 9.2 Services 1
Page 154 and 155: Figure 41. CICS Internet Gateway fo
Page 156 and 157: 9.3.3 Data Integrity The Web was or
Page 158 and 159: 9.3.5 High Availability The drawbac
Page 160 and 161: or employee records, eavesdropping
Page 164 and 165: • Type, size, and quantity of rec
Page 166 and 167: 10.3.3 Writing ECI and EPI Applicat
Page 168 and 169: The ANIMATOR debugging tool enables
Page 172 and 173: 10.8 Summary 154 CICS for AIX as th
Page 176 and 177: 11.1 The Big Picture 158 CICS for A
Page 178 and 179: 11.2 User Access 160 CICS for AIX a
Page 180 and 181: Figure 44. Access to Various DB2 Da
Page 184 and 185: takes place over TCP/IP or SNA comm
Page 186 and 187: provide greater protection in the u
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
How Customers Can Get ITSO Redbooks
Page 196 and 197:
Page 198 and 199:
design. The process of composing a
Page 200 and 201:
A year later ISC gave SQL formal in
Page 202 and 203:
Page 204 and 205:
designing efficient applications 15
Page 206:
IBML ® Printed in U.S.A. SG24-4752
show all

Addressing OLTP Solutions with CICS: The Transaction Server ... - Ibm

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

Delete template?

Save as template?