Create a new SQL Server database.
Run the script in the file attached at the end of this article called **Create-dbo.Orders-Table.sql** against your SQL Server database.
Go to **Admin Console** \> **Administration** \> **Jobs** \> **Connections**.
Click the **Add Integration Connection** button.
Choose **SqlServer** from the **Type Name** menu.
Populate the **Url**, **Log On** and **Password** fields to configure it to connect to the new SQL Server database created in Step 1.
Go to **Admin Console** \> **Administration** \> **Jobs** \> **Job Definitions**.
Click **Import** to import the integration job from the **Order-Submit-JobDefinition.json** file attached at the end of this article.
The new job must be called "**Order Submit**". If you rename this job it will NOT run automatically after an order has been submitted on the site.
In Visual Studio, create a new class library called **"Custom Integration"**.
Add these references to the class library:
Add a new class called **"IntegrationProcessorFakeERPSubmit"** using the code found in the file attached at the end of this article called **IntegrationProcessorFakeERPSubmit.cs**.
Update the values in this file for the database connection info on this line:
Build the project. After the build completes, go to the **CustomIntegration** folder within your project and copy the **CustomIntegration.dll** file.
Go to the install path of the WIS and paste the **CustomIntegration.dll** file into your **dll** folder.
Make sure to stop the WIS service first before copying in the dll file. Once the file is in your dll folder then start the WIS service again.
Verify the **WIS logfile.txt** contains the following: "**Found Custom Integration Processor FakeErpSubmit, registering in Unity**".
Return to the Admin Console to complete the configuration of the integration job definition.
Go back to the **Order Submit** job created earlier in this article. In the **IntegrationProcessor** field select the newly created processor "**FakeErpSubmit**".
Submit an order on the site and verify that the order record was created in your SQL Server database.
Use this link to download the files referenced in this article: <https://insitesoftwaresolutions.box.com/v/CustomOrderSubmitIntJob>