# US 2005/0240667 A1 · Message-oriented middleware server instance failover

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2005/0240667 A1
- Document ID: US20050240667A1
- Status: Published application
- Kind: A1
- Application number: 10/829,874
- Filed: 2004-04-21
- Published: 2005-10-27
- Earliest claimed: 2004-04-21
- Assignees: Sap SE
- Inventors: Michael Koegel
- Web page: https://patentgrep.com/patent/US20050240667A1

## CPC

- G06Q 10/10: Office automation; Time management
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

A system and method are provided for failover of a Message-Oriented Middleware (MOM) server instance in an MOM provider having multiple MOM server instances. In an embodiment, a first server node receives notification that an MOM server instance on a second server node is inoperative. The MOM server instance on the second server node may have one or more associated destinations. In an embodiment, the first server node attempts to obtain a lock for at least a portion of MOM server instance configuration information from a locking service. If the lock is obtained, the first server node may acquire the one or more destinations of the inoperative MOM server instance.

## Claims

### Claim 1

A method employed within a network comprising:
receiving a notification at a first server node that a Message-Oriented Middleware (MOM) server instance on a second server node is inoperative, the inoperative MOM server instance having one or more destinations;
attempting to obtain a lock for at least a portion of MOM server instance configuration information from a locking service; and
acquiring the one or more destinations of the inoperative MOM server instance at the first server node, if the lock is obtained.

### Claim 2 (depends on 1)

The method of claim 1, wherein
the first server node is identified by a first server node identifier,
the received notification includes the first server node identifier, and
the second server node is identified by a second server node identifier.

### Claim 3 (depends on 2)

The method of claim 2, wherein acquiring the one or more destinations of the inoperative MOM server instance at the first server node, if the lock is obtained, further comprises:
searching the MOM server instance configuration information, the MOM server instance configuration information including one or more destination configuration entities to define one or more destinations;
identifying one or more destination configuration entities having the second server node identifier; and
replacing the second server node identifier with the first server node identifier for each of the identified configuration entities.

### Claim 4 (depends on 1)

The method of claim 1, further comprising:
receiving a notification that the MOM server instance is operational; and
returning the one or more acquired destinations from the first server node to the second server node.

### Claim 5 (depends on 1)

The method of claim 1, wherein receiving the notification at a first server node that the MOM server instance on the second server node is inoperative comprises:
receiving the notification from a central service of a cluster of application servers that the MOM server instance on the second server node is inoperative.

### Claim 6 (depends on 1)

The method of claim 1, wherein receiving the notification at a first server node that the MOM server instance on the second server node is inoperative comprises:
receiving the notification from the second server node that the MOM server instance is inoperative.

### Claim 7 (depends on 1)

The method of claim 1, wherein the MOM server instance is a Java Message Service (JMS)-based server instance.

### Claim 8 (depends on 7)

The method of claim 7, wherein at least one of the first server node and the second server node is a Java 2 Enterprise Edition-based application server.

### Claim 9 (depends on 8)

The method of claim 8, wherein acquiring the one or more destinations of the inoperative JMS-based server instance at the first server node comprises:
acquiring at least one of
a queue of the inoperative JMS-based server instance and
a topic of the inoperative JMS-based server instance.

### Claim 10

A system comprising:
a plurality of server nodes communicatively coupled on an enterprise network, the plurality of server nodes to serve applications over the enterprise network to a plurality of clients; and
a Message-Oriented Middleware (MOM) provider to provide a message service for the plurality of server nodes, the MOM provider including a first MOM server instance having one or more associated destinations implemented on a first server node and a second MOM server instance implemented on a second server node, wherein the second MOM server instance is to acquire the one or more destinations, if the first MOM server instance becomes inoperative.

### Claim 11 (depends on 10)

The system of claim 10, further comprising:
a configuration store having a destination configuration entity for each of the one or more destinations, each destination configuration entity including a server node identifier to identify an associated server node.

### Claim 12 (depends on 11)

The system of claim 11, wherein the MOM provider is a Java Message Service (JMS)-based MOM provider.

### Claim 13 (depends on 11)

The system of claim 11, wherein at least one of the plurality of server nodes is a Java 2 Enterprise Edition based server node.

### Claim 14

A system comprising:
means for receiving a notification at a first server node that a Message-Oriented Middleware (MOM) server instance on a second server node is inoperative, the inoperative MOM server instance having one or more destinations;
means for attempting to obtain a lock for at least a portion of MOM server instance configuration information from a locking service; and
means for acquiring the one or more destinations of the inoperative MOM server instance at the first server node, if the lock is obtained.

### Claim 15 (depends on 14)

The system of claim 14, wherein
the first server node is identified by a first server node identifier,
the received notification includes the first server node identifier, and
the second server node is identified by a second server node identifier.

### Claim 16 (depends on 15)

The system of claim 15, wherein the means for acquiring the one or more destinations of the inoperative MOM server instance at the first server node, if the lock is obtained, further comprises:
means for searching the MOM server instance configuration information, the MOM server instance configuration information including one or more destination configuration entities to define one or more destinations;
means for identifying one or more destination configuration entities having the second server node identifier; and
means for replacing the second server node identifier with the first server node identifier for each of the identified configuration entities.

### Claim 17 (depends on 14)

The system of claim 14, wherein the means for receiving the notification at a first server node that the MOM server instance on the second server node is inoperative comprises:
means for receiving the notification from a central service of a cluster of application servers that the MOM server instance on the second server node is inoperative.

### Claim 18 (depends on 14)

The system of claim 14, wherein the MOM server instance is a Java Message Service (JMS)-based server instance.

### Claim 19 (depends on 18)

The system of claim 18, wherein the means for acquiring the one or more destinations of the inoperative JMS-based server instance at the first server node comprises:
means for acquiring at least one of
a queue of the inoperative JMS-based server instance and
a topic of the inoperative JMS-based server instance.

### Claim 20

An article of manufacture comprising:
an electronically accessible medium providing instructions that, when executed by an apparatus, cause the apparatus to
receive a notification at a first server node that a Message-Oriented Middleware (MOM) server instance on a second server node is inoperative, the inoperative MOM server instance having one or more destinations;
attempt to obtain a lock for at least a portion of MOM server instance configuration information from a locking service; and
acquire the one or more destinations of the inoperative MOM server instance at the first server node, if the lock is obtained.

### Claim 21 (depends on 20)

The article of manufacture of claim 20, wherein
the first server node is identified by a first server node identifier,
the received notification includes the first server node identifier, and
the second server node is identified by a second server node identifier.

### Claim 22 (depends on 21)

The article of manufacture of claim 21, wherein the instructions that, when executed by the apparatus, cause the apparatus to acquire the one or more destinations of the inoperative MOM server instance at the first server node, if the lock is obtained, cause the apparatus to
search the MOM server instance configuration information, the MOM server instance configuration information including one or more destination configuration entities to define one or more destinations;
identify one or more destination configuration entities having the second server node identifier; and
replace the second server node identifier with the first server node identifier for each of the identified configuration entities.

### Claim 23 (depends on 21)

The article of manufacture of claim 21, wherein the electronically accessible medium provides further instructions that, when executed by the apparatus, cause the apparatus to
receive a notification that the MOM server instance is operational; and
return the one or more acquired destinations from the first server node to the second server node.

### Claim 24 (depends on 20)

The article of manufacture of claim 20, wherein the instructions that, when executed by the apparatus, cause the apparatus to receive the notification at the first server node that a MOM server instance on the second server node is inoperative cause the apparatus to
receive the notification from a central service of a cluster of application servers that the MOM server instance on the second server node is inoperative.

### Claim 25 (depends on 24)

The article of manufacture of claim 24, wherein the instructions that, when executed by the apparatus, cause the apparatus to receive the notification from the central service of the cluster of application servers that the MOM server instance on the second server node is inoperative cause the apparatus to
receive the notification from the central service of the cluster of application servers that a Java Message Service (JMS)-based server instance on the second server node is inoperative.
