This section lists the prerequisites and explains how to apply the patch on Windows-based and Linux-based operating systems.
...
Expand |
---|
title | Applying patch on v6.9.7 |
---|
|
Expand |
---|
| - Download the latest patch from the provided URL.
- Extract the downloaded zip file in a folder.
- Open the Command Prompt.
- Go to the folder where you have extracted the zip file.
- Run the following command to apply the patch:
Apply-Patch.bat "<Path where Adeptia Suite is installed till AdeptiaServer 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. Start Kernel and WebRunner.
|
Expand |
---|
| - Open the Terminal.
- Download the latest patch from the provided URL.
- Extract the downloaded zip file in a directory.
- Go to the directory where you have extracted the zip file.
Run the following command to apply the patch: ./Apply-Patch.sh <Path where Adeptia Suite is installed till Adeptia Server folder> For example: ./Apply-Patch.sh /mnt/AdeptiaSuite-x.x/AdeptiaServer Once the patch is applied, a confirmation message will be displayed. - Start Kernel and WebRunner.
|
Info |
---|
- Patch application may take some time, in case there are a large number of records in the backend and log database.
- A PatchApplicationLog<Date>.log file is also 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.
- After applying the patch, clear the browser history before login to Adeptia Suite.
- Clear the Java cache and the previous certificate of Adeptia from Java Control Panel. Click here to know how to clear Java cache and delete Adeptia certificates.
- If any error occurs during patch deployment then the patch will be recovered automatically.
|
After applying this patch, refer to post patch deployment section for manual changes. |
Expand |
---|
title | Applying patch on v6.9.8 |
---|
|
Info |
---|
Prerequisites for MySQL database
This section is applicable only when MySQL is being used as a backend or log database. In case you are using MS SQL or Oracle as backend or log database then you can skip this step. If you are using MySQL as a backend/log database and applying the latest patch 'AdeptiaSuite_6_9_8_04_30April2020.zip' on the tags mentioned below then follow the steps below before applying the patch. Release_AS_6_9_7_17Oct2019Release_AS_6_9_7_01_05Dec2019- Release_AS_6_9_8_06March2020
Steps to remove the manual changes from server-configure.properties file: Info |
---|
You need to perform the below steps for the backend and log database. If you have configured a separate database for archiving the logs then you need to perform the same steps for the Archival log database. |
- Go to .../<AdeptiaInstallFolder>/AdeptiaServer/ServerKernel/etc location.
- Open server-configure.properties file.
- Go to Database Configuration section and do the following changes:
- Update the property 'abpm.jdo.driver' value as com.mysql.jdbc.Driver.
- Update the property 'abpm.jdo.url' by removing the value ?useSSL=false&serverTimezone=<time zone> at the end of the URL.
- Go to Database Appender section and do the following changes:
Save the file.
Steps to remove the manual changes from qaurtz.properties file: - Go to .../<AdeptiaInstallFolder>/AdeptiaServer/ServerKernel/etc location.
- Open quartz.properties file.
- Go to Configure Datasources section and do the following changes:
Save the file.
|
Expand |
---|
| - Download the latest patch from the provided URL.
- Extract the downloaded zip file in a folder.
- Open the Command Prompt.
- Go to the folder where you have extracted the zip file.
- Run the following command to apply the patch:
Apply-Patch.bat "<Path where Adeptia Suite is installed till AdeptiaServer 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. Start Kernel and WebRunner.
|
Expand |
---|
| - Open the Terminal.
- Download the latest patch from the provided URL.
- Extract the downloaded zip file in a directory.
- Go to the directory where you have extracted the zip file.
Run the following command to apply the patch: ./Apply-Patch.sh <Path where Adeptia Suite is installed till Adeptia Server folder> For example: ./Apply-Patch.sh /mnt/AdeptiaSuite-x.x/AdeptiaServer Once the patch is applied, a confirmation message will be displayed. - Start Kernel and WebRunner.
|
Info |
---|
- Patch application may take some time, in case there are a large number of records in the backend and log database.
- A PatchApplicationLog<Date>.log file is also 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.
- After applying the patch, clear the browser history before login to Adeptia Suite.
- Clear the Java cache and the previous certificate of Adeptia from Java Control Panel. Click here to know how to clear Java cache and delete Adeptia certificates.
- If any error occurs during patch deployment then the patch will be recovered automatically.
|
After applying this patch, refer to post patch deployment section for manual changes.
|
Anchor |
---|
| Patch Deployment Steps |
---|
| Patch Deployment Steps |
---|
|
Post Patch Deployment StepsChanges in jetty.xml File
...
Once the post patch deployment steps are done, start the services, i.e. Kernel and WebRunner.
Info |
---|
If you are using Database/Advanced Database Event, Source/Target activity with MySQL Database Server using an older version of MySQL JDBC jars then it is recommended to upgrade the jars to mitigate the vulnerability associated with the older jars. Click here to download the recommended version of MySQL jars (mysql-connector-java-8.0.18.jar) and follow the steps to upgrade it.
|
Updating database info for CDATA drivers
...
In case, you are using SQL as a backend database then it is recommended to change the jar. Click here to download the compatible version of SQL jar (mssql-jdbc-6.1.4.jre8-preview.jar) and follow the steps to update it.