Applying Patch

This section explains how to apply the patch.

Before applying the patch, it is recommended to take the backup of the database that is used as backend by Adeptia Suite. 

In case, the embedded database is used as backend, follow the below steps to take the backup:

1. Stop Kernel and WebRunner.
2. Go to ./AdeptiaServer/ServerKernel folder.
3. Copy the embeddedDB folder and keep it into a separate folder.

In case any other database is used as backend database, you need to follow the backup instruction given by that Database Server. To know, which database is used as backend database, refer to Appendix A: Identify Backend Database.

1. Make sure that you have Read and Write permission on all subfolders and files of ../AdeptiaSuite-<Version>
2. Before applying the patch, make sure that any process flow should not be in Running or Queued state.
3. Kernel and WebRunner must be stopped before you start applying the patch.

Following are the high level steps to apply the patch.

1. Download the latest patch.
2. Extract the downloaded zip file.
3. Open Command Prompt and change to the folder where you have extracted the patch zip.
4. Depending on the operating system you are using, run one of the following commands:
   

   For Windows 
   Apply-Patch.bat <Path where Adeptia Suite is installed.> 

   Example: 
   Apply-Patch.bat "C:\Program Files\AdeptiaSuite\AdeptiaSuite-<version>\AdeptiaServer" 

   For Linux 
   ./Apply-Patch.sh <Path where Adeptia Suite is installed.> 

    

5. This will apply the patch. This will also apply the B2Bi accelerator, in case, you have applied the patch with updated B2Bi accelerator.
   
   

   Patch application may take more time when there are large number of records in the backend and log databases.
   
   A PatchApplicationLog<Date>.log file is also created inside the logs folder in the same folder from where you have applied the patch. This file contains the log file generated during patch application and file can be used to troubleshoot any issue related to the patch application.
6. Restart the Kernel and Web Runner.