InfoCenter Home >
6: Administer applications >
6.6: Tools and resources quick reference >
6.6.47: Administering generic servers
6.6.47: Administering generic servers
By making generic
servers or processes known to the WebSphere administrative domain,
the administrator can stop and start these processes from the administrative console
when stopping or starting the applications that rely on them.
The WebSphere administrator configures one or more generic servers with settings for:
- Specifying the machine on which the server resides
- Specifying Java command line arguments and environment variables for starting the
server process (if applicable)
- Associating the server with an operating system user ID and security group
- Specifying how many times to try to start or ping the server before giving up
- Specifying the process priority on the operating system
- Defining standard in, standard error and standard out streams for the server runtime
- Specifying a working directory
Setting NodeStartState for generic servers via the admin.config file
You can apply an additional system property in the admin.config file to configure
the Generic Servers NodeStartState:
com.ibm.ejs.sm.adminServer.GenericServerNodeStartSate =
[Current|Running|Stopped]
To apply the property, add the following text to the admin.config file:
# NodeStartState of generic servers: [Current|Running|Stopped]
com.ibm.ejs.sm.adminServer.GenericServerNodeStartState = (NodeStartState)
NodeStartState options: Current: Each generic server is in its last state prior to Node restarts.
Running: Each generic server is in Running state regardless of last state.
Stopped: Each generic server is in Stopped state regardless of last state.
This property applies to generic servers as a whole. The property specified affects every generic server
created on the Node. The property does not affect generic servers created on other Nodes.
|