Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
Before you start the transfer of your artifacts, you need to understand what kind of artifacts need to be or can be transferred at all. Let’s start: Open Connectors has three kinds of artifact, namely connectors, common resources, and formulas. On top of that, there are the connector instances, common resource mappings, and formula instances which are the runtime artifacts containing authentication information. Important for you: Open Connectors does not support runtime data transfer. You can recreate runtime artifacts in the target system, after the artifacts have been transferred successfully.
Let’s continue: Open Connectors, capability of SAP Integration Suite, offers two types of connectors: system connectors and custom connectors. You do not have to transfer the system connectors to the target system, since the target system usually also has the same connectors.
That means for you, that you have to transfer the three artifacts from the source system: custom connectors, common resources, and formulas.
Transfer Custom Connectors
Let’s have a look at how you can export and import custom connectors.
Export Custom Connectors from the Source System
In Open Connectors, to ex custom connectors from the source system, you need to navigate to the Private tab of Connectors page. This page will show an overview of your custom connectors.
Select on custom connector and click on Overview. to get to the detail page of your connector.
On the details page, click on Export. The download of the metadata (json file) starts.
Import Custom Connectors to the Target System
In Open Connectors, login to your target system. Select Connectors from the navigation card and click on Build New Connector.
Select Import.
Select Connector as import option. Then, upload the metadata file you downloaded from another system. To finish, select CONTINUE IMPORT.
Select the resources you want to import and click on Import. In this example, we select all resources.
Save your changes
With this, you have transferred your connector successfully to the target tenant. As a next step, you can create a connector instance to validate. See: Authenticate a Connector Instance.
Transfer Common Resources
Similarly, let’s look at how to transfer common resources.
Export Common Resources from the Source System
In Open Connectors, go to Common Resources and check which common resources you want to export.
Click API Docs. It’ll forward you to the platform API document page.
Select Common Resources and perform “GET /vdrs” api to retrieve all the common resources you have. Click on Execute.
Select Download. This way, you will get all the common resources metadata (json file).
Import Common Resources to the Target System
In Open Connectors, login to the target system and select API Docs. It will take you to the platform API document page.
Go to Common Resources and perform the “POST /vdrs” api to create common resources in the target system. You can copy the body of this request from the metadata file you downloaded from the source system. Note: The metadata file you downloaded is the common resource collection, you need to create the common resource one by one in the target system.
Go to the Common Resources page and refresh the browser, you will see the common resources you imported successfully.
Now that we’ve looked at custom connectors and common resources, let’s
Export Formulas from the Source System
In Open Connectors, go to Formula and select of the formula you want to export.
Your browser will download the metadata (json file) of your formula.
Import Formulas from the Target System
In Open Connectors, login to the target system and select Import from the Formulas page.
Select the metadata file you’ve downloaded from the source system.
Provide a name for your formula and click Create. You are being sent to the formular detail page.
Back on the formulas page, you will see that the formula has been imported successfully. Next, create a formula instance to validate. See: Formula Instance.