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, export.xml, and connect_import.xml files xml 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 …<ConnectServerInstallFolder>…<AdeptiaInstallFolder>\AdeptiaServer\ServerKernel\etc location. These This backup files file will help you replicate the manual changes in case you have done earlier in these files 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 …<ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\MigrationUtility location.

2. Open connect_export.xml file.

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

Image Removed
Image Removed


3. Save the file.

Changes in export.xml

1. Go to …<ConnectServerInstallFolder><AdeptiaInstallFolder>\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

...

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

...

There are some properties that need to change after you finish the deployment. These changes can be done through the Connect Adeptia Suite 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 Log in to Adeptia Suite with your user ID and password.
6. Click Administer, and then Update System Properties.
7. Click  to expand the Performance Optimization property.Image Removed
8. Click  to expand the Spring Retry Policy Configurations.
   Image RemovedImage Added
   

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

   
   

10. Click Save.

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