Page Comparison

...

• You have Read and Write permissions on all subfolders and files of .../AdeptiaConnect-<Version>.
• Services such as Kernel, WebRunner, and AIMap are stopped.
• Take backup of launcher.properties file from …<ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\etc location. This file will help you to update the launcher.properties 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 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.
  
• Latest License details of Adeptia Connect. You can contact Adeptia Support for more details.
  
  

...

1. Go to …<ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\etc\jetty location.
2. Take backup of jetty.xml file from the above-mentioned location.
3. Go to the downloaded Adeptia Connect zip folder and copy jetty.xml file.
4. Replace the existing file with the copied file at the following location: …<ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\etc\jetty.
5. In case, you have configured SSL certificate then update the jetty.xml file to configure the SSL certificate.

Changes in

...

web.xml File

1. Go to the folder path where Adeptia Connect is installed. For example, C:\Program Files\AdeptiaConnect\AdeptiaConnect-3.0\ConnectPortal\conf…<ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\web\WEB-INF location.
2. Take back up of web.xml file from the above-mentioned location.
3. Go to the downloaded Adeptia Connect zip folder and copy web.xml.
4. Replace the existing file with the copied file at the following location …<ConnectPortalInstallFolder>\conflocation …<ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\web\WEB-INF.
5. Open the replaced file and do the following changes:
   1. If you had uncommented the following tag in the replaced file will comment it, therefore you need to uncomment it again:
      

       <!--<security-constraint>

              <web-resource-collection>

              <web-resource-name>Protected Context</web-resource-name>

              <url-pattern>/*</url-pattern>

              </web-resource-collection>

              <user-data-constraint>

              <transport-guarantee>CONFIDENTIAL</transport-guarantee>

              </user-data-constraint>

          </security-constraint>-->

6. Save the file.

Changes in

...

securityContext.xml File

1. Go to …<ConnectPortalInstallFolder>\resources_config\saml ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\etc\saml location.
2. Take backup of securityContext.xml file from the above-mentioned location.
3. Go to the downloaded Adeptia Connect zip folder and copy securityContext.xml.
4. Replace the existing file with the copied file at the following location: …<ConnectPortalInstallFolder>\resources_config…<ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\etc\saml.
5. Do the same manual changes that you have done in your previous securityContext.xml file (that you had saved as backup).

...

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 replaced securitycontextsecurityContext.xml file.
6. Save the file.
7. Restart Connect PortalServer.

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

...