Some SAP CPI customers do not have a full 3 tier system landscape for their SAP CPI. But you may want to experience having all the systems connected and be able to test the flow. You can do it manually, with using the copy functionality, but it requires a lot of governance to keep the QA updated.
We originally created the virtual landscape just to test how our transport system worked, because we only had one CPI system. Now we have improved the functionality because it enables customers to take advantage of our transport and leverage using one CPI system. We did earlier change Sender system to match with having a prefix with the system name.
We have now improved the functionality so the system is added to the Process Direct adapter. Here we are adding the prefix in the URL to both sender and receiver channels. You will thereby have the option to run it in a “QA environment”.
You can see a demonstration of how this works in the video.
Watch on YouTube Transport to Virtual SAP CPI landscapes
Update: if you import a package, it will be auto deployed.
The transport system also provides options to create iFlow documentation, and you can test the impact of a change. You can also make a modification of Externalize Parameters across the landscape, so you can specify that the target URL on QA is this. Then the Figaf DevOps Suite will handle the configuration once it deploys.
The tool also works for value mappings, but it is not possible to deploy the value mappings, because they already exist on the same system.
You can start a free trial of the Figaf DevOps Suite, on premise or in our cloud.
