Skip to main content
Version: 723.SP03

System Copy Export/Import CxLink Config

Every time refresh non-prod systems from production. One of the steps that should be performed before the database copy is to export the configuration related to the CxLink Suite from the non-prod system, import those printers back into that system after a refresh. Follow below steps

Exporting configuration before the System Copy​

  • Execute the backup program

    The first step in backing up the CxLink configuration is to run the program /LNKAWS/CONFIG_BACKUP. This program is designed to create a backup of the CxLink configuration by generating a snapshot of the current state of all relevant tables. This is crucial for preserving the configuration settings and ensuring that they can be restored in case of any system changes or failures.

  • Select Tables and Backup Mode.

    Upon executing the program, you will be prompted to select the tables you wish to include in the backup. It is important to select all tables related to the CxLink configuration to ensure a comprehensive backup. The mode "Generate a Table backup" should be chosen to create a backup in the form of database table snapshots. This mode is typically used to capture the data within the tables at a specific point in time.

  • Copy Data and Cofiles Locally.

    The final step is to copy the data and cofiles of the transport request to a local directory. The data and cofiles are the physical files that contain the changes captured in the transport request. The data file contains the actual data that has been exported, while the cofile contains information about the transport request itself, such as the sequence of importing the data.

    Copying these files locally provides an additional layer of backup. In case the transport request needs to be imported into another system, these files can be used to perform the import manually. This is especially useful if the standard transport management system (STMS) is not available or if the transport needs to be applied to a system outside of the current landscape.

  • You will see the export file content

It will generate a transport request with the contents. The next step is release the transport request and copy the data and cofiles of the order locally.

Importing configuration after the System Copy​

Now, import the transport request generated before the copy with all the options marked: