To exchange a configuration, you can export a project. All elements that are related to the project are exported. Transactions and history are not exported. For example, the related messages and web service actions are exported, but the message history and web service history are not exported.
Which settings are included in the export is defined by the Export options parameter in the Connectivity studio parameters. If you export a project, and the export option is:
As a result of the export, an XML file is created with the project configuration.
This topic explains how to export a project configuration to a file.
1. | Click Connectivity studio Integration Design. |
2. | Click Export project to file. |
  |
Note: |
3. | In the Download file field, you can change the default file name as desired. |
4. | You can include environment-specific properties in the project export. Environment-specific properties are, for example: - Passwords - Shares on connectors - File actions |
  | Select Yes in the Including environment specific properties field. |
  |
Note: If you import a configuration with environment-specific properties in another environment, it is not guaranteed that these properties work properly. |
5. | You can run the export of a project in the background. Usually, you do so if you export a project with many elements. While the project is exported, you can continue with other activities in the environment. |
  | Select Yes in the Run in background field. |
6. | Click OK. |
Related to | Notes |
---|---|
Manage Connectivity studio parameters when copying database |
  |
Manage Connectivity studio parameters when copying database |
  |
Export configuration |
  |