Bea Systems, Inc.

Oracle International Corporation

Bae Systems, Inc.

Christa Golding

Mitch Upton

Timothy A Potter

Rick DeGrande

Tim Potter

Highly-available processing of an asynchronous request can be accomplished in a single transaction. A distributed request queue receives a service request from a client application or application view client. A service processor is deployed on each node of a cluster containing the distributed request queue. A service processor pulls the service request from the request queue and invokes the service for the request, such as to an enterprise information system. If that service processor fails, another service processor in the cluster can service the request. The service processor receives a service response from the invoked service and forwards the service response to a distributed response queue. The distributed response queue holds the service response until the response is retrieved for the client application.

System and method for providing highly available processing of asynchronous requests using distributed request and response queues and a service processor

High availability event forwarding can be obtained utilizing distributed queues in a server cluster. Each server can receive an event from a data system, such as a database or SAP&#x2122; system. Event queues exist on servers in the cluster can store an event until, for example, the event is delivered to a user or retrieved for processing. An event processor examines the load of each event queue and selects the event queue with the lightest load. The event processor generates an alias for the selected queue, such that a user, integration system, or client application does not need to know the identity of the physical queue storing the event, but only needs to refer to the 'distributed queue' or alias. After a physical queue is selected and an alias assigned, the event is forwarded to the selected queue.

High availability for event forwarding

Local transactions are supported by an application view instance that can switch from a stateless session bean to a stateful session bean in order to open a connection for a local transaction. The state that the stateful session bean holds is ten the connection. The stateful session bean can hold the connection open across multiple requests in the local transaction interface allows a user to manage the transaction in the application view, and to switch the application view between a stateless session bean and a stateful session bean. A local transaction interface can contain a local transaction management contract, which enables an application server to provide an infrastructure and run-time environment for management of the transaction.

Systems and methods for application view transactions

High availability is obtained for the deployment and undeployment of application views by placing a redundant JMX server on each server in a cluster of servers for an application integration system. Each redundant JMX server can manage deployment work for the cluster, and is capable of sending a JMX notification to every other server in the cluster relating to the deployment work, such as a deploy, undeploy, or processing notification. While an administration server can manage the other servers in the cluster, the redundant JMX servers are capable of managing deployment work for the cluster in the event of a failure of the administration server. This description is not intended to be a complete description of, or limit the scope of, the invention. Other features, aspects, and objects of the invention can be obtained from a review of the specification, the figures, and the claims.

High availability application view deployment

Distributed request and response queues for service processor

Systems that use application view components to allow a user to exploit functionality in an EIS can utilize a shareable connection factory. Instead of having a connection factory for each application view, a single connection factory can be used that is simply referenced by each application view. Users can then choose to associate an application view with any available connection factory on the system, or can choose to create a new connection factory that can be available to any other application view or resource adapter.

Shared common connection factory

An adapter can be deployed into a system in a single step without recycle. An adapter can contain components, such as an integration adapter, event router, and resource adapter, which all conform to a given specification such that these components use some of the same classes. A class loader allows these components to share common classes, instead of having separate classes. A single Enterprise archive file contains files necessary to deploy the adapter, such as Web archive files, resource adapter archive files, event router Web application files, and shared Java archive files. The inclusion of these files in an Enterprise archive file allows all components for the adapter to be deployed in a single step without the need to recycle. This description is not intended to be a complete description of, or limit the scope of, the invention. Other features, aspects, and objects of the invention can be obtained from a review of the specification, the figures, and the claims.

Adapter deployment without recycle

System and method for providing highly available processing of asynchronous service requests

An integration component such as an application integration engine can be bundled as a single, self-contained J2EE Enterprise archive (EAR) file. The bundling of the component into an EAR file enables the component to be deployed to any valid system domain that is running and available. A recycling of the server then may be necessary only if a Java archive file is added to the classpath for non-system domains. This description is not intended to be a complete description of, or limit the scope of, the invention. Other features, aspects, and objects of the invention can be obtained from a review of the specification, the figures, and the claims.

Systems and methods for modular component deployment

High availability event forwarding can be obtained utilizing distributed queues in a server cluster. Each server can receive an event from a data system, such as a database or SAP&#x2122; system. Event queues exist on servers in the cluster can store an event until, for example, the event is delivered to a user or retrieved for processing. An event processor examines the load of each event queue and selects the event queue with the lightest load. The event processor generates an alias for the selected queue, such that a user, integration system, or client application does not need to know the identity of the physical queue storing the event, but only needs to refer to the 'distributed queue' or alias. After a physical queue is selected and an alias assigned, the event is forwarded to the selected queue. This description is not intended to be a complete description of, or limit the scope of, the invention. Other features, aspects, and objects of the invention can be obtained from a review of the specification, the figures, and the claims.

Growing community of inventors

Littleton, CO, United States of America

Christa Golding