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

Prerequisites

Ensure that you have:

• 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 file will help you to update the securityContext.xml file for manual changes, if you have done any.
• Take backup of web.xml file from …<ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\web\WEB-INF location. This file will help you to update the web.xml file for manual changes, if you have done any.
• Take backup of cacert file from …<ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\etc\truststore location. This file will help you to update the cacert file for manual changes, if you have done any.
• No process flow or transaction should be in running, waiting or queued state. 
• Latest License details of Adeptia Connect. You can contact Adeptia Support for more details.

Applying the patch

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

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. Open securityContext.xml file.
5. Do the same manual changes in the file in case you have done in your previous securityContext.xml file (that you had saved as a backup).
6. Save the file.

In case you are using SAML authentication then open the updated securityContext.xml file and do the following changes:

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

This patch introduces two new certificates to be added to the cacerts file in the application. 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.

Adding .dll files in System32 folder

If NTEvent Logging property in server-configure.properties file is enabled then copy the following .dll files in System32 folder.

• NTEventLogAppender.amd64.dll
• NTEventLogAppender.x86.dll

Follow the steps below to place these files in System32 folder:

1. Go to …<ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\etc location.
2. Copy the .dll files form this location.
3. Paste the files in C:\Windows\System32 folder.

Changes in server-configure.properties File

In case you are using MySQL as Backend and Log database then do the following manual changes.

1. Go to …<ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\etc location.
2. Take backup of server-configure.properties file from the above-mentioned location.
3. Open server-configure.properties file.
4. Go to Database Configuration section and do the following changes:
   1. Update the property 'abpm.jdo.driver' value as com.mysql.cj.jdbc.Driver.

   2. Update the property 'abpm.jdo.url' by appending the value ?useSSL=false&amp;serverTimezone=<time zone> at the end of the URL.

      • Append the value ?useSSL=false at the end of the URL. However, this argument is not required if SSL is configured on your MySQL database server.
      • Append the value &amp;serverTimezone=<time zone> at the end of the URL. For example, &amp;serverTimezone=UTC+3:00. This argument is required only when an error related to the time zone is displayed while starting the Connect Kernel.
        
        Here, <time zone> is the time zone of your MySQL server.

      
      
      
      

   3. Save the file.
      
      

5. Go to Database Appender section and do the following changes:
   1. Update the property 'log4j.appender.jdbc.dbclass' value as com.mysql.cj.jdbc.Driver.

   2. Update the property 'abpm.jdo.url' by appending the value ?useSSL=false&amp;serverTimezone=<time zone> at the end of the URL.

      • Append the value ?useSSL=false at the end of the URL. However, this argument is not required if SSL is configured on your MySQL database server.
      • Append the value &amp;serverTimezone=<time zone> at the end of the URL. For example, &amp;serverTimezone=UTC+3:00. This argument is required only when an error related to the time zone is displayed while starting the Connect Kernel.
        
        Here, <time zone> is the time zone of your MySQL server.

      

   3. Save the file.

Restoring user-defined jars

With the new patch the launcher.properties file is updated and no longer has the list of jars in it. If you have defined your own jars in previous version of launcher.properties file, you need to move them to the ext folder to load them at the time of Kernel and WebRunner start up. Follow the steps below:

1. Go to …<ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\etc location.
2. Open launcher-bak.properties file.
3. Identify your jars and move those jars from their current location to the following location: …<ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\ext.
   
   

Update window services

If you have upgraded from Adeptia Connect v2.9.2 or earlier to the higher versions, you need to remove the existing windows services i.e. Adeptia Suite Kernel and Adeptia Suite WebRunner and add two new windows services (Connect Kernel and Connect WebRunner).

Follow the steps below to remove the older services:

1. Open the Terminal as an administrator.
2. Go to the …<ConnectServerInstallFolder>\jre\bin.

3. Run the following command to remove the old Windows services:

   jsl -remove "…<ConnectServerInstallFolder>\ServerKernel\jsl-Kernel_Unregister.ini"

   jsl -remove "…<ConnectServerInstallFolder>\ServerKernel\jsl-WebRunner_Unregister.ini"

Follow the steps below to add the new services:

1. Open the Terminal as an administrator.
2. Go to the …<ConnectServerInstallFolder>\jre\bin.

3. Run the following command to add the new Windows services:

   jsl -install "…<ConnectServerInstallFolder>\ServerKernel\jsl-Kernel.ini"

   jsl -install "…<ConnectServerInstallFolder>\ServerKernel\jsl-WebRunner.ini"

Go to windows services to check if these services have been added successfully. To start Adeptia Connect server, you need to start these two services. 

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

Updating database info for CDATA drivers

If you are using any CDATA JDBC driver to connect with any business application such as salesforce, etc. then follow the steps below to update the database info:

1. Login into Adeptia application.
2. Edit the database info which is using CDATA driver.
3. Save it.

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.

Next Step

Applying Connect Portal patch