This section explains how to terminate each process of configuration software, resources, and J2EE applications.
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 form of system operation, but you can first terminate the Web server 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.
This point explains how to terminate a J2EE application.
You terminate a J2EE application with server management commands. To stop J2EE application, use the cjstopapp server management command. The method for terminating a J2EE application in the normal mode and test mode:
Note that you must have the root permission, or the permission of the Component Container Administrator to execute server management commands.
In some cases the request processing within a J2EE application does not finish even when the J2EE application is terminated, and hence, the termination processing is not complete. In such cases, you need to terminate the J2EE application forcefully. For forceful termination of a J2EE application, specify the -force option in the cjstopapp command, and then execute the command.
For specific procedures for terminating J2EE applications, see 10.2.2 Stopping J2EE applications in the uCosminexus Application Server Application Setup Guide.
This point explains how to terminate a resource.
You terminate a resource using the server management command (cjstoprar or cjstopjb).
Note that you must have root permission or Component Container administrator permission to execute the server management commands.
When you use a resource adapter included in the J2EE application, this operation is not required.
To terminate a J2EE server:
# cd /opt/Cosminexus/CC/server/bin |
# cjstopsv server-name |
An example for executing the cjstopsv command is explained below. In this example, the server name is 'MyServer'.
# cd /opt/Cosminexus/CC/server/bin |
Note that in some cases the processing on the J2EE server does not finish even when the J2EE server is terminated, and hence, the termination processing is not complete. In such cases, you must terminate the J2EE server forcefully. To forcefully terminate a J2EE server, specify the -f option or -fd option in the cjstopsv command, and then execute the command. If you specify the -fd option, the J2EE server is terminated forcefully after acquiring the failure information of the J2EE server.
You terminate an SFO server with the same procedure as a J2EE server.
For details on terminating J2EE servers, see E.4 (4) Terminating a J2EE server.
To terminate a CTM daemon:
# cd /opt/Cosminexus/CTM/bin |
# ctmstop |
Note that in some cases even after you terminate the CTM daemon, the termination processing of the CTM daemon does not finish. In such cases, you must terminate the CTM daemon forcibly. For forceful termination of the CTM daemon, specify the -CTMForce option in the ctmstop command, and then execute the command.
The procedure for terminating the CORBA Naming Service differs depending on how the CORBA Naming Service is invoked.
The details of the procedure for terminating the CORBA Naming Service when it is invoked manually in the background are explained below.
When you invoke the CORBA Naming Service manually in the background, it is not discriminated from other Java processes, and you may not understand which process is the CORBA Naming Service. As a result, how to acquire the process ID of the CORBA Naming Service differs depending on the existence of other active Java processes. Note that in AIX, if you execute the ps -ef command, the process arguments are displayed longer than in other platforms, and therefore, you can identify the CORBA Naming Service.
# ps -ef | grep java |
# kill Process-ID-of-CORBA-Naming-Service |
#!/bin/sh |
# kill `cat namesv_pid` |
To terminate CTM domain manager:
# cd /opt/Cosminexus/CTM/bin |
# ctmdmstop |
Note that in some cases even after you terminate the CTM domain manager, the termination processing of the CTM domain manager does not finish. In such cases, you must terminate the CTM domain manager forcibly. For forceful termination of the CTM domain manager, specify the -CTMForce option in the ctmdmstop command, and then execute the command.
The procedure for terminating the Smart Agent is as follows:
The method of terminating the Smart Agent will differ depending on how you started the Smart Agent.
# ps -ef | grep osagent |
# kill smart-agent-process-ID |
To terminate a PRF daemon:
# cd /opt/Cosminexus/PRF/bin |
# cprfstop |
Note that in some cases even after you terminate the PRF daemon, the termination processing of the PRF daemon does not finish. In such cases, you must terminate the PRF daemon forcefully. For forceful termination of the PRF daemon, specify the -Force option in the cprfstop command, and then execute the command.