Abstract: A system and method can provide a scalable data storage in a middleware environment. The system can include a cluster of replicated store daemon processes in a plurality of processing nodes, wherein each machine node can host a replicated store daemon process of the cluster of replicated store daemon processes. Additionally, the system can include one or more replicated stores associated with an application server the processing node. The replicated store daemon cluster can persist data from a replicated store to another node, the other node also being associated with the replicated store daemon cluster. The system and method can additionally support a messaging service in a middleware environment. The messaging service can use the replicated store to store a copy of a message in the local processing node and on another processing node associated with the same replicated store daemon cluster.

Abstract: In accordance with an embodiment, a system and method provides a dynamic clustered messaging service in an application server environment. A cluster includes one or more servers operating within the application server environment and is configured to vary a number of the servers based on a service load of applications running on the cluster. The number also varies based on failure and restart of the servers. A messaging service for communicating messages between components of the applications includes instances of messaging service artifacts running on the one or more servers. A placement engine operating on the cluster is configured to migrate the instances of messaging service artifacts between the one or more servers based on a set of rules as the number of the one or more servers in the cluster expands and contracts and as a number of the instances of messaging service artifacts expands and contracts.

Abstract: A system includes a resource adapter module in the form of executable code by a processor, the resource adapter module to, interact with an application running on an application server by receiving calls from applications, and provide communication between the application and any JMS provider by relaying the calls to the JMS provider.

Abstract: A computer-controlled method can include providing a resource adapter with an object wrapper having a plurality of features, a wrapper generation tool receiving a change to be made to the object wrapper, and the wrapper generation tool generating a new object wrapper based on the change. The resource adapter can receive an object from a messaging provider, adapt the object based on the newly generated object wrapper, and send the wrapped object to an application.

Abstract: A system has at least one requesting application residing upon a requesting application server, a cluster of processing message servers, a resource adapter in the form of executable code being executed by a processor on a first computer, the resource adapter to receive a request from the requesting application; transmit the request to the cluster of processing message servers; monitor processing of the request on the cluster of processing message servers; handling any exception in the processing of the request; and responding to the requesting application when the processing is complete. The system also includes an interposed transaction manager in the form of executable code being executed by a processor, the interposed transaction manager to receive transactional operations associated with the requests, and providing transaction guarantees related to the transactional operations.

Abstract: In accordance with an embodiment, a system and method provides a dynamic clustered messaging service in an application server environment. A cluster includes one or more servers operating within the application server environment and is configured to vary a number of the servers based on a service load of applications running on the cluster. The number also varies based on failure and restart of the servers. A messaging service for communicating messages between components of the applications includes instances of messaging service artifacts running on the one or more servers. A placement engine operating on the cluster is configured to migrate the instances of messaging service artifacts between the one or more servers based on a set of rules as the number of the one or more servers in the cluster expands and contracts and as a number of the instances of messaging service artifacts expands and contracts.

Abstract: A system and method can provide a scalable data storage in a middleware environment. The system can include a cluster of replicated store daemon processes in a plurality of processing nodes, wherein each machine node can host a replicated store daemon process of the cluster of replicated store daemon processes. Additionally, the system can include one or more replicated stores associated with an application server the processing node. The replicated store daemon cluster can persist data from a replicated store to another node, the other node also being associated with the replicated store daemon cluster. The system and method can additionally support a messaging service in a middleware environment. The messaging service can use the replicated store to store a copy of a message in the local processing node and on another processing node associated with the same replicated store daemon cluster.

Abstract: A system has at least one requesting application residing upon a requesting application server, a cluster of processing message servers, a resource adapter in the form of executable code being executed by a processor on a first computer, the resource adapter to receive a request from the requesting application; transmit the request to the cluster of processing message servers; monitor processing of the request on the cluster of processing message servers; handling any exception in the processing of the request; and responding to the requesting application when the processing is complete. The system also includes an interposed transaction manager in the form of executable code being executed by a processor, the interposed transaction manager to receive transactional operations associated with the requests, and providing transaction guarantees related to the transactional operations.

Abstract: A system includes a resource adapter module in the form of executable code by a processor, the resource adapter module to, interact with an application running on an application server by receiving calls from applications, and provide communication between the application and any JMS provider by relaying the calls to the JMS provider.

Abstract: A computer-controlled method can include providing a resource adapter with an object wrapper having a plurality of features, a wrapper generation tool receiving a change to be made to the object wrapper, and the wrapper generation tool generating a new object wrapper based on the change. The resource adapter can receive an object from a messaging provider, adapt the object based on the newly generated object wrapper, and send the wrapped object to an application.

Abstract: Disclosed herein is a system and method for client interoperability. In one embodiment, a method for client interoperability comprises establishing a network connection between a client and a proxy. The client requests a connection factory from the proxy. The proxy then obtains the connection factory from an application server using a Java Naming and Directory Interface (JNDI). Using the connection factory, a connection to a connection host from the client is created. When the client sends a message, the proxy receives the message and routes the message to a destination server. Similarly, when the client receives a message, the proxy receives the message from a destination server and passes the message to the client. The client can be specifically configured to extend JMS operability to a desired language. In one embodiment the client is a .NET client.

Abstract: The present invention enables a store-and-forward service providing an efficient and reliable forwarding of messages stored in a message queue to a distributed destination. It provides customers with high availability and scalability for applications such as JMS queues and topics. It achieves load balancing and failover amongst all individual members of the distributed destination while ensuring that each message is delivered exactly once.

Abstract: A logging last resource (LLR) system can provide a transaction log and transaction data to a LLR resource after a number of two-phase-commit resources have been prepared. The LLR resource manager can operate on the transaction log and transaction data in an atomic fashion so that the local commit can be done. The local commit can be done by the LLR manager in an atomic manner.

Abstract: A logging last resource (LLR) system can provide a transaction log and transaction data to a LLR resource after a number of two-phase-commit resources have been prepared. The LLR resource manager can operate on the transaction log and transaction data in an atomic fashion so that the local commit can be done. The local commit can be done by the LLR manager in an atomic manner.

Abstract: An embodiment of the invention provides a pluggable persistent store for use with queuing and messaging servers, such as a JMS server, which can be used to provide reliable messaging. The persistent store is accessed by the messaging server via a standard Application Program Interface (API) or interface that includes asynchronous persistence capability. A lower level pluggable API or interface allows the plugging-in of different persistent mechanisms, that can be used to support different persistence sources, such as file systems and databases. The standard API, combined with an asynchronous persistence capability, together provide a simple, flexible, and high-performance reliable messaging system.

Abstract: Disclosed herein is a system and method for client interoperability. In one embodiment, a method for client interoperability comprises establishing a network connection between a client and a proxy. The client requests a connection factory from the proxy. The proxy then obtains the connection factory from an application server using a Java Naming and Directory Interface (JNDI). Using the connection factory, a connection to a connection host from the client is created. When the client sends a message, the proxy receives the message and routes the message to a destination server. Similarly, when the client receives a message, the proxy receives the message from a destination server and passes the message to the client. The client can be specifically configured to extend JMS operability to a desired language. In one embodiment the client is a .NET client.

Abstract: The present invention enables a store-and-forward service providing an efficient and reliable forwarding of messages stored in a message queue to a distributed destination. It provides customers with high availability and scalability for applications such as JMS queues and topics. It achieves load balancing and failover amongst all individual members of the distributed destination while ensuring that each message is delivered exactly once.

Abstract: A logging last resource (LLR) system can provide a transaction log and transaction data to a LLR resource after a number of two-phase-commit resources have been prepared. The LLR resource manager can operate on the transaction log and transaction data in an atomic fashion so that the local commit can be done. The local commit can be done by the LLR manager in an atomic manner.

Abstract: A logging last resource (LLR) system can provide a transaction log and transaction data to a LLR resource after a number of two-phase-commit resources have been prepared. The LLR resource manager can operate on the transaction log and transaction data in an atomic fashion so that the one-phase or local commit can be done. The one-phase or local commit can be done by the LLR manager in an atomic manner.

Abstract: An embodiment of the invention provides a pluggable persistent store for use with queuing and messaging servers, such as a JMS server, which can be used to provide reliable messaging. The persistent store is accessed by the messaging server via a standard Application Program Interface (API) or interface that includes asynchronous persistence capability. A lower level pluggable API or interface allows the plugging-in of different persistent mechanisms, that can be used to support different persistence sources, such as file systems and databases. The standard API, combined with an asynchronous persistence capability, together provide a simple, flexible, and high-performance reliable messaging system.