Before you install DB2, decide what system configuration you need.
This section shows diagrams of the most common configurations that use DB2. Each diagram shows the products or components that are required for each system in the network (excluding operating system and communication requirements), and the approximate amount of memory required for such a configuration.
If you want to access data across a LAN from a remote database server, use the configuration shown in Figure 7. This diagram shows a DB2 Universal Database server and various clients connected to this server to access data. You must install the appropriate DB2 Client Application Enabler on each client.
Clients connect to a DB2 Universal Database server using one of the supported protocols: APPC, IPX/SPX, or TCP/IP.
Figure 7. Configuration for Accessing DB2 Servers on the LAN
|
The amount of memory you need on your server depends on the number of concurrent users you will have, and the size of the databases. The diagram shows a scenario of five concurrent clients connected to the server with a simple application using static SQL. For the server, it is recommended that a minimum of 64 MB of memory be installed to accommodate five concurrent clients. We suggest that you have a minimum of 96 MB of memory to accommodate 25 concurrent clients and 128 MB of memory for 50 concurrent clients. (If you have a more complex application environment, your server may require significantly more memory.) Use these guidelines to determine the amount of memory necessary in your environment.
An administration client is shown in the diagram. This client can be run on OS/2 or Windows 32-bit operating systems and can be used to manage DB2 servers on your network. Typically, 30 MB of memory is required to run all the graphical tools that you will need for an administration client.
For the DB2 clients in your environment, the amount of memory required depends on the database applications you are running.
If you want to access databases on both your local LAN and on host systems such as OS/390, OS/400, MVS, VM, or VSE, use the configuration shown in Figure 8. You will need to install the DB2 Connect Support option of DB2 Enterprise Edition.
DB2 client applications connect to DB2 Enterprise Edition or DB2 Workgroup Edition servers using one of the supported protocols: APPC, IPX/SPX, or TCP/IP. DB2 then connects to the appropriate host database management system using DRDA over either APPC or TCP/IP.
Figure 8. Configuration for Accessing LAN and Host Data
 |
The amount of memory you need on your server depends on the number of concurrent users you will have, and the size of the databases. The diagram shows a scenario of five concurrent clients connected to the server with a simple application using static SQL. For the server, it is recommended that a minimum of 64 MB of memory be installed to accommodate five concurrent clients. We suggest that you have a minimum of 96 MB of memory to accommodate 25 concurrent clients and 128 MB of memory for 50 concurrent clients. (If you have a more complex application environment, your server may require significantly more memory.) Use these guidelines to determine the amount of memory necessary in your environment.
An administration client is shown in the diagram. This client can be on an OS/2 or Windows 32-bit operating systems and can be used to manage DB2 servers on your network. Typically, 30 MB of memory is required to run all the graphical tools you will need for an administration client.
For the DB2 clients in your environment, the amount of memory required depends on the database applications you are running.
If you want Internet clients to use Web browsers to access data in databases on both LAN and host-based DB2 servers, use the configuration shown in Figure 5 or Figure 6.
Follow the guidelines in Configuration for Accessing DB2 Servers on the LAN and Configuration for Accessing LAN and Host Data to determine the memory required on your DB2 server and administration client.