Web Service Provide and HTTP Receive Activities

When a tenant deploys an orchestration containing Web Service Provide activity on to an environment in App Connect on Cloud, the same tenant cannot deploy another Web Service Provide orchestration on to the same environment having the same URL in the endpoint.

HTTP Receive Request activity

When a tenant deploys an orchestration containing HTTP Receive Request activity to an environment in App Connect on Cloud, the same tenant cannot deploy another HTTP Receive Request activity to the same environment with the same URL and method.

For single HTTP Receive Request activity:

If you deploy only one HTTP Receive Request activity for a URL, the orchestration accepts all requests of those URLs starting with that base URL*. For example, if you deploy /customer then it accepts requests for /customer, /customer/21, /customer/21/dept, and so on.

If you deploy an HTTP Receive Request activity for a URL with path parameters, then the orchestration accepts only those requests whose URLs match with the configured URL with values for path parameters. For example, if you deploy /customer/{custid} then it accepts requests such as /customer/10, /customer/21, /customer/dept . The following URLs are not accepted: /customer, /customer/21/dept, and so on.

For multiple HTTP Receive Request activities:

If you deploy two HTTP Receive Request activities that are configured with the same base URLs, and one with path parameter, then the activities accept requests whose URLs strictly match with the configured URL. For example, if you deploy /customer and /customer/{path parameter}, and if /customer is invoked the request goes to the activity configured with /customer. If /customer/007 is invoked, the request goes to the activity configured with /customer/{path parameter}. Also, if you invoke the following URLs: /customer/dept/1 or /customer/12/21, none of the activities accept the requests.

Note: If you deploy two activities, the first one as /customer/department and the second one as /customer/{path parameter}, and if /customer/department is invoked, then the request goes to the activity configured with /customer/department.
Note: It is also recommended that you do not deploy the same URL for Web Services and HTTP.
* BaseURL: Part of the URL before path parameters. For example - If the configured URL is /employee/manager/{id} then Base URL will be /employee/manager.



Feedback | Notices


Timestamp icon Last updated: Monday, 22 July 2019


http://pic.dhe.ibm.com/infocenter/wci/v7r0m0/topic/com.ibm.wci.live.doc/CloudHelp/Managing_Integration_Appliances/installing3rdPartyLibraries.html