Method for storing credentials in a J2EE connector architecture
View Patent ↗A connector architecture implementation that is J2EE compliant and provides improved connection management capabilities. The connector architecture implementation provides a connector leak detection mechanism that detects connection leaks both automatically and manually. The connector architecture implementation pre-configures and manages the growth and reduction of a connection pool. The connector architecture implementation may be pre-configured by pre-populating the connection pool. Connection pool growth may be managed by generating connections in response to connection requests. A connection pool may also be configured to reduce the number of connections in the pool. The number of connections may be reduced if the connection demand decreases. Password credentials allowing access to services are used to provide additional connection management.
1. A computer-implemented method to support a connector architecture comprising:
deploying at least one resource adapter in an application server to connect the application server with an enterprise information system;
initiating a connection pool at the application server, running on one or more microprocessors, to handle a connection request to the enterprise information system, wherein the connection pool is managed under a connection management contract between the application server and the resource adapter;
pre-populating the connection pool with an initial number of managed connection objects, wherein each said managed connection object is an application level entity that is adapted to connect an application component to the enterprise information system;
receiving a request for a connection to the enterprise information system from an application component on the application server;
instantiating a resource object in the application server for accessing the enterprise information system in response to the connection request;
obtaining an initiating principal associated with the application component making the connection request by querying security code of the application server;
obtaining credentials from the application server for the initiating principal; and handling the connection request to the enterprise information system with an existing managed connection object pre-populated in the connection pool after obtaining the credentials for the initiating principal;
allowing the connection pool to store call stacks of where each connection is located, in order to allow a user to debug an application component that fails to close connection objects.
2. The computer-implemented method of claim 1 , further comprising:
integrating the application server with the enterprise information system.
3. The computer-implemented method of claim 1 , further comprising:
instantiating a subject object;
associating the credentials to the subject object; and
associating the subject object with the resource object.
4. The computer-implemented method of claim 3 , further comprising:
adding the credentials to a private set in the subject object.
5. The computer-implemented method of claim 3 , further comprising:
allowing the subject object to be an instance of a security authentication subject class.
6. The computer-implemented method of claim 1 , further comprising:
determining, based on the credentials in a subject object associated with the resource object, whether the connection request to the enterprise information system through the resource adapter can be fulfilled with an existing managed connection objects in the connection pool.
7. The computer-implemented method of claim 1 , further comprising:
determining the initial number of managed connection objects based on an initial capacity element in a descriptor file that specifies how many managed connections the connection pool should be pre-populated with at the deployment of the at least one resource adapter.
8. The computer-implemented method of claim 1 , further comprising:
deploying at least another one resource adapter to connect the application server with another enterprise information system;
initiating another connection pool at the application server to handle a connection request to the another enterprise information system, wherein the another connection pool is also managed under a connection management contract between the application server and the resource adapter; and
pre-populating the another connection pool with another initial number of managed connections.
9. The computer-implemented method of claim 1 , further comprising:
using a garbage collector to recycle said managed connections automatically.
10. A non-transitory computer-readable storage medium, storing instructions to support a connector architecture, the instructions comprising:
deploying at least one resource adapter in an application server to connect the application server with an enterprise information system;
initiating a connection pool at the application server to handle a connection request to the enterprise information system, wherein the connection pool is managed under a connection management contract between the application server and the resource adapter;
pre-populating the connection pool with an initial number of managed connection objects, wherein each said managed connection object is an application level entity that is adapted to connect an application component to the enterprise information system;
receiving a request for a connection to the enterprise information system from an application component on the application server;
instantiating a resource object in the application server for accessing the enterprise information system in response to the connection request;
obtaining an initiating principal associated with the application component making the connection request by querying security code of the application server;
obtaining credentials from the application server for the initiating principal associated with the application component making the connection request; and
handling the connection request to the enterprise information system with an existing managed connection object pre-populated in the connection pool after obtaining the credentials for the initiating principal;
allowing the connection pool to store call stacks of where each connection is located, in order to allow a user to debug an application component that fails to close connection objects.
11. The non-transitory computer-readable storage medium of claim 10 , wherein the connector architecture is an architecture for integrating the application server with enterprise information systems.
12. A system to support a connector architecture comprising:
one or more microprocessors;
an application server running on the one or more microprocessors, wherein the application server operates to
connect with an enterprise information system via at least one resource adapter; initiate a connection pool at the application server to handle a connection request to the enterprise information system, wherein the connection pool is managed under a connection management contract between the application server and the resource adapter;
pre-populate the connection pool with an initial number of managed connection objects, wherein each said managed connection object is an application level entity that is adapted to connect an application component to the enterprise information system;
receive a request for a connection to the enterprise information system from an application component on the application server;
instantiate a resource object in the application server for accessing the enterprise information system in response to the connection request;
obtain an initiating principal associated with the application component making the connection request by querying security code of the application server;
obtain credentials from the application server for the initiating principal; and
handling the connection request to the enterprise information system with an existing managed connection object pre-populated in the connection pool after obtaining the credentials for the initiating principal;
allow the connection pool to store call stacks of where each connection is located, in order to allow a user to debug an application component that fails to close connection objects.