Configure an integration connection
To successfully configure the connection, a user will need to be set up in Optimizely Configured Commerce with the ISC_Integration role
- Go to the folder where the Integration Service is installed
- Open SiteConnections.xml in a text editor (such as Notepad) Inside the configuration file, you will find a block of code to configure the connection, which looks similar to this:
- Enter the name of the connection between the <IntegrationConnectionName> tags
- Enter the website domain for the Configured Commerce website between the <URL> tags
- Enter the username for the user that has the ISC_Integration role between the <Username> tags
- Enter the password for the user that has the ISC_Integration role between the <Password> tags
- If you are using a proxy with your integration, enter the appropriate proxy information between the <ProxyURL>, <ProxyUsername>, and <ProxyPassword> fields
- If you are using a different set of DLLs for the integration connection, specify the DLL directory between the <DllFolder> tags. A string must be in between these tags in order for the integration to work. If you are not using a different set of DLLs, leave the default string between the tags.
- Once you have finished configuring the connection string, save your document
Connection types
SAPDotNetConnector | |
|---|---|
Name | This field is used to define the name of the connection. This name must be unique. |
Type | This drop-down is used to define the type of connection for the integration. Changing this drop-down will change the fields available on this screen |
Debugging Enabled | This checkbox is used to enable additional debug logging for the integration connection |
System Number | The SAP system number against which a BAPI call will be made. This value is provided by the client. |
Client | he SAP client number against which a BAPI call will be made. Some clients may have separate SAP clients for development, QA and production. This value is provided by the client. |
App Server Host | The location of the application server where Optimizely can connect to make SAP BAPI calls. This is typically an address on the local network (such as appserver.clientURL.com), and is provided by the client. |
Login | This field is used to define the login name that the integration service will use to connect to the database |
Password | This field is used to define the password that the integration service will use to connect to the database |
Language | SAP Language that is passed into the SAP BAPI call. Typically, this value will be ‘EN' (for English), unless a client has a different language set up in their SAP environment. |
Peak Connections Limit | The maximum number of concurrent connections that can be made to the given integration point. |
Idle Timeout | The amount of time that passes until the integration connection will time out. If a request is sent into the connector and a response is not received in the given time, an error is thrown by the integration connection. |
FlatFile | |
|---|---|
Name | This field is used to define the name of the connection. This name must be unique. |
Type | This drop-down is used to define the type of connection for the integration. Changing this drop-down will change the fields available on this screen |
Debugging Enabled | This checkbox is used to enable additional debug logging for the integration connection |
Delimiter | This field is used to define the type of delimiter that is used in the flat file. A tab delimited file would be indicated by . |
Import Folder | This field is used to define the location of the XML file used for the integration on the server |
XMLFile | |
|---|---|
Name | This field is used to define the name of the connection. This name must be unique. |
Type | This drop-down is used to define the type of connection for the integration. Changing this drop-down will change the fields available on this screen |
Debugging Enabled | This checkbox is used to enable additional debug logging for the integration connection |
Filename | This field is used to define the location of the XML file used for the integration on the server |
ODBC | |
|---|---|
Name | This field is used to define the name of the connection. This name must be unique. |
Type | This drop-down is used to define the type of connection for the integration. Changing this drop-down will change the fields available on this screen |
Debugging Enabled | This checkbox is used to enable additional debug logging for the integration connection |
Connection String | This field is used to define the connection string that will be used to by the integration service |
Login | This field is used to define the login name that the integration service will use to connect to the database |
Password | This field is used to define the password that the integration service will use to connect to the database |
Generated String | This non editable field is generated from the data entered in the fields above, and shows the generated connection string that the integration service will use to contact the SQL Server |
OleDB | |
|---|---|
Name | This field is used to define the name of the connection. This name must be unique. |
Type | This drop-down is used to define the type of connection for the integration. Changing this drop-down will change the fields available on this screen |
Debugging Enabled | This checkbox is used to enable additional debug logging for the integration connection |
Connection String | This field is used to define the connection string that will be used to by the integration service |
Login | This field is used to define the login name that the integration service will use to connect to the database |
Password | This field is used to define the password that the integration service will use to connect to the database |
Generated String | This non editable field is generated from the data entered in the fields above, and shows the generated connection string that the integration service will use to contact the SQL Server |
WebService | |
|---|---|
Name | This field is used to define the name of the connection. This name must be unique. |
Type | This drop-down is used to define the type of connection for the integration. Changing this drop-down will change the fields available on this screen |
Debugging Enabled | This checkbox is used to enable additional debug logging for the integration connection |
URL | This field is used to define the URL for the Webservice used for integration |
Login | This field is used to define the login name that the integration service will use to connect to the database |
Password | This field is used to define the password that the integration service will use to connect to the database |
SQLServer | |
|---|---|
Name | This field is used to define the name of the connection. This name must be unique. |
Type | This drop-down is used to define the type of connection for the integration. Changing this drop-down will change the fields available on this screen |
Debugging Enabled | This checkbox is used to enable additional debug logging for the integration connection |
Database | This field is used to define the name of the database that the integration service will connect to |
SQLServer Name | This field is used to define the server address (typically and IP address) that the integration service will connect to |
Login | This field is used to define the login name that the integration service will use to connect to the database |
Password | This field is used to define the password that the integration service will use to connect to the database |
Generated String | This non editable field is generated from the data entered in the fields above, and shows the generated connection string that the integration service will use to contact the SQL Server |