Bea Systems, Inc.

Oracle International Corporation

Bae Systems, Inc.

Mitch Upton

Christa Golding

Timothy A Potter

Rick DeGrande

Tim Potter

An application view control can allow users of a software tool to interact with Enterprise applications using simple Java APIs. This can allow a user who is not an expert in the use of a given Enterprise system to utilize its capabilities in a manner a Java programmer can understand. A developer can invoke application view services both synchronously and asynchronously, and can subscribe to application view events. The developer can use simple Java objects in both the service and event cases. The developer need not understand XML, or the particular protocol or client API for the Enterprise application, such as an Enterprise Information System (EIS).

System and method for enterprise application interactions

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

A service adapter can be used to connect a client application to an enterprise system, or to connect application components, that otherwise might be unable to communicate with each other. A service adapter can invoke a service in the enterprise system, and can allow requests to be received to, and responses received from, the enterprise system. The service adapter can pass these requests and responses in a format such as XML, and can transform data passing between the enterprise system and an application or application component. An application view component can be used to provide an interface to an enterprise system for an application.

System and method for implementing a service adapter

Communication can be passed between components, such as an enterprise system and a client application, by utilizing schemas. A schema can ensure that a communication, such as a request or response, is in the proper format for one of the components. For instance, metadata can be received from an enterprise system in response to a request from a client application. That metadata can be transformed into an XML document that conforms to an XML schema, such as by an XML schema mechanism. At least portions of the XML document can be validated against the XML schema, such as by using a schema object model. The XML document can be passed on to the client application after validation. This description is not intended to be a complete and accurate description of the invention or to 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.

System and method for implementing a schema object model in application integration

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

Events can be extracted from a resource such as an enterprise system using an application view component in combination with an event adapter. The event can be pulled by a client application or pushed by the enterprise system. The application view component can provide an interface to the enterprise system for the client application. The event adapter allows the enterprise system to initiate communication with, or receive communication from, the client application. The event adapter can extract data about the event from the enterprise system, create an object such as an XML-based object containing the data, and notify the application view component. The application view component can pass the event to the client application.

System and method for implementing an event adapter

Functionality can be built upon the J2EE Connector architecture when integrating applications. Bi-directional communication can be added to the system, and a common protocol can be used so that each application does not need to be integrated with every other application. A common protocol can be used, such as by application view components, to allow applications having different protocols to communicate with each other, as well as with components such as enterprise system and integration system components. The applications do not have to know the other protocols, or even that they exist.

System and method using a connector architecture for application integration

An application view, which can represent a self-describing interface to functionality in a resource such as an application or enterprise system, can configure a security principal for a validated system user. A resource adapter can receive the request from the application view and can use a security principal map to map the security principal to a resource-appropriate principal. The resource adapter can perform a resource sign-on in a manner specific to the resource using the resource-appropriate principal.

Systems and methods for integration adapter security

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

A Java-based interface can be used to allow a Java client or application to access an application view component. An application view component can provide an interface to an application or enterprise system, using a resource adapter to expose functionality in the enterprise system. A Java-based interface for the resource adapter can allow the Java client to access the application view component. The interface can be a design-time graphical user interface, which can include a set of Java server pages and can be Web-based. The interface can allow a Java client to access the application view component in order to accomplish a task such as creating, defining, deploying, and testing the application view component. Each of these tasks can have their own page in the interface, such as a Java server page.

System and method for providing a java interface to an application view component

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.

Growing community of inventors

Highlands Ranch, CO, United States of America

Mitch Upton