Page Comparison

This section lists the prerequisites and explains how to apply the patch on Windows-based and Linux-based operating systems.

...

• 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 securityContext.xml file from …<AdeptiaInstallFolder>\AdeptiaServer\ServerKernel\etc\saml location. This backup file will help you replicate the manual changes in case you have done earlier in the securityContext.xml file before applying this patch.  
• 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. 1. 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 export.xml and connect_export.xml files file from  …<AdeptiaInstallFolder>\AdeptiaServer\ServerKernel\MigrationUtility location. These  This backup files file will help you replicate the manual changes in case you have done earlier in these files before this file before applying this patch.  
  

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

• Ensure that you have followed the Prerequisites' instructions given on the Installing Adeptia Suite page.

...

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

Changes in

...

export.xml

...

1. Go to …<AdeptiaInstallFolder><AdeptiaInstallFolder>\AdeptiaServer\ServerKernel\etc\saml MigrationUtility location.

2. Open securityContextexport.xml file.

3. Go to Security Search for the administration UI section and make the following change:

   Add the below property under the security headers tag:
   <security:hsts max-age-seconds="31536000"/>
   Image Removed
   Go to Secured pages with SAML as entry point section and make the following change:
   Add the below property under the security headers tag:
   <security:hsts max-age-seconds="31536000"/>
   Image Removed
   
4. Save the file.
   
5. Restart the Server.

Changes in connect_export.xml

...

Go to …<AdeptiaInstallFolder>\AdeptiaServer\ServerKernel\MigrationUtility location.

...

Open connect_export.xml file.

Search for List of all activity types that need to be exported and add the following activity under this section:

...

Save the file.

Changes in export.xml

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

2. Open export.xml file.

3. Search for List of all activity types that need to be exported and add the following activities under this section:
   <activity name="KafkaAccount" />
   <activity name="KafkaListener" />
   <activity name="KafkaTarget" />Image Removed
   Save the fileActivities tag containing the activityId="003" and add the following activities within this tag:
   <activity name="PDFSchema" />

   Image Added
   
   Image Added
   

4. Save the file.

Changes in applicationconfig.xml file

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

1. Log in to Adeptia Suite with your user ID and password.
2. Click Administer, and then Update System Properties.
3. Click Image Added to expand the Performance Optimization property.
4. Click Image Added to expand the Spring Retry Policy Configurations.
   Image Added
   

5. 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)
   maxAttempts	abpm.spring.retry.policy.maxAttempts
   initialInterval	abpm.spring.retry.backOff.policy.initialInterval
   multiplier	abpm.spring.retry.backOff.policy.multiplier
   maxInterval	abpm.spring.retry.backOff.policy.maxInterval

   
   

6. Click Save.

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