Versions Compared

Old Version 2

changes.mady.by.user Akash Kumar Jaiswal

Saved on

compared with

New Version 3

changes.mady.by.user Akash Kumar Jaiswal

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This section lists the prerequisites and explains how to apply the patch on Windows-based and Linux-based operating systems.

Prerequisites

Before applying the patch, ensure that you have:

...

    • 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
    titleNote

    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

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 folder 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 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.

  6. Start Kernel and WebRunner. 

...

  1. Open the Terminal.
  2. Download the latest patch from the provided URL.
  3. Extract the downloaded zip file in a directory.
  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> 

    For example:

    ./Apply-Patch.sh /mnt/AdeptiaSuite-x.x/AdeptiaServer

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

  6. 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 Steps

...

Changes in jetty.xml File

...

Changes in web.xml File

  1. Go to .../<AdeptiaInstallFolder>/AdeptiaServer/ServerKernel/web/WEB-INF location.
  2. Take backup of web.xml file from the above-mentioned location.
  3. Go to the downloaded Adeptia Suite zip folder and copy the web.xml file.
  4. Replace the existing file with the copied file at the following location: .../<AdeptiaInstallFolder>/AdeptiaServer/ServerKernel/web/WEB-INF.
  5. Open web.xml file.
  6. 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).
  7. Save the file.

Changes in server-configure.properties File

In case you are using MySQL as Backend and Log database then do the following manual changes. These changes are required because JDBC driver has been updated for this release. 

...

Update the property 'abpm.jdo.url' by appending the value ?useSSL=false&amp;serverTimezone=<time zone> at the end of the URL.

...

Update the property 'log4j.appender.jdbc.url' by appending the value ?useSSL=false&amp;serverTimezone=<time zone> at the end of the URL.

...

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. 

...

Update the property 'org.quartz.dataSource.aBPM.URL' by appending the value ?useSSL=false&serverTimezone=<time zone> at the end of the URL.

...

Restoring user-defined jars

With the new patch the launcher.properties file is updated and no longer has the list of jars in it. If you have defined your own jars in previous version of launcher.properties file, you need to move them to the ext folder to load them at the time of Kernel and WebRunner start up. Follow the steps below:

  1. Go to .../<AdeptiaInstallFolder>/AdeptiaServer/ServerKernel/etc location.
  2. Open launcher-bak.properties file.
  3. Identify your jars and move those jars from their current location to the following location: .../<AdeptiaInstallFolder>/AdeptiaServer/ServerKernel/ext.

...

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:

...

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.

...