Systems and/or methods for providing feature-rich proprietary and standards-based triggers via a trigger subsystem
The example embodiments disclosed herein relate to application integration techniques and, more particularly, to application integration techniques built around the publish-and-subscribe model (or one of its variants). In certain example embodiments, triggers are provided for establishing subscriptions to publishable document types and for specifying the services that will process documents received by the subscription. A standards-based messaging protocol (e.g., JMS messaging) may be fully embedded as a peer to a proprietary messaging protocol provided to an integration server's trigger subsystem so that all or substantially all of the feature-rich capabilities available via the proprietary protocol may also become available via the standards-based messaging protocol. The triggers may be JMS triggers in certain example embodiments.
1. An application integration system including a trigger subsystem and at least one processor configured to interface with the trigger subsystem, the trigger subsystem comprising:
at least one proprietary trigger subsystem embedded in the trigger subsystem;
at least one standards-based trigger subsystem embedded in the trigger subsystem, wherein all or substantially all existing capabilities of the at least one standards-based trigger subsystem are embedded in the trigger subsystem and,
common trigger facilities for the at least one proprietary trigger subsystem and the at least one standards-based trigger subsystem,
wherein the at least one proprietary trigger subsystem and the at least one standards-based trigger subsystem are provided as parallel subsystems,
wherein each said proprietary trigger subsystem and each said standards-based trigger subsystem is configured to access a corresponding trigger layer,
wherein each said trigger layer is configured to provide triggers in a format associated with the respective trigger layer,
wherein the triggers include instructions for causing a process to be executed in or by the application integration system or a component thereof, and
wherein the trigger subsystem is arranged to enable configuration of the at least one standards-based trigger subsystem free from implementation changes at an application services level.
2. The application integration system of claim 1 , wherein the triggers are configured to enable a publish-and-subscribe model to be used in the application integration system.
3. The application integration system of claim 2 , wherein the triggers include instructions for establishing subscriptions to publishable document types and for specifying one or more services to process documents received by the subscriptions.
4. The application integration system of claim 1 , wherein the trigger subsystem is configured to enable standards-based messaging free from any adapters provided to the integration system.
5. The application integration system of claim 1 , further comprising a Java Message Service (JMS) subsystem embedded therein as at least a part of said standards-based trigger subsystem and as a peer to the at least one proprietary messaging protocol.
6. The application integration system of claim 5 , wherein the JMS subsystem is configured to provide JMS triggers.
7. The application integration system of claim 1 , wherein the triggers for the at least one standards-based trigger layer are not modified from their original format(s).
8. An integration server provided as a component in an application integration system, the integration server comprising a processing system including at least one processor and configured to provide a messaging layer for use across the integration server or an integration server instance, the messaging layer comprising:
a trigger subsystem including:
at least one proprietary trigger subsystem embedded therein,
at least one standards-based trigger subsystem embedded therein, wherein all or substantially all existing capabilities of the at least one standards-based trigger subsystem are embedded in the trigger subsystem, and
common trigger facilities for the at least one proprietary trigger subsystem and the at least one standards-based trigger subsystem;
wherein the at least one proprietary trigger subsystem and the at least one standards-based trigger subsystem are provided as parallel subsystems in the trigger subsystem;
a plurality of parallel trigger layers respectively provided for each said proprietary trigger subsystem and each said standards-based trigger subsystem; and,
a plurality of messaging Application Programming Interface (API) layers respectively provided for each said proprietary trigger subsystem and each said standards-based trigger subsystem,
wherein each said trigger layer is configured to provide triggers in a format associated with the respective trigger layer,
wherein the triggers include instructions for causing a process to be executed in or by the application integration system or a component thereof, and
wherein the trigger subsystem is arranged to enable configuration of the at least one standards-based trigger subsystem free from implementation changes at an application services level.
9. The integration server of claim 8 , wherein the triggers enable a publish-and-subscribe model to be used in the application integration system.
10. The integration server of claim 9 , wherein the triggers include instructions for establishing subscriptions to publishable document types and for specifying one or more services to process documents received by the subscriptions.
11. The integration server of claim 8 , wherein the trigger subsystem enables standards-based messaging free from any adapters provided to the integration system.
12. The integration server of claim 8 , wherein the messaging layer further comprising a Java Message Service (JMS) subsystem embedded therein as at least a part of said standards-based trigger subsystem and as a peer to the at least one proprietary messaging protocol.
13. The integration server of claim 12 , wherein the JMS subsystem is configured to provide JMS triggers.
14. The integration server of claim 8 , wherein the triggers for the at least one standards-based trigger layer are not modified from their original format(s).
15. A method of configuring an application integration system, the method comprising:
providing a messaging layer for use across an integration server or an integration server instance provided as a component in the application integration system;
including in the messaging layer a trigger subsystem;
embedding at least one proprietary trigger subsystem in the trigger subsystem;
embedding at least one standards-based trigger subsystem in the trigger subsystem;
configuring the trigger subsystem to provide common trigger facilities for the at least one proprietary trigger subsystem and the at least one standards-based trigger subsystem, wherein all or substantially all existing capabilities of the at least one standards-based trigger subsystem are embedded in the trigger subsystem;
providing a plurality of trigger layers respectively for each said proprietary trigger subsystem and each said standards-based trigger subsystem; and,
providing a plurality of messaging Application Programming Interface (API) layers respectively for each said proprietary trigger subsystem and each said standards-based trigger subsystem,
wherein the at least one proprietary trigger subsystem and the at least one standards-based trigger subsystem are provided as parallel subsystems in the trigger subsystem,
wherein each said trigger layer is configured to provide triggers in a format associated with the respective trigger layer,
wherein the triggers include instructions for causing a process to be executed in or by the application integration system or a component thereof, and
wherein the trigger subsystem is arranged to enable configuration of the at least one standards-based trigger subsystem free from implementation changes at an application services level.
16. The method of claim 15 , further comprising enabling a publish-and-subscribe model to be used in the application integration system via the triggers.
17. The method of claim 16 , further comprising including in the triggers instructions for establishing subscriptions to publishable document types and for specifying one or more services to process documents received by the subscriptions.
18. The method of claim 15 , further comprising enabling standards-based messaging free from any adapters provided to the integration system.
19. The method of claim 15 , further comprising embedding a Java Message Service (JMS) subsystem in the trigger subsystem as at least a part of said standards-based trigger subsystem and as a peer to the at least one proprietary messaging protocol.
20. The method of claim 19 , wherein the JMS subsystem is configured to provide JMS triggers.
21. The method of claim 15 , wherein the triggers for the at least one standards-based trigger layer are not modified from their original format(s).
22. A method of operating an application integration system based on a publish-and-subscribe model or a variant of the publish-and-subscribe model, the method comprising:
providing a messaging layer for use across an integration server or an integration server instance provided as a component in the application integration system, the messaging layer including:
a trigger subsystem included therein, the trigger subsystem comprising at least one proprietary trigger subsystem embedded therein and at least one standards-based trigger subsystem substantially fully embedded therein, the trigger subsystem being configured to provide common trigger facilities for the at least one proprietary trigger subsystem and the at least one standards-based trigger subsystem, wherein all or substantially all existing capabilities of the at least one standards-based trigger subsystem are embedded in the trigger subsystem and
a plurality of trigger layers respectively provided for each said proprietary trigger subsystem and each said standards-based trigger subsystem, each said trigger layer being configured to provide triggers in a format associated with the respective trigger layer;
including in the triggers instructions for establishing subscriptions to publishable document types and for specifying one or more services to process documents received by the subscriptions;
publishing one or more documents to one or more subscribers in dependence on the instructions included in the corresponding trigger(s); and,
processing each said document in dependence on the instructions included in the corresponding trigger(s),
wherein the at least one proprietary trigger subsystem and the at least one standards-based trigger subsystem are provided as parallel subsystems in the trigger subsystem, and
wherein the trigger subsystem is arranged to enable configuration of the at least one standards-based trigger subsystem free from implementation changes at an application services level.