Use this page to provide the attributes for an enterprise server (MFES).
For more information about the configurable attributes of servers, see the chapter Configuration in your Configuration and Administration Guide.
Shows the name of the server.
Specify the network address used by the server to accept incoming client requests. The format is:
protocol:ip-address:port
where:
If this network address is not unique in the repository, this might cause enterprise server startup problems.
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. The default is %USERPROFILE%\Documents\Micro Focus User\Enterprise Developer\WORKAREA\es-name/var/mfcobol/es/es-name (where es-name is the name of the enterprise server).
If you specify a directory in this field, that directory must exist; Enterprise Server does not create it for you.
Choose whether this Enterprise Server is to run 32-bit or 64-bit applications.
A 32-bit working mode server can run only 32-bit applications. A 64-bit working mode server can run only 64-bit applications.
You cannot change the working mode of the server once it has been created; you can however, change the mode when you copy or import a server.
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.
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.
Specify the number of service execution processes that are to be started at server initialization.
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.
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.
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.
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.
Specify the number of licenses this enterprise server requires.
Check this to indicate that the auxiliary trace and dump files are to be deleted when the server starts.
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
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.
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.
Check this to indicate that this server is an MSS-enabled server, that is, a server that can run CICS applications.
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.
Check this to indicate that the server is to trace its task control component.
Check this to indicate that the server is to trace its storage control component.
Check this to indicate that the server is to trace its table management component.
Check this to indicate that the server is to trace its application container component.
Check this to indicate that the server is to trace its request handler component.
Check this to indicate that the server is to trace its resource manager interface component.
Check this to indicate that the server is to trace its communications component.
Check this to indicate that the server is to trace the CICS API calls made by a CICS application.
Check this to indicate that the server is to trace user and system exits.
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.
Specify a text description of the server, for example, its purpose and owner. Optional.
Click this to add the new server to the Directory Server repository.
Click this to return to the previous page.