Framework to resolve protocol endpoints in integration platform

A method, comprising:

• receiving, by an ingress component, from a client, a HyperText Transfer Protocol (“HTTP”) Uniform Resource Locator (“URL”) and HTTP header information for an incoming protocol message;
• determining, by a computer processor of an endpoint selector, the HTTP header information, wherein the endpoint selector supports incoming protocol messages associated with multiple types of message protocols, including all of the Applicability Statement 2 (“AS2”) protocol, the Applicability Statement 4 (“AS4”) protocol, and the Open Data (“OData”) protocol;
• determining, by the computer processor, an endpoint address associated with the incoming protocol message;
• based on the incoming HTTP header information and the endpoint address of the incoming protocol message, dynamically resolving, by the computer processor, an appropriate deployed endpoint;
• outputting, by the computer processor, an indication of the dynamically resolved appropriate deployed endpoint to an integration platform;
• and
• executing, by a runtime component of the integration platform coupled to the ingress component, the incoming protocol message by interfacing with the appropriate deployed endpoint;
• an integration studio that communicates with a deploy controller;
• wherein the deploy controller communicates with a policy engine and an integration runtime;
• wherein integration studio creates an iFlow object that models integration processes;
• wherein the iFlow object is transformed into a data format that includes both:
• (i) a first part understood by the policy engine to generate inbound endpoint addresses, and (ii) a second part that contains instructions and processing logic executed by the integration runtime.

A non-transitory, machine-readable medium comprising instructions thereon that, when executed by a processor, cause the processor to execute operations to perform a method, the method comprising:

• receiving, by an ingress component, from a client, a HyperText Transfer Protocol (“HTTP”) Uniform Resource Locator (“URL”) and HTTP header information for an incoming protocol message;
• determining, by a computer processor of an endpoint selector, the HTTP header information, wherein the endpoint selector supports incoming protocol messages associated with multiple types of message protocols, including all of the Applicability Statement 2 (“AS2”) protocol, the Applicability Statement 4 (“AS4”) protocol, and the Open Data (“OData”) protocol;
• determining, by the computer processor, an endpoint address associated with the incoming protocol message;
• based on the incoming HTTP header information and the endpoint address of the incoming protocol message, dynamically resolving, by the computer processor, an appropriate deployed endpoint;
• outputting, by the computer processor, an indication of the dynamically resolved appropriate deployed endpoint to an integration platform;
• and
• executing, by a runtime component of the integration platform coupled to the ingress component, the incoming protocol message by interfacing with the appropriate deployed endpoint;
• an integration studio that communicates with a deploy controller;
• wherein the deploy controller communicates with a policy engine and an integration runtime;
• wherein integration studio creates an iFlow object that models integration processes;
• wherein the iFlow object is transformed into a data format that includes both:
• (i) a first part understood by the policy engine to generate inbound endpoint addresses, and (ii) a second part that contains instructions and processing logic executed by the integration runtime.