Abstract: The embodiments of the invention provide a method of organizing assets having artifacts in a repository. The method begins by organizing artifacts of at least one of the assets as internal nodes in a graph based on a context. The method simultaneously organizes the assets as external nodes in the graph based on the context. The internal nodes comprise artifacts having metadata that is updated by an artifact producer and/or an asset producer. Moreover, the external nodes comprise artifacts that are defined and/or updated by roles other than an artifact producer and/or an asset producer.

Abstract: A method generates, based on an original business process comprising at least one component, a variant business process comprising at least one variation compared to the original business process. The method comprises the steps of developing a variant meta-model, representing the at least one variation, instantiating and verifying the developed variant meta-model portion to obtain a variant model, and implementing the variant model to generate the variant. The method also comprises developing a formalism for defining the at least one variation.

Abstract: A web service request is received by an intermediary that performs a conversion of the requestor's service interface to the service interface supported by a service provider matching the requested service, then invokes that service. A reverse conversion is performed when passing a reply to the requester. The web serving intermediary maintains a library of each target service in terms of the target service's tModel and on its binding protocol support. The intermediary receives web service requests from requesters including their source tModel and target web service information. The intermediary identifies a mapping aspect to invoke the target web service from the aspect library. The target service tModel is embodied in the mapping aspect which is weaved into the code invoking the target service at runtime. In this way, the interface logic is decided at run time.

Abstract: A web service request is received by an intermediary that performs a conversion of the requestor's service interface to the service interface supported by a service provider matching the requested service, then invokes that service. A reverse conversion is performed when passing a reply to the requester. The web serving intermediary maintains a library of each target service in terms of the target service's tModel and on its binding protocol support. The intermediary receives web service requests from requestors including their source tModel and target web service information. The intermediary identifies a mapping aspect to invoke the target web service from the aspect library. The target service tModel is embodied in the mapping aspect which is weaved into the code invoking the target service at runtime. In this way, the interface logic is decided at run time.

Abstract: A web service request is received by an intermediary that performs a conversion of the requestor's service interface to the service interface supported by a service provider matching the requested service, then invokes that service. A reverse conversion is performed when passing a reply to the requester. The web serving intermediary maintains a library of each target service in terms of the target service's tModel and on its binding protocol support. The intermediary receives web service requests from requestors including their source tModel and target web service information. The intermediary identifies a mapping aspect to invoke the target web service from the aspect library. The target service tModel is embodied in the mapping aspect which is weaved into the code invoking the target service at runtime. In this way, the interface logic is decided at run time.