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

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

Though every release of SecureBridge 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

  • You have Read and Write permissions on all subfolders and files of .../<SecureBridge>.
  • Take backup of AgentContext.xml file from …<ConnectPoratlInstallFolder>\conf location. This backup file will help you to go back to the previous version.
  •  Take backup of hubConfiguration.properties file from …<ConnectPoratlInstallFolder>\conf location. This backup file will help you to go back to the previous version.
  • Services such as Kernel, WebRunner, and AIMap are stopped.

Applying the patch

  1. Download the latest patch from the provided URL.
  2. Extract the downloaded zip file in a folder.
  3. Open the Command Prompt.
  4. Go to the folder where you have extracted the zip file.
  5. Run the following command to apply the patch:

    Apply-Patch.bat “<Path where Adeptia Connect is installed till AdeptiaServer folder>” 

    For example:

    Apply-Patch.bat "C:/Program Files/AdeptiaConnect/AdeptiaConnect-x.x/ConnectServer/AdeptiaServer"

  6. Once the patch is applied, a confirmation message is displayed.

    Note: While applying the patch you may come across following warning messages that you should ignore.

    Warning: Not deploying connect2.0 accelerator because no change list is present.
    Warning: Not deploying EDI accelerator because no change list is present.

  7. Start the services, i.e. Kernel, WebRunner, and AIMap.

After you have applied the patch, PatchApplicationLog_<Date>.log file is created inside the logs folder. The logs folder is available in the same folder from where you have applied the patch. PatchApplicationLog_<Date>.log file contains the logs generated during patch application and can be used to troubleshoot any issue related to the patch application.

Patch application may take some time, in case there are a large number of records in the backend and log database.

The patch will automatically rollback, in case of any error during the deployment.

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

Post patch deployment steps

Changes in AgentContext.xml file 

After deploying the patch, update database configuration in AgentContext.xml file to store heartbeat and other agent operation in the database. To update this file, follow the steps below:

  1. Go to .....
  2. Open AgentContext.xml file.




  4. Save the file.

Changes in hubConfiguration.properties file

Configure email notification property, recipientsEmail, in hubConfiguration.properties file. 

  1. Go to .....
  2. Open hubConfiguration.properties file.

  3. Set the "recipientsEmail" property with the email id of the recipient. 



    You can also update other properties like mailBodyContenType, mailSubject, mailBodyHeader, and mailBodyFooter based on your requirements. 
  4. Save the file.





  • No labels