Applying Connect Server patch AC v3.7.2

Owned by Ashhad Alam
Last updated: Jun 19, 2023
3 min read

This section lists the prerequisites and steps for applying and verifying 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

  • 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 the following files:
    • web.xml file located at …<ConnectServerInstallFolder>/AdeptiaServer/ServerKernel/web/WEB-INF.

    • jetty.xml file located at …<ConnectServerInstallFolder>/AdeptiaServer/ServerKernel/etc/jetty.

    • webdefault.xml file located at …<ConnectServerInstallFolder>/AdeptiaServer/ServerKernel/web/WEB-INF.
    • launcher.properties file located at …<ConnectServerInstallFolder>/AdeptiaServer/ServerKernel/etc.
  • No process flow or transaction should be in running, waiting, or queued state. 
  • Ensure that you have followed the Prerequisites' instructions given on the Upgrade page.

Applying the patch

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

    For example:

    Apply-Patch.bat   
    "C:/Program Files/AdeptiaConnect-x.x/ConnectServer/AdeptiaServer"
    or 
    Apply-Patch.bat  
    "C:/Program Files/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 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

In this release, some manual changes are required in Connect Server.


Changes in web.xml.

  1. Copy the web.xml file from patch location, and paste it at …<ConnectServerInstallFolder>/AdeptiaServer/ServerKernel/web/WEB-INF location replacing the existing one.
  2. Open the copied file and replicate the manual changes that you may have done in your previous web.xml file (that you had saved as a backup).

  3. Save the file.

Changes in jetty.xml

  1. Copy the jetty.xml file from patch location, and paste it at …<ConnectServerInstallFolder>/AdeptiaServer/ServerKernel/etc/jetty location replacing the existing one.
  2. Open the copied file and replicate the manual changes that you may have done in your previous jetty.xml file (that you had saved as a backup).

  3. Save the file.

Changes in webdefault.xml

  1. Copy the webdefault.xml file from patch location, and paste it at …<ConnectServerInstallFolder>/AdeptiaServer/ServerKernel/web/WEB-INF location replacing the existing one.
  2. Open the copied file and replicate the manual changes that you may have done in your previous webdefault.xml file (that you had saved as a backup).

  3. Save the file.

Changes in launcher.properties

  1. Copy the launcher.properties_Server file from patch location, and paste it at …<ConnectServerInstallFolder>/AdeptiaServer/ServerKernel/etc location.
  2. Rename the copied launcher.properties_Server file to launcher.properties.
  3. Open the copied file and replicate the manual changes that you may have done in your previous launcher.properties file (that you had saved as a backup).

  4. Save the file.

Changes in server-configure.properties

In case you are using SQL server database, you need to add the parameters encrypt=true and trustServerCertificate=true to the JDBC URL for backend and log database in the relevant sections of server-configure.properties file. The JDBC URL for backend database can be found under "Database Configuration" section and that for the log database can be found under "Database Appender" section. Examples for both backend and log db JDBC URLs is given below:

Backend db JDBC URL:

jdbc:sqlserver://<IP address>:<Port>;DataBaseName=<Name of backend db>;encrypt=true;trustServerCertificate=true; 

Log db JDBC URL:

jdbc:sqlserver://<IP address>:<Port>;DataBaseName=<Name of log db>;encrypt=true;trustServerCertificate=true; 

Changes in quartz.properties

In case you are using SQL server database, you need to add the parameters encrypt=true and trustServerCertificate=true to the JDBC URL for backend database given for the property org.quartz.dataSource.aBPM.URL in quartz.properties file. Example for backend db JDBC URL is given below:

jdbc:sqlserver://<IP address>:<Port>;DataBaseName=<Name of backend db>;encrypt=true;trustServerCertificate=true;

Verifying Connect Server patch

To verify whether the patch is applied successfully:

  1. Go to …<ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\etc\CVS location.

  2. Open the Tag file.

  3. Check the Build Tag. If the build tag matches the tag of the Connect Server, it indicates that the Connect Server patch is deployed successfully.

In case you need to recover the patch, refer to this page.


Next step

Applying Connect Portal patch AC v3.7.2