This section lists the prerequisites and explains how to apply the patch on Windows-based and Linux-based operating systems.
...
- Read and Write permissions on all sub-folders and files of ../AdeptiaSuite-<Version>.
- Stopped Kernel and Webrunner.
- Stopped process flows that are in Running or Queued state.
- Deactivated any running Mail Event.Take backup of launcher.properties file from .../<AdeptiaInstallFolder>/AdeptiaServer/ServerKernel/ext location. This file will help you to update the launcher.properties file for manual changes, if you have done any.
- Take backup of jetty.xml file from .../<AdeptiaInstallFolder>/AdeptiaServer/ServerKernel/etc/jetty location. This file will help you to update the jetty.xml file for manual changes, if you have done any.
- Taken the backup of a backend database.
- In case, the embedded database is used as the backend database, follow the below steps to take the backup:
...
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:
- Go to .../<AdeptiaInstallFolder>/AdeptiaServer/ServerKernel/etc location.
- Open launcher-bak.properties file that you had saved as a backup. file.
- Identify your jars and move those jars from their current location to the following location: .../<AdeptiaInstallFolder>/AdeptiaServer/ServerKernel/ext.
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.
|