Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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 then the connection. The stateful session bean can hold the connection open across multiple requests in the local transaction for the duration of the transaction. A 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.

Abstract: 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.

Abstract: 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.