The Entire Net-Work service, Kernels, and clients use UNIX resources. This document describes the use of TCP/IP sockets, threads, and semaphores by the various Entire Net-Work components in UNIX environments.
Entire Net-Work system resources are allocated dynamically, as they are needed, not when the products are started. However, you may encounter times when Kernels are so heavily used that they cannot accept new connections, incoming clients, or System Management Hub (SMH) inquiries. This can also happen when other applications on your system are used heavily.
UNIX systems are sometimes configured with specific platform resource defaults. You must take into consideration how many resources the individual applications require and configure their systems accordingly. Bear in mind:
Sockets that are not closed properly (for example, when applications crash) may linger in the system for a while and are not available for some time. We recommend that you set the socket linger time to a lower value.
Consider the system resources required when a client application, the Software AG Directory Server, SMH, and Kernels run on the same system at the same time as other applications you have installed. You may find it beneficial to run them on separate systems.
This document provides information on Entire Net-Work component resource usage to help you do this:
A simple client uses the following system resources:
Three semaphores and one thread are used for data protection.
One thread, semaphore, and socket are required for each connection made by the client.
If the client needs to retrieve Adabas access information from the Software AG Directory Server, another thread, semaphore, and socket are required temporarily. These are freed immediately after the information is obtained.
Bear in mind that some client applications are complex and may require multiple connections.
Entire Net-Work Kernels use the following system resources:
Fourteen semaphores and seven threads are used for data protection. If the gateway thread count is increased from its default of five, the number of threads required for Kernel data protection is increased accordingly.
Each access (e-business, e-business client, classic Entire Net-Work, and SMH) performed by the Kernel requires a thread, semaphore, and socket.
Each incoming or outgoing connection (e-business and classic Entire Net-Work) performed by the Kernel requires a thread, semaphore, and socket, during the life of the connection.
Each incoming client requires a thread, semaphore, and socket during the life of the client.
If the Kernel needs to retrieve network information from the Software AG Directory Server, another thread, semaphore, and socket are required temporarily. These are freed immediately after the information is obtained.
If SMH needs to retrieve Kernel information from the Software AG Directory Server, another thread, semaphore, and socket are required temporarily. These are freed immediately after the information is obtained.
Software AG Directory Server clients use the following system resources:
Six semaphores, a socket, and two threads are needed for Directory Server processing.
Directory Server allocates a semaphore, socket, and two threads for each incoming connection, for the life of the connection.
The following table summarizes use of system resources by the various Entire Net-Work components.
| Component | System Resource Requirements | Duration of Requirement | ||
|---|---|---|---|---|
| Sockets | Threads | Semaphores | ||
| Client data protection | 0 | 1 | 3 | Life of the client. |
| Client connection (each connection) | 1 | 1 | 1 | Life of the client. |
| Client retrieval of Adabas access information from the Directory Server | 1 | 1 | 1 | Temporarily; resources freed after information is retrieved. |
| Kernel data protection | 0 | 7 | 14 | Life of the Kernel. |
| Kernel access (e-business, e-business client, classic Entire Net-Work, and SMH) | 1 | 1 | 1 | Life of the access attempt. |
| Kernel incoming and outgoing connection (e-business and classic Entire Net-Work) | 1 | 1 | 1 | Life of the connection. |
| Kernel incoming client | 1 | 1 | 1 | Life of the client. |
| Kernel retrieval of network information from the Directory Server | 1 | 1 | 1 | Temporarily; resources freed after information is retrieved. |
| SMH retrieval of Kernel information from the Directory Server | 1 | 1 | 1 | Temporarily; resources freed after information is retrieved. |
| Directory Server base processing | 1 | 2 | 6 | Life of Directory Server. |
| Directory Server incoming connection handling | 1 | 2 | 1 | Life of the connection. |
