Browse Prior Art Database

System and method for making a context based selection on Administration Service’s RPC in enterprise application servers Disclosure Number: IPCOM000200910D
Publication Date: 2010-Oct-29
Document File: 6 page(s) / 97K

Publishing Venue

The Prior Art Database


In general, the existing J2EE based distributed enterprise application servers provide the Remote Procedure Call (RPC) mechanisms based on SOAP Connector or RMI Connector, for their communication across Java Virtual Machines (JVM). SOAP is a preferred mechanism when there is a firewall in place. However SOAP calls consume more time to process the requests, because of its HTTP request/response nature. Approach based on RMI mechanism, will be faster than SOAP but pure RMI has a disadvantage that it cannot make it through a firewall. This article proposes a system and method for making a context based selection of RPC protocol to overcome performance issues.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 42% of the total text.

Page 01 of 6

System and method for making a context based selection on Administration Service's RPC in enterprise application servers

Executive Summary:

Disclosed is a system and method for making a context based selection of RPC protocol to overcome the performance issues in distributed J2EE enterprise application servers.


JEE based Enterprise Application Server:-

Application servers provide the runtime environment for application code. They provide containers and services that specialize in enabling the execution of specific Java application components. Each application server runs in its own Java virtual machine (JVM). For J2EE applications, the application server functions like an extended virtual machine for running the applications.

Deployment manager:-

Deployment manager manages multiple servers and nodes in a distributed server environment. It provides a single, central point of administrative control for all elements of the distributed server environment. It contains the master copies of the configuration and application data files for all nodes and servers. Node also has a local copy of the configuration and application data files from the master repository that are relevant to the node. The deployment manager can be located on the same machine as one of the application servers or on a separate machine.


Node agent is an administrative process runs on each node and manages application servers running under that node. The node agent is purely an administrative agent and is not involved in application serving functions. Each application server managed by nodeagent has the configuration data necessary to start itself. Nodeagent is like a mediator between deployment manager and application server. Node agent communicates with the deployment manager to coordinate configuration synchronization. To perform management operations on behalf of the deployment manager, also nodeagent communicates with application servers to manage (start/stop) each server.


A node is a logical grouping of managed server processes that share common configuration and operational control. A node is associated with one physical installation


Page 02 of 6

of application server.


A subnetwork, or subnet, is a logically visible, distinctly addressed part of a single Internet Protocol network. The process of subnetting is the division of a computer network into groups of computers that have a common, designated IP address routing prefix.


A firewall is a part of a computer system or network that is designed to block unauthorized access while permitting authorized communications. It is a device or set of devices which is configured to permit or deny computer applications based upon a set of rules and other criteria. All messages entering or leaving the intranet pass through the firewall, which examines each message and blocks those that do not meet the specified security criteria.


Simple Object Access Protocol, a lig...