In some cases, it can be required that you copy a database to another environment. For example, you have a test environment and a production environment. An issue occurs in the production environment. So, testing is required to find the cause of the issue. However, you do not want to mess up the production environment with testing data. You can copy the full production database to the test environment.
Name | Responsible | Description |
---|---|---|
Export Connectivity studio parameters |
Application Consultant |
If you want to copy a database to the current environment and you want to keep the Connectivity studio parameters, first export these parameters. As a result, an XML file with the parameter settings is created and downloaded to your local downloads folder.
|
Import Connectivity studio parameters |
Application Consultant |
If you have copied a database to the current environment and you first exported the Connectivity studio parameters, you can import these parameters. As a result, the Connectivity studio parameters are automatically reset with the original environment parameters.
|
Delete Connectivity studio parameters |
Application Consultant |
If you have copied a database to the current environment and you want to manually reset the Connectivity studio parameters, first delete these parameters. As a result, all parameter settings are deleted, and a new environment ID is generated.
If the imported parameters are fine, you can also decide to only reset the Environment ID. As a result, only these fields are reset:
|
Set Connectivity studio parameters |
Application Consultant |
Before you start using Connectivity studio, set up the Connectivity studio parameters. |