Abstract:
A system and method for a program object to support generation of connections is disclosed. An embodiment of a method comprises establishing a first program object, the program object being designated as the connection factory for a plurality of program objects; receiving a request for a connection factory by the first program object; sending a request for the connection factory from the first program object; obtaining an instance of the connection factory; and deploying a program connection using the connection factory.

Description:
TECHNICAL FIELD  
       [0001]     Embodiments of the invention generally relate to the field of client/server systems and, more particularly, to a system and method for a program object to support connection generation.  
       BACKGROUND  
       [0002]     A conventional server system may include an application server that includes certain applications. The server system may provide interfaces to certain external resources. The server may include a J2EE (Java 2 Enterprise Edition) compatible system. In operation of the server system, connections may be required between the applications and the external resources. To produce such connections, an entity may make a request to generate an instance of a connection factory, the connection factory being a program object to generate a connection between an application and an external resource.  
         [0003]     However, a program object, such as an enterprise Java bean (EJB), may have multiple different properties that are specified for connection requirements. With the possible combinations of these properties, numerous different connection factories may be needed to provide all possible combinations of properties.  
         [0004]     Further, the process of generating a connection factory may require numerous operations. For example, a connection factory may be a serializable object. Under common connection requirements, serialization will be required to bind each of the different connection factory objects. Further, when a connection factory is requested, deserialization using the serialized form of the object and the appropriate class loader is then done in order to return a new instance of the connection factory. These operations may be time-consuming and thus slow the process of establishing connections for server applications.  
       SUMMARY OF THE INVENTION  
       [0005]     A system and method for a program object to support connection generation is described.  
         [0006]     Under an embodiment of the invention, a method comprises establishing a first program object, the program object being designated as the connection factory for a plurality of program objects; receiving a request for a connection factory by the first program object; sending a request for the connection factory from the first program object; obtaining an instance of the connection factory; and deploying a program connection using the connection factory.  
         [0007]     Under another embodiment of the invention a method comprises receiving a request for a connection factory from a program object, the connection factory to produce a connection between a program application on a server and an external resource, the request being received by a resource object factory in proxy for the server resource system; requesting a connection factory to produce the connection; receiving the connection factory; and returning the connection factory to the requesting program object.  
         [0008]     Under another embodiment of the invention a server system comprises an application container, the application container comprising a program application; an interface with an external resource, the external resource to be connected to the program application; a resource system to provide for the connections between the program application and the external resource; and a resource object factory, the resource object factory to assist in the establishment of the connection between the program application and the external resource.  
     
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0009]     Embodiments of the invention are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings in which like reference numerals refer to similar elements.  
         [0010]      FIG. 1  is an illustration of an embodiment of a server utilizing a resource object factory to support a resource system;  
         [0011]      FIG. 2  is an illustration of an embodiment of a server utilizing a resource object factory;  
         [0012]      FIG. 3  is an illustration of JNDI interfaces and naming manager for an embodiment of the invention;  
         [0013]      FIG. 4  is an illustration of a process of establishing a connection factory and generating an instance of the connection factory;  
         [0014]      FIG. 5  is an illustration of an embodiment of the establishment of a connection factory utilizing a resource object factory; and  
         [0015]      FIG. 6  is an illustration of an embodiment of a process for obtaining a connection factory.  
     
    
     DETAILED DESCRIPTION  
       [0016]     Embodiments of the invention are generally directed to server operations. Under an embodiment of the invention, a system may include a program object to support generation of connections.  
         [0017]     Under an embodiment of the invention, a program object is provided to assist in generation of connections. The program object is to assist in the processing of requests for connections between a server system and various resources. Under an embodiment of the invention, a resource object factory acts as a proxy between an entity and a resource system for processing connections. Under an embodiment of the invention, the resource object factory acts to tune up and assist in the operation of a resource system and to manage the lifecycle of connection factories.  
         [0018]     Under an embodiment of the invention, a resource system is a system for providing communications between containers on the server, each container being a container being an entity to provides life cycle management, security, deployment, and runtime services to program components, and resources such as JDBC connector, JMS connector, and connector container services. Under an embodiment of the invention, a resource object factory assists in the generation of connections, such as in supporting the operation of the resource system. Under an embodiment of the invention, a server may include a server that is compatible with the J2EE (Java 2 Enterprise Edition) specification, version 1.4, Nov. 24, 2003. Under an embodiment of the invention, the resource object factory may be utilized to assist in the provision of connections for the server in conformity with the J2EE Connector Architecture Specification (JCA), including version 1.0 Aug. 22, 2001 and version 1.5, Nov. 24, 2003.  
         [0019]     According to an embodiment of the invention, in the establishment of a connection, an entity may request generation of an instance of a connection factory from a resource system and a JNDI (Java Naming and Directory Interface). A JNDI is described in the JNDI Application Programming Interface (API), version 1.2, Jul. 14, 1999, and the JNDI Server Provider Interface (SPI), version 1.3, Jul. 14, 1999. Under an embodiment of the invention, a resource object factory acts as a proxy between the entity and the resource system and the JNDI, acting to process connection factory requests. Under an embodiment, the resource object factory will be used by each resource reference object within the JNDI namespace in the generation of connection factories. A connection factory is generally an object that produces connection objects that enable a component to access a resource. Under an embodiment of the invention, each resource reference declares the resource object factory to be the object factory for the resource reference, and the resource object factory then acts as the recipient of connection factory requests.  
         [0020]     The J2EE connector architecture provided by the JCA enables J2EE components to interact with enterprise information systems (EISs) and for the EISs to interact with J2EE components. A resource adapter is a component that implements the J2EE connector architecture for a specific EIS. A connector is a mechanism to provide connectivity to EISs, with a connector being specific to a particular EIS and consisting of the resource adapter and any application development tools for EIS connectivity. A resource adapter is generally stored in a resource adapter archive (RAR) file and can be deployed on any J2EE server to mediate communication between the server and the EIS via contracts.  
         [0021]     Pursuant to the JCA, an Enterprise Java bean may specify certain elements that are otherwise optional in J2EE deployment. These objects are res-sharing-scope to indicate whether a connection to a resource manager is shareable or unshareable; res-auth to indicate whether there is a programmatic sign-on to an EIS; and non-transactional, which indicates whether the resource adapter may be involved in a global transaction, if any. With combinations of these properties (each having two possible values), it may be necessary to bind eight different connection factories. A connection factory is generally from type javax.resource.cci.ConnectionFactory, which is thus java.io.Serializable. Serialization describes the process of converting object instances into a linear stream of bytes (thus a serial data stream), which may be done for purposes of transferring, storing, or manipulating data. For each of such eight connection factories, serialization will occur each time any of these items is bound. Further, deserialization will occur each time there is a look up of one of such connection factories.  
         [0022]     However, under the JNDI specification, it is also possible to bind objects of type reference instead of the serializable type that is specified for a connection factory. A reference object contains information, denoted as RefAddr properties to be stored within the reference object. The information may include the name of the object factory, which can be utilized to restore the object. Under an embodiment of the invention, the resource object factory is specified as an object factory for each relevant reference. In this way, the resource object factory acts as the recipient of each connection factory request, without requiring the serialization of the resource object factory on binding and the deserialization of a serialized object on look up. Under an embodiment of the invention, a connection factory that is provided is a Java object working in the same virtual machine as the resource object factory.  
         [0023]     Under an embodiment of the invention, a resource object factory is enabled by making the object factory singleton. A singleton is a design pattern that supports creation of only one instance of a class. Therefore, the resource object factory will support the creation of a single factory object to operate as the connection factory for each reference.  
         [0024]     Under an embodiment of the invention, normal bind and lookup operations may also then be modified to improve efficiency of operations. For example, utilizing the reference object, a bind operation for the connection factory may be replaced with an add to a given data structure. The lookup may then be replaced by getting the object from the given data structure. Under an embodiment of the invention, the name of the requested connection factory are included in the RefAddr properties specified under the JCA, these being the shareable property, the authority property, and the non-transaction property. The connection factory name thus will be:  
         [0025]     RefAddr: valueOfShareableProperty+valueOfResAuthProperty+valueOfNonTransactionProperty+nameOfRequestedConnecionFactory  
         [0026]     Under an embodiment of the invention, each instance of a connection factory is configured by passing the connection factory an appropriate connection manager. Therefore, a connection factory then may be modified and controlled by controlling the underlying connection manager. For example, the connection manager may be started or stopped or the properties of the connection manager may be changed. The properties of a connection manager then may be changed through the JNDI. Under an embodiment of the invention, a managed connection factory wrapper (MCFWrapper) is bound at deployment time and contains properties needed for an underlying resource system. The managed connection factory wrapper includes the managed connection factory object, which will serve as the factory for connection factory objects. The managed connection factory wrapper is cached within the resource object factory after the start of a given connection factory, and thus a change of properties for the connection factory can be made by invoking appropriate methods of the resource object factory.  
         [0027]      FIG. 1  is an illustration of an embodiment of a server utilizing a resource object factory to support a resource system. In  FIG. 1 , an application server  105  includes an application  110 . In  FIG. 1 , a resource system  115  is included to provide for connections between applications and resources, which in this instance may include a connection between the application  110  in application server  105  and an external resource  125 , as shown connected by resource adapter  120 . Under an embodiment of the invention, a resource object factory  130  is provided to assist the resource system  115  in the establishment of connections. The resource object factory  130  may be designated as the object factory for any reference. Under an embodiment of the invention, the resource object factory  130  acts as a proxy for receipt of a connection factory request  135 .  
         [0028]      FIG. 2  is an illustration of an embodiment of a server utilizing a resource object factory. In this illustration, program object containers include an enterprise Java bean (EJB) container  205 , a web container  210 , and another arbitrary container  215 . External resources include a database pool  225  that may be connected using a JDBC (Java database connection) connector server  220 , a JMS (Java message service provider)  235  that may be connected utilizing JMS connectors  230 , and a proprietary service  245  that may be connected using JCA (Java connector architecture) connectors  240 . The resource system  250  includes a connection manager  255 , and utilizes a connector container  260  to store managed connections. A transaction manager  265  maintains a relationship with the resource system  250 . Under an embodiment of the invention, a resource object factory  200  is present to assist the resource system  250  in the generation of connections between applications and resources. If a connection factory request is received, the resource object factory  250  acts as proxy for the request.  
         [0029]     The JNDI architecture consists of the JNDI API and the JNDI SPI. The JNDI API allows Java applications to access a variety of naming and directory services. The JNDI SPI is then used by multiple service providers, including directory service providers. The JNDI Service Provider Interface (SPI) provides the means by which naming and directory services are integrated into the JNDI framework. This arrangement enables a variety of directory and naming services to be plugged in transparently to a Java application.  
         [0030]      FIG. 3  is an illustration of JNDI interfaces and naming manager for an embodiment of the invention. In this illustration, a Java application  305  communicates with the JNDI naming manager via the JNDI API  310 . Similarly, any of the illustrated service providers  325  would communicate with the JNDI naming manger  315  via the JNDI SPI  320 . Under an embodiment of the invention, a request for a connection factory may be made to the JNDI naming manger and respectively to the resource object factory. However, under an embodiment of the invention, the JNDI properties may be used to modify connection factory processes. Using the reference type allowed by the JNDI API  310 , a connection factory is implemented through the JDNI naming manager  315  without requiring the normal serialization and deserialization processes.  
         [0031]      FIG. 4  is an illustration of a process of establishing a connection factory and generating an instance of the connection factory. In this illustration, there is a bind operation for the connection factory  405 . However, a program object may include certain properties, as specified by the J2EE connection architecture. With the varying properties, there may be a number of different connection factories  410  needed to support the connection architecture. Each of the connection factories is serializable, and thus serialization  415  is required in the binding operation for each factory.  
         [0032]     To generate an instance of a connection factory, there is a lookup operation  420 . For each of the multiple connection factories, there is a deserialization operation  425 , converting the serialized version of the program object data. The deserialized factory then may be utilized in the process of generating and returning an instance of the connection factory  430 . As illustrated in  FIG. 4 , multiple operations are needed to generate the connection factory. A connection factory needs to be bound for each combination of properties for the program object, and each of these connection factories is then serialized. Then, a deserialization operation is required each time there is a request to generate an instance of a connection factory.  
         [0033]      FIG. 5  is an illustration of an embodiment of the establishment of a connection factory utilizing a resource object factory. In this illustration, a resource object factory is used to assist in generating connection factories without the need for excessive operations. In  FIG. 5 , the connection factory is bound as a reference object  505 , and not as a serializable object. The resource object factory is then specified as the object factory for each reference  510 . Instead of an expensive serializing operation for each connection factory, there is an add operation  515 , in which the name of the resource is added to the properties of a reference object and thus a bind operation followed by serialization of the simple reference object, instead of the complex connection factory.  
         [0034]     To deploy a connection factory, there is a lookup request  520 , which, because of the establishment of a resource object factory, results in a get object instance request  525  to the resource object factory. There is then a request for an instance of the connection manager  530 , and a request to create a connection factory using the connection manager  535 . In the processes shown in  FIG. 5 , generation of a connection factory may be accomplished using the support of a resource object factory without the serialization and deserialization of the resource object.  
         [0035]      FIG. 6  is an illustration of an embodiment of a process for obtaining a connection factory. In this illustration, a resource object factory has been specified as an object factory for the reference, thereby allowing a streamlined process for obtaining a connection factory. An enterprise Java bean (EJBA)  605  requests a connection factory lookup  640 , with a resource object factory being designated as the object factory for the connection factory. According to an embodiment of the invention, the connection factory is bound as javax.naming.reference. The JNDI provider initial context  610  provides a get object instance request  642  to the JNDI naming manager  615 . An initial context is generally configured to have bindings to useful starting contexts in different naming and directory systems. In this instance, the JNDI naming manager  615  loads  644  the class of the resource object factory. Under an embodiment of the invention, the resource object factory acts as the object factory for each resource reference in the JNDI namespace. Following the load class return  646 , the JNDI naming manager  615  provides a get object instance request to the resource object factory  620 . The resource object factory  620  provides a get factory request  650  to an adapter cache  650 , with the reference address of the reference object being used to determine which adapter cache will process the request. The adapter cache  625  then makes a new instance  652  of the connection manager  630 . After the return of the new instance of the connection manager  654 , the adapter cache provide a create connection factory request  656  to the managed connection factory, using the connection manager as an argument. The managed connection factory acts as a factory for connection factories and managed connections.  FIG. 6  then illustrates the returns for the create connection factory request  658 , the get factory request  660 , the get object instance request  662  and  664 , and the connection factory lookup  668 .  
         [0036]     It should be appreciated that reference throughout this specification to “one embodiment” or “an embodiment” means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Therefore, it is emphasized and should be appreciated that two or more references to “an embodiment” or “one embodiment” or “an alternative embodiment” in various portions of this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures or characteristics may be combined as suitable in one or more embodiments of the invention.  
         [0037]     Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure aiding in the understanding of one or more of the various inventive aspects. This method of disclosure, however, is not to be interpreted as reflecting an intention that the claimed invention requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this invention.