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:
- Stop Kernel and WebRunner.
- Go to …<AdeptiaInstallFolder>/AdeptiaServer/ServerKernel folder.
- 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.xmland , 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.
...
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:
<activity type="Email Notification Format" />
Save the file.
Changes in export.xml
Go to …<AdeptiaInstallFolder>\AdeptiaServer\ServerKernel\MigrationUtility location.
Open export.xml file.
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" />Save the file.
Once the post patch deployment steps are done, start the services, i.e. Kernel and WebRunner.
Changes in connect_import.xml
Go to …<ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\MigrationUtility location.
- Open connect_import.xml file.
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).
Save the file.
Changes in applicationconfig.xml file
Note |
---|
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.
- Click Accounts > Settings.
- Expand the Server Node Settings in the left panel.
- Select the server node.
- Click Edit.
- Click to expand the Performance Optimization property.
- Click to expand the Spring Retry Policy Configurations.
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 - Click Save.
- Restart the server.