Abstract: Secure communication between processes in cloud platform may be performed by receiving a request from a client application process hosted in an application virtual machine at a load balancer. A first secure communication channel is established between the client application process and the load balancer. The first secure communication channel is encrypted with the client certificate. The first secure communication channel is terminated at the load balancer. A service process in a service virtual machine is identified based on the request received from the client application process. A new request is sent to the service virtual machine to establish a second secure communication channel between the load balancer and the service virtual machine. The load balancer certificate signed by the internal certificate authority is validated at the service virtual machine. Upon successful validation of the load balancer certificate, the second secure communication channel is accepted at the service virtual machine.

Abstract: Secure communication between processes in cloud platform may be performed by receiving a request from a client application process hosted in an application virtual machine at a load balancer. A first secure communication channel is established between the client application process and the load balancer. The first secure communication channel is encrypted with the client certificate. The first secure communication channel is terminated at the load balancer. A service process in a service virtual machine is identified based on the request received from the client application process. A new request is sent to the service virtual machine to establish a second secure communication channel between the load balancer and the service virtual machine. The load balancer certificate signed by the internal certificate authority is validated at the service virtual machine. Upon successful validation of the load balancer certificate, the second secure communication channel is accepted at the service virtual machine.

Abstract: A method is described that comprises executing a non distributed transaction by reading persistent data from a database and performing executions with the persistent data. A prepare command is sent to the database after a change to be made to the persistent data as a consequence of the non distributed transaction's execution is confirmed. A commit command is sent to the database to cause the database to commit the change to the database.

Abstract: A method is described for managing an application's cached persistent data with different isolation levels. The different isolation levels include: 1) requesting a lock for a first item of database data in response to the first item of database data not being cached and not yet having been used by the application; 2) requesting a lock for a second item of cached database data in response to the second item of database data being updated for a first time by the application; and, 3) requesting a lock for a third item of cached database data in response to it being confirmed that the third item of database data will need to be updated in its database.

Abstract: A method is described for making a change in an object oriented relational database in which objects that represent items of persistent data are related to other objects that represent items of persistent data. The method comprises referring to a backward reference contained in a first object that does not have visibility to a second object that the first object is in a unidirectional relationship with. The first object represents a first item of persistent data. The second object represents another item of persistent data. The backward reference identifies the second object. The method also comprises removing the unidirectional relationship, adding a new unidirectional relationship from a third object to the first object, and modifying the backward reference to identify the third object rather than the second object. A cascade delete method that uses a backward reference is also described.

Abstract: A method is described for making a change in an object oriented relational database in which objects that represent items of persistent data are related to other objects that represent items of persistent data. The method comprises referring to a backward reference contained in a first object that does not have visibility to a second object that the first object is in a unidirectional relationship with. The first object represents a first item of persistent data. The second object represents another item of persistent data. The backward reference identifies the second object. The method also comprises removing the unidirectional relationship, adding a new unidirectional relationship from a third object to the first object, and modifying the backward reference to identify the third object rather than the second object. A cascade delete method that uses a backward reference is also described.

Abstract: A system and method are provided for interacting with a persistence layer. In an embodiment, a persistence layer may receive a representation of Enterprise Java Bean (EJB) metadata. The persistence layer may determine whether the representation of Enterprise Java Bean (EJB) metadata is compatible with a version of the EJB specification. In an embodiment, a representation of an Object-Relational (OR) mapping schema may be generated based, at least in part, on the representation of EJB metadata.

Abstract: A system and method are provided to inspect memory leaks. In one embodiment, a garbage collector at a virtual machine is requested to provide a garbage collection file at a predetermined time. The garbage collection file is provided at the predetermined time.

Abstract: A method is described for managing an application's cached persistent data with different isolation levels. The different isolation levels include: 1) requesting a lock for a first item of database data in response to the first item of database data not being cached and not yet having been used by the application; 2) requesting a lock for a second item of cached database data in response to the second item of database data being updated for a first time by the application; and, 3) requesting a lock for a third item of cached database data in response to it being confirmed that the third item of database data will need to be updated in its database.

Abstract: A method is described that comprises executing a non distributed transaction by reading persistent data from a database and performing executions with the persistent data. A prepare command is sent to the database after a change to be made to the persistent data as a consequence of the non distributed transaction's execution is confirmed. A commit command is sent to the database to cause the database to commit the change to the database.

Abstract: A method is described in which a reference to an item of persistent data is established because the item of persistent data is cached. The reference is maintained whether or not the item of persistent data is used by an application. The reference is maintained whether or not the item of persistent data is referred to by another reference, where, the another reference is to implement a relational database relationship. The method includes removing the item of persistent data from the cache because the item of persistent data was only referred to by the reference.

Abstract: A method and apparatus to provide a general-purpose timeout management system for client-specific session objects. In one embodiment a timeout service is created that may be used by more than one Java Enterprise EJB container simultaneously, avoiding unnecessary duplication of timeout management services. Each EJB container may instantiate an “invalidation agent” which registers a callback interface with the timeout service. The timeout service invokes a timeout callback method on registered invalidation agents at specified time intervals. The time intervals correspond to the timeout values associated with the client-specific objects, obviating the need for the EJB container to make time-consuming queries to the system clock. The invention discloses a “timeout marker” data element associated with each client-specific session object created by the EJB container. Whenever a client accesses a client-specific session object, the timeout marker associated with that object is cleared.

Abstract: A method is described for making a change in an object oriented relational database in which objects that represent items of persistent data are related to other objects that represent items of persistent data. The method comprises referring to a backward reference contained in a first object that does not have visibility to a second object that the first object is in a unidirectional relationship with. The first object represents a first item of persistent data. The second object represents another item of persistent data. The backward reference identifies the second object. The method also comprises removing the unidirectional relationship, adding a new unidirectional relationship from a third object to the first object, and modifying the backward reference to identify the third object rather than the second object. A cascade delete method that uses a backward reference is also described.

Abstract: A system and method for a connection resource system is disclosed. According to an embodiment of the invention, a method includes establishing a first connection, the first connection being between one of one or more server applications and one of one or more external resources; and establishing a second connection, the second connection being between one of the one or more server applications and one of the one or more external resources; wherein the first connection and the second connection are established utilizing a single resource system.

Abstract: A system and method are provided for interacting with a persistence layer. In an embodiment, a persistence layer may receive a representation of Enterprise Java Bean (EJB) metadata. The persistence layer may determine whether the representation of Enterprise Java Bean (EJB) metadata is compatible with a version of the EJB specification. In an embodiment, a representation of an Object-Relational (OR) mapping schema may be generated based, at least in part, on the representation of EJB metadata.