Publishing in Development environment

This section describes how you can publish reports and tasks from the test system to the production system.


Reports

In order to publish a report from the test system to the production system, you need to open the list of reports in Mail & Deploy Client by clicking Reports in the left menu, selecting the report you want to publish and then clicking the button . This button can only be clicked, if the repository you are currently connected to has a production repository (see Production Repository) set up. In order to successfully publish a report, the following conditions must be met:

  • All datasources (see Datasources) which are used by the report to be published need to exist in the production repository. Datasources in the production repository need to have the same name as the ones of the test repository.

If any of these conditions are not met, you will receive a message indicating which element Mail & Deploy requires you to create in the production repository in order to publish the report.


Tasks

In order to publish a task from the test system to the production system, you need to open the list of tasks in Mail & Deploy Client by clicking Tasks in the left menu, selecting the task you want to publish and then clicking the button . This button can only be clicked, if the repository you are currently connected to has a production repository (see Production Repository) set up. In order to successfully publish a task, the following conditions must be met:

  • All users and user groups (see Users and User Groups) which are used by the task need to exist in the production repository. Users and user groups in the production repository need to have the same name as the ones of the test repository.

  • All datasources (see Datasources) which are used by the task need to exist in the production repository. Datasources in the production repository need to have the same name as the ones of the test repository.

  • All reports (see Reports) which are required by the task need to exist in the production repository. Reports in the production repository need to have the same name as the ones of the test repository.

  • All e-mail servers (see E-Mail Servers) which are required by the task need to exist in the production repository. E-Mail Servers in the production repository need to have the same name as the ones of the test repository.

  • If the task requires an active directory connection (see Active Directory Connection Settings) then the production repository needs to have a working active directory connection set up.

If any of these conditions are not met, you will receive a message indicating which element Mail & Deploy requires you to create in the production repository in order to publish the task.

Please note that execution plans (see Execution Plans) are not published to the production repository when publishing a task; if you publish a task that already exists in the production environment so that the task gets updated existing execution plans of that task will be kept.


T
Team is the author of this solution article.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.