Endpoints represent location and authentication information for SOAP and REST Web services and are used in applications and orchestrations. The endpoint in the process app itself is called a process app endpoint and corresponds to a place in the process app where a Web service is called. The values of the location URL and authentication information that are mapped to the endpoint at deployment or promotion are called environment endpoints. Environment endpoint values can be modified when you deploy or promote a process app into an environment, enabling you to use different values for different environments.
Endpoints enable you to test a process app with one environment, perhaps on an isolated network on a test server, and then roll out the process app to a production environment, with a more secure server. By specifying different endpoints in each of these environments, you can change the service used and/or authentication information without having to edit the details of the process app workflows.
Not all authentication types that are configurable in Composer (as hints) and in Application Repository are useable for all types of Web services. For example, the NTLM authentication type only applies to custom endpoints when calling REST services (from the REST Grid, RESTCaller, or in JavaScript that is embedded on an Application Engine page). Refer to the following table for a summary:
| Authentication Type | SOAP Calls | REST Calls |
|---|---|---|
| None | 
|
|
| SSO |
|
|
| HTTP Basic | (see below)
|
|
| NTLM | Not applicable |
|
| OAuth 2 | Not applicable |
|
| WS-Addressing (WSA) | (see below)
|
Not applicable |
- You can set HTTP Basic on the endpoint or explicitly in an orchestration. If both are set, the endpoint configuration overrides the orchestration setup.
- You cannot set WSA authentication on an endpoint in Application Repository, but WSA authentication can be set explicitly in orchestrations in a limited way.
On-premise installations only: To restrict access to an endpoint, you can use SBM Application Administrator to remove the permission to edit an environment in general and the permission to edit endpoints in particular. Note that without permission to edit the environment overall, a user can still edit the endpoints associated with that environment if the user has the Create, Edit, and Delete Endpoints privilege. If a user does have the permission to edit an environment, that user can edit endpoints even without the Create, Edit, and Delete Endpoints privilege, so you have to disable both privileges in that case.