Server-to-server event logging

• US 6,230,198 B1
• Filed: 09/10/1998
• Issued: 05/08/2001
• Est. Priority Date: 09/10/1998
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Dawson, Colin Scott, Kaczmarski, Michael Allen, Warren, Donald Paul Jr., Vining, Bonnie Jean
• Primary Examiner(s): Harrell, Robert B.
• Assistant Examiner(s): WILLETT, STEPHAN F
• Application Number:
  US09/150,339
• Time in Patent Office: 971 Days
• Field of Search: 709/106, 709/201, 709/224, 709/225, 709/237, 709/248, 709/253, 709/300, 714/48, 714/4, 707/202, 710/220, 702/189
• US Class Current: 709/224
• CPC Class Codes: G06F 11/327 Alarm or error message display
• CPC Class Codes: G06F 11/3476 Data logging G06F11/14, G06F11/2205 take precedence
• CPC Class Codes: G06F 11/3495 for systems
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: Y10S 707/99934 Query formulation, input preparation, or translation

Abstract

Disclosed are a method, embodiable in computer readable program code, and a system for providing server-to-server event logging. A server-to-server event message is generated including 1) an event identifier, 2) any text insert pertinent to the event message, and 3) a source trail indicating the origin and history of the event, the source trail comprising an identifier of any server forwarding the event, each identifier separated by a special character, so that the origin and any subsequently transmitting servers may be known. Further, the source trail of a received server-to-server event message is parsed to determine each identifier in the source trail, and the event message transmitted to a receiving server only if the receiving server identifier is absent from the parsed source trail, thus preventing any loops which might cause the event to be repeated. Additionally, a receiving server has a listing of events by event identifier with corresponding text messages in the text language of the receiving server. The received event identifier is found in the listing, and the receiving server logs the event, using the identified text message in the listing in the text language of the receiving server, and employing the text inserts.

Claims

1. A method of server-to-server event logging, between a present server and a receiving server, comprising the steps of:

receiving an event at said present server for which said receiving server is a receiver, wherein said event is received directly from a client or from a sending server;

where said received event is received directly from a client;

generating a server-to-server event message for said received event, said event message comprising

     1) an event identifier,

     2) any text insert pertinent to said event message, and

     3) a source trail indicating the origin and history of said event, said source trail comprising an identifier of said client supplying said event, and an identifier of said present server, each separated by a special character;

where said received event is a server-to-server event message from a sending server, said received event message comprising

     1) an event identifier,

     2) any text insert pertinent to said event message, and

     3) a source trail indicating the origin and history of said event, said source trail comprising any source trail from said sending server received with said event, with an identifier of said sending server, each said identifier separated by a special character;

generating a server-to-server event message for said received event, said message comprising

     1) said event identifier,

     2) any said text insert pertinent to said event message, and

     3) a source trail indicating the origin and history of said event, said source trail comprising said source trail received from said sending server with said event, and an identifier of said present server, each said identifier separated by said special character;

parsing said source trail of said received event message to determine each identifier in said source trail; and

transmitting said generated server-to-server event message to said receiving server only if said receiving server identifier is absent from said parsed source trail.

2. The method of claim 1, wherein said transmitting step is limited to transmitting said generated server-to-server message to only one said receiving server.

3. The method of claim 1, wherein said present server has a primary text language, and wherein said generating step additionally comprises generating in said server-to-server event message 4) a fully constructed text message in said text language of said present server.

4. A method of server-to-server event logging between a sending server and a present server, said present server having a primary text language, said present server having a listing of events by event identifier and corresponding text messages in said primary text language of said present server having insert locations, comprising the steps of:

receiving at said present server, a server-to-server event message from said sending server, said message comprising

     1) an event identifier, and

     2) any text insert pertinent to said event message;

identifying, in response to said received server-to-server event message event identifier, said received event identifier in said listing;

generating said text message corresponding to said identified event identifier in said primary text language of said present server;

providing any said received text inserts at appropriate ones of said insert locations; and

logging said received server-to-server event in said generated text message in said text language of said present server, with said provided text inserts.

5. The method of claim 4, wherein said sending server has a primary text language, and wherein said received server-to-server event message additionally comprises 4) a fully constructed text message in said text language of said sending server, comprising the additional step of:

upon said identifying step not identifying said event message in said listing of events, or upon an insert count or insert types not matching said insert locations of said corresponding text message, logging said received fully constructed text message.

6. A present server for logging an event to a receiving server, said event received directly from a client or from a sending server, comprising:

an event logging input for receiving events;

a logging event message generator coupled to said event logging input for generating event messages to be distributed to ones of receivers, said generator responding to ones of said received events for which said receiving server is a receiver;

where said received event is received directly from a client, said generator generating a server-to-server event message for said received event, said event message comprising

     1) an event identifier,

     2) any text insert pertinent to said event message, and

     3) a source trail indicating the origin and history of said event, said source trail comprising an identifier of said client supplying said event, and an identifier of said present server, each separated by a special character;

where said received event is a server-to-server event message from a sending server, said received event message comprising

     1) an event identifier,

     2) any text insert pertinent to said event message, and

     3) a source trail indicating the origin and history of said event, said source trail comprising any source trail received from said sending server with said event, comprising an identifier of said sending server, each said identifier separated by a special character, said generator generating a server-to-server event message for said received event, said event message comprising

     1) said event identifier,

     2) any said text insert pertinent to said event message, and

     3) a source trail indicating the origin and history of said event, said source trail comprising said source trail received from said sending server with said event, and an identifier of said present server, each said identifier separated by said special character;

a parsing processor parsing said source trail of said received event message to determine each identifier in said source trail; and

a logging distributor which transmits said generated server-to-server event message to said receiving server only if said receiving server identifier is absent from said parsed source trail.

7. The server of claim 6, wherein said logging distributor transmits said generated server-to-server message to only one said receiving server.

8. The server of claim 6, wherein said present server has a primary text language, and wherein said logging event message generator additionally generates said server-to-server event message with 4) a fully constructed text message in said text language of said present server.

9. A present server for logging a server-to-server event received from a sending server, said present server having a primary text language, comprising:

an event logging input for receiving said server-to-server events from said sending server, said event comprising a server-to-server event message from said sending server, said message comprising

     1) an event identifier, and

     2) any text insert pertinent to said event message;

a logging event message generator coupled to said event logging input for generating event messages to be distributed to ones of receivers, said generator having a listing of events by event identifier and corresponding text messages in said primary text language of said present server, said corresponding text messages having insert locations;

said generator responding to said server-to-server event message event identifiers of said server-to-server event received at said event logging input, identifying said received event identifier in said event listing;

said generator generating said text message corresponding to said identified event identifier in said present server primary text language of said present server;

said generator providing any said received server-to-server event message text inserts at appropriate ones of said insert locations; and

a logging distributor which transmits said generated server-to-server event message with said provided text inserts to said receivers.

10. The server of claim 9, wherein said sending server has a primary text language, and wherein said received server-to-server event message additionally comprises 4) a fully constructed text message in said text language of said sending server, and wherein said logging event message generator, upon being unable to match said event identifier in said listing of events, or upon an insert count or insert types not matching said insert locations of said corresponding text message, generates an event message for said received server-to-server event, employing said received fully constructed text message.

11. An article of manufacture comprising a computer readable medium having computer readable program code embodied therein for server-to-server event logging, between a present server and a receiving server, said present server having an event logging input for receiving events, and having a logging distributor for distributing said received events, comprising:

computer readable program code which causes a computer processor of said present server to generate event messages to be distributed to ones of receivers, said generator responding to ones of said received events for which said receiving server is a receiver, said event received directly from a client or from a sending director;

where said received event is received directly from a client, generating a server-to-server event message for said received event, said message comprising

     1) an event identifier,

     2) any text insert pertinent to said event message, and

     3) a source trail indicating the origin and history of said event, said source trail comprising an identifier of said client supplying said event, and an identifier of said present server, each separated by a special character;

where said received event is a server-to-server event message from a sending server, said received message comprising

     1) an event identifier,

     2) any text insert pertinent to said event message, and

     3) a source trail indicating the origin and history of said event, said source trail comprising any source trail from said sending server received with said event, with an identifier of said sending server, each said identifier separated by a special character, generating a server-to-server event message for said received event, said event message comprising

     1) said event identifier,

     2) any said text insert pertinent to said event message, and

     3) a source trail indicating the origin and history of said event, said source trail comprising said source trail received from said sending server with said received event, and an identifier of said present server, each said identifier separated by said special character;

computer readable program code which causes a computer processor of said Present server to parse said source trail of said received event message from said sending server to determine each identifier in said source trail; and

computer readable program code which causes a computer processor of said present server to operate said logging distributor to transmit said generated server-to-server event message to said receiving server only if said receiving server identifier is absent from said Parsed source trail.

12. The article of manufacture of claim 11, wherein said computer readable program code which causes a computer processor of said present server to operate said logging distributor, additionally operates said logging distributor to transmit said generated server-to-server message to only one said receiving server.

13. The article of manufacture of claim 11, wherein said present server has a primary text language, and wherein said computer readable program code which causes a computer processor of said present server to generate event messages, additionally causes said processor to generate said server-to-server event message with 4) a fully constructed text message in said text language of said present server.

14. An article of manufacture comprising a computer readable medium having computer readable program code embodied therein for logging a server-to-server event received by a present server from a sending server, said present server having a primary text language, said present server having an event logging input for receiving said server-to-server events from said sending server, said server-to-server event comprising a server-to-server event message from said sending server, said message comprising 1) an event identifier, and 2) any text insert pertinent to said event message, and said present server having a logging distributor for distributing said received events to receivers, comprising:

computer readable program code which causes a computer processor of said present server to have a listing of events by event identifier and corresponding text messages in said primary text language of said present server, said corresponding text messages having insert locations;

to cause said computer processor to respond to said server-to-server event message event identifier of said server-to-server event received at said event logging input, identifying said received event identifier in said event listing;

to cause said computer processor to generate said text message corresponding to said identified event identifier in said present server primary text language of said present server;

to cause said computer processor to provide any said received server-to-server event message text inserts at appropriate ones of said insert locations; and

computer readable program code which causes a computer processor of said present server to operate said logging distributor to distribute said generated server-to-server event message with said provided text inserts to said receivers.

15. The article of manufacture of claim 14, wherein said sending server has a primary text language, and wherein said received server-to-server event message additionally comprises 4) a fully constructed text message in said text language of said sending server, and wherein said computer readable program code which causes a computer processor of said present server to generate event messages, additionally causes said processor to, upon being unable to match said event identifier in said listing of events, or upon an insert count or insert types not matching said insert locations of said corresponding text message, generate an event message for said received server-to-server event, employing said received fully constructed text message.

16. A computer program product usable with a programmable computer having computer readable program code embodied therein for server-to-server event logging, between a present server and a receiving server, said present server having an event logging input for receiving events, and having a logging distributor for distributing said received events, comprising:

computer readable program code which causes a computer processor of said present server to generate event messages to be distributed to ones of receivers, said generator responding to ones of said received events for which said receiving server is a receiver, said event received directly from a client or from a sending director;

where said received event is received directly from a client, generating a server-to-server event message for said received event, said message comprising

     1) an event identifier,

     2) any text insert pertinent to said event message, and

     3) a source trail indicating the origin and history of said event, said source trail comprising an identifier of said client supplying said event, and an identifier of said present server, each separated by a special character;

where said received event is a server-to-server event message from a sending server, said message comprising

     1) an event identifier,

     2) any text insert pertinent to said event message, and

     3) a source trail indicating the origin and history of said event, said source trail comprising any source trail from said sending server received with said event, with an identifier of said sending server, each said identifier separated by a special character, generating a server-to-server event message for said received event, said event message comprising

     1) said event identifier,

     2) any said text insert pertinent to said event message, and

     3) a source trail indicating the origin and history of said event, said source trail comprising said source trail received from said sending server with said event, and an identifier of said present server, each said identifier separated by said special character;

computer readable program code which causes a computer processor of said present server to parse said source trail of said received event message from said sending server to determine each identifier in said source trail; and

computer readable program code which causes a computer processor of said present server to operate said logging distributor to transmit said generated server-to-server event message to said receiving server only if said receiving server identifier is absent from said parsed source trail.

17. The computer program product of claim 16, wherein said computer readable program code which causes a computer processor of said present server to operate said logging distributor, additionally operates said logging distributor to transmit said generated server-to-server message to only one said receiving server.

18. The computer program product of claim 16, wherein said present server has a primary text language, and wherein said computer readable program code which causes a computer processor of said present server to generate event messages, additionally causes said processor to generate said server-to-server event message with 4) a fully constructed text message in said text language of said present server.

19. A computer program product usable with a programmable computer having computer readable program code embodied therein for logging a server-to-server event received by a present server from a sending server, said present server having a primary text language, said present server having an event logging input for receiving said server-to-server events from said sending server, said server-to-server event comprising a server-to-server event message from said sending server, said message comprising 1) an event identifier, and 2) any text insert pertinent to said event message, and said present server having a logging distributor for distributing said received events to receivers, comprising:

computer readable program code which causes a computer processor of said present server to have a listing of events by event identifier and corresponding text messages in said primary text language of said present server, said corresponding text messages having insert locations;

to cause said computer processor to respond to said server-to-server event message event identifier of said server-to-server event received at said event logging input, identifying said received event identifier in said event listing;

to cause said computer processor to generate said text message corresponding to said identified event identifier in said present server primary text language of said present server;

to cause said computer processor to provide any said received server-to-server event message text inserts at appropriate ones of said insert locations; and

computer readable program code which causes a computer processor of said present server to operate said logging distributor to distribute said generated server-to-server event message with said provided text inserts to said receivers.

20. The computer program product of claim 19, wherein said sending server has a primary text language, and wherein said received server-to-server event message additionally comprises 4) a fully constructed text message in said text language of said sending server, and wherein said computer readable program code which causes a computer processor of said present server to generate event messages, additionally causes said processor to, upon being unable to match said event identifier in said listing of events, or upon an insert count or insert types not matching said insert locations of said corresponding text message, generate an event message for said received server-to-server event, employing said received fully constructed text message.