Bea Systems, Inc.

Other

Oracle International Corporation

Ananthan Bala Srinivasan

Dean Bernard Jacobs

Eric M Halpern

Rahul Srivastava

Reto Kramer

A transactional distribution infrastructure enables multiple participants to work together to deploy changes to an executing context. Embodiments can prepare new changes to executing applications based on a copy of the running context or domain rather than the actual running domain. Performing the changes on a copy of the running domain rather than on the actual running domain allows the changes to be examined, therefore providing an opportunity to detect errors and prevent the changes from causing failures on the domain.

System and method for application deployment service

A mechanism for making changes consistently across an application server domain or a cluster. Server configuration consistency is absolutely necessary for cluster deployments. The invention allows changes to the configuration repository and to the application deployment process to be managed via a Data Replication Service (DRS). The former requires that the configuration repository be version aware, while the latter breaks down the application deployment process into two phases&#x2014;one for data distribution and processing as far as possible, and the second to expose the changes through the Java Naming and Directory Interface (JNDI).

System and method for using a data replication service to manage a configuration repository

Data can be replicated over a network using a one or two phase method. For the one phase method, a master server containing an original copy of the data sends a version number for the current state of the data to each slave on the network so that each slave can request a delta from the master. The delta that is requested contains the data necessary to update the slave to the appropriate version of the data. For the two phase method, the master server sends a packet of information to each slave. The packet of information can be committed by the slaves if each slave is able to process the commit.

Data replication protocol

A Node Manager monitors the status of multiple servers. The Node Manager detects server failures, periodically monitors server health status, and performs server maintenance. When the Node Manager detects a server failure, it determines whether or not the server should be restarted. While periodically monitoring servers, the Node Manager may determine how often to trigger a health check, how long to wait for a response, and how to proceed if the server is deemed failed. The Node Manager may be controlled by an Administrative Server directly or by an external administrative agent. An administrative agent may control the Node Manager by interfacing with the Administrative Server. The Node Manager and AS may authenticate each other and encode their communications to each other for increased security.

Growing community of inventors

San Francisco, CA, United States of America

Ananthan Bala Srinivasan