This section lists the prerequisites and steps for applying and verifying this patch.
...
- You have Read and Write permissions on all sub-folders and files of .../AdeptiaConnect-<Version>.
- Services such as Kernel, WebRunner, and AIMap are stopped.
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.
Take backup of export.xml and connect_exportTake backup of securityContext.xml file from …<ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\etc\saml connect_export.xml, export.xml, and connect_import.xml files from …<ConnectServerInstallFolder>\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>from …<ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\etc locationetc location. This These backup file files will help you replicate the manual changes in case you have done earlier in the applicationconfig.xml file in these files before applying this patch. .
- Take the backup of the objects. Refer to this page to know why and how you need to back up and restore the objects.
- No process flow or transaction should be in running, waiting or in queued state.
- Ensure that you have followed the Prerequisites' instructions given on the Upgrade page.
...
In this release, some manual changes are required in Connect Server.
Changes in securityContext.xml file
...
Go to …<ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\etc\saml location.
...
Open securityContext.xml file.
Go to Security for the administration UI section and make the following change:
...
.
Changes in connect_export.xml
Go to …<ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\MigrationUtility location.
Open connect_export.xml file.
Search for the Activities tag containing the containing the activityRefId="002" and add add the following activities within this tag:
<activity type="Email Notification FormatPDF Schema" />
<activity nametype="KafkaAccountConnectors" /><activity name="KafkaListener" />
<activity name="KafkaTarget" />Save the file.
Changes in export.xml
Go to …<ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\MigrationUtility location.
Open export.xml file.
Search for the the Activities tag containing the tag containing the activityId="003" and add add the following activities within this tag:
<activity name="KafkaAccountPDFSchema" /><activity name="KafkaListener" /><activity name="KafkaTarget" />
Save the file.
Restart the Connect Server.
Changes in SecureBridge Agent Manager
After upgrading to Adeptia Connect v3.4, you need to run the SecureBridge Agent Manager Migration Utility to be able to make the older version of the SecureBridge compatible with that in AC v3.4.
Warning |
---|
This step is required only when you are a licensed user of SecureBridge Agent Manager in Adeptia Connect v3.3. |
To know how to run the utility, refer to this page in the Help documentation.
Changes in applicationconfig.xml
...
Changes in connect_import.xml
Copy the connect_import.xml file from the patch location.
Go to
…<ConnectServerInstallFolder>…<ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\
etc locationMigrationUtility location and paste the copied file here.
- Open applicationconfig.xml fileOpen connect_import.xml file.
Do the same manual changes in the file that you have done in your
previous applicationconfig.xml fileprevious 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.
Anchor | ||||
---|---|---|---|---|
|
...