Perform the following steps to create an app connection:
1In Application Integration, click New.
2In the New Asset dialog box, click App Connections > App Connection, and then click Create as shown in the following image:
Defining App Connection Properties
For each app connection, you enter descriptive properties, identify the scope, and set authentication parameters, if required.
These options display for all app connections:
•Connection Type: From this list, select a published service connector, native toolkit connector (such as JDBC), or web service connector (such as Salesforce). When you create a connection, the connection type that you select determines the connection properties that are displayed.
Note: After you publish an app connection, you cannot change its connection type.
•Name: Enter a name that identifies an app connection within processes and in the Designer. The name must start with a letter, and can contain only alphanumeric characters, multibyte characters, and hyphens (-). The name must not exceed 128 characters. This is a required field.
Important: If you define an app connection to be used for publishing processes in Salesforce, the Connection Name must be Salesforce to ensure that the processes are accessible to users in Salesforce. Only one Salesforce app connection is permitted for each Application Integration organization.
•Description: Enter a description to identify an app connection.
•Run On: Select the agent where you want to access a service behind your firewall or select Cloud Server or any Secure Agent. This list displays the agents available for your organization.
•Connection Test: Displays the results of any connection test run on the Cloud Server or the agent named in the Run On field.
•OData Enabled: Select Yes to enable OData feeds. If you select Yes, you must specify either the allowed users or the allowed groups that can access the connection at design time. You can also enable or disable Cloud access to the OData endpoint URLs.
After you enable OData in an app connection and publish the connection, you can click Actions > Properties Detail to view the generated OData Service URL and OData Swagger URL.
The OData Service URL is available on an Informatica Cloud endpoint and uses the following format:
For more information about enabling the OData protocol in a Data Access Service Connector, see Defining Properties.
•OData Cloud Access Enabled: If you enable OData and configure the connection to run on a Secure Agent machine or a Secure Agent group, you can choose to disable Cloud access to the OData endpoint URLs for security purposes.
•Allowed Users for OData:
The users that have access to this app connection at run time. You can enter more than one user in this field. After you specify the first value, press the Enter key or the Comma key, and then specify the next value.
Allowed Roles for OData:
The roles that have access to this app connection at run time. Users assigned these roles have access to an OData endpoint URL. You can enter a custom role or a system-defined role. You can enter more than one role in this field.
IMPORTANT: If you enter a custom role in the Allowed Roles for OData field, a user invoking the OData endpoint URL must have or belong to groups that have the custom role and the Service Consumer role.
Example:
Your organization has a custom role, Testers, with the Run privilege enabled for Application Integration. You create a process and enter 'Testers' in the Allowed Roles field.
For a user to be able to use the OData endpoint URL, the following conditions need to be met:
- Condition 1: The user has the Testers role, a role that this app connection requires.
- Condition 2: The user has the Service Consumer role. Application Integration requires this role to invoke any endpoint URL.
A user with the Testers role and the Service Consumer role will be able to invoke the OData endpoint URL. This is because both, Condition 1 and Condition 2, are satisfied.
A user with only the Testers role will be unable to invoke the OData endpoint URL. This is because Condition 1 is satisfied but Condition 2 is not satisfied.
A user with only the Service Consumer role will also be unable to invoke this OData endpoint URL. This is because Condition 2 is satisfied but Condition 1 is not satisfied.
•Schema: Enter the name of the schema that contains the tables that you want to include or exclude in the metadata. To view the appropriate results, you must enter a schema name in the app connection that uses the data access service connector.
•Include Tables: Enter the names of the tables that you want to include in the metadata. To include a list of tables, use a comma to separate multiple table names. You can also use '.*' for pattern matching. To view the appropriate results, you must also mention the included table names in the app connection that uses the data access service connector.
•Exclude Tables: Enter the names of the tables that you want to exclude from the metadata. To exclude a list of tables, use a comma to separate multiple table names. You can also use '.*' for pattern matching. To view the appropriate results, you must also mention the excluded table names in the app connection that uses the data access service connector.
The remaining properties are determined by the connector or the connection type that you selected. After you enter the property value, click anywhere outside the property row or press Enter to save the value.
For example, the Salesforce connection type in the following image requires a Name, Type, Authorization URL, and Token Request URL:
Specifying Event Sources
Event sources are available for some app connections based on the service connector.
For the following AMQP app connection that provides access to the AMQP listener service, you can add one or more event sources:
First, click Add Event Source to add a new event source for this app connection. Then enter the following information for each event:
•Name: Enter a unique name for each event source. The name must start with a letter, and can contain only alphanumeric characters, and hyphens (-). This is a required field.
•Description: Enter a description, if needed, for the event source.
•Enabled: Select No to disable the event source until you are ready to deploy it. This gives you the flexibility to configure multiple event sources and determine when to enable them.
The connection properties that you need to configure vary based on the connection type. In this case, the AMQP connection requires the Destination Type, Destination, and Payload Format fields to be configured.
A message displays on the tab to notify you if the preview option is not enabled or supported for the connection type.
Specifying Event Targets
Similar to event sources, you can specify one or more event targets for each app connection on a separate tab.
Each connector might define different types of event targets. For example, using the File connector, you can select either File Writer or Delimited Content Writer File Writer for each event target that you define. Each event target includes a set of properties unique to that event target type.
To create a new event target:
1Click Add Event Target (and choose the target type, if applicable) a new row is added.
2Highlight the row and add an event name and description.
