Multiple environments support

There can be scenarios that multiple SAP or Pricefx environments exist in one SAP Integration Suite environment. To use the same set of integration flows for multiple environment, you should ensure table structures, metadata and any custom API are identical in each of the environment. The only difference should be just the connection properties such as Host name, credentials, token names. The integration flows get the PFX environment and SAP environment from the header of the calling processes, and retrieve the connection properties from value mappings.

See Reusable Artifacts for SAP S/4HANA Integration with Pricefx | Get Pricefx connection properties by environment and

Other Utilities | Get AIR key from Pricefx and SAP Connection Properties

The sample value mappings are in “Sample Artifacts for SAP S/4HANA Integration with Pricefx” package. You should update the values accordingly.

Dynamic properties are used to access OData and Pricefx.

Some integration flows must be duplicated for each environment, such as:

1. Event Mesh Listener processes

2. RabbitMQ Listener processes

3. In each integration package, locate the first integration flow triggered by the listener if any. In the sample integration flows, very often they are the JMS consumer or the aggregator. If you will see pfx-env or/and sap-env in the configuration, that means this integration flow is required for each environment.