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

  • Take backup of connect_export.xml, export.xml, and connect_import.xml files from  …<AdeptiaInstallFolder>\AdeptiaServer\ServerKernel\MigrationUtility location. These backup files will help you replicate the manual changes in case you have done earlier in these files before applying this patch.  

  • Take the backup of applicationconfig.xml file from …<ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\etc location.These backup files will help you replicate the manual changes in case you have done earlier in these files before applying this patch.

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

  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.

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 connect_export.xml

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

  2. Open connect_export.xml file.

  3. Search for the Activities tag containing the activityRefId="002" and add the following activities within this tag:
    <activity type="PDF Schema" />
    <activity type="Connectors" />




  4. Save the file.

Changes in export.xml

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

  2. Open export.xml file.

  3. Search for the Activities tag containing the activityId="003" and add the following activities within this tag:
    <activity name="PDFSchema" />




  4. Save the file.

Changes in connect_import.xml

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

  2. Open connect_import.xml file.

  3. Do the same manual changes in the file that you have done in your previous connect_import.xml file (that you had saved as a backup).

  4. Save the file.

Changes in applicationconfig.xml file

You need to follow these instructions only if you have made changes to your previous applicationconfig.xml file.

There are some properties that need to change after you finish the deployment. These changes can be done through the Connect GUI. Following the steps below to change the four properties being discussed hereunder.


  1. Click Accounts > Settings.
  2. Expand the Server Node Settings in the left panel.
  3. Select the server node.
  4. Click Edit.
  5. Click  to expand the Performance Optimization property.
  6. Click  to expand the Spring Retry Policy Configurations.

  7. Update the values of the following properties from the backup of applicationconfig.xml file as explained below.

    Old Property Name (applicationconfig.xml backup)

    New Property Name (Settings UI)

    maxAttemptsabpm.spring.retry.policy.maxAttempts
    initialIntervalabpm.spring.retry.backOff.policy.initialInterval
    multiplierabpm.spring.retry.backOff.policy.multiplier
    maxIntervalabpm.spring.retry.backOff.policy.maxInterval
  8. Click Save.


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

  • No labels