+

Deploying AS2, HTTP, and HTTPS Receive Endpoints

You can deploy AS2 receive, HTTP receive, and HTTPS receive endpoints on a public port, private port, or on-premises.

Deploy to CloudHub on a Public Port

When an AS2, HTTP, or HTTPS receive endpoint is deployed with the public port configuration enabled, the endpoint application is deployed on the public HTTPS port (8082), with the traffic routed through the shared load balancer. The value in the URL field is automatically generated when you deploy a message flow to CloudHub that uses this endpoint.

You can view the runtime application name and external URL for a deployed endpoint from the endpoint details page. For example:

Example of a runtime application name and external URL

You can share the external URL with the partners that send AS2, HTTP, or HTTPS messages to this endpoint.

If your organization uses Anypoint VPC without a dedicated load balancer (DLB), your organization’s platform administrator can configure the necessary VPC firewall rules to allow specific partner or third-party connection IP addresses to access the endpoint.

Deploy to CloudHub on a Private Port

To deploy an AS2, HTTP, or HTTPS receive endpoint with the private port configuration enabled, do either of the following:

  • Deploy a message flow that includes the receive endpoint.

  • Set CloudHub to automatically deploy newly created endpoints to a private port, as described in CloudHub deployment settings.

Endpoints with the private port configuration enabled are deployed to the private HTTPS port 8092. You can view the runtime application name, internal URL, and external URL for a deployed endpoint from the endpoint details page, which you can access from the host page (AS2 endpoints) or partner page (HTTP or HTTPS endpoints), or from a message flow.

Once an endpoint is deployed, follow these steps:

  1. Configure URL mapping rules to forward the messages received from your partners to an application, as described in the following sections and in Dedicated Load Balancer Mapping Rules.

  2. Have your organization’s platform administrator add your partner’s IP addresses to a list of allowed addresses in the DLB setting, as described in Dedicated Load Balancer Allowlists.

External URLs and Mapping Rules for Deployed Receive Endpoints

The external URLS for receive endpoints deployed to public or private ports vary depending on the endpoint type, DLB domain, and input start_paths. You can share external URLs with your partners.

External URL and Mapping Rules for an AS2 Receive Endpoint

The external URL for an AS2 receive endpoint is https://{DLB-domain}/{Input-path}/receive-as2.

For example, if the name of your DLB domain is mythical.lb.anypointdns.net and the runtime application name is b2b-inbound-as2-zap3, then your administrator can add a URL mapping rule in the DLB settings to forward incoming requests to the runtime application within your VPC:

URL mapping rules for AS2 in the DLB settings

With this configuration, the external AS2 endpoint URL is https://mythical.lb.anypointdns.net/as2/mythical/receive-as2/.

External URL and Mapping Rule for an HTTPS Receive Endpoint

The external URL for an HTTPS endpoint is https://{DLB-domain}/{Input-path}/{base-path}/{message-type}.

For example, if the name of your DLB domain is mythical.lb.anypointdns.net, the base path you configured for the endpoint is send2, and the runtime application name is b2b-inbound-http-ognq, then your administrator can add a URL mapping rule in the DLB settings to forward incoming requests to the runtime application within your VPC. For example:

URL mapping rules for HTTPS in the DLB settings

External URL and Mapping Rules for an HTTP Receive Endpoint

The external URL for an HTTP Receive from Partners or Source at Host endpoint is http://{DLB-domain}/{Input-path}/{base-path}/{message-type}, where the partner supplies the values for {DLB-domain} and {Input-path}, the value for {base-path} is obtained from the endpoint configuration, and the value for {message-type} is obtained from the configuration of the associated message flow.

Suppose you configure an HTTP Receive from Partners endpoint to use in an inbound message flow. In this example, the name of your DLB domain is mythical.lb.anypointdns.net, the input path is apm/inbound, the base path of the endpoint is receive, the message type for the message flow is pacific-purchase-order, and the runtime application name is b2b-inbound-http-ognq.

Given these example values:

  • The external URL for the endpoint is http://mythical.lb.anypointdns.net/apm/inbound/receive/.

  • Your partner sends the application JSON and XML messages to your inbound message flow at https://mythical.lb.anypointdns.net/apm/inbound/receive/pacific-purchase-order.

Your administrator can add a URL mapping rule in the DLB settings like the following to forward incoming requests to the runtime application within your VPC:

URL mapping rule for the HTTP endpoint in this example

Deploy to an On-Premises Mule Instance

To deploy to an on-premises Mule instance that uses a firewall and load balancer, work with your organization’s hosting or network security team to obtain the externally accessible DNS or the name of the instance host. Replace the {runtime_host} value in the URL with the specific value for your organization.

Was this article helpful? Thanks for your feedback!
View on GitHub