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

This section lists the prerequisites and steps for applying 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

Ensure that you have:

  • Read and Write permissions on all subfolders and files of .../AdeptiaSuite-<Version>. 
  • Stopped Kernel and WebRunner. 

Steps to apply the patch


 For Windows
  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 directory where you have extracted the zip file.

  5. Run the following command to apply the patch:

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

    For example:

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

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

  6. Restart Kernel and WebRunner.
 For Linux
  1. Open Terminal.
  2. Download the latest patch from the provided URL.
  3. Extract the downloaded zip file in a folder.
  4. Go to the directory where you have extracted the zip file.

  5. Run the following command to apply the patch:

    ./Apply-Patch.sh <Path where Adeptia Suite is installed till Adeptia Server folder> 

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

  6. Restart Kernel and WebRunner.

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.


Next Steps

Post Deployment Steps

Verifying Patch

See also

Recovering Patch

  • No labels