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

More documents

Recommendations

Info

Figure 41. CICS Internet Gateway for AIX: Sample User Interface 9.3 OLTP and the Web 136 CICS for AIX as the Transaction Server The processing that takes place on the Web differs in a number of ways from the processing in a typical OLTP environment. It is important to understand the differences between these two types of processing so that the applications you provide are suitable or have adequate recovery processing, for example. The Web is designed to allow you to easily locate and read documents and other information that might be located on a system anywhere on the Internet. OLTP systems are designed to provide a highly reliable means to read and update
9.3.1 Higher User Expectation 9.3.2 User Interface centrally managed databases on which enterprises depend for their daily operation. There are, however, some important similarities between Web servers and traditional transaction monitors: • Both use standard data streams between the client and server—HTTP and HTML for Web servers or IBM 3270 and DEC VT series for OLTP, for example. • Both schedule and process short repetitive pieces of work on behalf of many users accessing shared data. • In both cases, the application runs on the server, and the client is dedicated to presentation. As the Web is used to access traditional OLTP applications, the challenge is to combine the ease of use and flexibility of the Web with the robustness of the traditional OLTP environment. When you use the Web, you are typically searching for information. You might be looking for a specific piece of information, or just looking to see what is there. If you select a hypertext link, and it is not available, or the content of the link is not useful, you simply look elsewhere for something that better meets your needs. When using an OLTP system, you are normally carrying out specific functions required to perform tasks that are part of your job. If a particular function does not work, you cannot successfully complete a task that is part of your job. Clearly, the OLTP user has a much higher level of expectation about the consistency of system behavior and its reliability. Therefore when you design network and server systems, make sure that your systems are as reliable and consistent as possible. Web browsers provide a GUI that is easy to use and intuitive. You can display documents that are both large and small. If the document is larger than the current size of your Web browser window, you can easily scroll backward and forward through the document. OLTP systems often use character-based, fixed-function display terminals. The user interface is typically optimized for efficient use by experienced users. Screen layouts are constrained by the number of rows and columns that the terminal can display. Where more data must be displayed than can fit on a screen, you may have to issue additional transactions to retrieve and display the additional data. Although a user can access the existing CICS application with the original user interface, without any change through the CICS Internet Gateway for AIX, you should think about whether the original user interface is friendly or not when viewed by a Web user. You should also consider the impact of increased delays in providing transaction input such as the result of additional delays due to the Web browser or network. Accordingly, you may have to optimize the user interface, taking as much advantage as possible from the Web browsers. Chapter 9. Accessing CICS from the Web 137
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:
Page 96 and 97:
6.1.2 Encina Toolkit Server Core 6.
Page 98 and 99:
Page 100 and 101:
is also necessary to use native AIX
Page 102 and 103:
Page 104 and 105: 7.1 X/Open XA Interface 7.1.1 X/Ope
Page 106 and 107: 88 CICS for AIX as the Transaction
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 138 and 139: Figure 37. CICS SM Component Distri
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 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 194 and 195: How Customers Can Get ITSO Redbooks
Page 198 and 199: design. The process of composing a
Page 200 and 201: A year later ISC gave SQL formal in
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

Create successful ePaper yourself

Delete template?

Save as template?