Versions Compared

Key

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

...

Expand
titleApplying patch on v3.2


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 'AdeptiaConnect_3_2_04_30April2020.zip' on the tags mentioned below then follow the steps below before applying the patch.

  • Release_AC_3_2_06March2020
  • Release_AC_3_2_01_29March2020
  • Release_AC_3_2_02_02April2020
  • Release_AC_3_2_03_09April2020

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

Info
You need to perform the below steps for Log, Backend, and Archival 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 'abpm.jdo.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 'abpm.jdo.url' by removing the value ?useSSL=false&serverTimezone=<time zone> at the end of the URL.

  4. Save the file.


Expand
titleFor 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/Connect Server is installed till AdeptiaServer folder>” 

    For example:

    Apply-Patch.bat   
    "C:/Program Files/AdeptiaConnect/AdeptiaSuite-x.x/ConnectServer/AdeptiaServer"
    or 
    Apply-Patch.bat  
    "C:/Program Files/AdeptiaSuite/AdeptiaSuite-x.x/AdeptiaServer"

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

    Note: While applying the patch you may come across following warning messages that you should ignore.

    Warning: Not deploying connect2.0 accelerator because no change list is present.
    Warning: Not deploying EDI accelerator because no change list is present.


Expand
titleFor Linux

 
Before you apply this patch on Linux, ensure that you take back up of your existing startup.sh and stop.sh files. 

  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/Connect Server is installed till AdeptiaServer folder> 

    For example:

    ./Apply-Patch.sh /mnt/AdeptiaConnect-x.x/ConnectServer/AdeptiaServer

    or

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

    Note: While applying the patch you may come across following warning messages that you should ignore.

    Warning: Not deploying connect2.0 accelerator because no change list is present.
    Warning: Not deploying EDI accelerator because no change list is present.

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


After you have applied the patch, PatchApplicationLog_<Date>.log file is 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.

Patch application may take some time, in case there are a large number of records in the backend and log database.

The patch will automatically rollback, in case of any error during the deployment.

After applying this patch, refer to post patch deployment section for manual changes.

...