This section lists the prerequisites and steps to update Adeptia Connect UI on Tomcat. This section is applicable only for those who have installed Adeptia Connect using a single installer provided with v2.9.3 onwards. Those who have deployed Tomcat on the UI separately (v.2.9.3 earlier) should refer to the patch application conditionsfor applying 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. |
...
Expand | ||
---|---|---|
| ||
|
Post
...
Patch Deployment Steps
In this release, some manual changes are required in Connect Portal.
Changes in
...
<Connector port="80" protocol="HTTP/1.1" connectionTimeout="20000"
...
Go to the following property and replace it with the property from the previous file (back up file of step no. 2)
<Connector port="443" protocol="HTTP/1.1" SSLEnabled="true" maxThreads="5000"
scheme="https" secure="true" compressionMinSize="128" connectionTimeout="20000"
maxConnections="10000" clientAuth="false" sslProtocol="TLS" 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" clientauth="true" />
...
Save the file.
Changes in Web.xml File
- Go to the folder path where Adeptia Connect is installed. For example, C:\Program Files\AdeptiaConnect\AdeptiaConnect-3.0\ConnectPortal\conf
- Take back up of web.xml file from the above-mentioned location.
- Go to the downloaded Adeptia Connect zip folder and copy web.xml.
- Replace the existing file with the copied file at the following location: C:\Program Files\AdeptiaConnect\AdeptiaConnect-3.0\ConnectPortal\conf
- Open the replaced file and do the following changes:
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>-->
- Save the file.
Changes in SecurityContext.xml File
- Go to the folder path where Adeptia Connect is installed. For example, C:\Program Files\AdeptiaConnect\AdeptiaConnect-3.0\ConnectPortal…<ConnectPortalInstallFolder>\resources_config\samlsaml location.
- Take back up backup of securitycontextsecurityContext.xml file from the above-mentioned location.
- Go to the downloaded Adeptia Connect zip folder and copy securitycontextcopy securityContext.xml.
- Replace the existing file with the copied file at the following location: C:\Program Files\AdeptiaConnect\AdeptiaConnect-3.0\ConnectPortal …<ConnectPortalInstallFolder>\resources_config\saml.
- Do the same manual changes that you have done in your previous securityContext.xml file (that you had saved as backup).
In case you are using SAML authentication then open the replaced 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:
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 NameDescriptionIt 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> - Remove or comment out the existing contextProvider bean
- If there were any other changes in the old file, you have to do the same changes manually in the replaced securitycontext.xml file.
- Save the file.
- Restart Connect Portal.
...
- Go to …<ConnectPortalInstallFolder>\conf location.
- Take backup of catalina.properties file from the above-mentioned location.
- Go to the downloaded Adeptia Connect zip folder and copy catalina.properties file.
- Replace the existing file with the copied file at the following location: …<ConnectPortalInstallFolder>\conf.
- Do the same manual changes that you have done in your previous catalina.properties file (that you had saved as backup).
Changes in securityContext.xml File
...
Next Steps
...