Applying Connect Server v3.0 Patch

This section lists the prerequisites and steps for applying 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

Ensure that you have:

Read and Write permissions on all subfolders and files of .../AdeptiaConnect-<Version>. However, for some versions, the path may be .../AdeptiaSuite-<Version>.
Stopped Kernel and WebRunner.
Latest License details of Adeptia Connect. You can contact Adeptia Support for more details.

Pre-Patch Deployment

If any of your Database (Backend, Log, Quartz, and Log Archival) is using jTDS driver to connect with MS SQL Server, then you must change the jTDS driver to sqljdbc driver.

Ensure that you do this change before applying this patch. Click here for the instructions given to change the driver to sqljdbc.

Steps to apply 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 Adeptia Suite/Connect is installed till AdeptiaServer folder>” 
```
For example:
```
Apply-Patch.bat   
```
```
"C:/Program Files/AdeptiaConnect/AdeptiaSuite-x.x/ConnectServer/AdeptiaServer"
```
```
or 
```
```
Apply-Patch.bat   
```
```
"C:/Program Files/AdeptiaSuite/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.

7. Start Kernel and WebRunner services. Thereafter, if required do the changes in startup.sh file manually from your backup startup.sh file.

After you have applied the patch, you need to manually start AIMap service. To start Adeptia AIMap:

Go to the path C:\Program Files\AdeptiaConnect\AdeptiaConnect-x.0\ConnectServer\AdeptiaServer\ServerKernel.
Right click on installAIMapService.bat file and click Run as administrator to create windows services for AIMap.
Start AIMap service.
1. To stop AIMap service go the same location and right click on removeAIMapService.bat file and click Run as administrator to stop/remove AIMap Service.

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 Adeptia Suite 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.
Start Kernel and WebRunner.

After you have applied the patch, you need to manually start AIMap. To start Adeptia AIMap:

Go to the path C:\Program Files\AdeptiaConnect\AdeptiaConnect-x.0\ConnectServer\AdeptiaServer\ServerKernel.
Execute ./startAIMap.sh file start AIMap.
1. To stop AIMap go the same location and execute ./stopAIMap.sh to stop AIMap.

Post Patch Application Changes

Log File Changes

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.

Changes in ldapConfiguration.xml File

In case, you are using LDAP authentication then open the ldapConfiguration.xml file and do the following changes:

Go to the folder path where Adeptia Connect is installed. For example, C:\Program Files\AdeptiaConnect\AdeptiaConnect-3.0\ConnectServer\AdeptiaServer\ServerKernel\etc.
Open ldapConfiguration.xmlfile in the Text Editor.
Add the following properties:
Save the file.

If you are using LDAP cross-domain authentication,

Uncomment the following property:
Save the file.
Restart Connect Server.

Next Step

Verifying Patch

See also

Recovering Patch