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 10 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 Event.
  • 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. In case you are using HSQL database, copy the following files (located at .../<AdeptiaInstallFolder>/AdeptiaServer/ServerKernel/embeddedDb/db) and keep then in a seperate folder:

        • indigo.script

        • logs.script

        • abpmquartz.script

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

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

    • webdefault.xml file located at .../<AdeptiaInstallFolder>/AdeptiaServer/ServerKernel/web/WEB-INF.
    • launcher.properties file located at  ...<AdeptiaInstallFolder>\AdeptiaServer\ServerKernel\etc.

  • Ensure that you have followed the Prerequisites' instructions given on the Installing Adeptia Suite 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 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.

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.

  • 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

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

Changes in web.xml.

  1. Copy the web.xml file from patch location, and paste it at .../<AdeptiaInstallFolder>/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 .../<AdeptiaInstallFolder>/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 .../<AdeptiaInstallFolder>/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  ...<AdeptiaInstallFolder>\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 located at .../<AdeptiaInstallFolder>/AdeptiaServer/ServerKernel/etc. 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>;enrypt=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 located at .../<AdeptiaInstallFolder>/AdeptiaServer/ServerKernel/etc. Example for backend db JDBC URL is given below:

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

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

Important

With an upgrade to Java 17, the JMS provider that connects to Apache Active MQ JMS server uses the two jars activemq-core-5.7.0.jar and geronimo-j2ee-management_1.1_spec-1.0.1.jar.

After you have deployed the patch, ensure that:

  • You use these two jars when you create a JMS provider that connects to Apache Active MQ JMS server.

  • You have updated any existing JMS provider that connects to Apache Active MQ JMS server to use these two jars.
    For more details, refer to this page.

  • No labels