Installing IBM Bluemix DevOps Connect
Install IBM® Bluemix™ DevOps Connect to share data between IBM™ UrbanCode™ Deploy, IBM UrbanCode Release, and IBM UrbanCode Cloud Services and Bluemix Services.
You must install a Java™ Runtime Environment version 7 or later on the host system and set the
PATH variable to its location.
- Stop the IBM UrbanCode Deploy server.
- Place the patch files in the \UCD_server\appdata\patches. If you renamed the appdata folder during installation, use that folder instead.
- Restart the IBM UrbanCode Deploy server.
After you install a patch, IBM Bluemix DevOps Connect is compatible with UrbanCode Deploy versions 6.2.0, 18.104.22.168, 22.214.171.124, 6.2.1, and 126.96.36.199. IBM Bluemix DevOps Connect is not compatible with UrbanCode Deploy versions earlier than 6.2.0.
The IBM Bluemix DevOps Connect installation file is an executable JAR file. After you download the file, place it on a computer that has access to the products that you want to integrate with, such as IBM UrbanCode Deploy. You start IBM Bluemix DevOps Connect by running the JAR file.
By default, the user that registers IBM Bluemix DevOps Connect is authorized to use it. An authorized user can authorize other users to use the application. Authorized users can access the IBM Bluemix DevOps Connect web-based dashboard and install plug-ins and create integrations.
Download IBM Bluemix DevOps Connect from the IBM developerWorks.
The downloaded file is an executable JAR file. You run this file to start IBM Bluemix DevOps Connect.
Open a command window where you placed the JAR file and start IBM Bluemix DevOps Connect by
using the following command:
java -jar devops-connect-build_number.jar. For example,
java -jar devops-connect-2.0.854198.jar.IBM Bluemix DevOps Connect displays start-up messages in the command window.
If you use a proxy, use this command to start IBM Bluemix DevOps Connect:
java -Dhttp.proxyHost=proxy_ip -Dhttp.proxyPort=proxy_port -jar cloud-sync-build_number.jar. If you use a proxy and SSL, use this command:
java -Dhttps.proxyHost=proxy_ip -Dhttps.proxyPort=proxy_port -jar cloud-sync-build_number.jar. The following is an example of a typical command:
java -Dhttps.proxyHost=10.0.0.100 -Dhttps.proxyPort=8800 -jar cloud-sync-1.0.787256.jar.
After IBM Bluemix DevOps Connect starts, use a web browser to access the application
The default URL is https://localhost:8443. You can change the port when you start the utility. For example, to change the port to
8444, use this command to run the JAR file:
java -Dserver.port=8444 -jar devops-connect.jar.
- On the registration page, if you are prompted to specify a name for the installation, provide a name. This name identifies the data from the installation in other places.
The first time that you access IBM Bluemix DevOps Connect, you are prompted to register.
On the Sign-in to IBM page, enter your IBMid and password, and then click
The IBM Bluemix DevOps Connect dashboard is displayed. The email address of the user that registers the utility is saved in the
sync.registrarproperty in the sync.properties file. Authorized users sign in each time they start the application.
Click Settings and then, in the Allowed Users
text box, enter the email addresses of users who are authorized to access the IBM Bluemix DevOps
Separate addresses with commas. You can use the asterisk (*) wildcard character in the email addresses. For example, the pattern
*@.my_company.comallows any user at
my_company.comwho has an IBMid to access the dashboard. Authorized users can install plug-ins and create integrations. The IBMid of the person who registered IBM Bluemix DevOps Connect is automatically authorized. The email addresses are saved in the
sync.userproperty in the sync.properties file.
To run IBM Bluemix DevOps Connect as a service on Linux, create a symlink from the IBM Bluemix
DevOps Connect jar file to the init.d program. For example:
$ sudo ln -s /var/myapp/cloud-sync-build_number.jar /etc/init.d/myapp. After you configure the application, you can use the standard service commands to manage IBM Bluemix DevOps Connect:
sync.IDproperty in the sync.properties file. The token that it receives from the IBM Cloud Service is saved in the
sync.tokenproperty. The token and ID identify the IBM Bluemix DevOps Connect instance.
You can use values in the /home/my_directory/.ibm/cloud-sync/sync.properties file to manage various aspects of IBM Bluemix DevOps Connect. This table describes the available properties.
||Directory where the devops-connect.jar file is located.|
||Unique identifier that is used to authenticate IBM Bluemix DevOps Connect to the IBM Bluemix services. This property should not be modified.|
||Optional name for the IBM Bluemix DevOps Connect instance. The name property can be used by IBM Delivery Insights and other IBM Bluemix services that integrate with multiple IBM Bluemix DevOps Connect instances.|
||Unique identifier that is generated by IBM Bluemix services and used to authenticate IBM Bluemix DevOps Connect. This property should not be modified.|
||IBMid of the user who registered IBM Bluemix DevOps Connect. This property should not be modified.|
||Comma-delineated list of users who are authorized to use the IBM Bluemix DevOps Connect dashboard. This property should not be directly modified. Use the dashboard Settings tab to manage authorized users.|
||IBM Bluemix DevOps Connect port number. If you set this property, you do not have to use the command line parameter when you start the application.|
||Proxy host URL. If you use a proxy, set this property and the
||Proxy port number.|