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, and EIS, terminate them at the end, as required.
- Note
- Depending on the system configuration, there are cases where only the Application Servers are terminated, while in some cases, integrated naming scheduler servers and session failover servers are also terminated along with the Application Servers.
- When you terminate an integrated naming scheduler server and a session failover server with an Application Server, take note of the following point:
- 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.
Terminate a system as per 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 the Web server depends on the mode of the system operation, but you can first terminate the Web server for controlling the reception of requests in a J2EE application. Furthermore, if you are using an in-process HTTP server, you need not terminate the Web server.
- Terminate J2EE applications
Terminate a J2EE application using the server management command (cjstopapp). For details on terminating a J2EE application, see D.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
If you are not using J2EE resources, this operation is not required.
Terminate the J2EE resource using the server management command (cjstoprar or cjstopjb). For details on terminating resources, see D.4 (3) Terminating resources.
Note that the next time you start a J2EE resource while starting a J2EE server, you need not terminate the J2EE resource.
- Terminate J2EE servers
Terminate the J2EE server using the cjstopsv command. For details on terminating a J2EE server, see D.4 (4) Terminating a J2EE server.
- Terminate SFO servers
Terminate the SFO server using the cjstopsv command. An SFO server is terminated with the same procedure as a J2EE server. For details on terminating SFO servers, see D.4 (5) Terminating an SFO 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 D.4 (6) Terminating a CTM daemon.
- Terminate the CORBA Naming Service
The method to terminate the CORBA Naming Service differs depending on how it is invoked. For details on terminating the CORBA Naming Service, see D.4 (7) Terminating the CORBA Naming Service.
- Terminate the CTM domain manager
If you are not using, 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 D.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 D.4 (9) Terminating the Smart Agent.
- Terminate the PRF daemon
Terminate the PRF daemon using the cprfstop command. For details on terminating a PRF daemon, see D.4 (10) Terminating a PRF daemon.