Unresolved Dependencies

When you select objects on the Source side for possible migration to the target system, a check is performed by ActiveBatch to determine whether any unresolved dependencies are present. For example, let’s assume we want to migrate JobA and JobA uses a queue named Server1. If Server1 is not part of the ChangeSet or Server1 doesn’t already exist on the Target system, that would be an unresolved dependency.

 

When an unresolved dependency is detected, a pane appears on the right indicating which object references are unresolved and provides you an opportunity for resolving those using objects from the Target system.

 

 

In the above figure, CaseStudy3 has been selected for migration. When the selection occurred, ActiveBatch detected three (3) unresolved dependencies. The Resolve button to the right of the object that does not exist on the Target system allows you to resolve each dependency separately. When you click on the Resolve button, you will be shown a navigation tree to the objects on the Target system - beginning with your connection point. You can then select an object on the Target system that will map to the Source object. This is one way to resolve the unresolved dependency. Another way to handle the unresolved dependency is to locate the dependencies on the Source side and check them, to include them in part of the ChangeSet. In this example, the unresolved dependencies are stored in the Source's "Objects" Folder. After checking the Objects Folder checkbox, the unresolved dependencies are resolved, and the Unresolved Dependencies pane is removed.

 

 

Now no unresolved dependencies are present. If we’re interested in migrating these objects we would proceed to Synchronization.