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 5 Next »

This section lists the prerequisites and steps for applying and verifying this patch.

Though every release of Adeptia comes with seamless upgrades and bug-free patches, for customer's complex use cases, we recommend applying the patch in a non-production environment first followed by testing. After the use cases run successfully without any errors or warnings, you can apply the patch in the production environment. 

Prerequisites

  • Read and Write permissions on all sub-folders and files of .../AdeptiaConnect-<Version>. 
  • Take backup of launcher.properties file from …<ConnectPoratlInstallFolder>\conf location. This backup file will help you replicate the manual changes in case you have done earlier in the launcher.properties file before applying this patch.  
  • Take backup of apps.properties file from …<ConnectPortalInstallFolder>\resources_config location. This backup file will help you replicate the manual changes in case you have done earlier in the apps.properties file before applying this patch.  
  • Connect Server services are running.
  • Connect Portal service is stopped.
  • Ensure that you have followed the Prerequisites' instructions given on the Upgrade page.

Applying the patch

 For Windows
  1. Extract the Adeptia Connect zip file from the downloaded folder.
  2. Open the Command Prompt.
  3. Go to the folder where you have extracted the zip file.
  4. Run the following command to apply the patch:
    Apply-Patch.bat -portal “<Path where Connect Portal is installed till ConnectPortal folder>” 

    For example:

    Apply-Patch.bat -portal  "C:/Program Files/AdeptiaConnect-x.x/ConnectPortal"
     
    Once the patch is applied, a confirmation message will be displayed. 
 For Linux
  1. Open the Terminal.
  2. Extract the downloaded zip file in a directory.
  3. Go to the directory where you have extracted the zip file.

  4. Run the following command to apply the patch:

    ./Apply-Patch.sh -portal <Path where Connect Portal is installed till ConnectPortal folder> 

    For example:

    ./Apply-Patch.sh -portal /mnt/AdeptiaConnect-x.x/ConnectPortal

    Once the patch is applied, a confirmation message will be displayed.

After applying this patch, refer to post patch deployment section for manual changes.

Post patch deployment steps

In this release, some manual changes are required in Connect Portal.

Changes in launcher.properties file

  1. Go to …<ConnectPoratlInstallFolder>\conf location.
  2. Open launcher.properties file.
  3. Do the same manual changes in the file that you have done in your previous launcher.properties file (that you had saved as a backup). For example, you may need to update the JVM settings and Truststore location as they are there in the backup file.
  4. Save the file.

Changes in apps.properties file

  1. Go to …<ConnectPortalInstallFolder>\resources_config location.

  2. Open apps.properties file.

  3. Search for Dropbox app section and replace the existing two properties with the updated code given below:

    Dropbox
    dropbox.refreshToken=https://api.dropboxapi.com/oauth2/token
dropbox.authorizationValueMap=response_type$code,token_access_type$offline

  4. Add the following code block for Zoho CRM next to the QuickBooks section:

    Zoho CRM
    #Zoho Crm
zohocrm.appKey=
zohocrm.appKeySecret=
zohocrm.oauthVersion = 2.0
zohocrm.oauth20.accessToken =  https://accounts.zoho.com/oauth/v2/token
zohocrm.oauth20.authorize = https://accounts.zoho.com/oauth/v2/auth
zohocrm.refreshToken =https://accounts.zoho.com/oauth/v2/token
zohocrm.authorizationValueMap=response_type$code,access_type$offline
zohocrm.refreshTokenValueMap=N/A
zohocrm.accessTokenValueMap=N/A
zohocrm.scope = ZohoCRM.settings.modules.ALL,ZohoCRM.settings.ALL,ZohoCRM.modules.ALL,ZohoCRM.users.ALL

  5. Search for Sage One app section and replace the existing code block with the one given below:

    Sage One
    sageone.oauth20.accessToken=https://oauth.accounting.sage.com/token
sageone.oauth20.authorize=https://www.sageone.com/oauth2/auth/central
sageone.refreshTokenValueMap=N/A

  6. Search for FreshBooks app section and replace the existing code block with the one given below:

    FreshBooks
    freshbooks.oauthVersion=2.0
freshbooks.oauth20.requestToken=https://api.freshbooks.com/auth/oauth/token
freshbooks.oauth20.authorize=https://my.freshbooks.com/service/auth/oauth/authorize
freshbooks.oauth20.accessToken=https://api.freshbooks.com/auth/oauth/token
freshbooks.refreshToken = https://api.freshbooks.com/auth/oauth/token


  7. Save the file.
  8. Restart the Connect Portal.

Verifying Connect Portal patch

To verify if the Connect Portal has been deployed successfully, login to the portal and check the build tag of the Connect Portal.

Follow the steps below to check the build tag:

  1. Click Help > About.
  2. On the About screen, check the Connect Portal tag. 
    If the build tag matches the tag of the Connect Portal, it indicates that the Connect Portal patch is deployed successfully.

Additionally, to verify if the user interface of the Connect Server is working as expected, follow the steps below:

  • Click Configure > Developer Studio > Proceed.
    If you are able to interact with the Connect Server interface, it indicates that the Connect Server is updated.
  • No labels