This section covers the steps that you need to follow to enable versioning in Adeptia Connect.
...
- Click Accounts > Settings.
- Expand Microservice Settings, and then select WebRunner in the left panel.
- Expand the property category, Version Control.
Double-click the corresponding value fields for the following properties to change their values.
Info The default value of the abpm.versionControl.enable property is false. To configure Git and enable versioning in the Adeptia Connect, you need to enter values for all the Version Control properties. - 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.
Info You need to define the hostname or IP address of Bitbucket server as per the syntax below:
<access protocol>://<hostname >:<port>
where
<access protocol> is the protocol that you will select to access the Bitbucket server. You access Bitbucket server by using the HTTPS or HTTP protocol.
<hostname> is the IP address of the Bitbucket server.
<port> is the port at which Bitbucket server is running. By default, the Bitbucket server uses the 7990 port.To get the Bitbucket Server Repository Link, follow the steps:
- On Bitbucket Repository page, select the Repository.
- Click Clone icon and copy the link.
Enter this link in the abpm.versionControl.repository.url property.- 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.
Info Ensure that Repository URL is changed accordingly in case you are updating the Project URL for seamless operation of Version Control System.
Info When you Check-In the activity of the Adeptia Connect for the first time, the Adeptia Connect creates a local copy of the project on the path that you have specified in the abpm.versionControl.projectPath property.
At the same time the Adeptia Connect also creates a project with the same name as in the Git.
If you have installed the Adeptia Connect on a Windows-based OS then, you can either define the absolute path or the relative path with respect to ServerKernel folder. For example, you can define the absolute path as c:\Adpetia\AdeptiaVersionControl. It means that the local Git project is created within c:\Adeptia\AdeptiaVersionControl folder.
You can also define the relative path like .\AdeptiaVersionControl. In this case, the Adeptia Suite creates the local project within ServerKernel > AdeptiaVersionControl folder.
The default value of the abpm.versionControl.projectPath property is .\AdeptiaVersionControl.
You can provide the path other than the default path in the abpm.versionControl.projectPath property as per your requirement.
If you have installed the Adeptia Suite on a Linux-based OS then you must specify the absolute path for the Local Version Control Project. For example /root/home/ADEPTIA/AdeptiaVersionControl/- 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 Update.
You'll see a message saying 'Properties saved successfully'.
...
You can remove the checked-in version of an activity from version control system by using the Uncheck option for that activity under More menu.
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:
- Identify the Truststore and its location
- Export the correct certificates
- Import the certificates into Truststore
...
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:
...
| Note |
|---|
| 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. |
...
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:
...
Go to …<ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\etc\truststore location.
| Tip |
|---|
| You must ensure that this path is same as what you had identified in the first step. |
...
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.