Bookshelf Home | Contents | Index | Search | PDF | ![]() ![]() ![]() ![]() |
Implementing Siebel eBusiness Applications on DB2 UDB for OS/390 and z/OS > Preparing for Implementation on the DB2 Host >
System Connectivity Architecture
The Siebel eBusiness Applications communicate with IBM DB2 Universal Database for OS/390 and z/OS (running on zSeries servers) through IBM DB2 Connect middleware.
The two editions of DB2 Connect are:
- DB2 Connect Enterprise Edition (EE). This edition is installed on a midtier server such as a Siebel Server machine. Siebel Server communicates with this middleware to support database connectivity for users running Siebel Web Client. Optionally, this edition can support database connectivity for multiple individual users running Siebel Dedicated Web Client.
- DB2 Connect Personal Edition (PE). This edition is installed on a user's local workstation. It supports database connectivity for an individual user running Siebel Dedicated Web Client on a workstation.
DB2 Connect EE can reside on common connection gateway machines. (Do not confuse the concept of a gateway machine with Siebel Gateway.) DB2 Connect EE is used to broker the connections to DB2 for multiple database clients (Siebel Servers or Dedicated Web Clients). See Table 4 for DB2 Connect configurations.
NOTE: If you deploy DB2 Connect EE with Siebel Dedicated Web Client, you must also install a DB2 Connect run-time component on your Siebel Dedicated Web Client machines.
Siebel Servers and Siebel Dedicated Web Clients communicate with DB2 Connect through TCP/IP. (DB2 Connect also supports communication through SNA, but SNA currently does not support connection pooling. For this reason, it is recommended that you use TCP/IP.)
Bookshelf Home | Contents | Index | Search | PDF | ![]() ![]() ![]() ![]() |
Implementing Siebel eBusiness Applications on DB2 UDB for OS/390 and z/OS Published: 18 April 2003 |