Integration connectors and jobs
Integration permissions
The integration infrastructure controls critical connections to various systems and data. As a result, it is important to carefully limit which roles can access to the job definitions and which ones can delete, create, edit, cancel, or run integration jobs.
Create an integration connection
You can create integration connections in the Admin Console to connect to external data sources, such as your Windows Integration Service (WIS) or an ODBC connection to your ERP. Go to Administration > Jobs > Connections in the Admin Console.
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.
Configure an integration job to add and map products and categories
This article provides details on configuring an integration job to read the datasets from an SQL Server database, then create Products, create Categories, and map or assign the Products to the Categories. Here are the steps involved Create a new SQL Server database.
Create and edit integration jobs
Optimizely Configured Commerce lets you enable integrations with external systems. You can create job definitions to define all appropriate attributes used for the integration.
Manually configured integration jobs
The following integration jobs do not execute automatically. They need to be scheduled manually.
Run an integration job manually
Many Integration Jobs are set up to run automatically during specific times, intervals or points within a workflow. However, there are other jobs that may need to be run infrequently or in an on-demand type scenario.
Create a nightly maintenance job
Optimizely Configured Commerce contains a nightly maintenance job that cleans up abandoned shopping cart records, maintains the application log, deletes orphaned custom properties, removes obsolete scheduled task records, and analyzes query plans to identify fast queries because a table is small. You should schedule the job to run each night during non-peak hours within your SQL server or by creating a Nightly Maintenance Scheduled Task within the Admin Console.
Create an integration job to run a report
This article outlines the specific steps to required to create an integration for users who need to generate or FTP a report. In the Admin Console , go to Administration > Jobs > Job Definitions Within the Details finger tab, select Add Job Definition .
Configure a custom order submit integration job
You can create an order submit integration job to submit orders from Optimizely Configured Commerce to an ERP. The ERP then handles order fulfillment.
Configure a product refresh integration job
You can create a product refresh integration job in Optimizely Configured Commerce. Pulling product data into Configured Commerce is required to support base functionality and can increase performance.
Create a Product Attributes Refresh integration job
You can create a Product Attributes Refresh integration job with Optimizely Configured Commerce. Because many refresh jobs query an ERP database directly, you should know where to find the required data in the ERP database.
Create an integration job to export data
You can configure an SFTP integration connection and create a recurring integration job to automate data exports from Optimizely Configured Commerce and deliver files to an SFTP site. Perform the steps in this section only if you want to deliver files to an SFTP site.
Configure SFPT client through proxy
If there is a need to run the SFTP through a proxy, then add the following keys and appropriate values to the appSettings.
Remove deleted child records via integration
After deleting a single order line in the ERP, you can add a job definition step to delete the child entries upon refresh of the parent record. Refreshing the order history is the primary scenario where this would be used.
Troubleshoot integration job failures
Integration is a series of jobs that run both real-time and batch. It is important to monitor that the jobs are all running properly and to take corrective action if they are not.
Troubleshoot delta datasets
This article describes a unique situation where, if certain steps are taken, records in the dataset may not accurately update. Basically, when delta datasets is enabled, the system takes a snapshot and saves it in the DllsFolder (as defined in the site connections file) under a folder called DeltaDataSets .