What's best practice around cloning and SOAP/REST Message records?

[peterraeves]

When creating an integration, you often have (at least) 2 environments on both sides. You have a test environment and production environment on both sides. In this case you would like to have your test environment linked to their test environment and your production environment to their production environment. So far so good, but you have to make sure that even after a clone, your test environment is still linked to their test environment.

Therefore, what would be best practice in setting up your SOAP or REST Message? What about authentication records? Is there a difference between setting up SOAP vs REST when it comes to cloning and multiple environments?

[Chuck Tomasi]

I would say 1) make sure your authentication table(s) is/are in the Exclude list.

[peterraeves]

Thanks Chuck. What about different WSDLs for SOAP and different endpoints for REST?

[sdivone]

I needed to do this with a remote system that had only one environment. So where I have DEV, TEST and PROD, they had only PROD.

What I ended up doing was creating multiple transaction contexts for the transaction on the destination side and then changed the context of my transaction on the SN side by using the instance name property.

Just another approach in case you do not have matching environments on either side.

I hope it helps.

[Chuck Tomasi]

Those are additional tables (when they are in the related lists of the records.) Just open a record and you can find out the table name. Add that to your exclusion list as well.