Table of Contents

Search

  1. Preface
  2. Understanding the Repository
  3. Using the Repository Manager
  4. Folders
  5. Managing Object Permissions
  6. Local and Global Shortcuts
  7. Team-Based Development with Versioned Objects
  8. Labels
  9. Object Queries
  10. Team-Based Development with Deployment Groups
  11. Copying Folders and Deployment Groups
  12. Exporting and Importing Objects
  13. Exchanging Metadata
  14. Copying Objects
  15. Metadata Extensions
  16. Appendix A: MX Views Reference

Repository Guide

Repository Guide

Copying or Replacing Running Workflows, Sessions, and Tasks

Copying or Replacing Running Workflows, Sessions, and Tasks

When you copy or replace a folder or deploy a deployment group, the Repository Service first copies the folder or deployment group to temporary tables in the target repository database. During this stage of the deployment, you have read-only access to the target repository if you are copying but not replacing a folder, or if you are copying a deployment group. Workflows, sessions, and tasks that are running in the target repository continue to run. You can view them running in the Workflow Monitor after the deployment operation begins.
If you are
replacing
a folder, you cannot view the folder in the target repository after the deployment operation begins. Also, all running workflows, sessions, and tasks are immediately blocked in the target folder, and they remain blocked for the duration of the deployment operation. Running workflows, sessions, and tasks in other folders in the target repository continue to run.
After the Repository Service copies all objects in the folder or deployment group to temporary tables, it moves the data from the temporary tables to the target repository. During this stage of the deployment, you no longer have read-only access to the target repository, and all running workflows, sessions, and tasks are blocked. When an Integration Service tries to access the repository to run a workflow, session, or task while a repository is blocked, the Repository Service denies access and returns the following message:
Access to the repository is blocked since a folder/object deployment is in progress. The current operation will be suspended until the deployment is completed.
The error message appears in the Administrator tool, workflow log, or session log, depending on which operation the Integration Service tried to perform. For example, if the Integration Service tried to fetch session information to run a session in a workflow, the message appears in the workflow log.
The Integration Service pauses until the repository completes the deployment. It cannot fetch objects in that repository during this time.
When the repository allows access again, it displays the following message:
The folder/object deployment has completed. The current operation will resume.
The Integration Service fetches the repository object and completes the workflow, session, or task.

0 COMMENTS

We’d like to hear from you!