Start Server Confirmation

Description Name Security settings Start processes as | Status Log Type Use Enterprise Server credentials of

Start Server Confirmation

  Use this page to confirm user credentials for starting an enterprise server.

  Top

Type

  Shows the server type. The only type of server you can stop is an MFES server. MFES stands for Micro Focus enterprise server. This is a server type that provides a run-time environment for COBOL programs running as services. MTO in brackets after MFES indicates that the server has Mainframe Transaction Option (MTO) enabled.

  Top

Name

  Shows the name of the server.

  Top

Status Log

  Shows information about the most recent event that occurred on this server, and how long the server has been in its current state.

  Top

Description

  Shows a description of the server.

  Top

Security settings

  This section indicates whether the server is using its own security settings and associated security manager list, or the Default ES Security configuration settings, which can be shared by multiple servers.

  Where it is using its own security settings, the security managers in its security manager list are displayed.

  Top

Start processes as

  This specifies the operating system account under which the enterprise server will run. You can choose to run it as the currently logged-on user (that is, the user account under which Directory Server is running), or you can specify the username and password for an alternative user.

  Top

Use Enterprise Server credentials of

  When an enterprise server starts, it connects to Directory Server to obtain its configuration details and, later in the startup process, to update Directory Server information. To do this, it requires Directory Server user credentials (that is, credentials that Directory Server will verify and authorize). In order to update the Directory Server information, this user must be granted modify permission on the appropriate enterprise server resource within Directory Server.

  The startup process also requires user credentials that the enterprise server will verify and authorize. In order to run the command used to start the enterprise server, the user must have Alter permissions on the casstart resource within the OPERCMDS resource class.

  It is important to note that the enterprise server is a separate security domain from the Directory Server. For example, it may be using different security configuration and different security managers.

  You can specify that startup should use built-in default users or the credentials with which you are currently logged on to Enterprise Server Administration. Alternatively, you can specify a different username and password.

  If you use the currently logged on user, or specify alternative user credentials, you must ensure that the user is present in both the Directory Server and the enterprise server security domains. Within the Directory Server domain, the user must have modify permission on the appropriate enterprise server resource within the Servers resource class. Within the enterprise server security domain, the user must have alter permissions on the casstart resource within the OPERCMDS resource class.

  Note: Usernames longer than 8 characters cannot be used for MTO. This restriction includes using them to start CAS. Therefore, if you sign on with a username longer than 8 characters, you will not be able to use the currently logged-on administration user option.

  Top