The procedure for terminating a system is the reverse of the procedure for starting a system. If you are using a database, LDAP directory server, or EIS, terminate them at the end as required.
- Note
- Depending on the system configuration, there are cases where only the Application Server is terminated while in some cases, the integrated naming scheduler server and session failover server is also terminated with the Application Server.
- When you terminate the integrated naming scheduler server and session failover server with the Application Server, take note of the following:
- When you use a session failover server, terminate the session failover server after you terminate the Application Server.
- You can terminate the integrated naming scheduler server in any order.
You terminate a system based on the termination operation explained below:
- Terminate the Web server
For details on terminating a Web server, see the manual on the Web server you are using.
Note that the timing of terminating a Web server depends on the mode of system operation, but you can terminate the Web server first for controlling the reception of requests in the J2EE application. Furthermore, if you are using an in-process HTTP server, you need not terminate the Web server.
- Terminate J2EE applications
Use the server management command (cjstopapp) to terminate the J2EE application. For details on terminating J2EE applications, see E.4 (2) Terminating a J2EE application.
Note that the next time you start a J2EE application and J2EE server at the same time, you need not terminate the J2EE application.
- Terminate resources
When you are not using J2EE resources, this operation is not required.
You use the server management command (cjstoprar) to terminate a J2EE resource. For details on terminating resources, see E.4 (3) Terminating a resource.
Note that the next time you start a J2EE resource while a J2EE server is being started, you need not terminate the J2EE resource.
- Terminate J2EE servers
You use the cjstopsv command to terminate the J2EE server. For details on terminating a J2EE server, see E.4 (4) Terminating a J2EE server.
- Terminate SFO servers
You use the cjstopsv command to terminate the SFO server. An SFO server is terminated with the same procedure as a J2EE server. For details on terminating SFO servers, see E.4 (4) Terminating a J2EE server.
- Terminate a CTM daemon
If you are not using CTM, this operation is not required.
Terminate a CTM daemon using the ctmstop command. For details on terminating a CTM daemon, see E.4 (6) Terminating a CTM daemon.
- Terminate the CORBA Naming Service
How to terminate the CORBA Naming Service differs depending on how it is invoked. For details on methods for terminating the CORBA Naming Service, see E.4 (7) Terminating the CORBA Naming Service.
- Terminate the CTM domain manager
If you are not using CTM, this operation is not required.
Terminate the CTM domain manager using the ctmdmstop command. For details about how to terminate the CTM domain manager, see E.4 (8) Terminating the CTM domain manager.
- Terminate the Smart Agent
If you have not started the Smart Agent, this operation is not required.
For details on terminating the Smart Agent, see E.4 (9) Terminating the Smart Agent.
- Terminate the PRF daemon
You use the cprfstop command to terminate the PRF daemon. For details on terminating a PRF daemon, see E.4 (10) Terminating a PRF daemon.