Provide the login endpoint to initiate communication with the SaaS provider. Example: https://login.salesforce.com/services/Soap/u/31.0.

The number of milliseconds Integration Cloud waits for a response before canceling its attempt to connect to the back end. In case the network is slow or the back end processing takes longer than usual, increase the Response Timeout value. It is recommended to specify a value other than 0. If you specify 0, Integration Cloud will wait indefinitely for a response.

The number of times Integration Cloud attempts to connect to the back end to read a response if the initial attempt fails. If an I/O error occurs, it will retry only if you have selected the Retry on Response Failure option.

Whether Integration Cloud should attempt to resend the request when the response has failed, even though the request was sent successfully. Select this option if you want to re-establish the connection.

This is the user account name on the SaaS provider that the Account will use to connect to the SaaS provider.

The password for the user name provided in the Username field. When you access Salesforce from outside your company’s trusted networks, you must append a security token (provided by Salesforce) to your password. Your security token may have been emailed to you when you had set up your Salesforce account or if you had reset your password. For example, if your password is abc and your security token is xxxx, then you must enter abcxxxx. For more information about logging in to Salesforce, see the Salesforce documentation.

The type of HTTP authorization scheme to use for the connection. If you select none, no additional authorization scheme will be executed at run time. For example, when you specify a Username and Password, but do not specify a value for the Authorization Type, the user credentials are not inserted into an Authorization header. If you enter the username and password, then set the authorization type as basic. Basic refers to HTTP Basic Authentication. This option can be used if the Application requires or supports HTTP Basic authentication using a username and password.

The number of minutes you want Integration Cloud to wait before terminating an idle session. The session timeout value must be within the range of 10 and 60 minutes.

Enable this option if you want to send or receive a large binary stream with a chunk size of 8192 bytes. This is applicable only if the back end supports HTTP/1.1 chunking.

Select the alias name of the Integration Cloud trust store configuration. The trust store contains trusted certificates used to determine trust for the remote server peer certificates. You can also add a new Truststore from this field.

Select a hostname verifier implementation. Guards against man-in-the-middle (MITM) attacks. The default is org.apache.http.conn.ssl.DefaultHostnameVerifier, which will enable hostname verification. Select org.apache.http.conn.ssl.NoopHostnameVerifier to disable hostname verification.

Select the alias for the Integration Cloud key store configuration. This is a text identifier for the keystore alias. A keystore file contains the credentials (private key/signed certificate) that a client needs for authentication. You can also add a new Keystore from this field.

Alias to the private key in the keystore file specified in the Keystore Alias field. The outbound connections use this key to send client credentials to a remote server. To send the client’s identity to a remote server, you must specify values in both the Keystore Alias and the Client Key Alias fields.

Select this option if you want to enable connection pooling for a connection.

Integration Cloud includes a connection management service that dynamically manages connections and connection pools based on configuration settings that you specify for the connection. A connection pool is a collection of connections with the same set of attributes. Connection pools improve performance by enabling Integrations to reuse open connections instead of opening new connections for every service request.

When you enable connection pooling, Integration Cloud creates the number of connection instances you specified in the connection's Minimum Pool Size field. Whenever an Integration needs a connection, Integration Cloud provides a connection from the pool. If no connections are available in the pool, and the Maximum Pool Size has not been reached, Integration Cloud creates one or more new connections (according to the number specified in the Pool Increment Size field) and adds them to the connection pool.

If the pool is full (as specified in the Maximum Pool Size field), the requesting service will wait for Integration Cloud to obtain a connection till one sec, until a connection becomes available. Periodically, Integration Cloud inspects the pool and removes inactive connections that have exceeded the expiration period of one sec.

The minimum number of connection objects that remain in the connection pool at all times, if connection pooling is enabled. When the connector creates the pool, it creates this number of connections.

The maximum number of connection objects that can exist in the connection pool if connection pooling is enabled. When the connection pool has reached its maximum number of connections, the connector will reuse any inactive connections in the pool, or, if all connections are active, it will wait for a connection to become available.

The number of connections by which the pool will be incremented, up to the maximum pool size, if connection pooling is enabled and connections are needed.

Provide the login endpoint to initiate communication with the SaaS provider. Example: https://login.salesforce.com/services/Soap/u/44.0.

This is the user account name on the SaaS provider that the Account will use to connect to the SaaS provider.

The password for the user name provided in the Username field. When you access Salesforce from outside your company’s trusted networks, you must append a security token (provided by Salesforce) to your password. Your security token may have been emailed to you when you had set up your Salesforce account or if you had reset your password. For example, if your password is abc and your security token is xxxx, then you must enter abcxxxx. For more information about logging in to Salesforce, see the Salesforce documentation.

The type of HTTP authorization scheme to use for the connection. If you select none, no additional authorization scheme will be executed at run time. For example, when you specify a Username and Password, but do not specify a value for the Authorization Type, the user credentials are not inserted into an Authorization header. If you enter the username and password, then set the authorization type as basic. Basic refers to HTTP Basic Authentication. This option can be used if the Application requires or supports HTTP Basic authentication using a username and password.

The number of minutes you want Integration Cloud to wait before terminating an idle session. The session timeout value must be within the range of 10 and 60 minutes.

The number of milliseconds Integration Cloud waits for a response before canceling its attempt to connect to the back end. In case the network is slow or the back end processing takes longer than usual, increase the Response Timeout value. It is recommended to specify a value other than 0. If you specify 0, Integration Cloud will wait indefinitely for a response.

The number of milliseconds a connection waits before canceling its attempt to connect to the resource. If you specify 0, the connection waits indefinitely. It is recommended that you specify a value other than 0 to avoid using a socket with no timeout.

The number of times the system should attempt to initialize the connection at startup if the initial attempt fails.

The system retries to establish a connection when an I/O error occurs while sending the request message to the back end. If an I/O exception occurs when the system is reading a response back from the back end, the system will only retry if Retry on Response Failure is enabled.

Applicable when you select the Salesforce OAuth 2.0 JWT Token Flow as the Authentication Type. This is the Client ID, or Identifier, or name of the server or system issuing the JWT token.

Applicable when you select the Salesforce OAuth 2.0 JWT Token Flow as the Authentication Type. This is the identifier or the name of the user this token represents.

Applicable when you select the Salesforce Web Server Authentication Flow as the Authentication Type. Also referred to as the Client ID, this is a client identifier issued to the client to identify itself to the authorization server.

Applicable when you select the Salesforce Web Server Authentication Flow as the Authentication Type. Also referred to as the Client Secret, this is a secret matching to the client identifier.

Applicable when you select the Salesforce Web Server Authentication Flow as the Authentication Type. This token is used for authentication and is issued by the Authorization Server.

Applicable when you select the Salesforce Web Server Authentication Flow as the Authentication Type. A token used by the client to obtain a new access token without involving the resource owner.

Applicable when you select the Salesforce Web Server Authentication Flow as the Authentication Type. This is the provider specific URL to refresh an Access Token.

The number of times Integration Cloud attempts to connect to the back end to read a response if the initial attempt fails. If an I/O error occurs, it will retry only if you have selected the Retry on Response Failure option.

Whether Integration Cloud should attempt to resend the request when the response has failed, even though the request was sent successfully. Select this option if you want to re-establish the connection.

Select the alias name of the Integration Cloud trust store configuration. The trust store contains trusted certificates used to determine trust for the remote server peer certificates. You can also add a new Truststore from this field.

Select the alias for the Integration Cloud key store configuration. This is a text identifier for the keystore alias. A keystore file contains the credentials (private key/signed certificate) that a client needs for authentication. You can also add a new Keystore from this field.

Alias to the private key in the keystore file specified in the Keystore Alias field. The outbound connections use this key to send client credentials to a remote server. To send the client’s identity to a remote server, you must specify values in both the Keystore Alias and the Client Key Alias fields.

Select a hostname verifier implementation. Guards against man-in-the-middle (MITM) attacks. The default is org.apache.http.conn.ssl.DefaultHostnameVerifier, which will enable hostname verification. Select org.apache.http.conn.ssl.NoopHostnameVerifier to disable hostname verification.

Enable this option if you want to send or receive a large binary stream with a chunk size of 8192 bytes. This is applicable only if the back end supports HTTP/1.1 chunking.

Server Name Indication (SNI) is an extension to the TLS protocol by which a client indicates which host name it is attempting to connect to at the start of the handshaking process. Enable this option if the SaaS provider offers SNI-based TLS connectivity, and if you want to connect to an SNI enabled SAAS provider to send the host name specified in the Server URL field, as part of the TLS SNI Extension server_name parameter.

If you want to explicitly specify a host name to be included as a part of the SNI extension server_name parameter, in case the host name is other than the host name specified in the Server URL field, specify the host name value in the SNI Server Name field.

Select this option if you want to enable connection pooling for a connection.

Integration Cloud includes a connection management service that dynamically manages connections and connection pools based on configuration settings that you specify for the connection. A connection pool is a collection of connections with the same set of attributes. Connection pools improve performance by enabling Integrations to reuse open connections instead of opening new connections for every service request.

When you enable connection pooling, Integration Cloud creates the number of connection instances you specified in the connection's Minimum Pool Size field. Whenever an Integration needs a connection, Integration Cloud provides a connection from the pool. If no connections are available in the pool, and the Maximum Pool Size has not been reached, Integration Cloud creates one or more new connections (according to the number specified in the Pool Increment Size field) and adds them to the connection pool.

If the pool is full (as specified in the Maximum Pool Size field), the requesting service will wait for Integration Cloud to obtain a connection till one sec, until a connection becomes available. Periodically, Integration Cloud inspects the pool and removes inactive connections that have exceeded the expiration period of one sec.

The minimum number of connection objects that remain in the connection pool at all times, if connection pooling is enabled. When the connector creates the pool, it creates this number of connections.

The maximum number of connection objects that can exist in the connection pool if connection pooling is enabled. When the connection pool has reached its maximum number of connections, the connector will reuse any inactive connections in the pool, or, if all connections are active, it will wait for a connection to become available.

The number of connections by which the pool will be incremented, up to the maximum pool size, if connection pooling is enabled and connections are needed.