Disponible avec une licence Standard ou Advanced.
Disponible avec une licence Workflow Manager.
ArcGIS Workflow Manager repository replication allows organizations to maintain multiple Workflow Manager repositories locally in different geographic regions for performance reasons, while the users at each location continue to work on the same set of jobs. Workflow Manager replication is not an extension of geodatabase replication. It is accomplished with Workflow Manager services or configuration files. ArcGIS Workflow Manager replication is a two-way replication.
You'll define a collection of Workflow Manager repositories that will have identical Workflow Manager contents after replication. This collection of repositories is known as a repository cluster.
One Workflow Manager repository is designated as the parent repository and is tasked with coordinating the synchronization between each repository. After the parent repository is specified, each child repository is added. The child repositories can be designated as connected repositories, where the synchronization happens automatically, or disconnected repositories, where the synchronization occurs by creating files that can be manually imported.
- Repository Cluster—A cluster is a collection of Workflow Manager repositories that participate in repository replication. Each repository is identified as a node. Nodes can be added to the cluster at any time. For example, a cluster might be created for the Workflow Manager repositories at Redlands, California; Washington, D.C.; St. Louis, Missouri; and Denver, Colorado. The repositories at these locations must have Workflow Manager installed, and the Creation of Workflow Database tool must have been executed to create the necessary tables. For the purpose of replication, the minimum configuration can be imported.
- Parent node—Each cluster must have a parent node. In connected replication, the parent node initiates all replication and synchronization processes. The parent node must be a repository that has the configuration you want to distribute to users in the other locations.
- Child node—A cluster can have more than one child node. The children have identical elements when replicas are created and changes are synchronized.
- Elements—Elements are considered configuration items like job types and step types. However, they are not limited to just configuration items. Your jobs are also elements, and they all get replicated and synchronized.
- Last Sync date—This date is a property of each node in the cluster. It's used when you create a replica or synchronize changes. As changes are made to each of your elements, the date and time that it occurred are updated. If there is an element with a newer date and time stamp, the application imports that to the parent and pushes this change to all the children in the cluster.
- Connected or Not—This is the status of the node. A connected node means that it is online, and the replication and synchronization changes relay immediately. If the node is disconnected, specify a file location to export the configuration file and manually import it later using tools in the Workflow Manager geoprocessing toolbox.
Replicas
Create replicas is the process of making all child repositories an identical copy of the parent repository. It exports the configuration from the parent repository, deletes existing configuration in child repositories, and imports the parent repository configuration in child repositories. Replicas can be created in Workflow Manager Administrator or by using Workflow Manager geoprocessing tools.
Synchronization of changes
Synchronization is the process of making the changes match between the parent and child repositories. Changes from child repositories are sent to the parent repository, and consolidated changes are sent to all child repositories. Changes can be synchronized in Workflow Manager Administrator or by using Workflow Manager geoprocessing tools.
Connected replication
Connected replication is ideal for locations that have network access as it requires ArcGIS Workflow Manager for Server and is accomplished using Workflow Manager services. When using connected replication, the information is automatically exchanged using Workflow Manager services with minimal user interaction. Workflow Manager for Server must be installed at each node, and the parent and child repositories must be published as Workflow Manager services. There are two ways to set up connected replication:
- Workflow Manager Administrator—Use the