The operation management of a business system becomes complicated with increasing volume. An operation method that is efficient, has a controlled operational cost, and that achieves the maximum system performance is required. Therefore it is mandatory to have an interface with an excellent operability, and a mechanism for automatic operations.
Application Server provides the following operation management functions to fulfil these requirements:
- Batch operation of a business system
An environment built with the Setup Wizard, Operation Management Portal, and Smart Composer Function is managed based on the concept of an operation management domain. The operation management domain is managed by the processes called Management Server. You can manage the start and stop processes of multiple J2EE servers and Web servers in a batch.
In addition to this, you can execute operations such as monitoring, automation of operations, and analysis of operation status of the overall business systems including systems that are not built with Application Server in a batch, by linking with JP1.
- Output of operation information or resource usage status of a system
You can output the operation status and resource usage status of a system. It is possible to prevent the occurrence of trouble and take countermeasures if trouble occurs by monitoring the output contents. The output information is also used for system tuning. You can also output this information to a file.
- Automation of operations
You can automate recovery operations when an error occurs and automate operations to prevent errors by using functions such as the function for restarting the server when an error occurs and functions for issuing events and executing actions linked with the operation management.
You can automate the operations of all the systems including the systems that are not built with Application Server, by linking with JP1.
- Log operations
You can collect the logs output by the Application Server system in a batch. It is possible to handle the logs of J2EE applications developed by the user in the same manner as that of the logs output by an Application Server system. It is possible to execute a highly reliable log operation by managing the logs of the overall system in a batch.
In JavaVM used by Application Server, the output contents of logs are extended so that they can be used for cause analysis when an error occurs and for checking the system status. You can improve the system availability by executing appropriate tuning using this log.
- Performance analysis by trace information
When executing a request, the trace information is output at every point starting from the Web server up to the database connection. You can clarify the process bottlenecks and specify the location of error occurrence, by analysing this information.
Note that you can output the trace information in a system and also in an application developed by the user.
- Integrated user management
You can execute the integrated management of users logged in a system built with Application Server. Since the information of the users managing the respective J2EE applications is linked and managed, you can log in to the various J2EE applications, with a one-time login process. Note that you can use the LDAP directory service and the database as a repository to manage the user information.
- Efficiency of switching application at the time of maintenance
You can manage the applications in two formats; the archive format and the deployable directory format. For an application in the deployable directory format, you need not re-archive when switching the application but the switching is done just by reloading the changed class file. For an application in the archive format, switching (redeploy) is possible without stopping and restarting the application in case of local changes. As a result of this, the switching efficiency increases during maintenance and the system operation cost is also controlled.
All Rights Reserved. Copyright (C) 2013, 2015, Hitachi, Ltd.