Patents by Inventor Ananthan Bala Srinivasan
Ananthan Bala Srinivasan has filed for patents to protect the following inventions. This listing includes patent applications that are pending as well as patents that have already been granted by the United States Patent and Trademark Office (USPTO).
-
Patent number: 7660879Abstract: 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.Type: GrantFiled: May 19, 2005Date of Patent: February 9, 2010Inventor: Ananthan Bala Srinivasan
-
Patent number: 7571215Abstract: 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.Type: GrantFiled: October 11, 2001Date of Patent: August 4, 2009Assignee: BEA Systems, Inc.Inventors: Dean Bernard Jacobs, Reto Kramer, Ananthan Bala Srinivasan
-
Patent number: 7287075Abstract: 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.Type: GrantFiled: January 9, 2003Date of Patent: October 23, 2007Assignee: BEA Systems, Inc.Inventors: Rahul Srivastava, Ananthan Bala Srinivasan, Eric M. Halpern, Dean Bernard Jacobs
-
Patent number: 7233989Abstract: 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.Type: GrantFiled: January 9, 2003Date of Patent: June 19, 2007Assignee: BEA Systems, Inc.Inventors: Rahul Srivastava, Ananthan Bala Srinivasan, Eric M. Halpern, Dean Bernard Jacobs
-
Patent number: 7152185Abstract: 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.Type: GrantFiled: January 9, 2003Date of Patent: December 19, 2006Assignee: BEA Systems, Inc.Inventors: Rahul Srivastava, Ananthan Bala Srinivasan, Eric M. Halpern, Dean Bernard Jacobs
-
Publication number: 20030236880Abstract: 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.Type: ApplicationFiled: January 9, 2003Publication date: December 25, 2003Inventors: Rahul Srivastava, Ananthan Bala Srinivasan, Eric M. Halpern, Dean Bernard Jacobs
-
Publication number: 20030229804Abstract: 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.Type: ApplicationFiled: January 9, 2003Publication date: December 11, 2003Inventors: Rahul Srivastava, Ananthan Bala Srinivasan, Eric M. Halpern, Dean Bernard Jacobs
-
Publication number: 20030225880Abstract: 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.Type: ApplicationFiled: January 9, 2003Publication date: December 4, 2003Inventors: Rahul Srivastava, Ananthan Bala Srinivasan, Eric M. Halpern, Dean Bernard Jacobs
-
Publication number: 20030023898Abstract: Data is replicated from a master server to a slave server on a network by first sending a start call from a master user level to a master service level on the master server, the start call containing version information for data on the master server. The information is then sent to a slave service layer on a slave server so the slave server layer can determine whether data on the slave server is current. The slave server layer can request a delta from the master server if the slave data is not current. A delta containing the information necessary to update the slave data is sent from the master service layer to the slave service layer so the slave service layer can process the delta and send the updated information to the slave user layer.Type: ApplicationFiled: October 11, 2001Publication date: January 30, 2003Inventors: Dean Bernard Jacobs, Reto Kramer, Ananthan Bala Srinivasan
-
Publication number: 20030018732Abstract: 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.Type: ApplicationFiled: October 11, 2001Publication date: January 23, 2003Inventors: Dean Bernard Jacobs, Reto Kramer, Ananthan Bala Srinivasan