Invoke

Back Next

REST and Process Designer SOAP Endpoints to Access Message Events

You can access message events using REST and SOAP 1.1 endpoints generated by Process Designer. If SOAP 1.2 endpoints are required please use Process Developer to generate these endpoints. To obtain endpoints of services created using Process Developer, refer to information on policy-driven bindings in the Process Developer Guide
.

When the number of REST or SOAP request exceeds the rate limit within the designated time frame, a HTTP 429 status code appears.

The following table specifies the pattern for each REST or SOAP 1.1 endpoint based on the type of access required when you invoke message events.

The process uses HTTP Basic access authentication when you uncheck

Allow anonymous access

in the process Start properties or the Messages properties for message events. You can define a process to authenticate differently than the callback it receives, in message events or subprocess calls.

Type of Access	REST URL Format	SOAP 1.1 URL Format
Process with HTTP Basic access authentication	https://{host}/active-bpel/rt/{ProcessName}	https://{host}/active-bpel/soap/{ProcessName}
Process with OAuth2 authentication	https://{host}/active-bpel/rt/{ProcessName}	https://{host}/active-bpel/soap/{ProcessName}
Process with Anonymous access	https://{host}/active-bpel/public/rt/{TenantName}/{ProcessName}	https://{host}/active-bpel/public/soap/{TenantName}/{ProcessName}
Process Message Event with Anonymous access	https://{host}/active-bpel/public/rt/{TenantName}/{ProcessName}/event/{MessageName}	https://{host}/active-bpel/public/soap/{TenantName}/{ProcessName}/event/{MessageName}
Process Message Event with HTTP Basic access authentication	https://{host}/active-bpel/rt/{ProcessName}/event/ {MessageName}	https://{host}/active-bpel/soap/{ProcessName}/event/{MessageName}
Process Message Event in subProcess with Anonymous access	https://{host}/active-bpel/public/rt/{TenantName}/{SubProcessName}/event/{MessageName}	https://{host}/active-bpel/public/soap/{TenantName}/{ProcessName}/event/{MessageName} or https://{host}/active-bpel/public/soap/{TenantName}/{SubProcessName}/event/{MessageName}
Process Message Event in subProcess with HTTP Basic access authentication	https://{host}/active-bpel/rt/{SubProcessName}/event/{MessageName}	https://{host}/active-bpel/soap/{ProcessName}/event/{MessageName} or https://{host}/active-bpel/soap/{SubProcessName}/event/{MessageName}

For SOAP requests, you can use the default process or sub process endpoint if the event has the same access, either anonymous or HTTP Basic access authentication, as the process or sub process.

Invoking Processes Deployed to the Cloud Server

Download Guide

Watch

Comments

Cloud Application Integration Homepage