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 19 Next »

This section lists the prerequisites and steps for applying this patch.

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


 Applying patch on v3.1


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

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

 Applying patch on v3.2


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:

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

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

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.

This is required as MySQL JDBC jars have been upgraded to the latest version. 
  1. Go to …<ConnectServerInstallFolder>\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 …<ConnectServerInstallFolder>\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 …<ConnectServerInstallFolder>\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: …<ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\ext.

Update window services

If you have upgraded from Adeptia Connect v2.9.2 or earlier to the higher versions, you need to remove the existing windows services i.e. Adeptia Suite Kernel and Adeptia Suite WebRunner and add two new windows services (Connect Kernel and Connect WebRunner).

Follow the steps below to remove the older services:

  1. Open the Terminal as an administrator.
  2. Go to the …<ConnectServerInstallFolder>\jre\bin.
  3. Run the following command to remove the old Windows services:

    jsl -remove "…<ConnectServerInstallFolder>\ServerKernel\jsl-Kernel_Unregister.ini"

    jsl -remove "…<ConnectServerInstallFolder>\ServerKernel\jsl-WebRunner_Unregister.ini"

Follow the steps below to add the new services:

  1. Open the Terminal as an administrator.
  2. Go to the …<ConnectServerInstallFolder>\jre\bin.
  3. Run the following command to add the new Windows services:

    jsl -install "…<ConnectServerInstallFolder>\ServerKernel\jsl-Kernel.ini"

    jsl -install "…<ConnectServerInstallFolder>\ServerKernel\jsl-WebRunner.ini"

Go to windows services to check if these services have been added successfully. To start Adeptia Connect server, you need to start these two services. 

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

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

  • If you are using Spazio Listener, Spazio Source, and Spazio Target then you have to copy active MQ jars in ext folder. Click here for detailed information.


Updating database info for CDATA drivers

If you are using any CDATA JDBC driver to connect with any business application such as salesforce, etc. 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. 


Next Step

Verifying Patch

See also

Recovering Patch


  • No labels