4.9.4 Considering system operating procedures
This subsection gives examples of the system operating procedures to be written in the System Operating Procedure document. When preparing a System Operating Procedure document, refer to these sample procedures.
To operate a secure system, Smart Composer functionality commands and the snapshotlog command are used. When adding an operation other than those described here to the work procedure document, use commands that create audit log entries. For details about commands that create audit log entries, see Chapter 6 in the uCosminexus Application Server Operation, Monitoring, and Linkage Guide.
Among the tasks described here, certain tasks involving starting the Web system and non-Web system maintenance work should be performed by a System operator. Web system maintenance should be performed by the System administrator when so requested by a System operator.
- Organization of this subsection
(1) Starting the Web system
The Web system on the administrator terminal of the management server should be started by a System operator. However, the resource adapters and J2EE applications should be started by the System administrator, using server management commands. The procedure for starting the Web system is as follows:
-
The System operator uses the cmx_start_target command to set the service unit within the Web system to a ready state.
-
The System operator requests the System administrator to start services.
-
The System administrator uses the cjstartrar command to start the resource adapters.
-
The System administrator uses the cjstartapp command to start the J2EE application.
-
The System operator uses the cmx_start_target command to set the service unit within the Web system to a running state.
(2) Stopping the Web system
The System operator should use the appropriate Smart Composer functionality commands on the administrator terminal of the management server to stop the Web system. The procedure for stopping the Web system is as follows:
-
Use the cmx_stop_target command to set the service unit within the Web system to a stopped state.
(3) Managing end-users
The System operator should manage end-user access permissions and user IDs according to the System Operating Procedure document. The following tasks are performed by a System operator:
-
Registering and deleting end-users
-
Changing end-user permissions
-
Changing end-user passwords
In the System Operating Procedure document, include detailed procedures for these tasks.
(4) Notifying end-users
The System operator should notify each end-user registered in (3) Managing end-users of his or her user ID and password. The procedure for notifying an end-user of his or her user ID and password is as follows:
-
Use the user ID and password registered for the end-user in accordance with the System Operating Procedures document to ensure the end-user can use the services.
-
Make sure that an audit log is output during service use.
-
After completing the checks in steps 1 and 2, use a safe means to notify the end-user of his or her user ID and password.
(5) Maintaining the Web system
The Web system should be maintained as necessary. Web system maintenance should be performed by the System administrator when so requested by the System operator. The procedure for maintaining the Web system is as follows:
-
The System operator uses the cmx_stop_target command to block or stop the service unit to be maintained.
-
To apply a fix patch to the application server, the System operator stops the application server-related programs. If no fix patch is applied, proceed to step 3.
-
The System operator requests the System administrator to maintain the system.
-
The System administrator uses the System administrator user ID to log into the OS.
-
The System administrator applies service packs and security patches to the OS and applies fix patches to the application server. A System operator must be in attendance while the System administrator is performing this step.
-
If a fix patch is applied to the application server, the System operator restarts the application server-related programs.
-
The System operator uses the cmx_start_target command to restart the service unit.
(6) Troubleshooting the system
If an error occurs, it should be handled by the System operator. The procedure for troubleshooting a system error is as follows:
-
Use the snapshotlog command to collect application server logs.
-
If necessary, separately collect any logs that cannot be collected with the snapshotlog command.
-
Send the collected logs to maintenance personnel for examination.
-
Conduct system maintenance based on the examination results.