This topic is relevant for NextGen Synchronizer only, embedded in Agile Manager's configuration area. For details about the ALM Synchronizer, see for .
After your link is created and configured, run an integrity check to verify that records will be synchronized correctly.
If the integrity check passes, run a simulation to verify how much data will change.
Then run manual tasks, or start automatic synchronizations.
If you make certain changes to a link's configuration after having already synchronized, such as updated rules or field mapping, you'll need to run a full synchronization to ensure that all records are aligned with those changes. Agile Manager will notify you when a full synchronization is required.
Caution: Once records have been synchronized, they cannot be removed from the synchronization. When first setting up a link's configuration, use a favorite defined with one record only. Widen the favorite slowly, as you go ensuring that the synchronizations run as you expect.
You must run an integrity check before running a synchronization task to verify that the task will run smoothly. Use the integrity check to debug any errors before actually synchronizing the records.
Right-click the link in the navigation tree on the left and select Run Integrity Check, or while viewing the link details, select Run > Run Integrity Check from the toolbar.
The integrity check status is displayed at the bottom of the screen.
For example:
Click the expand arrow at the top of the status to display all log messages. From there, click View Report or View Log for more details.
Run a simulation after your integrity check passes, and before you actually synchronize your data, to verify the number of records that will be added or updated in the next synchronization.
Note: The simulation run does not detect possible errors that may occur during synchronization.
Right-click the link in the navigation tree on the left and select Run Simulation, or while viewing the link details, select Run > Run Simulation from the toolbar.
The run status is displayed at the bottom of the screen.
Click the expand bars at the top of the status to display all log messages. From there, click View Report or View Log for more details.
The following data is included in the simulation report:
The number of items to be deleted in each endpoint
Run tasks manually when you want to test a link, such as when configuring or debugging the link settings. If there were errors in the last synchronization run, a manual synchronization will automatically re-synchronize those records.
Right-click the link in the navigation tree on the left and select Run Manual Sync., or while viewing the link details, select Run > Run Manual Sync. from the toolbar.
The run status is displayed at the bottom of the screen.
Click the expand bars at the top of the status to display all log messages. From there, click View Report or View Log for more details.
Automatic synchronizations are scheduled to run every 30 seconds, around the clock.
Note: If a single run task takes longer than 30 seconds, the automatic runs are performed farther apart as needed.
Certain types of changes detected in your link, such as updated rules or field mapping, require to you to synchronize all records in your link. Agile Manager will notify you when a full synchronization is required.
Synchronizing all records ensures that all records are aligned with the changes in the link configuration or fields.
Note: Performing a full synchronization may take some time. We recommend doing this when the system is not otherwise busy.
To run a full synchronization, in the navigation tree, right-click the link name, or select the link. Then, select More Actions > Schedule Full Sync. in Next Run.
The next synchronization that starts will synchronize all records in the link.
If your link is in automatic mode, and a synchronization ran with errors, the records with errors are not necessarily fixed in subsequent runs.
This may happen if the errors occurred because of changes outside of the link configuration, such as if the schema changed, but the field mapping was not updated. If you fix the cause of the error (such as refreshing the Field Mapping tab and map the new fields), Synchronizer will re-synchronize those records if changes in the actual record are detected.
Synchronizer also periodically re-synchronizes all records, including those that had run with errors, but have had no subsequent changes.
To ensure that records that ran with errors are indeed re-synchronized in the next upcoming run, manually set the link to re-synchronize those records.
Do one of the following:
On the Link Configuration page
|
Right-click the link name, or select the link and then select More Actions > Retry Errors in Next Run. |
On the Dashboard
|
In the Link Summary area, expand the workspace and link nodes until you see the specific issues that occurred in recent synchronizations. Find the link for which you want to retry records with issues, and click Retry next run next to the link. |
The next automatic synchronization that starts will synchronize all records in the link, regardless of whether changes were detected. For details, see Automatic synchronizations.