Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

...

...

...

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


Info

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. 

Anchor
Prerequisites
Prerequisites
Prerequisites

Ensure that you have:

  • Read and Write permissions on all sub-folders and files of .../AdeptiaConnect-<Version>
  • Take backup of launcher.properties file from …<ConnectPoratlInstallFolder>\conf location. This backup file will help you replicate the manual changes in case you have done earlier in the launcher.properties file before applying this patch.  
  • Take backup of server.xml file from …<ConnectPortalInstallFolder>\conf location. This backup file will help you replicate the manual changes in case you have done earlier in the server.xml file before applying this patch.  
  • Take backup of securityContext.xml file from …<ConnectPortalInstallFolder>\resources_config\saml location. This backup file will help you replicate the manual changes in case you have done earlier in the server.xml file before applying this patch.  
  • Take backup of apps.properties file from …<ConnectPortalInstallFolder>\resources_config location. This backup file will help you replicate the manual changes in case you have done earlier in the apps.properties file before applying this patch.  
  • Connect Server services are running.
  • Connect Portal service is stopped.

Anchor
Applying the patch
Applying the patch
Applying the patch

Expand
titleFor Windows
  1. Extract the Adeptia Connect zip file from the downloaded folder.
  2. Open the Command Prompt.
  3. Go to the folder where you have extracted the zip file.
  4. Run the following command to apply the patch:
    Apply-Patch.bat -portal “<Path where Connect Portal is installed till ConnectPortal folder>” 

    For example:

    Apply-Patch.bat -portal  "C:/Program Files/AdeptiaConnect/AdeptiaConnect-x.x/ConnectPortal"
     
    Once the patch is applied, a confirmation message will be displayed. 


Expand
titleFor Linux
  1. Open the Terminal.
  2. Extract the downloaded zip file in a directory.
  3. Go to the directory where you have extracted the zip file.
  4. Run the following command to apply the patch:

    ./Apply-Patch.sh -portal <Path where Connect Portal is installed till ConnectPortal folder> 

    For example:

    ./Apply-Patch.sh -portal /mnt/AdeptiaConnect-x.x/ConnectPortal

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

Anchor
Post Patch Deployment Steps
Post Patch Deployment Steps
Post patch deployment steps

In this release, some manual changes are required in Connect Portal.

Changes in launcher.properties file

  1. Go to …<ConnectPoratlInstallFolder>\conf location.
  2. Open launcher.properties file.
  3. If you have done any change in the previous file related to JVM memory parameters then do the same in the latest file. 
  4. Do the same manual changes in the file in case you have done in your previous launcher.properties file (that you had saved as a backup).
  5. Save the file.


Changes in server.xml File

  1. Go to …<ConnectPortalInstallFolder>\conf location.
  2. Open server.xml filand do the following changes:
    1. Add parameter secretRequired="false" in Connector tag for AJP.

      Image Modified

    2. Copy the code in service section as shown below and paste in the existing server.xml file.

      Code Block
      collapsetrue
      <Service name="SoapService">
      	
      			<!-- 
      			<Connector port="80" protocol="HTTP/1.1" connectionTimeout="20000"
      			redirectPort="443" compression="on" noCompressionUserAgents="gozilla, 
      			traviata" compressableMimeType="text/html,text/xml,text/css,application/javascript,application/json" 
      			useSendfile="false" server="Adeptia" xpoweredby="false" />
      			 -->
      			
      			<!-- 
      			<Connector port="443" protocol="HTTP/1.1" SSLEnabled="true" maxThreads="5000" 
      			scheme="https" secure="true" compressionMinSize="128" connectionTimeout="20000" 
      			maxConnections="10000" clientAuth="false" sslProtocol="TLSv1.2" sslEnabledProtocols="TLSv1.2" keystoreFile="./keystore/adeptiaBPM.keystore" 
      			keystoreType="JKS" keystorePass="password" compression="on" noCompressionUserAgents="gozilla, 
      			traviata" compressableMimeType="text/html,text/xml,text/css,application/javascript,application/json" 
      			useSendfile="false" server="Adeptia" xpoweredby="false" />
      			-->
      			
      			<Engine defaultHost="localhost" name="soapwebapps">
      			
      				<Realm className="org.apache.catalina.realm.LockOutRealm">
      					<Realm className="org.apache.catalina.realm.UserDatabaseRealm" resourceName="UserDatabase"/>
      				</Realm>
      				
      				<Host appBase="soapwebapps/wars" autoDeploy="true" name="localhost" unpackWARs="true">
      					<Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs" pattern="%h %l %u %t &quot;%r&quot; %s %b" prefix="localhost_access_log" suffix=".txt"/>
      					<Valve className="org.apache.catalina.valves.ErrorReportValve" showReport="false" showServerInfo="false"/>
      				</Host>
      				
      			</Engine>
      	</Service>
      	
      	  <Service name="RestService">
      	
      			<!-- 
      			<Connector port="80" protocol="HTTP/1.1" connectionTimeout="20000"
      			redirectPort="443" compression="on" noCompressionUserAgents="gozilla, 
      			traviata" compressableMimeType="text/html,text/xml,text/css,application/javascript,application/json" 
      			useSendfile="false" server="Adeptia" xpoweredby="false" />
      			-->
      			
      			<!-- 
      			<Connector port="443" protocol="HTTP/1.1" SSLEnabled="true" maxThreads="5000" 
      			scheme="https" secure="true" compressionMinSize="128" connectionTimeout="20000" 
      			maxConnections="10000" clientAuth="false" sslProtocol="TLSv1.2" sslEnabledProtocols="TLSv1.2" keystoreFile="./keystore/adeptiaBPM.keystore" 
      			keystoreType="JKS" keystorePass="password" compression="on" noCompressionUserAgents="gozilla, 
      			traviata" compressableMimeType="text/html,text/xml,text/css,application/javascript,application/json" 
      			useSendfile="false" server="Adeptia" xpoweredby="false" />
      			-->
      			
      			<Engine defaultHost="localhost" name="restwebapps">
      			
      				<Realm className="org.apache.catalina.realm.LockOutRealm">
      					<Realm className="org.apache.catalina.realm.UserDatabaseRealm" resourceName="UserDatabase"/>
      				</Realm>
      				
      				<Host appBase="restwebapps/wars" autoDeploy="true" name="localhost" unpackWARs="true">
      					<Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs" pattern="%h %l %u %t &quot;%r&quot; %s %b" prefix="localhost_access_log" suffix=".txt"/>
      					<Valve className="org.apache.catalina.valves.ErrorReportValve" showReport="false" showServerInfo="false"/>
      				</Host>
      				
      			</Engine>
      	</Service>


  3. Save the file.

Changes in securityContext.xml file

  1. Go to the downloaded Adeptia Connect zip folder and rename the securityContext.xml_Portal file to securityContext.xml.
  2. Copy the renamed securityContext.xml file.
  3. Replace the existing file with the copied file at the following location: …<ConnectPortalInstallFolder>\resources_config\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 replaced 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:

    Image Modified

  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:

    schemeName of the scheme (http or https).
    serverNameName of the server.
    serverPortPort number of the server.
    includeServerPortInRequestURLTo include server port number in the URL or not. It must be false.
    contextPathPrefix 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 securitycontext.xml file.
  6. Save the file.
  7. Restart Connect Portal.

Changes in apps.properties File

  1. Go to …<ConnectPortalInstallFolder>\resources_config location.
  2. Open apps.properties file.

  3. Do the same manual changes in the file that you have done in your previous apps.properties file (that you had saved as backup).
  4. Search for "Microsoft SharePoint" and update below content into the file:
  5. # Microsoft SharePoint
    microsoftsharepoint.oauthVersion=2.0
    microsoftsharepoint.oauth20.authorize={baseUrl}/_layouts/15/OAuthAuthorize.aspx
    microsoftsharepoint.oauth20.accessToken=https://accounts.accesscontrol.windows.net/{realmId}/tokens/OAuth/2
    microsoftsharepoint.scope=Site.Manage List.Manage Web.Manage Web.Write AllSites.Manage AllProfiles.Manage
    microsoftsharepoint.AccessTokenValueMap=resource$00000003-0000-0ff1-ce00-000000000000/{domain}.sharepoint.com@{realmId}

  6. Save the file.

Once the post installation steps are done, start the Connect Portal.

Info

If you are using Database/Advanced Database Event, Source/Target activity with MySQL Database Server using an older version of MySQL JDBC jars then it is recommended to upgrade the jars to mitigate the vulnerability associated with the older jars.

Click here to download the recommended version of MySQL jars (mysql-connector-java-8.0.18.jar) and follow the steps to upgrade it.

Anchor
Verifying Connect Portal patch
Verifying Connect Portal patch
Verifying Connect Portal patch

Login to Adeptia Connect. If you log in successfully, indicates Connect Portal is updated successfully.


Next Step

Recovering Connect Portal

...

Panel
borderStylesolid
titlePages in this topic
Child pages (Children Display)
styleh5

Panel
borderStylesolid
titleYou may be interested in...
What's new
Best practices
Frequently asked questions
Adeptia Connect APIs
Adeptia security report

...

borderStylesolid
titleRelated links
Upgrading Spazio jar files

...