MDM Transport Operations

MDM provides two sets of operations for transporting repository schemas:

• Schema Migration. Includes Export and Import Schema commands.

• CTS+. Includes Export and Import Change File commands.

S

M

Schema migration refers to the pre-existing Export Schema and Import Schema commands in the MDM Console.

Commands

The Export Schema command creates an XML file of the current (originating) repository’s entire schema.

The Import Schema command compares the current (target)

repository’s schema against the schema contained in the selected XML file. From the Import Schema dialog, the user can see where the current and import schemas differ and choose which of these

differences to apply. Note that the Import Schema command does not replace the existing schema with the import schema. Rather, it allows the user to merge the import schema with the current repository schema.

Schema migration commands do not require that the originating and target repositories share the same underlying schema structure.

Files

The Export Schema command creates a name.xml file in a file location selected by the user. The Import Schema command opens a name.xml file from a location selected by the user.

CTS +

CTS+ refers to the new set of MDM Console commands created to work with the SAP Change and Transport System.

Commands

The Create Transport Reference command creates an XML file of a repository’s schema. This reference schema is identical to the XML file created by the Export Schema command. Users should create the reference file on the originating repository at a time when the originating and target repositories have identical schemas.

NOTE ►► The Create Transport Reference command should only be executed once. After the original reference file is created, MDM assumes responsibility for creating future reference files.

MDM Console Reference Guide 187 The Export Change File command compares the repository’s current schema against the schema contained in its latest reference file. From the Export Changes dialog (similar in appearance to the Import Schema dialog), the user can see where the current schema differs from the reference schema and choose which of these differences to export.

The resulting changes file does not contain an entire schema but instead contains only the changes selected from the Export Changes dialog. Changes that are not selected for the current export remain available for future exports.

During normal operation, the CTS+ system will pick up changes files and apply them through the Java API command:

com.sap.mdm.repository.commands.ApplyTransportDeltaCommand The Import Change File command opens whatever changes file is selected by the user and automatically applies all of the schema changes contained in the file to the current repository. Unlike the Import Schema command, the user has no choice of which changes to apply. In order to execute Import Change File commands, Console users need access to the relevant Transport/Outbound directory.

The Transport Management System command opens a link to the relevant SAP Transport Management System.

CTS+ commands require that originating and target repositories share the same schema structure.

Files

Transport files are stored in the Master Data Server's transport

directories. The mds.ini parameter Transport Dir sets the location of the root Transport directory. The Transport directory has two subfolders, Outbound and Inbound.

The Create Transport Reference command creates a

RepositoryName_XXX_reference.xml file (where XXX represents a sequentially incrementing number) in the Transport/Outbound directory.

The Export Changes command creates a new

RepositoryName_XXX_delta.xml file AND a new reference file in the Transport/Outbound directory. The XXX value on the new files is incremented by 1 from the XXX value on the last such files created for the repository.

Each change file should have a matching reference file (e.g.

RepositoryName_005_delta.xml file should have a corresponding RepositoryName_005_reference.xml file). However, the opposite need not be true: a reference file will not have a matching changes file until the “next” Export Changes command is executed.

188 MDM Console Reference Guide NOTE ►► The CTS+ system assumes that changes files with lower XXX values should be imported prior to those with larger XXX values.

NOTE ►► MDM will not delete or overwrite existing reference or change files because MDM does not know when change files are actually imported by the CTS+ system.

Errors

Error messages appear under the following circumstances:

 Export Changes command is issued but no corresponding reference file is found.

 Import Changes command is issued but the current repository ‘s schema is not compatible with the selected changes file

S

T

CTS+

Table 47 describes the basic behavioral differences between schema migration and CTS+ related commands.

Table 47. Differences between Schema Transport and CTS+

Behavior Schema Migration CTS+

Entire schema transported? Yes No

User can choose changes to export? No Yes

User can choose changes to import? Yes No

Requires target repository to be based on same schema as originating repository?

No Yes

File location Determined by user Transport/Outbound

291

PART 7: MDS ADMINISTRATION

This part of the reference guide contains information about MDM options for configuring the Master Data Server and its underlying DBMS.

MDM Console Reference Guide 191