8.3    Migrating Enterprise Services Repository Content

When migrating the ES Repository, a number of objects need to be moved. You can move the objects one by one, but we personally prefer moving all SCs or namespaces at once because it’s faster and helps avoid mistakes made by leaving out dependent objects while cherry-picking. After the SCs or namespaces have been successfully migrated to the target SAP PO system, you can remove objects that you don’t need or objects that aren’t supported by SAP PO. These are mostly ABAP-based objects, such as ccBPM. We’ll detail the steps of exporting the ES Repository objects from the source SAP PI system and importing them into the target system in the next sections.

8.3.1    Exporting Objects

To export the ES Repository objects, follow these steps:

1. From the SAP PI landing page of the source system, launch the ES Repository.
2. In the ES Repository, right-click on the SC or namespace that you want to export, and then click on the Export button.
3. Specify a location on your local file system in which to save the TPZ file. Don’t forget to properly name the TPZ file.

If you want to export multiple SCs, then repeat steps 1 to 3 for each SC.

8.3.2    Importing Objects

To import the data that you just exported from the previous steps, follow these steps:

1. From the target SAP PO landing page, launch the ES Repository.
2. Click on Tools in the menu, and select Import Configuration Objects.
3. From the pop-up menu that appears, select Client, and choose the TPZ file from your local file system.
4. Click on Import.
5. Repeat steps 1 to 3 multiple times to export more SCs or namespaces if necessary.

Note

You can import SCs without problems and without creating any inconsistencies because they already exist in the target SLD. Because the software component versions (SWCVs) and IDs match the ones in the SLD, it almost looks like you imported the SCs from the SLD. Be advised that you can also use the standard transport mechanism to migrate these objects instead of using the manual export and import features.

You should now have the ES Repository of your target system populated with all the required SCs. If you implemented ccBPM processes in your SAP PI system, then now is the time to remove them. This step in needed because the ccBPM component is no longer supported in SAP PO. You’ll need to reimplement your ccBPM processes in SAP BPM. See Chapter 16 for more details and considerations for migrating your ccBPM processes to equivalent SAP BPM processes.