This topic is relevant for NextGen Synchronizer only, embedded in Agile Manager's configuration area. For details about the ALM Synchronizer, see for .
This topic covers the following scenarios:
If the bridge does not appear on the Integrations > Link Configuration page in Agile Manager after installation is complete, click Refresh Agent, or refresh the browser page.
If the bridge still does not appear, verify whether the agent and service has started. For details, see Manage the bridge agent and service.
The Integration Bridge service attempts to start the agent several times. If it is not successful, the application shuts down and the service stops.
If the agent is not started, verify whether the value of the Drmi.server.port in the <installation folder>\product\log\controller\wrapper.log file is set to an available port.
If the defined port is in use by another application when the Integration Bridge service attempts to start the agent, the following errors are printed to log files:
In the wrapper log file | java.rmi.server.ExportException: Port already in use: <port> |
In the controller log file | java.rmi.NotBoundException: ControllerAPI |
The Integration Bridge service is down. In Agile Manager, click the agent name to view the last time the agent accessed the service.
Check the following log files in the Integration Bridge log folder (<Bridge_installation_directory>\product\log\controller):
Additionally, check the <Endpoint type name>.log file located in the <Bridge_installation_directory>\product\log\<Endpoint type name> directory.
The credentials defined for the endpoint may be incorrect. For details about verifying or modifying credentials, see Manage credentials.
The user accessing Agile Manager from the Integration Bridge is not defined with the Integration Bridge role.
Modify this user's role in the Agile Manager configuration area (Site > Users).
Note: For security purposes, the Integration Bridge user should not have any additional roles.
By default, the Integration Bridge is run using the Windows Local System user. If you need to enable flows for additional endpoint types, you can modify the Local System user to include additional required access rights.