Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

SAP Integration

Rekha Jalle
Tera Contributor

3 hours ago

Hi All,

I implemented an integration with SAP where we have three connectors across the Dev, UAT, and Prod environments. The web services provided by the client are different in each environment. These web services are used in catalog forms and flows. We have three catalog items, and we are calling the web services in a custom action script step.
Since the web services differ across environments, but the overall logic remains the same, everything currently works correctly in Dev, UAT, and Prod. However, the client wants to clone Prod, and if they do that, the Dev and UAT integrations will stop working due to the overwritten web service URLs.

0 Helpfuls
  • 11 Views
1 REPLY 1

tiagomacul
Giga Sage

18 seconds ago

Hi!

This is a very common and critical challenge in Application Lifecycle Management (ALM) when dealing with integrations (especially with SAP or other external systems).

 

You are correct: cloning Production down to Dev and UAT will overwrite the non-production integration configurations (like the endpoint URLs in the Outbound REST Messages or SOAP Messages), causing them to point back to the Production SAP environment.

 

The solution is to use CMDB Data Preservers and System Properties to secure the environment-specific values during the clone process.

0 Helpfuls