Note: This topic is relevant for NextGen Synchronizer only. For details about the ALM Synchronizer, see ALM Synchronizer for Agile Manager or search using the ALM Synchronizer filter.
See the following common questions about NextGen Synchronizer below.
New field values created in a destination endpoint during synchronization are automatically sent back the record in the source endpoint.
So, for example, when you create a record in ALM and synchronize it to Agile Manager, that new record is created in Agile Manager, and assigned an Agile Manager ID.
NextGen Synchronizer recognizes this new ID field value, and sends it back to ALM, adding it to the source record.
This last step is the update you see in your run history.
The following types of synchronization runs are removed from the run history after subsequent synchronizations are run:
An empty run is only displayed in the run history when it is the latest run, and was run in the last 10 days.
Runs with errors that have not yet been resolved are displayed in the run history until the related records are synchronized successfully.
Previous runs that contain errors, which also appeared in later runs, are deleted when they are more than 10 days old.
|Fatal runs that are more than 10 days old||For synchronizations run in the last 10 days, only the last 20 runs are displayed.|
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.
For details, see Re-synchronizing records with fixed errors (automatic mode only).
To improve synchronization performance between Agile Manager and ALM, add indices to your ALM project schema as follows, depending on the type of database you use:
CREATE INDEX BG_VTS_IDX ON [td].[BUG] (BG_VTS, BG_BUG_ID);
CREATE INDEX RQ_VTS_IDX ON [td].[REQ] (RQ_VTS);
CREATE INDEX RT_VTS_IDX ON [td].[REQ_TRACE] (RT_VTS);
CREATE INDEX RT_CREATION_DATE_IDX ON [td].[REQ_TRACE] (RT_CREATION_DATE);
CREATE INDEX LN_CREATION_DATE_IDX ON [td].[LINK] (LN_CREATION_DATE);
CREATE INDEX BG_VTS_IDX ON BUG (BG_VTS, BG_BUG_ID);
CREATE INDEX RQ_VTS_IDX ON REQ (RQ_VTS);
CREATE INDEX RT_VTS_IDX ON REQ_TRACE (RT_VTS);
CREATE INDEX RT_CREATION_DATE_IDX ON REQ_TRACE (RT_CREATION_DATE);
CREATE INDEX LN_CREATION_DATE_IDX ON LINK (LN_CREATION_DATE);
Group stories are not reflected in the ALM requirements tree. Therefore, Synchronizer does not automatically recognize Agile Manager Group Stories, and does not synchronize any group (parent/child) relationship between stories.
If Agile Manager is the master of the synchronization link, and a user story that was synchronized with ALM is broken into a group story in Agile Manager, Synchronizer considers the user story to have been deleted.
If ALM is the master of the synchronization link, breaking a synchronized user story into a group story in Agile Manager causes no changes on ALM.
Tip: Synchronize the group story by creating a user defined field in ALM and mapping it to the Agile Manager Story Group field. The name of the group (parent) story is synchronized to the mapped ALM user defined field.
This synchronization is always unidirectional, from Agile Manager to ALM.
You cannot search in the link tree when a link is in edit mode. Save any changes or click Cancel Edit to enable the search box.
After a link is synchronized, you can no longer remove mapped requirement types. You can still add types that are not yet mapped.
To edit requirement type mapping you must be in edit mode. For details see Edit requirement type mapping.
If inexplicable errors occur, such as an inability to read run reports, constant synchronization failures, errors while creating links, verify that you are synchronizing with a supported version of ALM. For details, see Supported ALM versions.
If your version of ALM is supported, contact
If this is the case:
The following error will appear in the Agile Manager log files:
java.net.SocketException: Too many open files
The maximum number of open files allowed by the operating system is too low, and must be increased.
Check the list of custom fields defined in Agile Manager (Site/Workspace> Fields configuration page). Make sure that the field in question still defined for the workspace you are synchronizing.
- The custom field may have been previously defined as a site-level field, and then moved to other workspaces.
- The custom field may have been removed from the system.
This may happen if an ALM entity has an attachment whose name contains special characters (
Workaround: On Agile Manager, remove the added attachment. On ALM, rename the attachment so that it does not contain special characters.