SAP NetWeaver 7.0: Importing Process Integration Content

Symptom
SAP NetWeaver uses the usage type ‘Process Integration’ (this usage type includes all previous functions of the SAP NetWeaver Exchange Infrastructure and the Business Process Management functions) to support cross-system applications. In addition to their product, cross-system applications that are based on SAP NetWeaver deliver interface descriptions, mappings and other objects that are relevant for the exchange of messages. Customers must import these contents, the ‘Process Integration Content’ (XI Content) into the Integration Repository of SAP NetWeaver. The import is the prerequisite for configuring the cross-system application in the Integration Directory.
For SAP NetWeaver 7.0 (previously called SAP NetWeaver 2004s), you can import XI Content from SAP NetWeaver 7.0, XI 3.0 and also from XI 2.0 into the Integration Repository (all databases that are released for XI 3.0 or SAP NetWeaver 7.0 are also supported when you import XI 2.0 Content). The Integration Builder migrates the objects from XI 2.0 to SAP NetWeaver 7.0. The XI Content from XI 3.0 and the XI Content from SAP NetWeaver 7.0 are always compatible and can be imported into the Integration Repository without migration. The procedure described in this note applies to the migration and to the import of XI Content based on SAP NetWeaver 7.0.

Other terms
XI Content, Integration Repository, delivery, Integration Builder, Process Integration Content

Reason and Prerequisites
SAP NetWeaver 7.0 must already be installed in your system with the relevant Support Packages and the usage type “Process Integration”. A general description of the installation process is available in the Installation Guide on SAP Service Marketplace at http://service.sap.com/instguidesNW70. Also see the notes of the Master Guide for your cross-system application. The export and import of XI Content is not a task for individual developers, but rather for administrators or for those who are responsible for the organization of XI Content. Therefore, the functions for exporting and importing must be called only for users with the role SAP_XI_ADMINISTRATOR or SAP_XI_CONTENT_ORGANIZER.

Solution
The XI Content for an SAP application is available on SAP Service Marketplace at service.sap.com/swdc -> Download -> Support Packages and Patches -> Entry by Application Group -> SAP Content -> ESR Content (XI Content) -> -> (for the name of the software component and the version, refer to the Master Guide of the application). To import the XI Content into the Integration Repository, copy the export files that are provided in the Integration Repository into an import directory of the host for the Integration Builder and use a menu in the Integration Builder to import them. In the following, indicates the path for the system directory of the host (generally, = “usrsapSYSglobal”).

1. Obtain the export files for the XI Content of the cross-system application. The files are generally stored as zip files on SAP Service Marketplace (see above). You can use the naming convention of these zip files to determine their Support Package level (SP level): _. For example, the files SCM4003_00.ZIP and SCMBASIS4003_00.ZIP refer to Support Package level 03 with patch level 0 of the XI Content.

Remark: When you import XI Content with an older version, this does not overwrite the content that you already imported into the Integration Repository. Support Packages for XI Content always contain both the previous objects and the changes and enhancements that are delivered in the relevant Support Package.

2. Copy the export files into the import directory for the Integration Repository (“xirepository_serverimport”). If the files are packed, you must unpack them before the import. (We advise you to retain the zip files. For more information, also see the remarks for the last step.)

Remark: The actual export files have the extension .tpz. You must not unpack these files. The import directory is created when you first call the Integration Builder.

3. Start the Integration Builder for the design time. To do this, log on to the SAP system in which the Integration Builder has been installed. To call the initial screen of the Integration Builder, use your user menu or call transaction SXMB_IFR. Then choose “Integration Repository”.
4. After you start the Integration Builder, follow the menu path “Tools -> Import design objects…” to import the XI Content. When you do this, only the files from the import directory (see above) are available for the import. The sequence in which you import the export files is not important.

Remark: If version conflicts occur during the import, you can process and resolve them in the Integration Builder. If there are corrupt export objects, you can force the import and skip objects that cannot be imported. As a result, the import is incomplete and references to objects that have not been imported are lost.

5. After a successful import, the Integration Builder moves the imported tpz files into the directory “/xi/repository_server/importedFiles”. The Support Package level of imported software component versions is available in the Integration Builder on the “Details” tab for the relevant software component version. This information is important for support if an error occurs. Take one of the following two precautions to retain the overview of the imported XI Content:
If the release and the Support Package level are clear from the file name of the tpz file, simply leave the files in the directory “importedFiles” (see above). Note that the Integration Builder adds the date and time of the import to the file name of the imported export files if a file with the same file name already exists in the directory “importedFiles”. This enables you to check which file was last imported.
After a successful import, you can keep the packed files, from whose naming convention you can derive the Support Package level. Move them into the directory “importedFiles”, for example.
More information is available in the SAP Help Portal at http://help.sap.com, in the online documentation for SAP NetWeaver, in the section “SAP NetWeaver Exchange Infrastructure -> Design and Configuration Time -> Software Logistics for XI Objects”.