Working with Environments → About Environments → About Endpoints
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.
|Authentication Type||SOAP Calls||REST Calls|
|HTTP Basic||(see below)|
|OAuth 2||Not applicable|
|WS-Addressing (WSA)||(see below)||Not applicable|
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.
Copyright © 2007–2016 Serena Software, Inc. All rights reserved.