Abstract: In a workload managed system comprising a plurality of server processes each capable of supporting a given program entity, such as an Enterprise JavaBeans™ specified stateful session bean, a stateful session bean instance is passivated, by writing it to a bean store, on completion of a unit of work. On next use the session bean is reactivated, by reading it from the bean store, in any one of the plurality of servers thereby allowing workload management for stateful session beans. A routing table is maintained, in non-volatile mass storage, that contains location information for units of work and stateful session bean instances, used to maintain unit of work-server affinity for the lifetime of the unit of work Stateful session beans instances are associated with ID keys that include a flag that is used to indicate whether or not the routing table contains location information for the bean instance.

Abstract: The present invention provides a more flexible version of an EJB container which permits easy definition an EJB component which observes a behavior pattern which is not typical of a session, entity or message driven bean types. In this flexible EJB container, behavior characteristics normally fixed by the bean type of the EJB component, such as passivation policy, usage, recoverability, and relocatability can be separately defined for each EJB component.

Abstract: In a workload managed system comprising a plurality of server processes each capable of supporting a given program entity, such as an Enterprise JavaBeans™ specified stateful session bean, a stateful session bean instance is passivated, by writing it to a bean store, on completion of a unit of work. On next use the session bean is reactivated, by reading it from the bean store, in any one of the plurality of servers thereby allowing workload management for stateful session beans. A routing table is maintained, in non-volatile mass storage, that contains location information for units of work and stateful session bean instances, used to maintain unit of work-server affinity for the lifetime of the unit of work Stateful session beans instances are associated with ID keys that include a flag that is used to indicate whether or not the routing table contains location information for the bean instance.

Abstract: The present invention provides a more flexible version of an EJB container which permits easy definition an EJB component which observes a behaviour pattern which is not typical of a session, entity or message driven bean types. In this flexible EJB container, behaviour characteristics normally fixed by the bean type of the EJB component, such as passivation policy, usage, recoverability, and relocatability can be separately defined for each EJB component.

Abstract: Disclosed are a system, method and computer program for component-based processing, comprising a component specification element, a control flow specification element, a data flow specification element, a resource specification element, a quality of service specification derivation element having for output an application model in combination with a quality of service specification derived by implication from relations between components, control flows, data flows and resources, and a runtime engine for deploying said quality of service specification as a runtime contract in a runtime processing environment. Examples of such qualities of service are requirements of a process to have provided for it support for transactionality, recoverability, asynchronous messaging and the like.

Abstract: A system and method for efficiently employing procedural transaction managers from an object oriented transaction processing system. Implementation classes are introduced to bridge selected functions from an object oriented transaction processing system into a procedural system. Bridging allows both the reuse of existing procedural transaction managers and interoperation between procedural and object transactions systems which eases migration to new object oriented systems. Implementation classes include methods necessary to manage information necessary to use a procedural transaction API and to manage information returned by the procedural API.

Abstract: A system and method for using the TRAN procedural transaction coordinator, from the Encina product produced by Transarc Corporation, as the core of an OMG-compliant Object Transaction Service. The method allows the object-oriented Object Transaction Service to interoperate with Encina procedural applications. The interoperation involves coordinated processing of both object oriented transactional requests and Encina procedural transactional requests. Both object oriented and procedural requests can be part of a single atomic transaction without requiring gateways between the products. A system of implementation classes are used to transform object-oriented method invocations into the necessary procedural calls. The implementation classes also accept upcalls from the procedural TRAN and transform them into the necessary Object Transaction Service method invocations.

Abstract: A system and process for enhancing procedural software using object oriented classes. Implementation classes are constructed that provide a defined object oriented interface to applications and are able to invoke the procedural software using defined procedural application program interfaces (APIs). New function is added to the software by adding classes that interface to the implementation classes or directly to the procedural API. The new function builds upon the procedural software without accessing the procedural software source code or modifying that source code.

Abstract: In brief, an object oriented thread context manager, a method and computer program product are provided for object oriented thread context management, particularly for relational databases working with distributed transactions. A context manager is provided for managing a plurality of ContextControl objects. Each ContextControl object comprises a plurality of methods for creating, resuming and suspending context on a thread for a target object. A ContextCoordinator class is provided for managing calls to the plurality of ContextControl objects. A ContextHandleList is provided for storing context information for the ContextControl objects. A specialized ContextCoordinator is provided for managing calls to a specialized ones of the ContextControl objects. A DatabaseContextCoordinator is an example of the specialized ContextCoordinator. The specialized ones of the ContextControl objects are registered and unregistered with the ContextCoordinator class and then registered DatabaseContextCoordinator.