Add Server - Details

Add Application Application Container Auxiliary Trace Active Back Cold Start Diagnostics File Communications Configuration Information Description Dump on System Abend Exit Local Trace Size Mainframe Transaction Option Maximum Diagnostics File Size Name Requested Licenses | Request Handler RM Interface Server Address Service Execution Processes Shared Memory Cushion Shared Memory Pages Show Local Console Startup Options Storage Control System Directory Table Management Task Control Trace Flags Trace Table Size

Add Server - Details

  Use this page to provide the attributes for an enterprise server (MFES).

  Note: For more information about the configurable attributes of servers, see the chapter Configuration in your Configuration and Administration Guide.

  Top

Name

  Shows the name of the server.

  Top

Server Address

  Specify the network address used by the server to accept incoming client requests. The format is:

  protocol:ip-address:port

  where:

  - protocol is tcp.
  - ip-address is either the text host name or IP address of the server listener. An asterisk (*) indicates that the address is dynamically assigned for the enterprise server when it starts.
  - port is the port value. An asterisk (*) indicates that the port is dynamically assigned for the enterprise server when it starts.

  If this network address is not unique in the repository, this might cause enterprise server startup problems.

  Top

System Directory

  Specify the location for system work files output by the Enterprise Server, such as the console log, and trace and dump diagnostics files. This directory cannot be shared between Enterprise Servers. On Windows the default is C:\Documents and Settings\user-ID\My Documents\Micro Focus\Net Express 5.0\WORKAREA\es-name\console.log (where user-ID is the user account that is running Enterprise Server, and es-name is the name of the enterprise server). On UNIX the default is /var/mfcobol/es es-name.

  If you specify a directory in this field, that directory must exist; Enterprise Server does not create it for you.

  Note: On Windows, if you are running the Directory Server as a service that logs on as the Local System account (LocalService), any Enterprise Server that it starts will also run under that account. Hence, the default location of the System Directory will be C:\Documents and Settings\LocalService\My Documents\Micro Focus\Net Express 5.0\WORKAREA\es-name. By default, Windows hides the LocalService subdirectory of Documents and Settings. In order to view this directory, you must configure your Windows Explorer so that: Show hidden files and folders is set, and Hide protected operating system files is not set.

  Top

Startup Options

  Use these fields to specify the server configuration you want when the server first starts up. Any changes you make to these fields while a server is running do not take effect until the next time you start the server.

  Top

Shared Memory Pages

  Specify the number of shared pages in memory to be reserved for all the processes that run in the Directory Server. Each page is 4KB long.

  Top

Service Execution Processes

  Specify the number of service execution processes that are to be started at server initialization.

  Top

Shared Memory Cushion

  Specify the number of 4KB pages that should be reserved from the shared memory pages to allow the server to continue processing when the shared memory allocation is too small for the operational requirements of the server. The range is 1 through the number of shared memory pages.

  Top

Trace Table Size

  Specify the number of entries the trace buffer can hold before it wraps back to the start. (The trace buffer is also written to disk at this point if you checked Auxiliary Trace Active.) A value of 2 means that there is space for only one entry, and if you checked Auxiliary Trace Active each entry is written straight out to disk. Each entry is 24 bytes long.

  Top

Local Trace Size

  Specify the number of entries the local trace table can hold before it wraps back to the start. A value of 0 (zero) means that no local trace table is allocated. Each service execution process has its own local trace table. Each entry is 24 bytes long.

  Top

Maximum Diagnostics File Size

  Specify the maximum size of the auxiliary trace and dump file in kilobytes. A value of 0 (zero) means that there is no maximum size.

  Top

Requested Licenses

  Specify the number of licenses this enterprise server requires.

  Top

Cold Start Diagnostics File

  Check this to indicate that the auxiliary trace and dump files are to be deleted when the server starts.

  Top

Dump on System Abend

  Check this to indicate that the server should produce a dump if one of its own processes, such as a service execution process, terminates abnormally. The dump information can help you to determine the cause of the abnormal termination

  Top

Auxiliary Trace Active

  Check this to indicate that trace records are to be flushed to disk before the trace table is overwritten. You should do this only if you have adequate disk space available, since the file can become very big very quickly. If you have a high-activity system use this field in conjunction with Maximum Diagnostics File Size to limit the disk usage. Writing out to a file also degrades performance.

  Top

Show Local Console

  Check this if you want to see a text window containing enterprise server messages while the server is running. the messages are written to a file called console.log, in the directory specified in System Directory. You can see the text window only on the machine running the enterprise server. The system messages are also available on the Enterprise Server Console page.

  Top

Mainframe Transaction Option

  Check this to indicate that this server is an MTO-enabled server, that is, a server that can run CICS applications.

  Top

Trace Flags

  Use these flags to control what information is written to the trace file for this server. Any changes you make to these fields while a server is running take effect immediately.

  Top

Task Control

  Check this to indicate that the server is to trace its task control component.

  Top

Storage Control

  Check this to indicate that the server is to trace its storage control component.

  Top

Table Management

  Check this to indicate that the server is to trace its table management component.

  Top

Application Container

  Check this to indicate that the server is to trace its application container component.

  Top

Request Handler

  Check this to indicate that the server is to trace its request handler component.

  Top

RM Interface

  Check this to indicate that the server is to trace its resource manager interface component.

  Top

Communications

  Check this to indicate that the server is to trace its communications component.

  Top

Application

  Check this to indicate that the server is to trace the CICS API calls made by a CICS application.

  Top

Exit

  Check this to indicate that the server is to trace user and system exits.

  Top

Configuration Information

  Specify textual configuration information that determines the start-up and run-time behavior of the server. Optional. For details of the valid entries, see the section Configuration Information in the chapter Servers in your Configuration and Administration Guide.

  Top

Description

  Specify a text description of the server, for example, its purpose and owner. Optional.

  Top

Add

  Click this to add the new server to the Directory Server repository.

  Top

Back

  Click this to return to the previous page.

  Top