This section covers the steps that you need to follow to enable Versioning in Adeptia Connect.

Pre-Requisites
You must login as Admin user to change the system properties.

Steps to configure Adeptia Connect for Versioning

Click Configure > Developer Studio.
Click Proceed and you will be redirected to Adeptia Suite home page.
On the Adeptia Suite home page, click Administer tab.
Go to Setup menu and select the Application Settings option.
Click the Update System Properties option.
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.

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

Ensure that Repository URL is changed accordingly in case you are updating the Project URL for seamless operation of Version Control System.

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 the Save button to save the new values.
Reload the settings and restart the services.

Browser not supported