This section lists the prerequisites and explains how to apply the patch on Windows-based and Linux-based operating systems.
...
- In case, any other database is used as the backend database, you need to follow the backup instructions given by that Database Server. To know, which database is used as the back end database, refer to Appendix A: Identify Backend Database.
In case you have updated export.xml (during Migration of objects), and you wish to keep changes after applying the patch, keep a backup of this file from the path: ...\<AdeptiaInstallFolder>\AdeptiaServer\ServerKernel\MigrationUtility. After the patch application is complete, merge the changes done in the backed up file with the new file (export.xml) generated.
Info title Note Do not replace the backup of export.xml to the newly created export.xml. Only merge the changes from the old file to the new one.
Applying the patch
Expand | |||||
---|---|---|---|---|---|
| |||||
|
...
After applying this patch, refer to post patch deployment section for manual changes. |
Expand | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||
|
Anchor | ||||
---|---|---|---|---|
|
Changes in jetty.xml File
...
- Go to .../<AdeptiaInstallFolder>/AdeptiaServer/ServerKernel/web/WEB-INF location.
- Take backup of web.xml file from the above-mentioned location.
- Go to the downloaded Adeptia Suite zip folder and copy the renamed the web.xml file.
- Replace the existing file with the copied file at the following location: .../<AdeptiaInstallFolder>/AdeptiaServer/ServerKernel/web/WEB-INF.
- Open web.xml file.
- Do the same manual changes in the file that you have done in your previous web.xml file (that you had saved as a backup).
- Save the file.
...
- Go to .../<AdeptiaInstallFolder>/AdeptiaServer/ServerKernel/etc location.
- Take backup of server-configure.properties file from the above-mentioned 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.cj.jdbc.Driver.
Update the property 'abpm.jdo.url' by appending the value ?useSSL=false&serverTimezone=<time zone> at the end of the URL.
Info - Append the value ?useSSL=false at the end of the URL. However, this argument is not required if SSL is configured on your MySQL database server.
- Append the value &serverTimezone=<time zone> at the end of the URL. For example, &serverTimezone=UTC+3:00. This argument is required only when an error related to the time zone is displayed while starting the Connect Kernel.
Here, <time zone> is the time zone of your MySQL server.
Save the file.
- Go to Database Appender section and do the following changes:
- Update the property 'log4j.appender.jdbc.dbclass' value as com.mysql.cj.jdbc.Driver.
Update the property 'abpmlog4j.appender.jdojdbc.url' by appending the value ?useSSL=false&serverTimezone=<time zone> at the end of the URL.
Info - Append the value ?useSSL=false at the end of the URL. However, this argument is not required if SSL is configured on your MySQL database server.
- Append the value &serverTimezone=<time zone> at the end of the URL. For example, &serverTimezone=UTC+3:00. This argument is required only when an error related to the time zone is displayed while starting the Connect Kernel.
Here, <time zone> is the time zone of your MySQL server.
Save the file.
Changes in quartz.properties File
In case you are using MySQL as Backend and Log database then do these manual changes.
Info |
---|
This is required as MySQL JDBC jars have been upgraded to the latest version. |
- Go to .../<AdeptiaInstallFolder>/AdeptiaServer/ServerKernel/etc location.
- Take backup of quartz.properties file from the above-mentioned location.
- Open quartz.properties file.
- Go to Configure Datasources section and do the following changes:
- Update the property 'org.quartz.dataSource.aBPM.driver' value as com.mysql.cj.jdbc.Driver.
Update the property 'abpm.jdo.urlorg.quartz.dataSource.aBPM.URL' by appending the value ?useSSL=false&serverTimezone=<time zone> at the end of the URL.
Info - Append the value ?useSSL=false at the end of the URL. However, this argument is not required if SSL is configured on your MySQL database server.
- Append the value &serverTimezone=<time zone> at the end of the URL. For example, &serverTimezone=UTC+3:00. This argument is required only when an error related to time zone is displayed while starting the Connect Kernel.
Here, <time zone> is the time zone of your MySQL server.
- Save the file.
Restoring user-defined jars
...
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.
|
Updating database info for CDATA drivers
If you are using any CDATA JDBC driver to connect with salesforce application then follow the steps below to update the database info:
- Login into Adeptia application.
- Edit the database info which is using CDATA driver.
- Save it.
Info |
---|
This will update the license of upgraded CDATA driver into database info activity. |
Updating SQL jar
This section is applicable if you are using the Rich Form v7.3.2 in Adeptia Suite.
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.