This feature enables the user to checkout, pull, commit and push the Applications, Group Processes and/or API Projects to the version control repository.

Version Control Integration for Event Processes

1. After starting the server, open eStudio and login to the Enterprise Server.
2. Expand the EnterpriseServer node and right-click the Event Process Repository node.
3. In the Version Control option, click Configuration.
   
   
   
   

4. In the Version Control panel, provide the version control details.

   Icon

   Since Fiorano provides GIT integration, Class Name will be fiorano.esb.util.GitUtil by default. But a customized Class Name may be used to integrate with a preferred version control tool different than the default one.

   
   
   

5. Click Finish to save the version control configuration details.
   
   
6. After the details are saved, select the Commit option to push the Event Processes to the remote repository (Event Process Repository > Version Control).
   Provide the commit message in the Commit Applications popup.
   
   
   
   
7. Similarly, to perform the Checkout operation, select the Checkout option (Event Process Repository > Version Control > Checkout ). 

8. A warning pops up prompting to overwrite event processes.

   Icon

   Checking out from the version control leads to loss of all Event Processes that are created locally. Click No to take a backup and click Yes after ensuring that the backup has been taken.

   
   
   

9. For pulling the Event Processes from the remote repository, select the Update option.
   A similar warning will popup prompting to backup the Event Processes.
   
   
   
   
10. Click Yes to sync the local repository with the remote.

Version Control Integration for Extended Service

After starting the server,

1. Open eStudio and login to the Enterprise Server.
2. Expand the EnterpriseServer node and right-click the Extended Service Repository node.
3. In the Version Control option, click Configuration.
   
   
   
   

4. In the Version Control panel, provide the version control details.

   Icon

   Since Fiorano provides GIT integration, Class Name will be fiorano.esb.util.GitUtil by default. But a customized Class Name may be used to integrate with a preferred version Control tool different from the default one.

   
   
   

5. Click Finish to save the version control configuration details.
6. After the details are saved, select the Commit option to push the Extended Services to the remote repository (Extended Service Repository > Version Control).
   Provide the commit message in the popup.
   
   
   
7. Similarly, to perform the Checkout operation, select the Checkout option (Extended Service Repository > Version Control > Checkout). 

8. A warning pops up prompting to overwrite extended services.

   Icon

   Checking out from the version control leads to loss of all extended services that are created locally. Click No to take a backup and click Yes after ensuring that the backup has been taken.

   
   
   

9. For pulling the extended services from the remote repository, select the Update option.
10. A warning pops up prompting to backup the Extended Services.
    
    
    
    
11. Select Yes to sync the local repository with the remote.

Version Control Integration for API Projects

1. After starting the API Management server, login to the API Management Dashboard.
2. Click the username (admin) drop-down present at the upper-right part of the Dashboard and click Preferences. Fig 11 
   
   
   
   
3. Click the Version control tab.
   
   Fig 12
   
   

4. Provide the version control details and click Save.

   Icon

   Since Fiorano provides GIT integration, Class Name will be fiorano.esb.util.GitUtil by default. But a customized Class Name may be used to integrate with a preferred version Control tool different from the default one.

5. To commit the API Projects to the remote repository, navigate to the APIProjects tab and select the Version Control icon.
   
   

Viewing the logs

The logs can be viewed inside the jetty.log file present in <FioranoHome>/runtimedata/<serverType>/ <profile>/<mode>/run/logs.

Points to Notes

• Fiorano provides integration with GIT where the user can perform Push, Pull, and Checkout operations for Applications, Extended Services, and API Projects.
• Custom classes can be used to integrate a different version Control tool.
• Ensure that a backup of the local repository is taken before checking out or pulling from the version control as these operations might lead to loss of any local change in Applications, Extended Services or API Projects repository.
• While trying to sync the local repository with the remote one for the first time separately for Applications, Extended Services and API Projects respectively, the user should select the Update option rather than Checkout. This Update is a git pull call which will first execute the git init method, create the head and point it to the correct location.
• Once remote and local repo are synched, Update option, which is git pull, will not perform any action until the remote repo gets modified again.
• If any change is made to the local repository and the user wants to revert back to the previous change, the checkout operation needs to be performed.
• If HA servers are used, a .git directory will get created on the active server. In order to sync this .git for the first time with the passive server, restart the passive server.