Hitachi

Hitachi Application Server V10 User's Guide (For Windows® Systems)


6.1.1 Process monitoring

For processes that are started on a domain administration server, the startup status, running status, and termination are automatically monitored. For the other processes to be monitored, a monitoring application or monitoring system needs to be used.

Quick and safe recovery from any error occurring on Application Server requires monitoring of all processes. All the Application Server processes can be monitored by using both the process monitoring function of the domain administration server and a monitoring application or monitoring system. Note that the domain administration server itself must also be monitored. Therefore, this section also describes how to do this.

Process monitoring function of the domain administration server

When a domain administration server is running, its process monitoring functionality monitors any processes that are running on the Java EE server, web server, and performance tracer. Therefore, if you use a generic process monitoring product or monitoring system to monitor processes, monitor only the domain administration server rather than monitoring individual processes. The following figure illustrates the sections where the user can set any values for the timeouts and intervals in the flow of a process monitored by the process monitoring function of the domain administration server.

[Figure]

The following table describes the setting items in the figure. You can set any length of time for each setting item by using a parameter.

Number in the figure

Monitored process

Description of the setting item

Parameter

1

  • Performance tracer

  • Web server

A startup timeout period

  • Performance tracer:

    hitachi-prf-configs.hitachi-prf-config.configuration_name_of_the_performance_tracer.hitachi-manage-info.start-timeout-in-seconds

  • Web server:

    hitachi-webserver-configs.hitachi-webserver-config.configuration_name_of_the_web_server.hitachi-manage-info.start-timeout-in-seconds

  • Java EE server:

    configs.config.configuration_name_of_the_Java_EE_server.hitachi-manage-info.start-timeout-in-seconds

2

Java EE server

3

  • Performance tracer

  • Web server

  • Java EE server

The interval at which to monitor the running status of the server This section monitors server errors such as service stoppages resulting from process failures or hangs. The running status of the server process is periodically checked at the preset interval until server error monitoring ends.

A monitoring process is periodically generated to check the running status for each monitored process. Because this processing consumes CPU resources, increase the monitoring interval if online processing performance is affected.

  • Performance tracer:

    hitachi-prf-configs.hitachi-prf-config.configuration_name_of_the_performance_tracer.hitachi-manage-info.running-watch-interval-in-seconds

  • Web server:

    hitachi-webserver-configs.hitachi-webserver-config.configuration_name_of_the_web_server.hitachi-manage-info.running-watch-interval-in-seconds

  • Java EE server:

    configs.config.configuration_name_of_the_Java_EE_server.hitachi-manage-info.running-watch-interval-in-seconds

4

  • Performance tracer

  • Web server

A stop timeout period

  • Performance tracer:

    hitachi-prf-configs.hitachi-prf-config.configuration_name_of_the_performance_tracer.hitachi-manage-info.stop-timeout-in-seconds

  • Web server:

    hitachi-webserver-configs.hitachi-webserver-config.configuration_name_of_the_web_server.hitachi-manage-info.stop-timeout-in-seconds

  • Java EE server:

    configs.config.configuration_name_of_the_Java_EE_server.hitachi-manage-info.stop-timeout-in-seconds

5

Java EE server

Process monitorability

The following table shows the processes to be monitored. This table also shows whether the processes can be monitored by the domain administration server, or by generic monitoring applications or systems. Processes that cannot be monitored by the domain administration server can be monitored by other monitoring applications or monitoring systems if necessary.

Component

Process to be monitored

Domain administration server

Generic monitoring applications or systems

Application client

java

N

Y

Web server

httpsd

Y#

Y

---

rotatelogs2

N

Y

---

rotatelogs

N

Y

---

httpsd

N

Y

Java EE server

java

Y#

Y

Performance tracer

cprfd

Y#

Y

Domain administration server

service_name

N

Y

---

cmd

Y

---

---

java

Y

---

---

---

java

Y

(Legend)

Y: Can monitor the process.

N: Cannot monitor the process.

#:

If the process is directly started without using the asadmin utility command, the process cannot be monitored by the domain administration server.

Monitoring the domain administration server and Java EE server

The process names of the domain administration server and Java EE server are java. When monitoring these processes, distinguish them from other java processes by including options in the command. Command line examples are shown below.

Example of monitoring the domain administration server process
wmic process where "(name='java.exe')" get name,processid,commandline |
 find "-domainname domain1"
Example of monitoring the Java EE server process
wmic process where "(name='java.exe')" get name,processid,commandline |
 findstr /r /c:"-instancedir .*/localhost-domain1/JavaEE1"