Integrating enterprise support systems

• US 7,536,697 B2
• Filed: 08/09/2001
• Issued: 05/19/2009
• Est. Priority Date: 06/19/2001
• Status: Active Grant

• Current Assignee: Accenture Global Services Limited (Accenture PLC)
• Original Assignee: Accenture Global Services GmbH (Accenture PLC)
• Inventors: Wiseman, Lise, Tjon, Nicole
• Primary Examiner(s): Zhen; Li B
• Application Number:
  US09/927,957
• Publication Number:
  US 20040015366A1
• Time in Patent Office: 2,840 Days
• Field of Search: 709/101, 709/203, 709/310, 295/680, 370/84, 718/101, 719/315, 719/316
• US Class Current: 719/315
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling

Abstract

Facilitating the exchange of information among applications (e.g., business support systems or operational support systems or a combination thereof) may involve receiving a data object from a first application, using a first controller to route the received data object to a first transformer, using the first transformer to transform the data object from a first format used by the first application into a common format object, publishing the common format object to a communication channel, receiving a request from a subscribing application to subscribe to the communication channel, using a second controller to route the common format object to a second transformer, using the second transformer to transform the common format object into a data object in a second format used by the subscribing application, and sending the data object in the second format to the subscribing application.

Claims

1. A computer-implemented method of exchanging information among applications, the method comprising:

providing a plurality of transformers, each transformer corresponding to a unique transformation from one format into another;

using a first transformer to transform a data object from a format understandable by a first application into a common format data object;

determining a business event type for the common format data object, the business event type representing one or more of a type of function and activity performed by a business;

selecting, from among multiple communication channels defined in an integration hub, a communication channel corresponding to the determined business event type, each of the multiple communication channels defined in the integration hub corresponding to a single business event type and being configured to communicate those common format data objects in the integration hub that correspond to the single business event type;

publishing the common format data object to the selected communication channel that is defined in the integration hub to correspond to the single business event type determined for the common format data object and configured to communicate those common format data objects in the integration hub that correspond to the single business event type determined for the common format data object;

prioritizing communication of the published common format data object on the selected communication channel based on a relative priority associated with the selected communication channel;

subscribing to the selected communication channel to retrieve the published common format data object; and

using a second transformer to transform the published common format data object into a format understandable by a second application,

wherein the common format data object includes data needed to perform the one or more of the type of function and activity represented by the business event type determined for the common format data object, and

wherein using the second transformer to transform the published common format data object into the format understandable by the second application comprises translating the data needed to perform the one or more of the type of function and activity included in the common format data object to a vendor-specific format used by the second application in processing data objects to enable the second application to perform operations completed in performing the one or more of the type of function and activity represented by the business event type.

2. The method of claim 1 wherein the data object corresponds to one or more of a plurality of business events.

3. The method of claim 1 wherein using a first transformer to transform the data object from the format understandable by the first application into the common format data object is performed in response to a recognition of a business event by the first application.

4. The method of claim 1 wherein the method is performed in accordance with a plurality of process models that collectively define when information is to be exchanged among applications.

5. The method of claim 1 wherein publishing the common format data object to a communication channel is performed by a source connector and subscribing to the communication channel is performed by a target connector.

6. The method of claim 1 in which information is exchanged among business support systems or operational support systems or a combination thereof.

7. The method of claim 1 in which at least one of the transformers comprises a class defined in an object-oriented programming language.

8. The method of claim 1 further comprising providing, for each transformer, a controller that is configured to route data objects to an associated transformer.

9. The method of claim 8, further comprising routing a data object to the first transformer using a first controller.

10. The method of claim 8, further comprising routing the common format data object to the second transformer using a second controller.

11. The method of claim 8 in which at least one of the controllers comprises a class defined in an object-oriented programming language.

12. The method of claim 1 further comprising using an acknowledgement class to exchange status messages among applications.

13. The method of claim 12 further comprising using the acknowledgement class to perform exception handling.

14. The method of claim 1 wherein prioritizing communication of the published common format data object on the selected communication channel based on a relative priority associated with the selected communication channel comprises prioritizing communication of the published common format data object on the selected communication channel based on a relative priority of the selected communication channel with respect to other communication channels included in the multiple communication channels.

15. The method of claim 1 wherein:

the common format data object corresponds to a business event, and

prioritizing communication of the published common format data object on the selected communication channel based on a relative priority associated with the selected communication channel comprises prioritizing communication of the published common format data object on the selected communication channel to ensure business events are sent to applications in a correct order.

16. The method of claim 1 wherein the multiple communication channels are prioritized to ensure that business events are sent to applications in a correct order.

17. The method of claim 1 further comprising publishing an acknowledgement message to an acknowledgement communication channel assigned to communicate acknowledgement messages, the acknowledgement channel being different than the selected communication channel and the acknowledgement message indicating success or failure of communication of information included in the common format data object to the second application.

18. The method of claim 1 wherein each of the multiple communication channels defined in the integration hub are incapable of properly communicating common format data objects of business event types that are different than the single business event type to which the communication channel corresponds.

19. The method of claim 1 wherein translating the data needed to perform the one or more of the type of function and activity included in the common format data object to a vendor-specific format used by the second application in processing data objects comprises changing fields with the data needed to perform the one or more of the type of function and activity from numeric fields to alphanumeric fields and from status values to enumerator or Boolean values.

20. The method of claim 1 wherein the multiple communication channels defined in the integration hub represent logical partitions of data communication internal to the integration hub.

21. A computer-implemented method of exchanging information among applications, the method comprising:

providing a plurality of transformers, each transformer corresponding to a unique transformation from one format into another;

using a first transformer to transform a data object from a format understandable by a first application into a common format data object;

determining an event type associated with the common format data object;

selecting, from among multiple communication channels each corresponding to a specific event type, a communication channel corresponding to the determined event type;

publishing the common format data object to the selected communication channel;

prioritizing communication of the published common format data object on the selected communication channel based on a relative priority associated with the selected communication channel;

subscribing to the selected communication channel to retrieve the published common format data object; and

using a second transformer to transform the published common format data object into a format understandable by a second application,

wherein using the first transformer to transform the data object from the format understandable by the first application into the common format data object comprises translating the data object from a vendor-specific format associated with the first application to an Interface Description Language (IDL) object and storing the IDL object in a shared object model.

22. The method of claim 21 wherein the shared object model comprises a central repository of data objects corresponding to business events.

23. A computer-implemented method of exchanging information among applications, the method comprising:

providing a plurality of transformers, each transformer corresponding to a unique transformation from one format into another;

using a first transformer to transform a data object from a format understandable by a first application into a common format data object;

determining an event type associated with the common format data object;

selecting, from among multiple communication channels each contending to a specific event type, a communication channel corresponding to the determined event type;

publishing the common format data object to the selected communication channel;

prioritizing communication of the published common format data object on the selected communication channel based on a relative priority associated with the selected communication channel;

subscribing to the selected communication channel to retrieve the published common format data object; and

using a second transformer to transform the published common format data object into a format understandable by a second application,

wherein using the second transformer to transform the common format data object into the format understandable by the second application comprises retrieving a stored Interface Description Language (JDL) format object from a central repository and translating the JDL object into a vendor-specific format associated with the second application.

24. A computer-implemented method of facilitating the exchange of information among applications, the method comprising:

receiving a data object from a first application;

using a first controller to route the received data object to a first transformer;

using the first transformer to transform the data object from a first format used by the first application into a common format object;

determining a business event type for the common format data object, the business event type representing one or more of a type of function and activity performed by a business;

selecting, from among multiple communication channels defined in an integration hub, a communication channel corresponding to the determined business event type, each of the multiple communication channels defined in the integration hub corresponding to a single business event type and being configured to communicate those common format data objects in the integration hub that correspond to the single business event type;

publishing the common format data object to the selected communication channel that is defined in the integration hub to correspond to the single business event type determined for the common format data object and configured to communicate those common format data objects in the integration hub that correspond to the single business event type determined for the common format data object;

prioritizing communication of the published common format data object on the selected communication channel based on a relative priority associated with the selected communication channel;

receiving a request from a subscribing application to subscribe to the selected communication channel;

using a second controller to route the published common format object to a second transformer;

using the second transformer to transform the published common format object into a data object in a second format used by the subscribing application; and

sending the data object in the second format to the subscribing application.

25. The method of claim 24 wherein the data object received from the first application corresponds to one or more of a plurality of business events.

26. The method of claim 24 wherein using the first transformer to transform the data object from the format used by the first application into the common format object comprises translating the data object from a vendor-specific format associated with the first application to an Interface Description Language (IDL) object and storing the IDL object in a shared object model.

27. The method of claim 26 wherein the shared object model comprises a central repository of data objects corresponding to business events.

28. The method of claim 24 wherein using the first transformer to transform the data object from the format used by the first application into the common format object is performed in response to a recognition of a business event by the first application.

29. The method of claim 24 wherein the method is performed in accordance with a plurality of process models that collectively define when information is to be exchanged among applications.

30. The method of claim 24 wherein, if requests are received from a plurality of subscribing applications, then, for each subscribing application, the common format object is transformed using an associated transformer into a format corresponding to the subscribing application and sent to the subscribing application.

31. The method of claim 24 wherein using the second transformer to transform the common format object into a data object in the second format used by the subscribing application comprises retrieving a stored Interface Description Language (JDL) format object from a central repository and translating the IDL object into a vendor-specific format associated with the subscribing application.

32. The method of claim 24 in which information is exchanged among business support systems or operational support systems or a combination thereof.

33. A system for facilitating the exchange of information among applications, the system comprising:

a plurality of digital computers, each of which executes an application, each application being configured to exchange information representative of business events with other applications; and

an integration hub in data communication with each of the digital computers for enabling transfer of information representative of business events between applications, the integration hub including a computer-readable medium on which is encoded instructions for causing a computer to perform operations comprising;

receiving a data object from a first application executing on a first of the plurality of digital computers;

using a first controller to route the received data object to a first transformer;

using the first transformer to transform the data object from a first format used by the first application into a common format object;

determining a business event type for the common format data object, the business event type representing one or more of a type of function and activity performed by a business;

selecting, from among multiple communication channels defined in the integration hub, a communication channel corresponding to the determined business event type, each of the multiple communication channels defined in the integration hub corresponding to a single business event type and being configured to communicate those common format data objects in the integration hub that correspond to the single business event type;

publishing the common format data object to the selected communication channel that is defined in the integration hub to correspond to the single business event type determined for the common format data object and configured to communicate those common format data objects in the integration hub that correspond to the single business event type determined for the common format data object;

prioritizing communication of the published common format data object on the selected communication channel based on a relative priority associated with the selected communication channel;

receiving a request from a subscribing application executing on a second of the plurality of digital computers to subscribe to the selected communication channel;

using a second controller to route the published common format object to a second transformer;

using the second transformer to transform the published common format object into a data object in a second format used by the subscribing application; and

sending the data object in the second format to the subscribing application.

34. The system of claim 33 further comprising a channel architecture defining a plurality of communication channels to which data objects from an application are to be published.

35. The system of claim 33 further comprising an acknowledgement class configured to exchange status messages among applications.

36. The system of claim 35 wherein the acknowledgement class is further configured to perform exception handling.

37. The system of claim 33 wherein the common format data object corresponds to a shared object model, the shared object model comprises a central repository of data objects in an Interface Description Language (JDL) format.

38. A tangible medium having encoded thereon instructions for facilitating the exchange of information among applications, execution of the instructions causing one or more machines to perform operations comprising:

receiving a data object from a first application;

using a first controller to route the received data object to a first transformer;

using the first transformer to transform the data object from a first format used by the first application into a common format object;

determining a business event type for the common format data object, the business event type representing one or more of a type of function and activity performed by a business;

selecting, from among multiple communication channels defined in an integration hub, a communication channel corresponding to the determined business event type, each of the multiple communication channels defined in the integration hub corresponding to a single business event type and being configured to communicate those common format data objects in the integration hub that correspond to the single business event type;

publishing the common format data object to the selected communication channel that is defined in the integration hub to correspond to the single business event type determined for the common format data object and configured to communicate those common format data objects in the integration hub that correspond to the single business event type determined for the common format data object;

prioritizing communication of the published common format data object on the selected communication channel based on a relative priority associated with the selected communication channel;

receiving a request from a subscribing application to subscribe to the selected communication channel;

using a second controller to route the published common format object to a second transformer;

using the second transformer to transform the published common format object into a data object in a second format used by the subscribing application; and

sending the data object in the second format to the subscribing application.

39. The tangible medium of claim 38 wherein the machine-readable instructions comprise computer software instructions executable by one or more computer systems.

40. The tangible medium of claim 38 wherein the data object received from the first application corresponds to one or more of a plurality of business events.

41. The tangible medium of claim 38 wherein using the first transformer to transform the data object from the format used by the first application into the common format object comprises translating the data object from a vendor-specific format associated with the first application to an Interface Description Language (IDL) object and storing the IDL object in a shared object model.

42. The tangible medium of claim 41 wherein the shared object model comprises a central repository of data objects corresponding to business events.

43. The tangible medium of claim 38 wherein using the first transformer to transform the data object from the format used by the first application into the common format object is performed in response to a recognition of a business event by the first application.

44. The tangible medium of claim 38 wherein one or more of the instructions are executed in accordance with a plurality of process models that collectively define when information is to be exchanged among applications.

45. The tangible medium of claim 38 wherein, if requests are received from a plurality of subscribing applications, then, for each subscribing application, the common format object is transformed using an associated transformer into a format corresponding to the subscribing application and sent to the subscribing application.

46. The tangible medium of claim 38 wherein using the second transformer to transform the common format object into the data object in the second format used by the subscribing application comprises retrieving a stored Interface Description Language (IDL) format object from a central repository and translating the IDL object into a vendor-specific format associated with the subscribing application.

47. The tangible medium of claim 38 in which information is exchanged among business support systems or operational support systems or a combination thereof.

48. A computer-implemented method of exchanging information among applications, the method comprising:

providing a plurality of transformers, each transformer corresponding to a unique transformation from one format into another;

using a first transformer to transform a data object from a format understandable by a first application into a common format data object;

determining a business event type for the common format data object, the business event type representing one or more of a type of function and activity performed by a business;

selecting, from among multiple communication channels defined in an integration hub, a communication channel corresponding to the determined business event type, each of the multiple communication channels defined in the integration hub corresponding to a single business event type and being configured to communicate those common format data objects in the integration hub that correspond to the single business event type;

publishing the common format data object to the selected communication channel that is defined in the integration hub to correspond to the single business event type determined for the common format data object and configured to communicate those common format data objects in the integration hub that correspond to the single business event type determined for the common format data object;

prioritizing communication of the published common format data object on the selected communication channel based on a relative priority associated with the selected communication channel;

subscribing to the selected communication channel to retrieve the published common format data object; and

using a second transformer to transform the published common format data object into a format understandable by a second application,

wherein determining the business event type for the common format data object comprises determining a business event type of at least one of a create order business event type, an add product business event type, an add service instance business event type, an apply account level adjustment business event type, a cancel product business event type, a cancel service instance business event type, a create customer business event type, a maintain account business event type, a maintain service instance business event type, an update account status business event type, and an update product status business event type; and

wherein selecting, from among multiple communication channels defined in the integration hub, the communication channel corresponding to the determined business event type comprises selecting a communication channel corresponding to at least one of the create order business event type, the add product business event type, the add service instance business event type, the apply account level adjustment business event type, the cancel product business event type, the cancel service instance business event type, the create customer business event type, the maintain account business event type, the maintain service instance business event type, the update account status business event type, and the update product status business event type.