Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 33 Current »

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:

  • 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 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:
      1. Stop Kernel and WebRunner.
      2. Go to .../<AdeptiaInstallFolder>/AdeptiaServer/ServerKernel folder.
      3. Copy the embeddedDB folder and keep it into a separate folder.
    • 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.

    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


 Applying patch on v6.9.7


 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. 

 For Linux

 

  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.


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

 Applying patch on v6.9.8


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_8_06March2020

Steps to remove the manual changes from server-configure.properties file:

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.

  1. Go to .../<AdeptiaInstallFolder>/AdeptiaServer/ServerKernel/etc location.
  2. Open server-configure.properties file.
  3. 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.
  4. Go to Database Appender section and do the following changes:
    • Update the property 'log4j.appender.jdbc.dbclass' value as com.mysql.jdbc.Driver.

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

  5. Save the file.

Steps to remove the manual changes from qaurtz.properties file:

  1. Go to .../<AdeptiaInstallFolder>/AdeptiaServer/ServerKernel/etc location.
  2. Open quartz.properties file.
  3. Go to Configure Datasources section and do the following changes:
    • Update the property 'org.quartz.dataSource.aBPM.driver' value as com.mysql.jdbc.Driver.

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

  4. Save the file.

 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. 

 For Linux
  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.


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

Post Patch Deployment Steps

Changes in jetty.xml File

  1. Go to .../<AdeptiaInstallFolder>/AdeptiaServer/ServerKernel/etc/jetty location.
  2. Open jetty.xml file.
  3. Update the sslContextFactory bean class value by adding $Server at the end.
  4. Add one Array type item as <Item>TLSv1.1</Item> to exclude the TLSv1.1 protocol.



  5. Save the 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. 

  1. Go to .../<AdeptiaInstallFolder>/AdeptiaServer/ServerKernel/etc location.
  2. Take backup of server-configure.properties file from the above-mentioned location.
  3. Open server-configure.properties file.
  4. Go to Database Configuration section and do the following changes:
    1. Update the property 'abpm.jdo.driver' value as com.mysql.cj.jdbc.Driver.

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

      • 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 &amp;serverTimezone=<time zone> at the end of the URL. For example, &amp;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.


    3. Save the file.

  5. Go to Database Appender section and do the following changes:
    1. Update the property 'log4j.appender.jdbc.dbclass' value as com.mysql.cj.jdbc.Driver.

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

      • 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 &amp;serverTimezone=<time zone> at the end of the URL. For example, &amp;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.


    3. Save the file.

Changes in quartz.properties File

In case you are using MySQL as Backend and Log database then do these manual changes. 

This is required as MySQL JDBC jars have been upgraded to the latest version. 
  1. Go to .../<AdeptiaInstallFolder>/AdeptiaServer/ServerKernel/etc location.
  2. Take backup of quartz.properties file from the above-mentioned location.
  3. Open quartz.properties file.
  4. Go to Configure Datasources section and do the following changes:
    1. Update the property 'org.quartz.dataSource.aBPM.driver' value as com.mysql.cj.jdbc.Driver.

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

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


  5. Save the file.

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.

Once the post patch deployment steps are done, start the services, i.e. Kernel and WebRunner.

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

If you are using any CDATA JDBC driver to connect with salesforce application then follow the steps below to update the database info:

  1. Login into Adeptia application.
  2. Edit the database info which is using CDATA driver.
  3. Save it.

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.

  • No labels