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

More documents

Recommendations

Info

or employee records, eavesdropping must be prevented through appropriate cryptographic techniques. The authorization protocols supported by the Web are still evolving, and there is no widely accepted implementation. Two security packages have been around for a while: Pretty Good Privacy and Kerberos. Two relatively new transaction security standards are likely to become integral parts of a future integrated security solution for the Web: secure HTTP and secure sockets. See the following URLs: http://www.netscape.com/newsref/std/SSL.html http://www.eit.com/projects/s-http/index.html http://www.ofs.org/www/dceweb/DCE-Web-Home-Page.html http://hoohoo.ncsa.uiuc.edu/doce/PEMPGP.html http://www.ibm.com/Security/glossary.html The IBM Internet Connection Secured Network Gateway (SNG) is an effective tool to protect your network from unauthorized access. It is based on research at IBM′s Yorktown Research Laboratory and experience running large networks for more than eight years. SNG supports all of the implementations above. The IBM Internet Connection Secure Servers and the Secure WebExplorer browsers ensure the validity of the parties in a transaction and keep communications private. 9.5 Planning Considerations for the CICS Internet Gateway for AIX 9.5.1 Preparation A presence on the Internet is intended to give competive advantage to an enterprise, not compromise its security. Therefore you must carefully plan your approach to making applications available from the Internet and address a few configuration issues for implementing the CICS Internet Gateway for AIX. Before implementing the CICS Internet Gateway for AIX, become familiar with what the Web is and is not and understand what the differences between OLTP and the Web mean for your applications (see 9.3, “OLTP and the Web” on page 136). 9.5.2 Choosing Your Applications 9.5.3 Accessing Sensitive Data 142 CICS for AIX as the Transaction Server Decide which applications and data are suitable for use on the Internet. The applications should be informative and helpful. It may be neccesary to redevelop applications, possibly focusing on the user interface. The typical user is likely to be far less computer literate than the employees of the your enterprise who were previously using the application Determine whether sensitive data in the CICS system in which the Internet-accessible applications are running can be accessed. You may want to provide an isolated system whose sole purpose is to run the Internet-accessible applications.
9.5.4 Availability 9.5.5 Operations 9.5.6 Capacity Any Internet-accessible applications should be highly available so that they can be accessed by anyone at any time. A service that is unavailable does not create a good impression for your enterprise. Ensure that the operation of any new CICS service that is created to support Internet-accessible applications is integrated into existing operations procedures. Regularly monitor the level of use of Web-accessible applications to ensure that there is sufficient processing and network capacity to cope with the volume of work. If you are using the application to collect marketing intelligence, for example, users may not be patient enough to wait for responses if the application is slow because of insufficient capacity of either the Web or CICS server. The objective of being connected to the Web has been lost for the enterprise. 9.5.7 Performance Considerations 9.6 Summary The CICS Internet Gateway for AIX runs as a single process CICS EPI client (see Chapter 4, “Using CICS Clients” on page 49) to establish a terminal connection to the CICS for AIX region. The number of concurrent active connections could be constrained by: • Web server limits on the number of concurrent active users or CGI scripts • CICS Internet Gateway for AIX limits. There is a limit of 240 concurrently active users awaiting a response. • CICS Client limits on the number of active CICS terminals per process. An Internet user is the same as a terminal in this case. • Operating system limits on the number of threads per process. Each user uses up to two threads. 9.5.7.1 Restrictions and Limitations Be aware that the CICS Internet Gateway for AIX does not support ATI requests for terminals. It uses dynamic terminals and so cannot support this function. Establishing a presence on the Internet can be a difficult and complex process. This is a new area of technology where skills are still scarce. One critical success factor in establishing a presence is the creation of the necessary applications that Internet users will access. The CICS Internet Gateway for AIX enables an enterprise to make existing CICS for AIX applications acessible to Internet users, typically without modification. You may want to modify those applications to restrict the options or functions. That is a business decision, however. Because existing CICS skills can be used to develop new applications, application development is rapid and inexpensive. OLTP and the Web are different forms of processing. There are similarities, but there are also significant differences in the type of conversation and in recovery and security considerations. It is important that you understand the differences and act accordingly. Chapter 9. Accessing CICS from the Web 143
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:
Page 108 and 109:
Communication between the transacti
Page 110 and 111: 92 CICS for AIX as the Transaction
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 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 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?