Importing and Exporting Integration Objects 

Use

Importing and exporting integration objects enables you to do the following:

·        Copy objects from one Integration Repository to another Integration Repository. The software component version must be the same in the source and target repository in this case.

·        Copy objects from one Integration Directory to another Integration Directory. In this way, you can copy a test configuration to a productive landscape.

Use the release transfer function to transfer objects within an Integration Repository from one software component version to another.

Prerequisites

During the export, a binary file is created in a directory defined on the repository server (or directory server). To import this file to another repository (or directory), you must manually copy it to an import directory (see below). You require the appropriate authorizations to be able to access directories on the SAP Web Application Server.

Import and Export Directories

Type	Integration Repository	Integration Directory
Export	<systemdir> /xi/repository_server/export	<systemdir> /xi/directory_server/export
Import	<systemdir> /xi/repository_server/import	<systemdir> /xi/directory_server/import

<systemdir> is the system directory from the server installation.

Features

Integration Repository

You can either export all objects of a namespace, or all objects of a software component version. The export file also contains information about higher-level software components when exporting objects of a namespace, because the version of the software component of the object to be imported must be checked when you import.

If you have only exported the objects of a namespace, the namespaces of the same software component version are nevertheless visible in the target repository following the import. However, these namespaces are empty because they could not be exported. SAP recommends that you only export complete software component versions so as to avoid confusion.

During the import, version management checks whether the objects to be imported already exist in the target repository, and if so, what their version status is (see: Versioning in Transports).

Integration Directory

Directory objects are assigned to business scenarios:  A receiver determination references interface determinations, end points and logon data. You can export just the receiver determination or the referenced interface determination as well. End points and logon data are specific to the technical system and must therefore be entered manually after the export.

Unlike importing in the Integration Repository, version management always creates a new version for the object to be imported in the target directory. Object versions of the source and target repository are therefore independent of each other. This means that you can also import configuration objects that have a version that is older than the version currently in the directory.

Activities

Importing and Exporting Repository Objects

...

        1.      To import or export repository objects, call the design maintenance screen of the Integration Builder.

        2.      Call the context menu for a namespace or a software component version in the navigation tree and choose Export….

        3.      Confirm that you want to export in the dialog that is then displayed.

The Integration Builder saves an export file with the suffix tpt in the export directory of the repository server (see above). When exporting IDocs or RFC schema from the repository, there is also a file with the suffix _classic.tpt in the export directory.

Do not change the file name of the export file. If you do, the Integration Builder will not accept it as the appropriate file when you import. Furthermore, note that this file is a binary file.

        4.      To import the export file(s) to another Integration Repository, first copy or move it to the import directory of the target repository.

        5.      Call the design maintenance screen of the Integration Builder for the target repository. Choose Object ® Import XI 2.0 Development Objects...

        6.      Select the export file(s) saved in the import directory by using the dialog that is then displayed.

If the import is successful, the export files are moved to the sub-directory <serverdir> /xi/repository_server/importedFiles.

Importing and Exporting Directory Objects

Prerequisites

Test and productive directories both access the same System Landscape Directory. To import configuration objects into the productive directory from the test directory, you must define transport targets in the System Landscape Directory. In the process, business systems of the test directory are assigned to business systems of the productive directory.

See also: Configuring Groups and Transport Targets.

Objects in the Integration Directory reference objects in the Integration Repository. Therefore, you must import repository objects into the productive repository before you can import them into the productive directory.

Procedure

...

        1.      To import or export directory objects, call the configuration maintenance screen of the Integration Builder.

        2.      Call the context menu for the business scenario in the navigation tree and choose Export With/Without Interface Determinations.

The Integration Builder saves an export file with the suffix tpt in the export directory of the directory server (see above).

Do not change the file name of the export file. If you do, the Integration Builder will not accept it as the appropriate file when you import. Furthermore, note that this file is a binary file.

        3.      To import the export file(s) to another Integration Directory, first copy or move it to the import directory of the target directory.

        4.      Call the configuration maintenance screen of the Integration Builder for the target directory. Choose Object ® Import XI 2.0 Configuration Objects...

        5.      Select the export file saved in the import directory by using the dialog that is then displayed.

If the import is successful, the export file is moved to the sub-directory <serverdir> /xi/directory_server/importedFiles. The objects are not activated when they are imported into the target directory. They are visible in the change list of the user who imported them.

        6.      Check the imported objects in the change list and adjust the configuration data to match your system landscape, if necessary.

        7.      Activate the change list that contains the imported objects.