Abstract: One embodiment of the present invention relates to a system that enables a single software application instance to support multiple tenants, wherein each tenant is associated with a separate database. First, the software application instance receives an input, wherein the input requires an operation to be performed on a database of one of the supported tenants. Next, the software application instance identifies the tenant with which the input is associated. The software application instance then obtains a context associated with the tenant. From the context, the software application instance obtains a service object. Finally, the software application invokes a method provided by the service object's class. This enables a data access object, which is encapsulated within the service object, to perform the operation on the database.

Abstract: Individuals using a data management system are provided the capability to make corrections to default values presented in a simulation of at least part of a webpage including default data indicating the layout of the webpage, and/or one or more identified data fields determined by heuristic analysis and/or from data collected from other individuals/users. These contributing individual corrections are then transformed into contributing individual originated parser scripts associated with the webpage. The contributing individual originated parser scripts are then implemented and/or applied to the webpage for all individuals, including the contributing individual.

Abstract: The disclosed embodiments provide a system that authenticates a user. During operation, the system identifies a first tenant associated with a first request for a first resource from the user and obtains an authentication policy for the first tenant. Next, the system uses an authentication mechanism associated with the authentication policy to authenticate the user. Upon authenticating the user, the system provides a first security token for enabling access to the first resource by the user.

Abstract: Various embodiments of a system and method for each node in a cluster including a peer-to-peer communication channel compiling and maintaining its own cluster membership are disclosed. In one embodiment, each cluster node may be coupled to every other node and commonly-accessible storage through a network. When a node starts up and attempts to join the cluster, it may access cluster information data stored in the commonly-accessible storage. This information may include a list of all nodes that are potential cluster members. Based on the cluster membership information, the joining node may request a peer-to-peer connection with each potential cluster member. When such a request results in establishment of a connection, the joining node may add the name of the target node to its cluster membership list. Likewise, when a member node grants a connection to a node, it may add the joining node to its cluster membership list.

Abstract: Various embodiments of a system and method for balancing nodal loading in a cluster are disclosed. In a cluster, each node may execute an instance of a distributed application component. A pluggable load balancer may receive requests targeted at the application component. For each request, the load balancer may invoke a pluggable load-balancing function to determine a next node to which the request should be forwarded to balance the workload of the cluster nodes. Each node of the cluster may include a load-balancing framework that provides a standard load-balancing API. In order to determine the next node to which a request should be milted, the load balancer may send requests for node information conforming to the API, to the cluster members. This information may include nodal CPU speed, memory capacity, number of queued requests, and number of requests serviced during a specified time period.

Abstract: Various embodiments of a system and method for failing over one cluster node to another are disclosed. The system may include a client networked to a cluster of computer nodes, connected to a persistent data store such as a database resident on a backend system. Each node of the cluster may be configured to run a distributed application component. The client may be configured to communicate with an instance of the application running on a first node. The client may include an augmented stub capable of accessing the instance of the application on the first node and capable of detecting a failure of the first node. In response to detecting a failure in the first node, the augmented stub may be capable of failing over to a second node and accessing the instance of the application on the second node, transparently to the client.

Abstract: Computer systems often strive to retrieve and process data from multiple sources. Integration and processing of data from multiple data sources tends to increase processing demands and decrease throughput due to the additional deployment of computational resources for handling multiple sources. An executable entity, such as a bean, which accesses each data source by the location of the data objects, and retrieves data objects corresponding to rows of data, is operable to access a plurality of data sources independently of the storage medium (i.e. DBMS), or format, and aggregate multiple objects from each of the data sources into a set of compound objects, in which each compound object includes associated fields from the accessed objects of the individual data sources.