Design

Back Next

Start Properties

Use the

Start

tab to define the binding type, access details, and the runtime environment details.

You can define the following start properties for a process:

Binding

The

Binding

property defines how a process is invoked and run.

You can select one of the following values:

REST/SOAP
: Select the

REST/SOAP

binding type if you want to run the process by using a service URL. When you select this option, you can use the

Allowed Groups

and the

Allowed Users

fields to define the user groups and users who can run a published process as an API. If you do not want to assign any user, you can select the

Allow anonymous access

option.

Event
: Select the

Event

binding type if you want the process to be invoked when the specified event occurs. For example, a process can be invoked upon an event such as arrival of a file in a file system. The

Event Source Name

field is available where you can select an event source.

Default is REST/SOAP.

Allowed Groups

The groups that have access to the process service URL at run time. If the users in the group also have the Run privilege, they can invoke the process service URL.

Use the

Allowed Groups

field when you want a group of users to have access to a service URL. For example, you have a group called 'Order Approvers'. If you enter

Order Approvers

in the

Allowed Groups

field, all users within the group will have access to the service URL.

The following image shows the Order Approvers group added to the

Allowed Groups

field:

You can enter more than one group in the field.

You can configure the

Allowed Groups

and the

Allowed Users

fields. If a user falls into either the

Allowed Groups

or the

Allowed Users

category, the user will have access to the service URL.

If you configure the

Allowed Groups

or the

Allowed Users

field, and select the

Allow anonymous access

option, the entered group or user details disappear.

If you select the

Allow anonymous access

option, the

Allowed Groups

and the

Allowed Users

fields are not available for edit.

If you do not configure the

Allowed Groups

or the

Allowed Users

field, or do not select the

Allow anonymous access

option, no service URL is available for the process. However, you can call the process as a subprocess.

If you want the process to appear in API Manager, you must either select the

Allow anonymous access

option, or configure the

Allowed Groups

or the

Allowed Users

field. For more information about managing APIs, see the API Manager help.

If a process uses the

Allowed Groups

or the

Allowed Users

fields, you can use one of the following ways to invoke the process through a REST client such as Postman:

Use basic authentication, and enter the user name and password.

Use session ID in the HTTP header to invoke the process without providing the user name and password.

For example, to invoke a process service URL using Postman, authenticate the GET request in one of the following ways:

Use basic authorization and specify the Informatica Intelligent Cloud Services user name and password.

For example:

GET <Informatica Intelligent Cloud Services URL>/active-bpel/rt/<API unique name>
Accept: application/json
Authorization: Basic Auth
username: <Informatica Intelligent Cloud Services user name>
password: <Informatica Intelligent Cloud Services password>

Use the IDS-SESSION-ID in the HTTP header.

For example:

GET <Informatica Intelligent Cloud Services URL>/active-bpel/rt/<API unique name> 
Accept: application/json
IDS-SESSION-ID: <sessionId>

To get the SESSION-ID, use the Platform REST API version 3 login resource. For more information about the login resource, see

REST API Reference

Allowed Users

The users that have access to the process service URL at run time. If the users also have the Run privilege, they can invoke the process service URL.

Use the

Allowed Users

field when you want a specific user to have access to the service URL.

The following image shows the user

jsmith

in the

Allowed Users

field and the group

Order Approvers

in the

Allowed Groups

field:

In this process, users in the Order Approvers group and the user jsmith will have access to the service URL.

You can enter more than one user in the field.

If you configure the

Allowed Groups

or the

Allowed Users

field, and select the

Allow anonymous access

option, the entered group or user details disappear.

If you select the

Allow anonymous access

option, the

Allowed Groups

and the

Allowed Users

fields are not available for edit.

If you do not configure the

Allowed Groups

or the

Allowed Users

field, or do not select the

Allow anonymous access

option, no service URL is available for the process. However, you can call the process as a subprocess.

If you want the process to appear in API Manager, you must either select the

Allow anonymous access

option, or configure the

Allowed Groups

or the

Allowed Users

field. For more information about managing APIs, see the API Manager help.

If a process uses the

Allowed Groups

or the

Allowed Users

fields, you can use one of the following ways to invoke the process through a REST client such as Postman:

Use basic authentication, and enter the user name and password.

Use session ID in the HTTP header to invoke the process without providing the user name and password.

For example, to invoke a process service URL using Postman, authenticate the GET request in one of the following ways:

Use basic authorization and specify the Informatica Intelligent Cloud Services user name and password.

For example:

GET <Informatica Intelligent Cloud Services URL>/active-bpel/rt/<API unique name>
Accept: application/json
Authorization: Basic Auth
username: <Informatica Intelligent Cloud Services user name>
password: <Informatica Intelligent Cloud Services password>

Use the IDS-SESSION-ID in the HTTP header.

For example:

GET <Informatica Intelligent Cloud Services URL>/active-bpel/rt/<API unique name> 
Accept: application/json
IDS-SESSION-ID: <sessionId>

To get the SESSION-ID, use the Platform REST API version 3 login resource. For more information about the login resource, see

REST API Reference

Only accepts HTTP authorization requests from the API Gateway

Select this option to enable OAuth2 authentication for the process and configure the API to accept only HTTP authorization requests from the API Gateway.

To invoke the API from the API Gateway, the following users must complete configuration tasks:

API provider: The API provider must perform the following tasks:
Create a managed API for the process in API Manager and enable OAuth2 authentication for the managed API.
Create an OAuth2 client in API Manager, and generate the client ID and client secret.
Send the Informatica Intelligent Cloud Services OAuth 2.0 server URL and the client credentials to the API consumers.
API consumers: API consumers must perform the following tasks:
Authenticate against the Informatica Intelligent Cloud Services OAuth 2.0 server and use the OAuth 2.0 client credentials to generate an OAuth 2.0 authorization token.
Use the OAuth 2.0 authorization token to invoke the API.

For more information about creating an OAuth2 client and invoking an API with OAuth2 authentication, see the API Manager help.

You can use the

Only accepts HTTP authorization requests from the API Gateway

option only for processes that run on the Cloud Server. Processes that use the

Only accepts HTTP authorization requests from the API Gateway

option can also be scheduled and run with one or more process inputs.

Allow anonymous access

When selected, Process Designer lets anyone use the process. This means that access to the process is not tied to a specific user or to any user group.

If you select the

Allow anonymous access

option, the

Allowed Groups

and the

Allowed Users

fields are not available for edit.

If you configure the

Allowed Groups

or the

Allowed Users

field, and select the

Allow anonymous access

option, the entered group or user details disappear.

If you do not configure the

Allowed Groups

or the

Allowed Users

field, or do not select the

Allow anonymous access

option, no service URL is available for the process. However, you can call the process as a subprocess.

If you want the process to appear in API Manager, you must either select the

Allow anonymous access

option, or use the

Allowed Groups

Allowed Users

fields. For more information about managing APIs, see the API Manager help.

Applies To

The type of object associated with the process. The objects that display in this list are the process objects you defined separately or generated in a defined connection. Drill down the list to see process objects and connections, and then select one of these items. Select a process object only if the process will be embedded in another process.

To change the

Applies To

property of a published process, you must first unpublish the process. Then, change the

Applies To

property and republish the process

There are two special values:

Any
: Choose Any if you do not want to associate the process with a specific object. When you select this option, the process does not automatically have access to an object's fields.

Use this object type when a process creates a new object and does not access information within existing objects.

Home (Salesforce)
: Select Home if you want a process to be visible from Home or any initial location where users launch all processes, regardless of the object type.

If you directly invoke a process, the

Applies To

setting must be either

Any

or a specific object in a service, but not a process object.

Run On

Use this list to specify where the process must run. You can select

Cloud Server

, a specific agent, or a Secure Agent group.

If a process uses a connector that is event based, ensure that you run the process on the same agent that the connector runs on.

When the process is in the published state, the

Run On