ALI Dev Bridge deployment
To learn more about the ALI Dev Bridge, see ALI Dev Bridge Overview.
Java 7 or 8 SDK must be available on the machine where you plan to run the ALI Dev Bridge.
Caution: If you install JRE 8 and not the whole SDK, make sure that you use the Server JRE package.
Download the ALI Dev Bridge.
In Agile Manager, click Configuration > Workspace > ALI Summary.
Under Integration, select Download ALI Dev Bridge from the drop down list.
The ALI Dev Bridge application is downloaded in a bundle with the Jetty Servlet Container.
After downloading, unzip the ALI Dev Bridge bundle. Follow the instructions in the README.txt file to start and configure the ALI Dev Bridge.
Download additional tenant descriptors.
The ALI Dev Bridge is, by default, configured for the specific site for which it was downloaded. If you are working with more than one Agile Manager site, you must download and configure a tenant descriptor for each additional site.
On the ALI Summary configuration page, under Integration, click Download Tenant Descriptor.
Follow the instructions for configuring the tenant descriptor in the README.txt file located in the downloaded ALI Dev Bridge bundle.
Verify that the ALI Dev Bridge is successfully deployed and can connect to Agile Manager.
To connect the ALI Dev Bridge to Agile Manager, you must have a user account assigned with the Site Administrator or ALI Dev Bridge role. This user role can be defined by site administrators on the Site or Workspace > Users configuration pages.
In your browser, enter the location of the ALI Dev Bridge, in the following format: http://<yourApplicationServerHostname>:<yourApplicationServerPort>/ali-dev-bridge.
Log in with the credentials of the Site Administrator or ALI Dev Bridge user.
If you are notified that the deployment URI is not configured, click Fix it for me automatically.
Note: This link is not available if you are connecting to the ALI Dev Bridge using the local hostname/IP address.
- To save your credentials and automatically reconnect after restarting the Dev Bridge, select Automatic reconnect in the top right-hand corner of the ALI Dev Bridge page.
Set the Bridge location in Agile Manager.
Alternatively, you can set the ALI Dev Bridge location from within Agile Manager.
- In Agile Manager, browse to the Workspace > ALI Summary configuration tab.
- Under Integration, click Configure ALI Dev Bridge.
- In the ALI Dev Bridge URI field, enter the location of the ALI Dev Bridge, in the following format: http://<yourApplicationServerHostname>:<yourApplicationServerPort>/ali-dev-bridge.
- Click Save Configuration.
No. You need a tenant descriptor for each of your sites. You can download additional tenant descriptors from Agile Manager.
For instructions on configuring the tenant descriptor, see the README.txt file located in the ALI Dev Bridge bundle you downloaded from Agile Manager.
For instructions on starting and working with the ALI Dev Bridge, as well as how to configure multiple sites, see the README.txt file. The README is included in the ALI Dev Bridge bundle, downloaded from Agile Manager.
In the ALI Dev Bridge bundle that you downloaded from Agile Manager, navigate to the following folder: tenants/<tenant-name>/logs. This folder contains the following logs from the ALI Dev Bridge web application:
- error_log. Contains information about errors.
- audit_log. Contains information about every operation performed by the bridge.
- Additional logs that contain descriptive information about last performed operations, such as last clean up, last SCM synchronization, last Build synchronization, and so on.
When an HTTP Proxy is required for your outbound HTTP traffic, requiring that the bridge needs to open new HTTP connections to Agile Manager, you can set proxy settings in the connection.properties file.
In the ALI Dev Bridge bundle that you downloaded from Agile Manager, this file is located in the following folder: tenants/<site-name>/conf. This properties file is created after the ALI Dev Bridge is started for the first time. Locate the following section in the connection.properties file:
# proxy to be used #httpProxy=<host:port> #httpProxyUser=<proxy_user> #httpProxyPassword=<proxy_password> # uncomment to setup proxy using a PAC file URL #httpProxyPac=http://your-company.com/proxy.pac
You can either define a proxy server directly, or define a Proxy Auto-Configuration (PAC) file URL.
Define a proxy directly
Uncomment the relevant lines, and fill in your proxy settings.
Example: If your proxy runs on the host 220.127.116.11, uses port 3128, and no user/password is needed to connect to the proxy, your settings should be as follows:
# proxy to be used
Uncomment the relevant lines and fill in your PAC file URL value.
Example: If your PAC file URL is http://18.104.22.168/proxy.pac, your settings should be as follows:
# uncomment to setup proxy using a PAC file URL
- There might be a white/black list of hosts that can connect to the HTTP proxy. If this is the case, make sure that the host where the bridge is running is allowed to connect to your HTTP proxy.
- After making changes to the connection.properties file, you must restart the ALI Dev Bridge.
ALI Dev Bridge troubleshooting
Check the following:
- Make sure that the bridge has started.
- Verify that the user that you are using to connect the bridge has the Administrator or ALI Dev Bridge role.
- If an HTTP proxy is needed for outbound HTTP traffic in your environment, configure the proxy settings and restart the bridge.
- Verify that there are no serious problems in the error log.
Enable HTTPS for ALI Dev Bridge. If you use a self-signed certificate, ensure that the certificate is trusted on all client machines.
Note: All supported versions of Internet Explorer, Chrome versions 21 and higher, and Firefox versions 23 and higher, protect users from pages that mix secured and unsecured content (content that comes from both HTTP and HTTPS connections).
In effect, this:
- Disables the ALI file diff and file view features
- Prevents the ALI Dev Bridge status in the ALI Summary tab from loading properly, even when the ALI Dev Bridge is successfully connected to Agile Manager
- Prevents ALI from configuring new Build Servers, Build Configurations, SCM Repositories, or SCM Branches.
Modify the Jetty configuration file so that the network communication is displayed on the console. Add the following options to the wrapper-custom.conf file. This file is located in the wrapper folder, included in the ALI Dev Bridge bundle downloaded from Agile Manager.
wrapper.java.additional.105=-Dorg.apache.commons.logging.Log="org.apache.commons.logging.impl.SimpleLog" wrapper.java.additional.106=-Dorg.apache.commons.logging.simplelog.log.httpclient.wire.header="debug" wrapper.java.additional.107=-Dorg.apache.commons.logging.simplelog.log.org.apache.commons.httpclient="debug"
The bridge requires Java 7. Verify whether you have Java 7 installed on the machine hosting the bridge, and update Java if necessary.
Note: Agile Manager notifies you when there is a new version of Dev Bridge.
If the Agile Manager connection to the SVN repository is failing, and continues to request that you provide correct credentials, verify that you have Basic Authentication enabled together with Windows Authentication.
The ALI Hudson or Jenkins plugins also require Maven, Subversion, and CVS plugins. These are installed by default together with the Jenkins installation, and with Hudson installations for versions lower than 3. If you use Hudson 3 or higher, you must install the additional plugins manually.
If you are using Hudson version 3 or higher and did not manually install these plugins, the following error is generated in the Hudson log file:
java.io.IOException: Dependency maven-plugin (2.1.0), subversion (2.0.1), cvs (2.1.0_1) doesn't exist