Using the Oracle CRM On Demand Connection Manager
The Oracle CRM On Demand Connection Manager is an SSIS connection manager component that can be used to establish connections with Oracle CRM On Demand.
To add a new connection, right-click the Connection Manager area in your Visual Studio project, and choose "New Connection..." from the context menu.
You will be prompted the "Add SSIS Connection Manager" window. Select the "OracleCRMOnDemand" item to add a new Oracle CRM On Demand Connection Manager.
The Oracle CRM On Demand Connection Manager contains the following configuration pages:
- General
- More Info
General Page
The General page allows you to specify connection properties and login credentials to Oracle CRM On Demand.
- Server Information
-
- Web Service URL
-
The Web Service URL field lets you specify the URL to the Oracle CRM On Demand Web Service. It should follow the pattern: https://secure-ausomx[POD].crmondemand.com/Services/Integration, where POD is the 3-letter Pod Identifier for your Oracle CRM On Demand instance. This address may vary and can be obtained in the Service section of any WSDL file that you obtain from CRM On Demand -> Admin -> Web Services Administration.
- Authentication
-
- Authentication Mode
-
Oracle CRM On Demand supports different authentication modes. However, our connection manager currently only supports Login Credentials in SOAP Security Header.
- User Name
-
The User Name allows you to specify the user account used to authenticate with Oracle CRM On Demand.
- Password
-
The Password field allows you to specify the password for the above user account.
Note: By default, the Password is not shown in the Oracle CRM On Demand connection manager's ConnectionString property. This is done by design for security reasons. However, you can include it in your ConnectionString if you want to parameterize your connection manager. The format would be Password=myPassword; (make sure you have a semicolon as the last character). It can be placed anywhere in the ConnectionString property.
- Service Timeout
-
- Timeout
-
The Timeout value lets you indicate the length of time (in seconds) to expect a response from a web service call before failing.
- Test Connection
-
After all the connection information has been provided, you may click the "Test Connection" button to test if the user credentials entered can authenticate with Oracle CRM On Demand.
Advanced Settings Page
The Advanced Settings page allows you to configure your connection to Oracle CRM On Demand to use a proxy server.
- Proxy Server Settings
-
- Proxy Mode (since v4.0)
-
The Proxy Mode option allows you to specify how you want to configure the proxy server setting. There are three options available.
- No Proxy
- Auto-detect (Using system-configured proxy)
- Manual
- Proxy Server
-
Using the Proxy Server option, you can provide a proxy server to connect to Salesforce.com.
- Port
-
The Port option allows you to specify the port number of the proxy server for the connection.
- Username (Proxy Server Authentication)
-
The Username option (under Proxy Server Authentication) allows you to specify the proxy user account.
- Password (Proxy Server Authentication)
-
The Password option (under Proxy Server Authentication) allows you to specify the proxy user's password.
Note: The Proxy Password is not included in the connection manager's ConnectionString property by default. This is by design for security reasons. However, you can include it in your ConnectionString if you want to parameterize your connection manager. The format would be ProxyPassword=myProxyPassword; (make sure you have a semicolon as the last character). It can be anywhere in the ConnectionString.
- Miscellaneous Settings
-
- Retry on Intermittent Errors
-
This is an option designed to help recover from possible intermittent outages or disruption of service. It prevents the integration process from stopping due to temporary issues. Enabling this option will allow service calls to be retried upon certain types of failure. A service call may be retried up to 3 times before an exception is fired. Retries occur after 0 seconds, 15 seconds, and 60 seconds.
Warning: We have designed our retry feature carefully such that the retry should only occur when it is deemed safe to do so; however, in some occasions, such retry service calls could result in the creation of duplicate data.
More Info Page
The More Info page shows some basic information about the toolkit. On this page, you can find the version information of the toolkit.
