In this section: |
The server uses a series of processes to accomplish various tasks. Some processes have specialized administrative functions, such as workspace management and logging, while others do end-user tasks. System administrators may want to know what processes the server creates and how many of each. The administrator may want this information for machine sizing or simply to know what processes to consider or ignore when a problem occurs.
Note that each operating environment uses operating system-specific commands to view processes. The processes are described generically, not how they would appear in a system listing.
The server workspace is control by a daemon process know as PTH. There is one process per server.
The server has several types of special services. The DFM daemon is used for deferred (DFM) and Scheduler requests. There is one process per server.
The server log (edaprint.log) is now written using a single daemon process. Previous versions wrote to the log independently from the various processes that might write to the log. In very rare and specific cases, the prior methods were problematic, hence, the change to the use of a daemon. As a result, starting a server brings up this additional server log daemon (edaplog).
The server has always had a process that wakes up and checks various states and takes actions. An example of this is stopping agents that are inactive past the idle limit. In the past this process has been part of the Workspace Manager function, but is now a separate daemon that runs independently. As a result, starting a server brings up this additional server check up daemon (edachkup).
The server has several types of listeners. The HTTP daemon is used for requests using the HTTP protocol. There is one process per server.
The server has several types of listeners. The TCP daemon is used for requests using the TCP protocol. There is one process per server.
The server has several types of special services. The FDS daemon (HLISNK) is used for FOCUS Database requests from agent processes. There is one process per server.
The JSCOM daemon is used for requests using Java. There can be more than one process per server.
The actual worker processes for requests are known as agents or tscom3 processes (tscom3 is the actual program name). There is one process per configured agent that is active. Agent processes normally are reused until a recycle point or until they become inactive for a set period. Thus, for a given server, the number of processes associated with agents will change over time.
| iWay Software |