JP2003216455A - Operation control system and method for application server - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an economically advantageous operations control system with reduced costs while preventing a collection oversight of log data when resuming operation after an operations control server has stopped operation due to failure or the like. <P>SOLUTION: In a normal time, the operations control server MS collects pieces of log data LD<SB>1</SB>, LD<SB>2</SB>and LD<SB>3</SB>from application servers AS<SB>1</SB>, AS<SB>2</SB>and AS<SB>3</SB>, and it monitors each application server. When there is failure in the operations control server MS and its operation is stopped, a log data collecting server LCS collects the pieces of log data LD<SB>1</SB>, LD<SB>2</SB>and LD<SB>3</SB>instead. Since the log data collecting server LCS is a simple server having only a log data collecting feature, rising is fast and there is almost no collection oversight of the log data. It is inexpensive by comparison to the operations control server MS, and the costs can be reduced. <P>COPYRIGHT: (C)2003,JPO

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an application server operation management system and method.

[0002]

2. Description of the Related Art FIG. 4 is an explanatory diagram showing a configuration of a conventional application server operation management system. In this figure, the operation management server MS and the application servers AS1, AS2, AS3 are connected on a network such as a LAN. In normal times, the operation management server M
S is the application server AS1, AS2,
Log data LD1, LD2, and LD3 are collected from AS3 in a predetermined cycle, and each server is monitored based on checking these log data. In addition,
The operation management server MS collects the collected log data LD1, L
It internally has a disk (HDD) for storing D2 and LD3.

In such a conventional operation management system, the operation management server MS may fail for some reason and stop operating. In such a case, the operation management server MS accesses the application servers AS1, AS2, AS3 at once when resuming the operation after the restoration,
The log data LD1, LD2, and LD3 are collected during the suspension period from the suspension of operation to the restart of operation. Then, similarly to the normal time, each server is monitored based on the check of these log data.

However, when the operation management server MS is stopped for a long period, the data amount of the log data LD1, LD2, LD3 becomes very large, and the operation management server MS
Log data LD1, LD2, LD3 during the suspension period
It takes a lot of time to complete the data collection, and has a drawback that the traffic on the network also increases.

Therefore, in order to eliminate the above-mentioned drawbacks, an operation management system as shown in FIG. 5 may be adopted. The operation management server MS1 in FIG. 5 has an external shared disk HDD, and the log data L from the application servers AS1, AS2, AS3.
D1, LD2 and LD3 are stored in this shared disk HDD. Further, in this system, a preliminary operation management server RMS having the same function as the operation management server MS1 is provided.

If the operation management server MS1 fails and the operation is stopped, the backup operation management server RMS
Starts, and instead of the operation management server MS1, the log data LD1, LD2, LD3 from the application servers AS1, AS2, AS3 is stored in the shared disk HDD, and the stored log data LD1, LD2, LD3 is checked to check the application. Server AS1, AS
2. It is designed to monitor AS3.

[0007]

However, in the operation management system of FIG. 5, only the operation management server MS1 normally operates to collect the log data LD1, LD2, LD3, and the standby operation management server RMS. Is in a stopped state. Therefore, even if a failure occurs in the operation management server MS1 and an attempt is made to start the backup operation management server RMS, this backup operation management server RMS has the same function as that of the operation management server MS1. It will take a considerable amount of time to complete (it usually takes a few minutes to tens of minutes, depending on the size of the system). In other words, it takes a considerable amount of time to complete the switching from the operation management server MS1 to the standby operation management server RMS. Therefore, after the operation management server MS1 is stopped, a considerable omission of collection of log data LD1, LD2, LD3 occurs until the operation management function is switched to the standby operation management server RMS.

Further, in the system configuration of FIG. 5, since an expensive spare operation management server RMS1 having the same function as the operation management server MS1 is provided in case of an abnormality, it is economically disadvantageous. This is also a factor that hinders cost reduction.

The present invention has been made in view of the above circumstances, and does not cause log data collection omission when restarting the operation after the operation management server is stopped due to a failure or the like, and is economical. It is another object of the present invention to provide an operation management system and method for an application server, which is advantageous and can reduce costs.

[0010]

As a means for solving the above problems, the invention according to claim 1 collects log data from a plurality of application servers at a predetermined cycle,
In an application server operation management system including an operation management server that monitors these servers based on this log data check, a log data collection server that collects log data from the plurality of application servers at the predetermined cycle is provided. When the operation management server stops the operation and then resumes the operation, the log data of the plurality of application servers during the stop period is acquired from the log data collection server.

According to a second aspect of the present invention, the operation of the application server that causes the operation management server to collect the log data from a plurality of application servers at a predetermined cycle and monitor these servers based on the check of the log data. In the management method, when log data is collected from the plurality of application servers using the log data collection server at the predetermined cycle, the operation management server stops the operation, and then restarts the operation, during the stop period. The log data for the plurality of application servers in the above is acquired from the log data collection server.

[0012]

1 is an explanatory diagram showing the configuration of an operation management system according to an embodiment of the present invention. 1 is different from FIG. 4 in that a log data collection server LCS is provided. This log data collection server LCS
Does not have a monitoring function and other functions for the application servers AS1, AS2, AS3 like the operation management server MS, and is simply the application server A.
Log data LD1, LD2, LD3 from S1, AS2, AS3
It only has the function of collecting. Therefore,
The operation management server MS is considerably cheaper than the spare operation management server RMS in FIG. 5, and the system of FIG. 1 is economically advantageous and has a configuration in which cost reduction is realized. The operation management server MS and the log data collection server LCS each have a disk (HDD) for storing the log data LD1, LD2, LD3 therein.

Next, an operation management method performed using the system configuration of FIG. 1 will be described. First, in normal times, as in the conventional system of FIG. 4, the operation management server MS collects log data LD1, LD2, LD3 from these application servers AS1, AS2, AS3 at a predetermined cycle, respectively, and these log data are collected. Each server is monitored based on the check.

When a failure occurs in the operation management server MS for some reason, the log data LD1, LD2, LD3 from the application servers AS1, AS2, AS3 are immediately replaced by the log data collection server LCS as indicated by the arrow in FIG. Will be collected in. As described above, since the log data collection server LCS is a simple server having only a data collection function, its start-up time is short and almost no log data is missed. After this, the log data collection server LCS is the operation management server M.
Until S is restored, log data LD1, LD2, LD
Collection operation 3 will be continued.

Next, when the operation management server MS is restored, as shown by the arrow in FIG.
The log data collection server LCS collects the log data LD1, LD2, LD3 which the log data collection server LCS has collected from the application servers AS1, AS2, AS3 until then, from this log data collection server LCS. In this case, the log data LD1, LD2, and LD3 are acquired from one log data collection server LCS, and three application servers AS1, AS2, and AS3 are used as in the case of FIG.
Not done from. Therefore, this log data L
The time required to acquire D1, LD2, and LD3 is short, and the traffic on the network is greatly reduced.

The operation management server MS sends log data LD1 during the suspension period from the log data collection server LCS,
After obtaining LD2 and LD3 and confirming that there is no abnormality,
Or in parallel with this, the application server AS1,
New log data LD1, LD2, LD from AS2, AS3
Enter 3 to perform normal monitoring work.

As described above, in the configuration of FIG. 1, the log data collection server LC has only a simple function of collecting log data during the suspension period of the operation management server MS.
Since S is provided, there is no omission of log data collection during the suspension period, and the cost is very advantageous.

In the above-described embodiment, the case where the number of application servers per operation management server MS is three has been described in order to make the description easy to understand, but the number of application servers is particularly limited. However, the number may be two or four or more.

Further, in the above embodiment, the case where the cause of the operation management server MS stopping its operation is based on an abnormality such as a failure has been described. However, the software of the application servers AS1, AS2, AS3 or the operation management server MS is described. The system and method of the present invention can be applied to the case where the software is changed and the version of the system is upgraded.

[0020]

As described above, according to the present invention, a log data collection server that collects log data from a plurality of application servers at a predetermined cycle is provided so that the operation management server stops its operation and then When the operation is restarted, the log data of multiple application servers during the suspension period is acquired from this log data collection server, so the operation management server restarts the operation after the operation is stopped due to a failure. In this case, it is possible to realize an operation management system that does not cause omission of log data collection, is economically advantageous, and can reduce costs.

[Brief description of drawings]

FIG. 1 is an explanatory diagram showing a configuration of an operation management system according to an embodiment of the present invention.

FIG. 2 is an operation management server MS according to the embodiment of the present invention.
FIG. 6 is an explanatory diagram showing a flow of log data when a failure occurs.

FIG. 3 is an operation management server MS according to the embodiment of the present invention.
Explanatory diagram showing the flow of log data at the time of recovery.

FIG. 4 is an explanatory diagram showing a configuration of a conventional application server operation management system.

FIG. 5 is an explanatory diagram showing the configuration of a conventional application server operation management system different from that of FIG. 4;

[Explanation of symbols]

MS, MS1 operation management server AS1, AS2, AS3 Application server LD1, LD2, LD3 log data RMS spare operation management server HDD shared disk LCS log data collection server

Continued front page    F-term (reference) 5B034 BB02                 5B042 GA12 HH30 KK01 KK09 LA20                       MA08 MA09 MC40                 5B045 JJ09 JJ13                 5B089 GA11 GB02 JA35 KA12 KC30                       MC03 ME01 ME09

Claims (2)

[Claims] 1. An application server operation management system including an operation management server that collects log data from a plurality of application servers at a predetermined cycle and monitors these servers based on a check of the log data. A log data collection server that collects log data from one application server at the predetermined cycle, and when the operation management server stops operation and then resumes operation, the plurality of application servers during the stop period Is acquired from the log data collection server, the operation management system of the application server. 2. An application server operation management method for causing an operation management server to collect log data from a plurality of application servers at a predetermined cycle and monitoring these servers based on a check of the log data. The log data is collected from the plurality of application servers using the collection server at the predetermined cycle, and when the operation management server stops the operation and then resumes the operation, the plurality of applications during the stop period. An operation management method for an application server, characterized in that log data about the server is acquired from the log data collection server.