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

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 Mail Event.
  • Take backup of web.xml file from .../<AdeptiaInstallFolder>/AdeptiaServer/ServerKernel\web\WEB-INF location. This file will help you to update the web.xml file for manual changes, if you have done any.
  • 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. Copy the embeddedDB folder and keep it into a separate folder.
    • 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.

  • In case you have updated export.xml (during Migration of objects), and you wish to keep changes after applying the patch, keep a backup of this file from the path: ...\<AdeptiaInstallFolder>\AdeptiaServer\ServerKernel\MigrationUtility. After the patch application is complete, merge the changes done in the backed up file with the new file (export.xml) generated.

    Note

    Do not replace the backup of export.xml to the newly created export.xml. Only merge the changes from the old file to the new one.

Steps to apply 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.

  6. Start Kernel and WebRunner. 

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.

  6. Start Kernel and WebRunner.
  • 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.
If you wish to use upgraded Rich Forms in Adeptia Suite and not configured yet then click here.

Upgrading Rich Form

This section is applicable for upgrading Rich Form in Adeptia Suite v6.9.6.

Follow the below steps if you have Rich Forms v7.3.2 in Adeptia Suite and want to upgrade it.

  1. Stop Kernel and WebRunner. 
  2. Go to the folder where you have extracted the zip file.
  3. Copy these jar files to  .../<AdeptiaInstallFolder>\AdeptiaServer\ServerKernel\RichForms\WEB-INF\lib location.
    • hibernate-search-engine-4.4.6.Final.jar
    • hibernate-search-orm-4.4.6.Final.jar
    • lucene-core-3.6.0.jar
  4. Start Kernel and WebRunner.  

Post Patch Deployment Steps

Log File Changes

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.

Changes in jetty.xml File

  1. Go to .../<AdeptiaInstallFolder>/AdeptiaServer/ServerKernel\etc\jetty location.
  2. Take backup of jetty.xml file from the above-mentioned location.
  3. Go to the downloaded Adeptia Suite zip folder and copy jetty.xml file.
  4. Replace the existing file with the copied file at the following location: .../<AdeptiaInstallFolder>/AdeptiaServer/ServerKernel\etc\jetty.
  5. In case, you have configured SSL certificate then update the jetty.xml file to configure the SSL certificate.

Changes in web.xml File

  1. Go to .../<AdeptiaInstallFolder>/AdeptiaServer/ServerKernel\web\WEB-INF location.
  2. Open web.xml file.
  3. Do the same manual changes in the file that you have done in your previous web.xml file (that you had saved as backup).
  4. Save the file.

Changes in server-configure.properties File

In case you are using MySQL as Backend and Log database then do these manual changes. 

  1. Go to …<ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\etc location.
  2. Open server-configure.properties file.
  3. 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 at the end of URL.
  4. Go to Database Appender section and do the following changes:
    1. Update this property 'log4j.appender.jdbc.dbclass' value as com.mysql.cj.jdbc.Driver.
    2. Update this property 'log4j.appender.jdbc.url' by appending the value ?useSSL=false at the end of URL.
  5. Save the file.

Changes in quartz.properties File

In case you are using MySQL as Backend and Log database then do these manual changes. 

  1. Go to …<ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\etc location.
  2. Open quartz.properties file.
  3. 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 at the end of URL.
  4. Save the file.

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

 

  • No labels