Versions Compared

Old Version 19

changes.mady.by.user Akash Kumar Jaiswal

Saved on

compared with

New Version Current

changes.mady.by.user Akash Kumar Jaiswal

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Corrected links that should have been relative instead of absolute.

...

Info

Though every release of Adeptia comes with seamless upgrades and bug-free patches. For customer's complex use cases, we recommend applying the patch in a non-production environment first followed by testing. After the use cases run successfully without any errors or warnings, you can apply the patch in the production environment. 

Prerequisites

Ensure that you have:

  • You have Read and Write permissions on all sub-folders and files of .../AdeptiaConnect-<Version>.
  • Services such as Kernel, WebRunner, and AIMap are stopped.
  • Take backup of jetty.xml file from …<ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\etc\jetty location. This file will help you recover the patch manually, if required.
  • No process flow or transaction should be in running, waiting or queued state. 

  • Latest License details of Adeptia Connect. You can contact Adeptia Support for more details.

Applying the patch


Expand
titleApplying patch on v3.1


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.


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-configconfigure.properties file:

Info

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 to …<ConnectServerInstallFolder>\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 to …<ConnectServerInstallFolder>\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.


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.

Anchor
Post Patch Deployment Steps
Post Patch Deployment Steps
Post Patch Deployment Steps

Changes in jetty.xml File

  1. Go to …<ConnectServerInstallFolder>\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 …<ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\web\WEB-INF location.
  2. Take backup of web.xml file from the above-mentioned location.
  3. Go to the downloaded Adeptia Connect zip folder and rename the web.xml_Server file to web.xml.
  4. Copy the renamed web.xml file.
  5. Replace the existing file with the copied file at the following location: …<ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\web\WEB-INF.
  6. Open web.xml file.
  7. 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).
  8. 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.

...