Configuring Connect for Version Control using Git
- Akash Kumar Jaiswal (Unlicensed)
This section covers the steps that you need to follow to enable versioning in Adeptia Connect.
This page contains the following information:
Prerequisites
You must login as Admin user to change the system properties.
Installing Git Version Control system
To download installer, refer to the website https://git-scm.com/downloads.
Download Git from any of the distributor of your choice. Run the downloaded Git Installer and complete the installation by referring to https://git-scm.com/book/en/v2/Getting-Started-Installing-Git.
Configuring Version Control using Git
Click Configure > Developer Studio > Proceed.
On the Connect Server home page, click Administer tab.
Go to Setup menu and select the Application Settings.
Click the Update System Properties.
Expand the Systems node.
To enable versioning, expand the Version Control sub-node. This action will display you the properties to be set for Version Control.
Set the value of the abpm.versionControl.enable property to true.
Set the value of the abpm.versionControl.client property to GIT.
You can set the value of the abpm.versionControl.repository.access.protocol property to HTTPS or HTTP.
In the abpm.versionControl.repository.url property, enter the IP address of the Bitbucket server. This action enables you to connect the Git server with the Adeptia Connect by using the protocol mentioned in the previous step.
In the abpm.versionControl.username property, enter the username that you want to use to access host repository.
In the abpm.versionControl.password property, enter the password of the username that you have mentioned in the previous steps.
In the abpm.versionControl.projectPath property, enter the path where you want to create the local copy of the Git project. This path must exist on the machine, where you have installed the Adeptia Connect.
Enter the Keystore path for client authentication in the abpm.versionControl.keystore.path property.
Enter the password of the Keystore for client authentication in the abpm.versionControl.keystore.password property.
You need to enter the values in the abpm.versionControl.keystore.path and abpm.versionControl.keystore.password properties only when you use a HTTPS or HTTP protocol on an Bitbucket server which is client authenticated.
Click Save.
Reload the settings and restart the services.
Handling certificate errors
While connecting to Git, you may sometime encounter errors related to certificates that can prove to be bottlenecks in establishing a successful connection. You can handle such errors by following the instructions in the same order as given below:
Identifying the Truststore and its location
The first step towards resolving the errors is to identify the Truststore and its location in your application. Follow the steps below to do this:
Log in to Adeptia Connect.
Click Configure > Developer Studio >Proceed.
On the Connect Server home page, click Administer tab.
Go to Setup menu and select the Application Settings.
Click the Update System Properties.
Expand the Services > SSL Configuration node.
In the javax.net.ssl.trustStore property, you can get the truststore and its location.
If you already have the certificates available with you, skip the next step (export option) and go directly to the steps for importing the certificates.
Exporting the correct certificates
It is recommended to export the key using DER encoded binary format X.509 (.CER). The following are the steps to export the public key in Google Chrome browser. Follow the steps below to export the correct certificates:
Open the Version Control Repository URL in Google Chrome browser.
Click > More tools > Developer tools.
Click Security tab.
Click View Certificate.
On the Certificate window, under the Details tab, click Copy to File.
Click Next to start exporting the certificates.
Choose DER encoded binary X.509 (.CER) and click Next.
Specify the location to save the exported file and click Next.
Click Finish to export.
A dialog box appears confirming the export process have been completed successfully.Click OK to exit from the wizard.
Importing the certificates into Truststore
Open Command Prompt.
Go to …<ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\etc\truststore location.
Run the following Keytool command to import a certificate,
keytool -import -trustcacerts -file <Path_of_SSL_Certificate> -alias <alias_name> -keystore <Path of Truststore file> -storepass <password>
where,
<Path_of_SSL_Certificate> is the path of SSL certificate.
<Path of Truststore file> is the path of Connect Server Truststore.
For example, keytool -import -trustcacerts -file "C:/connect-adeptia-com.cer" -alias adeptia -keystore " C:\Program Files\AdeptiaConnect\AdeptiaConnect-XX\ConnectServer\AdeptiaServer\ServerKernel\etc\truststore\cacerts" -storepass changeit
Once you have finished importing the certificates, restart the Connect Server.