Exposing process flows and choreography controllers as web services
View Patent ↗The present invention relates to computer-based devices and methods supporting document exchange choreographies. More particularly, aspects of the present invention relate to devices and methods that facilitate evolution of systems by various combinations of choreography versioning, service versioning and document versioning. It provides for choreography management using a choreography agent and presents choreography-enabled interfaces to non choreography enabled applications. Additional aspects of the present invention include a graphical design tool and transparent aliasing of a host service as multiple context setting franchised services. Particular aspects of the present invention are described in the claims, specification and drawings.
1. The method of supporting web service interoperability among a plurality of service entities, including determining at run-time:
a particular version of a message choreography to be used for exchange of messages among the entities, wherein versions of the message choreography use substantially the same first message;
service versions in use by one or more service providers among the service entities; and
document versions to be used by the service entities in the message exchanges and translations, if needed, among the document versions.
2. The method of claim 1 , wherein the method is adapted to a plurality of choreography definition languages.
3. The method of claim 1 , wherein the method is adapted to a plurality of service entity interface definition languages.
4. A method of choreographing web services, wherein a choreography includes a plurality of messages mapped to standard-compliant interfaces of a plurality of service entities, assigning a conversation identifier to the messages, and conducting message exchanges among the service entities according to the choreography, the method including:
maintaining choreography versions of a choreography, wherein the choreography versions use substantially similar first messages; and
responsive to a first message, determining a particular message choreography version supported by the service entities and utilizing the particular choreography version after the first message.
5. The method of claim 4 , wherein determining a message choreography version includes accessing a registry that identifies choreography versions supported by the service entities.
6. The method of claim 5 , wherein the registry further identifies preferences of the service entities among the supported choreography versions and determining further includes utilizing the preferences of at least one of the service entities.
7. The method of claim 4 , wherein the messages include documents, further including:
maintaining document versions of the documents and translation logic to convert among versions; and
determining particular document versions to be used by the service entities and translations, if needed, among the particular document versions.
8. A method of choreographing web services, wherein a choreography includes a plurality of messages mapped to standard-compliant interfaces of a plurality of service entities, assigning a conversation identifier to the messages, and conducting message exchanges among the service entities according to the choreography, the method including:
maintaining choreography versions of a choreography, wherein the choreography versions use substantially similar first messages;
maintaining in a registry data that identifies choreography versions supported by the service entities;
accessing the registry and determining a particular message choreography version supported by the service entities; and
utilizing the particular choreography version for the message exchanges.
9. The method of claim 8 , wherein the registry further identifies preferences of the service entities among the supported choreography versions and determining further includes utilizing the preferences of at least one of the service entities.
10. The method of claim 8 , wherein the messages include documents, further including:
maintaining document versions applicable to the documents and translation logic to convert among versions; and
determining particular document versions to be used by the service entities and translations, if needed, among the particular document versions.