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 jetty.xml file from .../<AdeptiaInstallFolder>/AdeptiaServer/ServerKernel/etc/jetty location. This file will help you to update the jetty.xml file for manual changes, if you have done any.
  
• 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. 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.
  
  

  Note

  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

1. Download the latest patch from the provided URL.
2. Extract the downloaded zip file in a folder.
3. Open the Command Prompt.
4. Go to the folder where you have extracted the zip file.
5. 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.

6. Start Kernel and WebRunner. 

For Linux  

1. Open the Terminal.
2. Download the latest patch from the provided URL.
3. Extract the downloaded zip file in a directory.
4. Go to the directory where you have extracted the zip file.

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

6. Start Kernel and WebRunner.
   
   

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

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

1. 1. Uncomment the following property:

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

   2. Update the URL as required. Where localhost is the IP address and port of the Connect Server.
   3. Uncomment the idp.xml property:
      
      
      
      
   4. 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:

      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: http://hostname.com/contextPath/, where each of the path elements can be zero or more separated elements. It must be /adeptia.
      Property Name	Description

      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>

   5. If there were any other changes in the old file, you have to do the same changes manually in the updated securityContext.xml file.
   6. Save the file.
2. Restart the Connect Server.

Changes in web.xml file

1. Go to …<ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\web\WEB-INF location.
2. Go to the downloaded Adeptia Connect zip folder and rename the web.xml_Server file to web.xml.
3. Copy the renamed web.xml file.
4. Replace the existing file with the copied file at the following location: …<ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\web\WEB-INF.
5. Open web.xml file.
6. 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).
7. 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: 

1. Stop the Connect Server.
2. Download the following two certificates from this link. 
   • 1199354.crt
   • 1720081.crt

3. 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'.
   
   

4. Restart the Connect Server.

Installing Fontconfig Library on Linux

This section is applicable only if you are using Connect 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 Connect Server is running.  

Follow the steps below to install the Fontconfig library:

1. Run the following command to install the Fontconfig library:
          yum install fontconfig
   

   Command to install Fontconfig library may vary for different Linux editions.
2. Restart the machine.  

Configuring SMTP and Windows NTEvent Appender 

In case you have been using SMTP and Windows NTEvent Appender for message logging in the previous version, you need to configure these two Appenders in this version of Adeptia Connect.

• To configure SMTP Appender, click here.
• To configure Windows NTEvent Appender, click here.

Verifying Connect Server patch

To verify whether the patch is applied successfully:

1. Open the browser and visit the URL:

   http://<hostname>:8080/adeptia/control

   where hostname is the name of the server on which Connect Server is running. Developer Studio home page appears.

2. Type the username and password in the User Id and Password text boxes respectively.
3. Click Login.
4. Click Help > About.
5. Check the Build Tag. If it is the same you applied, indicates patch is deployed successfully.