This section lists the prerequisites and explains how to apply the patch on Windows-based and Linux-based operating systems.

Prerequisites

Before applying the patch, ensure that you have:

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.
Take backup of web.xml file from …<AdeptiaInstallFolder>\AdeptiaServer\ServerKernel\web\WEB-INF location. This backup file will help you replicate the manual changes in case you have done earlier in the web.xml file before applying this patch.
Take backup of cacert file from …<AdeptiaInstallFolder>\AdeptiaServer\ServerKernel\etc\truststore location. This backup file will help you replicate the manual changes in case you have done earlier in the cacert 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:

1. 1. Stop Kernel and WebRunner.
  2. Go to …<AdeptiaInstallFolder>/AdeptiaServer/ServerKernel folder.
  3. 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.
In case you have updated export.xml (during Migration of objects), and you wish to keep changes after applying the patch, keep a backup of this file from the path: ...\…<AdeptiaInstallFolder>\AdeptiaServer\ServerKernel\MigrationUtility. After the patch application is complete, merge the changes done in the backed up file with the new file (export.xml) generated.

Do not replace the backup of export.xml to the newly created export.xml. Only merge the changes from the old file to the new one.

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 Adeptia Suite is installed till AdeptiaServer folder>"

For example:

Apply-Patch.bat "C:/Program Files/AdeptiaSuite/AdeptiaSuite-x.x/AdeptiaServer"

Once the patch is applied, a confirmation message will be displayed.

Start Kernel and WebRunner.

For Linux

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 Adeptia Server folder>

For example:

./Apply-Patch.sh /mnt/AdeptiaSuite-x.x/AdeptiaServer

Once the patch is applied, a confirmation message will be displayed.

Start Kernel and WebRunner.

Patch application may take some time, in case there are a large number of records in the backend and log database.
A PatchApplicationLog<Date>.log file is also 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.
After applying the patch, clear the browser history before login to Adeptia Suite.
Clear the Java cache and the previous certificate of Adeptia from Java Control Panel. Click here to know how to clear Java cache and delete Adeptia certificates.
If any error occurs during patch deployment then the patch will be recovered automatically.

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

Changes in securityContext.xml file

Go to the downloaded Adeptia Suite zip folder and rename the securityContext.xml_Server file to securityContext.xml.
Copy the renamed securityContext.xml file.
Replace the existing file with the copied file at the following location: …<AdeptiaInstallFolder>\AdeptiaServer\ServerKernel\etc\saml.
In case you are using SAML authentication, open the updated securityContext.xml file and do the following changes:

Uncomment the following property:

<!-- <property name="entityBaseURL" value="http://localhost:8080/adeptia"/> -->

Update the URL as required. Where localhost is the IP address and port of the Connect Server.
Uncomment the idp.xml property:

If you are using Adeptia Connect with load balancer, follow these steps:

Remove or comment out the existing contextProvider bean
<bean id="contextProvider" class="org.springframework.security.saml.context.SAMLContextProviderImpl"/>

Add the below contextProvider bean

<bean id="contextProvider" class="org.springframework.security.saml.context.SAMLContextProviderLB">
 <property name="scheme" value="http"/>
 <property name="serverName" value="www.myserver.com"/>
 <property name="serverPort" value="8080"/>
 <property name="includeServerPortInRequestURL" value="false"/>
 <property name="contextPath" value="/adeptia"/>
</bean>

This table explains the each property of contextProvider bean:

Property Name	Description
scheme	Name of the scheme (http or https).
serverName	Name of the server.
serverPort	Port number of the server.
includeServerPortInRequestURL	To include server port number in the URL or not. It must be false.
contextPath	Prefix of a URL path used to select the context(s) to which an incoming request is passed. A URL is in the format: h ttp://hostname.com/contextPath/, where each of the path elements can be zero or more separated elements. It must be /adeptia.

It will look like:

<bean id="contextProvider" class="org.springframework.security.saml.context.SAMLContextProviderLB">
 <property name="scheme" value="http"/>
 <property name="serverName" value="www.myserver.com"/>
 <property name="serverPort" value="8080"/>
 <property name="includeServerPortInRequestURL" value="false"/>
 <property name="contextPath" value="/adeptia"/>
</bean>

If there were any other changes in the old file, you have to do the same changes manually in the updated securityContext.xml file.
Save the file.

Restart the Server.

Changes in web.xml file

Go to …<AdeptiaInstallFolder>\AdeptiaServer\ServerKernel\web\WEB-INF location.
Go to the downloaded Adeptia Suite zip folder and rename the web.xml_Server file to web.xml.
Copy the renamed web.xml file.
Replace the existing file with the copied file at the following location: …<AdeptiaInstallFolder>\AdeptiaServer\ServerKernel\web\WEB-INF.
Open web.xml file.
Do the same manual changes in the file that you have done in your previous web.xml file (that you had saved as a backup).
Save the file.

Adding certificates in cacerts file

Two new certificates need to be added to the cacerts file in the application. This step is required to update the cacerts file with COMODO renewed certificates as the existing certificates of COMODO have expired.

Follow the steps below to add the certificates:

Stop the Server.
Download the following two certificates from this link.
- 1199354.crt
- 1720081.crt
On the command prompt, run the following command to import the two new certificates to the cacerts file:
keytool -import -file "<path_to_Certificate_file>" -keystore "<path_to_application_folder>\ServerKernel\etc\truststore\cacerts" - alias "<alias_name>" - storepass "<cacerts file password>"

Where,
path_to_Certificate_file: The location where you have downloaded the certificates.
path_to_application_folder: Location of the cacerts file in the Connect Server.
alias_name: Alias name for '1199354.crt' and '1720081.crt' are 'USERTrust RSA Certification Authority' and 'COMODO RSA Certification Authority' respectively.
cacerts file password: Password for the cacerts file. By default, the password for the cacerts file is 'changeit'.
Restart the Server.

Installing Fontconfig Library on Linux

This section is applicable only if you are using Server in Linux environment.

In view of using open source Amazon Coretto JRE with this release, it is mandatory for you to install the Fontconfig library on the machine where Server is running.

Ensure that you have Read, Write, and Execute permissions in Linux environment.

Follow the steps below to install the Fontconfig library:

Run the following command to install the Fontconfig library:
yum install fontconfig
Command to install Fontconfig library may vary for different Linux editions.
Restart the machine.

Once the post patch deployment steps are done, start the services, i.e. Kernel and WebRunner.