Many of our installations start with a test environment.  When testing and configuration is complete we have to move everything over to the live environment.  I have developed a process and check list to help with the process.   So I provide this as a starting point for anyone.   Your specific steps will vary.

This section assumes that you set up the integration using a test Solomon system and a production CRM system. Effectively redeploying a working Infuse to a new server.

1. Create a maintenance collaboration folder and copy your DTS files to it to serve as a backup.
2. Delete the test data in the CRM system or restore the backup of the CRM system.
3. Set up Solomon Publisher on production Solomon system.

i. Run the Solomon Infuse Solomon Table Creation sql script.

ii. Run the Solomon Infuse Trigger and view sql scripts.

iii. Run the Solomon Infuse Init sql script.

    4.   Connect DTSs to production systems.

i. This is going to require changing the ODBC connector on the dts to point to the Production Solomon database.

    5.  Complete the initial sync process. Use InitialSync.sql to set syncstatus1 in the shadow table to “M”.
         This will move all of the products, accounts, orders, and invoices from Solomon to CRM.

        a. At this point your DTS files should be unit tested and your Integration Processes should be active.

        b. You should run the script one object at time, then resolve any errors you find before running the script
             on the next object.

6.    Do a system test with the production systems.

7.    Re run the InfuseViews.sql script to point to the production Solomon database. This view sits in Infuse database but points across the network to Solomon.

8.    Valitdate the Data views. Each of them point to specific database locations. Each one will have to be open and changed to point to Solomon.

9.    Complete the data review process.

Refers to

Step 5

When you do the initial sync, you can do it as a manual process to open each DTS file and run them individually, resolving errors before running the next DTS file. Alternatively, you could let the Integration Processes run the DTS files for you. Whichever method you choose, you should run the InitialSync.sql one object at a time, run the associated DTS file, and resolve errors before moving on to the next object.

By default, the integration will move all of the products, customers, orders and invoices from the Solomon system. Considerations for limiting the data include:

• Date filter for orders and/or invoices. For example, only move new orders/invoices from the past 12 months instead of all order/invoice history.
• Subset of the product catalog and/or product price lists.
• Subset of accounts. For example, if customers and vendors are in the same table in the Solomon database, only move customers. Be careful if you decide to move a subset of accounts. You need to make sure that you do not later try to move orders/invoices for accounts that you filtered.

 Here are are the specific steps in a table format.  I use this as my starting point.  I will fill in the specific DTS's and who on the team is going to do each step.  Hope this is helpful for you.

Pierre is currently rockin' to " You Need Love" By: Styx - on the  Come Sail Away: The Styx Anthology Disc 1 album.