System and method for exposing features of integration platform adapters as first-class actions in an orchestration template
Systems and methods for exposing features of integration platform adapters as first-class actions in orchestration template are provided. Exposing features of an adapter as first-class actions in the orchestration template can allow integration designers focus on the business logic being worked upon and pick the correct feature from the adapter based on the context. As the features of adapters are exposed as first-class actions, even new features will be visible to the user along with context sensitive help explaining usage of the feature.
1 . A system for exposing features of integration platform adapters as first-class actions in an orchestration template comprising:
a computer including one or more microprocessors;
an integration platform running on the computer;
wherein instructions are received at the integration platform, the instructions comprising information indicative of an integration flow to be built within the integration platform, wherein the instructions indicate a plurality of adapters to be used within the integration flow;
wherein the instructions indicate a first adapter, the first adapter being associated with a first application external to the integration platform, of the plurality of adapters to be utilized within the integration flow, the first adapter of the plurality of adapters being associated with a set of properties defined within metadata associated with the first adapter, the set of properties comprising at least action properties and runtime properties,
wherein the first adapter of the plurality of adapters is associated with a role defined within the integration flow;
wherein the action properties associated with the first adapter of the plurality of adapters comprise at least a set of first-class action properties, wherein each of the set of first-class action properties are compiled during development of the first adapter and marked with specific properties including a property indicating to the first adapter to render an action based wizard for each of the set of first-class action properties; and
wherein a determined set of a plurality of adapter specific actions associated with the first adapter of the plurality of adapters, the determined set of the plurality of adapter specific actions being selected from the set of properties associated with the first adapter, said selection excluding runtime properties, is displayed, together with associated context sensitive information, as a set of selectable options, via a user interface of the integration platform, each of the determined set of the plurality of adapter specific actions being associated with the defined role of the first adapter within the integration flow, each of the determined set of the plurality of adapter specific actions being defined within a configuration of the first adapter of the plurality of adapters, the configuration being associated with the integration flow, wherein the determined set of the plurality of adapter specific actions are determined based upon an action of the first adapter within the integration flow;
wherein, based upon a second adapter of the plurality of adapters, the second adapter being associated with a second application external to the integration platform, the second application being different than the first application, having a same defined role within the integration flow, the second adapter of the plurality of adapters being associated with a second set of properties defined within metadata associated with the second adapter, the second set of properties comprising at least action properties and runtime properties, another determined set of a plurality of adapter specific actions, the determined another set of the plurality of adapter specific actions being selected from the second set of properties associated with the second adapter, said selection excluding runtime properties, associated with the second adapter of the plurality of adapters is selected to be displayed, and is displayed as another set of selectable options, together with the display of the determined set of the plurality of adapter specific actions associated with the first adapter of the plurality of adapters;
wherein upon an indication a selection of one of the determined set of the plurality of adapter specific actions being received via the user interface, the configuration of the first adapter of the plurality of adapters is updated and actions of the first adapter of the plurality of adapters within the integration flow are accordingly modified.
2 . The system of claim 1 , wherein each of the plurality of adapter specific actions associated with the first adapter are stored as extensible markup language (XML) within the metadata associated with the first adapter.
3 . The system of claim 2 , wherein the first adapter comprises a connection having a trigger role within the integration flow.
4 . The system of claim 3 ,
wherein a further instruction is received at the integration platform, the further instruction indicating a selection of another of the plurality of adapter specific actions associated with the first adapter to be used within the integration flow; and
wherein upon the selection of the another of the plurality of adapter specific actions associated with the first adapter to be used within the integration flow, the non-selected adapter specific actions are excluded from use within the integration flow.
5 . The system of claim 2 , wherein the first adapter comprises a connection having an invoke role within the integration flow.
6 . The system of claim 5 ,
wherein a further instruction is received at the integration platform, the further instruction indicating a selection of another of the plurality of adapter specific actions associated with the first adapter to be used within the integration flow; and
wherein upon the selection of the another of the plurality of adapter specific actions associated with the first adapter to be used within the integration flow, the non-selected adapter specific actions are excluded from use within the integration flow.
7 . A method for exposing features of integration platform adapters as first-class actions in an orchestration template, comprising:
providing a computer including one or more microprocessors;
providing an integration platform running on the computer;
receiving instructions at the integration platform, the instructions comprising information indicative of an integration flow to be built within the integration platform, wherein the instructions indicate a plurality of adapters to be used within the integration flow, wherein the instructions indicate a first adapter of the plurality of adapters, the first adapter being associated with a first application external to the integration platform, to be utilized within the integration flow, the first adapter of the plurality of adapters being associated with a set of properties defined within metadata associated with the first adapter, the set of properties comprising at least action properties and runtime properties,
wherein the first adapter of the plurality of adapters is associated with a role defined within the integration flow;
wherein the action properties associated with the first adapter of the plurality of adapters comprise at least a set of first-class action properties, wherein each of the set of first-class action properties are compiled during development of the first adapter and marked with specific properties including a property indicating to the first adapter to render an action based wizard for each of the set of first-class action properties;
displaying, as a set of selectable options, a determined set of a plurality of adapter specific actions associated with the first adapter of the plurality of adapters, the determined set of the plurality of adapter specific actions being selected from the set of properties associated with the first adapter, said selection excluding runtime properties, together with associated context sensitive information, via a user interface of the integration platform, each of the determined set of the plurality of adapter specific actions being associated with the defined role of the first adapter within the integration flow, each of the determined set of plurality of adapter specific actions being defined within a configuration of the first adapter of the plurality of adapters, the configuration being associated with the integration flow, wherein the determined set of the plurality of adapter specific actions are determined based upon an action of the first adapter within the integration flow;
based upon a second adapter of the plurality of adapters, the second adapter being associated with a second application external to the integration platform, the second application being different than the first application, having a same defined role within the integration flow, the second adapter of the plurality of adapters being associated with a second set of properties defined within metadata associated with the second adapter, the second set of properties comprising at least action properties and runtime properties, selecting to be displayed another determined set of a plurality of adapter specific actions, the determined another set of the plurality of adapter specific actions being selected from the second set of properties associated with the second adapter, said selection excluding runtime properties, associated with the second adapter of the plurality of adapters, wherein the another determined set of a plurality of adapter specific actions associated with the second adapter are displayed as another set of selectable options together with the display of the determined set of the plurality of adapter specific actions associated with the first adapter of the plurality of adapters; and
upon an indication a selection of one of the determined set of the plurality of adapter specific actions being received via the user interface, updating the configuration of the first adapter of the plurality of adapters and accordingly modifying actions of the first adapter of the plurality of adapters within the integration flow.
8 . The method of claim 7 , wherein each of the plurality of adapter specific actions associated with the first adapter are stored as extensible markup language (XML) within the metadata associated with the first adapter.
9 . The method of claim 8 , wherein the first adapter comprises a connection having a trigger role within the integration flow.
10 . The method of claim 9 ,
wherein a further instruction is received at the integration platform, the further instruction indicating a of another of the plurality of adapter specific actions associated with the first adapter to be used within the integration flow; and
wherein upon the selection of the another of the plurality of adapter specific actions associated with the first adapter to be used within the integration flow, the non-selected adapter specific actions are excluded from use within the integration flow.
11 . The method of claim 8 , wherein the first adapter comprises a connection having an invoke role within the integration flow.
12 . The method of claim 11 ,
wherein a further instruction is received at the integration platform, the further instruction indicating a selection of another of the plurality of adapter specific actions associated with the first adapter to be used within the integration flow; and
wherein upon the selection of the another of the plurality of adapter specific actions associated with the first adapter to be used within the integration flow, the non-selected adapter specific actions are excluded from use within the integration flow.
13 . A non-transitory computer readable storage medium, having instructions for exposing features of integration platform adapters as first-class actions in an orchestration template, which when read an executed cause a computer to perform steps comprising:
providing a computer including one or more microprocessors;
providing an integration platform running on the computer;
receiving instructions at the integration platform, the instructions comprising information indicative of an integration flow to be built within the integration platform, wherein the instructions indicate a plurality of adapters to be used within the integration flow, wherein the instructions indicate a first adapter of the plurality of adapters, the first adapter being associated with a first application external to the integration platform, to be utilized within the integration flow, the first adapter of the plurality of adapters being associated with a set of properties defined within metadata associated with the first adapter, the set of properties comprising at least action properties and runtime properties,
wherein the first adapter of the plurality of adapters is associated with a role defined within the integration flow;
wherein the action properties associated with the first adapter of the plurality of adapters comprise at least a set of first-class action properties, wherein each of the set of first-class action properties are compiled during development of the first adapter and marked with specific properties including a property indicating to the first adapter to render an action based wizard for each of the set of first-class action properties;
displaying, as a set of selectable options, a determined set of a plurality of adapter specific actions associated with the first adapter of the plurality of adapters, the determined set of the plurality of adapter specific actions being selected from the set of properties associated with the first adapter, said selection excluding runtime properties, together with associated context sensitive information, via a user interface of the integration platform, each of the determined set of the plurality of adapter specific actions being associated with the defined role of the first adapter within the integration flow, each of the determined set of plurality of adapter specific actions being defined within a configuration of the first adapter of the plurality of adapters, the configuration being associated with the integration flow, wherein the determined set of the plurality of adapter specific actions are determined based upon an action of the first adapter within the integration flow;
based upon a second adapter of the plurality of adapters, the second adapter being associated with a second application external to the integration platform, the second application being different than the first application, having a same defined role within the integration flow, the second adapter of the plurality of adapters being associated with a second set of properties defined within metadata associated with the second adapter, the second set of properties comprising at least action properties and runtime properties, selecting to be displayed another determined set of a plurality of adapter specific actions, the determined another set of the plurality of adapter specific actions being selected from the second set of properties associated with the second adapter, said selection excluding runtime properties, associated with the second adapter of the plurality of adapters, wherein the another determined set of a plurality of adapter specific actions associated with the second adapter are displayed as another set of selectable options together with the display of the determined set of the plurality of adapter specific actions associated with the first adapter of the plurality of adapters; and
upon an indication a selection of one of the determined set of the plurality of adapter specific actions being received via the user interface, updating the configuration of the first adapter of the plurality of adapters and accordingly modifying actions of the first adapter of the plurality of adapters within the integration flow.
14 . The non-transitory computer readable storage medium, of claim 13 , wherein each of the plurality of adapter specific actions associated with the first adapter are stored as extensible markup language (XML) within the metadata associated with the first adapter.
15 . The non-transitory computer readable storage medium, of claim 14 , wherein the first adapter comprises a connection having a trigger role within the integration flow.
16 . The non-transitory computer readable storage medium, of claim 15 ,
wherein a further instruction is received at the integration platform, the further instruction indicating a selection of another of the plurality of adapter specific actions associated with the first adapter to be used within the integration flow; and
wherein upon the selection of the another of the plurality of adapter specific actions associated with the first adapter to be used within the integration flow, the non-selected adapter specific actions are excluded from use within the integration flow.
17 . The non-transitory computer readable storage medium, of claim 14 ,
wherein the first adapter comprises a connection having a trigger role within the integration flow;
wherein a further instruction is received at the integration platform, the further instruction indicating a selection of another of the plurality of adapter specific actions associated with the first adapter to be used within the integration flow; and
wherein upon the selection of the another of the plurality of adapter specific actions associated with the first adapter to be used within the integration flow, the non-selected adapter specific actions are excluded from use within the integration flow.