Versions Compared

Old Version 4

changes.mady.by.user Avinash Kumar

Saved on

compared with

New Version Current

changes.mady.by.user Avinash Kumar

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Corrected links that should have been relative instead of absolute.

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

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

  2. Open connect_export.xml file.

  3. 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" />
    Image Removed

    Image Added

    Image Added

  4. Save the file.

Changes in export.xml

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

  2. Open export.xml file.

  3. 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" />
    Image Removed

    Image Added

    Image Added

  4. Save the file.

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

  1. Copy the connect_import.xml file from the

    folder you have extracted the

    patch location.

  2. Go to 

    …<ConnectServerInstallFolder>

    …<ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\

    etc location

    MigrationUtility location and paste the copied file here.

  3. Open applicationconfig.xml fileOpen connect_import.xml file.

  4. Do the same manual changes in the file that you have done in your

    previous applicationconfig.xml file

    previous connect_import.xml file (that you had saved as a backup).

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

  1. Click Accounts > Settings.
  2. Expand the Server Node Settings in the left panel.
  3. Select the server node.
  4. Click Edit.
  5. Click Image Added to expand the Performance Optimization property.
    Image Added
  6. Click Image Added to expand the Spring Retry Policy Configurations.
    Image Added

  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)
    maxAttemptsabpm.spring.retry.policy.maxAttempts
    initialIntervalabpm.spring.retry.backOff.policy.initialInterval
    multiplierabpm.spring.retry.backOff.policy.multiplier
    maxIntervalabpm.spring.retry.backOff.policy.maxInterval


  8. Click Save.
  9. Restart the server.

Anchor
Verifying Connect Server Patch
Verifying Connect Server Patch
Verifying Connect Server patch

...