This section lists the prerequisites and steps for applying and verifying this patch.

Though every release of Adeptia comes with seamless upgrades and bug-free patches, for customer's complex use cases, we recommend applying the patch in a non-production environment first followed by testing. After the use cases run successfully without any errors or warnings, you can apply the patch in the production environment.

Prerequisites

You have Read and Write permissions on all sub-folders and files of .../AdeptiaConnect-<Version>.
Services such as Kernel, WebRunner, and AIMap are stopped.
Take backup of securityContext.xml file from …<ConnectServerInstallFolder>\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.
Take backup of export.xml and connect_export.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.
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.

Applying the patch

For Windows

Download the latest patch from the provided URL.
Extract the downloaded zip file in a folder.
Open the Command Prompt.
Go to the folder where you have extracted the zip file.
Run the following command to apply the patch:
```
Apply-Patch.bat “<Path where Connect Server is installed till AdeptiaServer folder>” 
```
For example:
```
Apply-Patch.bat   
```
```
"C:/Program Files/AdeptiaConnect-x.x/ConnectServer/AdeptiaServer"
```
```
or 
```
```
Apply-Patch.bat  
```
```
"C:/Program Files/AdeptiaSuite-x.x/AdeptiaServer"
```
Once the patch is applied, a confirmation message will be displayed.
Note: While applying the patch you may come across following warning messages that you should ignore.
Warning: Not deploying connect2.0 accelerator because no change list is present.
Warning: Not deploying EDI accelerator because no change list is present.

For Linux

Before you apply this patch on Linux, ensure that you take back up of your existing startup.sh and stop.sh files.

Open the Terminal.
Download the latest patch from the provided URL.
Extract the downloaded zip file in a directory.
Go to the directory where you have extracted the zip file.
Run the following command to apply the patch:
```
./Apply-Patch.sh <Path where Connect Server is installed till AdeptiaServer folder> 
```
For example:
```
./Apply-Patch.sh /mnt/AdeptiaConnect-x.x/ConnectServer/AdeptiaServer
```
or
```
./Apply-Patch.sh /mnt/AdeptiaSuite-x.x/AdeptiaServer
```
Note: While applying the patch you may come across following warning messages that you should ignore.
Warning: Not deploying connect2.0 accelerator because no change list is present.
Warning: Not deploying EDI accelerator because no change list is present.
Once the patch is applied, a confirmation message will be displayed.

After you have applied the patch, PatchApplicationLog_<Date>.log file is created inside the logs folder. The logs folder is available in the same folder from where you have applied the patch. PatchApplicationLog_<Date>.log file contains the logs generated during patch application and can be used to troubleshoot any issue related to the patch application.

Patch application may take some time, in case there are a large number of records in the backend and log database.

The patch will automatically rollback, in case of any error during the deployment.

After applying this patch, refer to post patch deployment section for manual changes.

Post patch deployment steps

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:
1. Add the below property under the security headers tag:
  <security:hsts max-age-seconds="31536000"/>
Go to Secured pages with SAML as entry point section and make the following change:
1. Add the below property under the security headers tag:
  <security:hsts max-age-seconds="31536000"/>
Save the file.

Changes in connect_export.xml

Go to …<ConnectServerInstallFolder>\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 activities under this section:
<activity type="Email Notification Format" />
<activity name="KafkaAccount" />
<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 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.
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.

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.

Verifying Connect Server patch

To verify whether the patch is applied successfully:

Go to …<ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\etc\CVS location.
Open the Tag file.
Check the Build Tag. If the build tag matches with that of Connect Server, it indicates that the Connect Server patch is deployed successfully.

Next step

Applying Connect Portal patch

Applying Connect Server patch