Start and terminating generic application servers
This topic describes how to start and terminate generic servers.
For the WAS (base) product, we cannot use the administrative console to create a generic application server definition or use the administrative console to start, stop or, in any way, control or manage that application server. The Base product administrative console can only be used to create server definitions and, if necessary, adjust the server definitions that it creates. To manage Base generic application servers, use the command prompt environment, such as startServer <genericServerName> or stopServer <genericServerName> or serverStatus <genericServerName>. The wsadmin tool has no functional role in the Base application server environment.
If we create a generic server in a WAS Network Deployment environment, we can use the administrative console to start and terminate this server.
- Start a generic application server.
There are two ways to start a generic server in a WAS Network Deployment environment. We can use the managed bean (MBean) NodeAgent launchProcess operation of wsadmin.sh, or we can use the administrative console. To use the administrative console:
- In the administrative console, click Servers > Server Types > Generic servers.
- Select the name of the generic server to start, and then click Start.
- View the Status value and any messages or logs to see whether the generic server starts.
- Terminate generic servers.
There are two ways to terminate a generic server in a WAS Network Deployment environment. We can use the MBean terminate launchProcess operation of the wsadmin tool, or we can use the administrative console. To use the administrative console:
- In the administrative console, click Servers > Server Types > Generic servers.
Select the check box for the name of the generic server, and then click Terminate.
- View the Status value and any messages or logs to see whether the generic server terminates.
Related tasks
Manage generic servers
Get started with wsadmin scripting