Abstract: A method for using available server threads to process resources and reduce the overall time of performing XA interactions in two-phase commit protocol implemented by the transaction manager. A TM processing XA interactions dispatches interaction commands for multiple resources to a thread manager, which dispatches the commands to idle server threads. In one embodiment, the TM attempts to dispatch all but one of the interaction commands to separate threads. The primary thread then processes the remaining resource command. Any commands relating to dispatch requests that were unable to be dispatched to separate threads due to unavailability are processed by the primary thread. Once the primary server has processed its interaction commands and received a signal indicating the threads receiving dispatch requests have completed their respective processing of dispatched commands, the next group of commands is processed in a similar manner.

Abstract: A system and method for an extendable application framework, comprising a user interface, at least one service, at least one extension, wherein one of the at least one extensions can provide access to functionality in the user interface, and wherein one of the at least one services can provide access to functionality in one of the at least one extensions.

Abstract: An improved resource pool is provided that provides for dynamic configuration and is comprised of code that is configured to be used for different subsystems, including JDBC, Connector, and JMS subsystems. Pool maintenance, resource object creation and timeout, multiple deque management, and pool state transition features are provided. An application server may include at least one resource pool object, wherein each resource pool object represents a resource pool in the application server. An improved prepared statement cache is also provided that works in conjunction with the resource pool implementation to more effectively provide for prepared statement processing.

Abstract: A two-phase deployment framework can allow multiple types of components to register and be part of a two-phase deployment.

Abstract: An embodiment of the invention provides a pluggable persistent store for use with queuing and messaging servers, such as a JMS server, which can be used to provide reliable messaging. The persistent store is accessed by the messaging server via a standard Application Program Interface (API) or interface that includes asynchronous persistence capability. A lower level pluggable API or interface allows the plugging-in of different persistent mechanisms, that can be used to support different persistence sources, such as file systems and databases. The standard API, combined with an asynchronous persistence capability, together provide a simple, flexible, and high-performance reliable messaging system.

Abstract: Providing a framework for developing, deploying and managing sophisticated mobile solutions, with a simple Web-like programming model that integrates with existing enterprise components. Mobile applications may consist of a data model definition, user interface templates, a client side controller, which includes scripts that define actions, and, on the server side, a collection of conduits, which describe how to mediate between the data model and the enterprise. In one embodiment, the occasionally-connected application server assumes that data used by mobile applications is persistently stored and managed by external systems. The occasionally-connected data model can be a METAdata description of the mobile application's anticipated usage of this data, and be optimized to enable the efficient traversal and synchronization of this data between occasionally connected devices and external systems.

Abstract: Business logic plug-ins can be implemented as Java classes that perform specialized processing of business messages as those messages pass through an integration engine, such as a “B2B” engine for business-to-business messaging. Logic plug-ins can insert rules and business logic along the path traveled by business messages as they make their way through the B2B engine. Logic plug-ins can be defined and stored in an integration repository and executed in the B2B engine, and can be transparent to users. The plug-ins can utilize a plug-in framework, composed of a plug-in manager, as well as interfaces and mechanisms for plug-ins to implement. A plug-in manager can manage all plug-ins in the framework, can be a concrete implementation of the plug-in framework on the server, and can be a central hub through which all plug-in related client requests are routed. This description is not intended to be a complete description of, or limit the scope of, the invention.

Abstract: A system and method to update a patch index such that one or more properties in the patch index are associated with the patch, wherein the patch includes one or more components for the target software system; updating a class path at run-time for the target software system such that the patch associated with each one of the one or more properties supersedes prior patches for the same property; and wherein a component can include a class.

Abstract: An event server receiving input streams of events and producing output streams of events is adapted to be clustered with other event servers. The event server uses configuration data to control the event processing. The event server multicasting updates of the configuration data to the other event servers of the cluster and receiving multicasted configuration updates from one of the other event servers of the cluster.

Abstract: An event server adapted to receive events from an input stream and produce an output event stream. The event server uses a processor using code in an event processing language to process the events. The event server obtaining input events from and/or producing output events to a cache.

Abstract: There are provided mechanisms and methods for mapping information from disparate data sources into a single user profile. Embodiments can provide the capability to work with profiles for users as well as for other entities. These external data sources can include, without limitation: relational databases, file system and Java classes, Enterprise Java Beans (EJBs), Lightweight Directory Access Protocol (LDAP) servers and other network accessible sources. These mechanisms and methods can enable creating a single user profile from attributes residing in disparate data stores. The ability of embodiments to provide mechanisms and methods for creating a single user profile from attributes residing in disparate data stores can enable easier configuration of profiles, without requiring users to write code to perform the mapping.

Abstract: A highly available transaction recovery service migration system in accordance with one embodiment of the present invention implements a server's Transaction Recovery Service (TRS) as a migratable service. In one embodiment of the present invention, the TRS is a server instance or software module implemented in JAVA. The TRS migrates to an available server that resides in the same cluster as the failed server. The migrated TRS obtains the TLOG of the failed server, reads the transaction log, and performs transaction recovery on behalf of the failed server. The migration may occur manually or automatically on a migratable services framework. The TRS of the failed server migrates back in a fail back operation once the failed primary server is restarted. Failback operation may occur whether recovery is completed or not. This expedites recovery and improves availability of the failed server thereby preserving the efficiency of the network and other servers.

Abstract: 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—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).

Abstract: Backing files and backing contexts can be associated with portal elements controls for the construction of a portal. The backing files and backing contexts can allow interactions with the portal element controls before rendering. In one embodiment, developers are allowed to have access to backing files and backing contexts. The backing files allows developer code to be run before rendering. The backing contexts allow the setting and getting of information from the portal element controls.

Abstract: A dynamic dependency representation 402 may be iteratively constructed and maintained as resources are changed, including resources that are automatically generated. A type differencing component 404 can be employed to more accurately identify when dependent resources should be analyzed or built. And an ordered task set 406 can be used to order the scheduled analysis or build tasks such that duplicate work is reduced or avoided.

Abstract: A computer-implemented system that can support executing a third party module with Web Servers comprises one or more web server instances, a third party module that interacts with the one or more web server instances, and an execution environment that contains a web server wrapper instance that can encapsulate a web server instance of the one or more web server instances. The web server wrapper instance is associated with a web server configuration tool that can configure the one or more web server instances based on the third party module.

Abstract: A system and method for layered application server processing. Embodiments of the system are particularly useful in extreme transaction processing (XTP) environments to support hundreds of thousands of simultaneous users, and perhaps millions of simultaneous transactions. Applications can be built from service components. Mashups can be performed on applications, services, and data, to create a more dynamic form of application. Data center consolidation and server virtualization techniques can be used to distribute applications over multiple machines or data centers. A horizontal Operating System (OS) fabric is then used to integrate components of the data centers in a dynamic fashion, including for example integrating portal or Service Component Architecture (SCA) components into personality profiles that can be federated over many (e.g. thousands) of Java machines and data centers.

Abstract: A method for adaptively authenticating a subject, said method adapted to cooperate with a security provider interface hierarchy, said method comprising the steps of providing for the implementation of an authentication interface adapted to extend and implement at least a portion of the security provider hierarchy, providing for the authentication of the subject when so directed by the authentication interface, and providing for the association of a signed principal with the subject upon the successful authentication of the subject.

Abstract: In accordance with embodiments, one or more authentication filters may be employed to supplement an authentication process. The authentication process to be supplemented may be executed by one or more servlets in a servlet container. A servlet authentication filter is an authentication filter that may be invoked by a servlet. Requests may be made by requestors (also called “users”), which include humans as well as computational entities. The ability to modify a request and/or request state can enable multi-phase authentication processes, i.e., authentication processes with more than one authentication step, or modification to a default authentication process, i.e., authentication processes invoked if no other authentication processes are provided.

Abstract: A method for adaptively authenticating a subject based on authentication information, comprising the steps of providing for the receipt of the authentication information; providing for the performance of Java Authentication and Authorization Service (JAAS) authentication of the subject based on the authentication information and wherein successful authentication of the subject results in the association of a principal with the subject; providing for the signing of the principal by determining an authentication code for the principal that is a function of the principal and a key.