You can export and import a profile in Lobster_data together with the corresponding configuration files, macros and test files as a package (.pak). Configuration files are only taken into account if their file path starts with ./conf and has been entered as a fixed value. If the path of a configuration file uses variables, the file will not be taken into account. Replacement values for functions will also be part of export packages.

Note: Lobster_data also provides the Transport Manager , which allows an online transport of profiles without the intermediate step via files. However, the versions of both systems must be within the same major release, e.g. 4.0.0 and 4.1.0. Versions 3.5.4 and 4.0.0 would not work.

Export

See also section Context Menu Profiles. When exporting a profile, you can choose between the following options.

(standard, importable) Profile and all configuration files as package file (.pak). Note: Configuration files in any subfolder named _exclude_ are not included in .pak files. This can be used to make sure that important files do not 'wander' from the test to the productive system, for example. Example:./conf/sub1/_exclude_/test.txt

(deprecated, importable) Only the profile without configuration files (.obj).
(not importable) XML file (.xml). The export as XML file only support a profile comparison (diff).
(not importable) Gefeg.FX file (.xml). Only creates a tree structure.
(not importable) RESTful API Modeling Language (RAML). Only creates a tree structure.

Import

See also section Context Menu Profiles. Importing a profile will open another dialogue. Here you can import the formats .pak and .obj, please always use format .pak.

images/download/attachments/91137350/752-version-1-modificationdate-1650448825725-api-v2.png

(1) You can either drag an export file directly into the field or use the button to search for one in the directory structure.

(2) A new profile is created. and all settings of the export file are applied.

(3) The selected profile (in the profile overview) will be overwritten with the content of the export file.

(4) A new profile is created. Only the source structure, the target structure and variables are imported. The settings for the Input Agent and the Response Routes are unchanged.

(5) The selected profile will be cloned. Only the source structure, the target structure and variables are imported. The settings for the Input Agent and the Response Routes are unchanged.

Note: When you import a package, you can decide which of the contained files you really want to import.

Note: Only when a new profile is saved after the import, it is permanently available. The same applies to other imported files.

Guidelines for Creating Profiles in the Test System for Transporting to the Productive System

See section Transport (Export and Import) of Profiles.