Transporting Configuration DataLocate this document in the navigation structure

Use

You can use the Export and Import functions to move individual configuration objects or larger parts of the configuration, including all referenced configuration data, between portals. For example, this allows you to transfer the configuration from a test system to a production system.

You can perform the transport manually using the commands integrated in the Configuration iView. If you have implemented the Change and Transport System (CTS), you can also have it perform the export and import of configuration data.

You can generate a transport package in the following formats:

  • Config Archive: Format with the file extension .configarchive

    The configuration data in XML format is available in this file compressed as a ZIP file.

  • SDA Archive : Format with the file extension .sda

    The Software Deployment Archive (SDA) is the delivery format for SAP applications in programming languages other than ABAP. The SDA contains the manifest information that is package-related data of the contained archive (for example, jar, war) and an SAP manifest containing additional information about the software logistics.

Note the following special features after starting the export function:

  • The extended view of configuration objects is switched on.

  • Configuration objects that are otherwise hidden and used internally become visible.

  • You can browse the configuration hierarchy and display entries. You cannot edit configuration objects in this mode. You can only edit objects if you interrupt the export.

  • More functions, which you can normally launch by choosing Actions in the menu bar, are deactivated.

Prerequisites

If you want to use the CTS, you must set up the enhanced CTS beforehand. For more information, see the section about transporting non-ABAP objects in the documentation about the enhanced CTS.

Procedure

The transport of configuration data comprises the creation of the transport package, the export of the transport package, and the import of the transport package. You may need to restart the Application Server Java (AS Java) to activate the configuration changes.

1. Create the Transport Package

To create a transport package, proceed as follows:

  1. Start the export function.

    1. In the portal, choose Start of the navigation path System Administration Next navigation step System Configuration  Next navigation step  Knowledge Management Next navigation step Content Management End of the navigation path.

    2. In the menu bar, choose Start of the navigation path Actions Next navigation step Export  Next navigation step  Start End of the navigation path.

  2. Put together the transport package.

    1. In the configuration, navigate to the object that you want to export.

    2. Select the required instances and choose Export .

      From the options, you can choose whether referenced configuration objects are to be exported as well. If you have activated this option, you can use another option to specify whether invalid references are also to be exported.

      Alternatively, you can use the menu bar to put the export package together. Choose Start of the navigation path Actions Next navigation step Export Next navigation step Add End of the navigation path. This allows you to choose not only individual instances, but also subareas of the configuration, such as all repository managers.

      In the menu, the following options are available:

      • Topic : Adds all instances of a configuration object to the transport package.

      • Topic Area : Adds all configuration objects in the current area and their instances to the transport package.

      • Topic Area and Related Areas : Adds all configuration objects in the current area and their instances to the transport package. In addition, the system includes the configuration objects and their instances that are listed in Related Areas.

      • Complete Configuration : Adds the entire configuration to the transport package.

        Note

        You can leave the creation of the transport package at any time and return to it later.

        To interrupt an export and switch to the normal mode to edit the package, choose Start of the navigation path Actions Next navigation step Export Next navigation step Suspend End of the navigation path.

        To resume an interrupted export, choose Start of the navigation path Actions Next navigation step Export Next navigation step Resume End of the navigation path.

  3. Check what you have put together.

    In the menu bar, choose Start of the navigation path Actions Next navigation step Export  Next navigation step  Edit... End of the navigation path. You can check here which entries the transport package currently contains. You can remove configuration objects by deselecting the checkbox in front of the object and choosing OK .

2. Generate the Transport Package and Complete the Export

You can perform the transport manually or use CTS.

  • To export the configuration package manually, proceed as follows.

    1. In the menu bar, choose Start of the navigation path Actions Next navigation step Export  Next navigation step  Create Transport Package... End of the navigation path.

      The selected configuration objects are listed and, if necessary, the configuration objects that they reference.

    2. Specify a name for the configuration archive to be exported and choose whether the system is to generate the transport package in the Config Archive format or the SDA Archive format.

    3. Choose OK .

    4. Choose Download and make sure that the file with the ending for the chosen format ( .configarchive or .sda ) is saved.

  • To export the configuration package using CTS, proceed as follows.

    1. In the menu bar, choose Start of the navigation path Actions Next navigation step  Export  Next navigation step Create Transport Package for CTS... End of the navigation path.

    2. Specify a name for the transport package. Optionally, you can enter a comment for this transport.

      The selected configuration objects are listed and, if necessary, the configuration objects that they reference.

    3. Choose Start Export to CTS .

      On the next screen, you can find information about the transport to CTS.

    4. Choose Close to exit the transport mode.

  • Optionally, you can cancel an export. To do so, choose Start of the navigation path Actions Next navigation step Export  Next navigation step  Cancel End of the navigation path.

3. Import the Configuration Data

Depending on the transport mode you have chosen, you import the configuration data manually or use CTS.

  • Importing the configuration data manually

    If you have chosen the manual mode, you must manually import the configuration archive to the target system. Depending on the format, proceed as follows:

    • Import the transport package in the format .configarchive

      1. In the portal, choose Start of the navigation path System Administration Next navigation step System Configuration Next navigation step Knowledge Management Next navigation step Content Management End of the navigation path. In the menu bar, choose Start of the navigation path Actions Next navigation step Import. End of the navigation path.

      2. Choose a configuration archive with the ending .configarchive to import and choose Preview .

        The system displays the objects that are added to the configuration, replaced in it, or deleted from it.

        Note

        If the configuration archive is identical to the existing configuration, the system does not import the file.

      3. Choose OK to import the configuration archive.

        If errors occur during the import, you can display them using the link See Technical Details .

    • Import the transport package in the format .sda

      You use the SAP Deployment Perspective in the SAP NetWeaver Developer Studio to deploy transport packages in the format of SDA archive. The system performs the import automatically during the deployment. For more information, see Deploying and Undeploying with SAP NetWeaver Developer Studio .

  • Importing the configuration data using CTS

    If you are using the transport via CTS, CTS automatically transports the transport package to the target system. Once it arrives, the configuration data is automatically unpacked and installed. You may have to restart the application server for the target system.

4. Check if the AS Java Requires Restart After the Import of the Transport Package

Transport packages contain an additional Boolean property in their MANIFEST file, which indicates whether you need to restart the application server after the import of configuration data. If the value of the property is false , the application server does not require restart. If the value is true , you need to restart the application server to activate the imported configuration data.

Depending on the transport mode and the stage of the transport process, you have the following options for checking the need for restart:

  • Checking the need for restart in the application <file_number> . <n> .log file.

    You can check whether the application server requires restart in the application <file_number> . <n> .log file of the target system. This file is stored in the /j2ee/cluster/server<n>/log directory. You can use this option for both the manual and the CTS transport modes after the import of the transport packages.

    1. Display the logged data using the SAP NetWeaver Administrator or the Log Viewer.

    2. Check the value of the Requires restart property.

      For more information, see: Deploying Archives

      Logging Configuration Changes

      Log Viewer .

  • Checking the need for restart in the CTS.

    When performing the transport of configuration via CTS, you can check if the system requires restart in the CTS system. You can use this option for the CTS transport mode only, and before the import of the transport packages.

    1. Log on to the CTS, and choose Transport Management System or call transaction STMS .

    2. Choose Import Overview.

    3. In the list with SAP systems, select the target system and choose Display Import Queue.

      The import queue of the target system appears.

    4. Select your transport request, and choose Object List.

    5. In the Object List tree structure, browse to your transport package and double-click it to display its attributes.

    6. On the Display KM Object screen, choose Other Attributes, and check the value of the Requires restart attribute.

5. Restart the AS Java if Required

You restart the AS Java using the SAP Management Console (SAP MC). For more information, see Starting and Stopping the Application Server Java (AS Java) .