Page Comparison

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

...

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

...

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

2. Open connect_export.xml file.

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

   <activity type="Email Notification Format" />
   
   Image Modified
   
   

4. 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 Modified
   
   

4. Save the file.

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

...

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

...

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.
   Image Modified
   

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)
   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

   
   

8. Click Save.
9. Restart the server.