If the bridge does not appear on the Integrations > Synchronizer or Link Configuration page in Agile Manager after installation is complete, click Refresh, or refresh the browser page.

• If the bridge still does not appear, make sure the bridge is running. For details, see Start and stop the Integration Bridge.

  The Integration Bridge service attempts to start the bridge several times. If it is not successful, the application shuts down and the service stops.

• If the bridge does not start, make sure 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 bridge, 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 is down. In Agile Manager, click the bridge name to view the last time the bridge accessed the server.

If the connection status of your bridge is displayed as Offline in Agile Manager, try restarting the bridge. For details, see Start and stop the Integration Bridge.

If the bridge remains offline, the Integration Bridge user's Agile Manager password may have expired.

Modify your bridge to connect to Agile Manager using OAuth and no longer depend on user credentials:

1. On the Integrations > API configuration page, add an Integration Bridge client. Agile Manager generates a client ID and secret for the bridge.

   Note: If you are not a Site Administrator on your Agile Manager system, have your administrator add the Integration Bridge API client and provide you with the generated client ID and secret.

2. Use the generated client ID and secret for the credentials that the bridge uses to connect to Agile Manager. For details, see Modify Agile Manager credentials and proxy.

Check the following log files in the Integration Bridge log folder (<Bridge_installation_directory>\product\log\controller):

• controller.log
• wrapper.log

Additionally, check the <Endpoint type name>.log file located in the <Bridge_installation_directory>\product\log\<Endpoint type name> directory.

Check the connection setup defined for the endpoint:

• Check the credentials defined for the endpoint.
• Check proxy configuration if relevant.
• If ALM is configured to require HTTPS for logging in, configure the bridge to connect to ALM using HTTPS.

For details, see Manage connection setup and Integration Bridge security.

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).

Issue: You uninstalled the Integration Bridge, but the next time you install a bridge, the suggested default name implies that a bridge already exists.

Cause: You might have performed the uninstall using a non-root user.

Solution: 

• You can ignore the listed existing bridge, and install a new one.
• Locate and remove the init scripts that were left over from the Integration Bridge service installation.

Issue: During a synchronization run, some entities fail to synchronize. The errors indicate that a required field is missing. However, in the Link Configuration page, I do not see any mandatory fields that are not mapped.

Cause: 

A field that is currently mandatory in ALM is not mapped, or it is mapped to an Agile Manager field that does not contain a value.

• The field in question may have been marked as mandatory in ALM after the link or entity itself was created.
• The field might be mandatory in ALM only when other fields contain certain values.

Solution: 

Map the field to an Agile Manager field that contains a value, or manually enter a value in Agile Manager for the relevant field.

The URL that the Integration Bridge uses to connect to Agile Manager is downloaded from Agile Manager with the Integration Bridge. In most cases, you should not need to modify this URL.

If the URL for your Agile Manager changed, do the following:

1. Navigate to the <Integration Bridge installation folder>\product\conf folder (on Linux, reverse the slashes).

2. Open the server-connection.conf file for editing.

3. Update the agm.base.url property with the new URL.

   Format: http(s)://<server hostname or IP address>:<port number>/agm

   Tip: If you can login to the Agile Manager that you want the Integration Bridge to use, login and then use the URL from your address bar. Take the URL from the beginning up to /agm. Ignore the rest.

4. Restart the bridge.