Abstract: A system and method for monitoring dynamic scopes in a runtime environment is disclosed. The system and method utilizes an algorithm which may be applied to both synchronous and asynchronous invocations. The method comprises determining an initial scope of a source component, the initial scope being a scope of the source component upon providing a synchronous call to invoke a target component. The scope declaration specified by the target component is determined. A resultant scope present upon invocation of the target component is then determined. The resultant scope is determined based on the initial scope of the source component and the scope declaration specified by the target component. A record is stored in a centralized location identifying the resultant scope, and the target component as a participant in the resultant scope.

Abstract: A computer implemented method, apparatus, and computer usable program code for updating multiple concurrent versions of shared artifact libraries. Shared artifact libraries are associated with a consuming application for establishing shared artifact libraries upon which the consuming application has a dependency for artifacts. A snapshot of the shared artifact libraries associated with the consuming application in an active session is created in response to starting a session. The shared artifact libraries are updated in response to new versions and updates of the shared artifact libraries becoming available. Artifacts are dispensed from the shared artifact libraries to the consuming application based on the snapshot of the session.

Abstract: An apparatus, system, and method are disclosed for automatically maintaining identity relationships among disparate enterprise information systems. The apparatus comprises a synchronization hub comprising an identity relationship repository, a relationship service module, a consistency module, and an adjustment module. The relationship service is configured to access a target relationship entry using a unique key from a source business object, wherein the source business object is representative of changes made in a source enterprise information system. The various components and modules of the synchronization hub cooperate to determine identity relationships that need updating and to propagate identity relationship changes to one or more destination enterprise information servers.

Abstract: An apparatus, system, and method are disclosed for synchronizing change histories in enterprise applications. An access module accesses a source data object container provided by a source EIS and a destination data object container provided by a destination EIS. The source data object container comprises a source change history, and the destination data object container comprises a destination change history. A transformation module may retrieve a transformation definition from an integration server, or the transformation definition may be provided in some other fashion. An interpretation module interprets the transformation definition to determine the relationships between the source data object container and the destination data object container. A copy module may copy select portions of the source change history to the destination change history.

Abstract: A computer implemented method, an apparatus and computer instruction are provided for deployment of roles. Aspects of the present invention allow user to define in a schema a definition of a relationship that comprises a set of roles participating in the relationship. Each role in the set of roles is defined as an inlined role or an independent role. After the schema is processed, aspects of the present invention determine if the role in the set of roles is an inlined role or an independent role based on the definition of the relationship, deploy the relationship and the role as a single entity if the role is an inlined role, and deploy the relationship and the role as separate entities if the role is an independent role.

Abstract: A method, system, and computer program code for integrating components with different interfaces in an enterprise application integration environment. When an enterprise application is assembled, a user may try to wire a component to another component in the enterprise. However, if the reference on the source component does not match the interface on the target component, the components cannot be wired together. In this situation, the user is prompted to introduce an interface mediation component between the source and target application components. The mediation component comprises an interface matching the reference on the source component and a reference matching the interface on the target component. The mediation component mediates the different interfaces at runtime by binding an operation in the source component to an operation in the target component, and performing a parameter mediation of parameters in the first operation to parameters in the second operation.

Abstract: A system and method for monitoring dynamic scopes in a runtime environment is disclosed. The system and method utilizes an algorithm which may be applied to both synchronous and asynchronous invocations. The method comprises determining an initial scope of a source component, the initial scope being a scope of the source component upon providing a synchronous call to invoke a target component. The scope declaration specified by the target component is determined. A resultant scope present upon invocation of the target component is then determined. The resultant scope is determined based on the initial scope of the source component and the scope declaration specified by the target component. A record is stored in a centralized location identifying the resultant scope, and the target component as a participant in the resultant scope.

Abstract: A business integration (BI) system receives business objects from a source application at an event partitioner. Event partitioner partitions received business objects into independent sets based on interdependent events, and allocates each independent group of business events to a separate event queue based a partitioning modulo reduction transformation of the independent sets to determine the correct event queue for storing a particular received business object. This transformation reduces the number of independent sets to a number of event groups equal to the number of allocated event queues. Events in different groups are delivered to an interchange server through the separate event queues so that they may be processed independently and in parallel, thus improving the overall performance of the interchange server, while guaranteeing that dependent events are processed in the correct serial order.