Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Current »

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

Pre-Requisites

You must login as Admin user to change the Adeptia Suite system properties.
 

Steps to configure Adeptia Suite for Versioning 

Follow these steps to configure SVN in Adeptia Suite for Versioning.

 SVN
  1. On the Adeptia Suite home page, click on the Administer tab.
  2. Go to Setup menu. This action will display you the menu options of the Setup menu.

  3. Select the Application Settings option.

     

  4. Click the Update System Properties option.

     

  5. Expand the Systems node.

     

  6. To enable versioning in the Adeptia Suite, 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 SVN and enable versioning in the Adeptia Suite, you need to enter values for all the Version Control properties.

  7. Set the value of the abpm.versionControl.enable property to true.
  8. Set the value of the abpm.versionControl.client property to SVN.
  9. You can set the value of the abpm.versionControl.repository.access.protocol property to either SVN, or HTTP, or HTTPS.

  10. In the abpm.versionControl.repository.url property, enter the IP address of the SVN server. This action enables you to connect the SVN server with the Adeptia Suite by using the protocol mentioned in the previous step.

    You need to define the hostname or IP address of SVN server as per the syntax below:
     <access protocol>://<hostname >:<port> 
    where
     <access protocol> is the protocol that you will select to access the SVN server. You access SVN server by using the following protocol: SVN, HTTP, and HTTPS.
     <hostname> is the IP address of the SVN server.
     <port> is the port at which SVN server is running. By default, the SVN server uses the 3690 port.
     
    For example, if your SVN Server is on a host with 192.168.1.1 IP address and is using 3690 port then the URL will be:
     svn://192.168.1.1:3690/ 
     
    In case you have installed your SVN server on a Linux-based OS then you need to provide the absolute path of the SVN server according to the syntax:
     <access protocol>://<hostname>:<SVN port><Absolute Path of the Repository including the Repository Name> 
    When you install SVN server, you are asked to create a repository. In this property you need to provide the path where you have created the repository.
    For example, if the SVN Server is installed on a host with IP address 192.168.1.1 using the port 3690 and the path of the SVN Repository is /Adeptia/Version_Control_Repository, then you need to define then the URL will be:
     
     svn://192.168.1.1:3690/Adeptia/Version_Control_Repository

  11. In the abpm.versionControl.username property, enter the username that you want to use to access host repository.
  12. In the abpm.versionControl.password property, enter the password of the username that you have mentioned in the previous steps.

  13. In the abpm.versionControl.projectPath property, enter the path where you want to create the local copy of the SVN project,. This path must exist on the machine, where you have installed the Adeptia Suite.

    When you Check-In the activity of the Adeptia Suite for the first time, the Adeptia Suite 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 Suite also creates a project with the same name as in the SVN.
     
    If you have installed the Adeptia Suite 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 SVN 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/




  14. Enter the Keystore path for client authentication in the abpm.versionControl.keystore.path property.

  15. 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 protocol on an SVN server which is client authenticated.

  16. Click the Save button to save the new values.
  17. Reload the settings and restart the services.

Follow these steps to configure Git in Adeptia Suite for Versioning.

 Git
  1. On the Adeptia Suite home page, click on the Administer tab.
  2. Go to Setup menu. This action will display you the menu options of the Setup menu.

  3. Select the Application Settings option.

     

  4. Click the Update System Properties option.

     

  5. Expand the Systems node.

     

  6. To enable versioning in the Adeptia Suite, 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.

  7. Set the value of the abpm.versionControl.enable property to true.
  8. Set the value of the abpm.versionControl.client property to GIT.
  9. You can set the value of the abpm.versionControl.repository.access.protocol property to HTTPS or HTTP.

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

  11. In the abpm.versionControl.username property, enter the username that you want to use to access host repository.
  12. In the abpm.versionControl.password property, enter the password of the username that you have mentioned in the previous steps.

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

    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 Suite for the first time, the Adeptia Suite 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 Suite also creates a project with the same name as in the SVN.
     
    If you have installed the Adeptia Suite 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 SVN 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/




  14. Enter the Keystore path for client authentication in the abpm.versionControl.keystore.path property.

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

  16. Click the Save button to save the new values.
  17. Reload the settings and restart the services.

 

  • No labels