1.3 Overview of system operations
Perform the operations for system maintenance such as replacing business applications and performance tuning using the statistical information, in the running system. You can classify the operations as normal operations, maintenance operations, and troubleshooting operations based on the execution timing and the contents. Use the management portal (GUI) or the Smart Composer functionality (CUI) tool for executing these operations.
- Regular operations
-
Among the regular operations executed on Application Server, the following tasks are to be executed daily after starting the operations. Besides starting and stopping the system, execution of tasks such as confirming the operational status or status of logical servers that configure the system are also required for maintaining the stable operational status.
-
Starting the system (starting business operations)
-
Confirming the operational status of the system
-
Stopping the system (ending business operations)
For details on the procedure of regular operations, see 3.1 Regular operations of Application Server.
-
- Maintenance operations
-
Among the maintenance operations executed on Application Server, execute the following tasks according to the operating status. These tasks include tasks that must be executed according to the operational status, such as changing or replacing the settings of business applications in accordance with the methods provided by the service or the system maintenance, optimizing the operating environment by analyzing the data for operational status and adjusting the scale of maintenance operations.
-
Replacing the business applications
-
Performance tuning
-
Changing the IP address
-
Changing the database connection environment
-
Setting up the system, and acquiring the definition information
-
Removing the unwanted J2EE servers
-
Changing the settings of the management user account of the management functionality
For details on the procedure of maintenance operations, see 3.2 Maintenance operations of Application Server.
-
- Troubleshooting operations
-
If there is a failure in Application Server, you must collect the failure information, and restore the system to restart the operations. Such operations are called troubleshooting operations. After restarting the operations, analyze cause of the failure based on the collected information. Application Server functionality also provides operations for automatic restart and recovery of the process, if a process is down or a process hangs up (non-responding status). For details on prerequisite setting of the troubleshooting operations and failure information collection, see the uCosminexus Application Server Maintenance and Migration Guide.