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. |
...
- Read and Write permissions on all sub-folders and files of .../AdeptiaConnect-<Version>.
Take backup of apps.properties file from …<ConnectPortalInstallFolder>\resources_config location. This backup file will help you replicate the manual changes that you may have done in this file in the past before applying this patch.
Take backup of web.xml file from …<ConnectPortal>\conf location. This backup file will help you replicate the manual changes that you may have done in this file in the past before applying this patch.
Tip |
---|
In case you are upgrading from AC v3.6.11, you need not take the backup of the apps.properties and web.xml files. |
- Take backup of securityContext.xml file from …<ConnectPortalInstallFolder>\ConnectPortal\resources_config\saml location. This location. This backup file will help you replicate the manual changes that you may have done in this file in the past before applying this patch.
- Take backup of launcher.properties file from …<ConnectPortalInstallFolder>\ConnectPortal\conf location. This backup file will help you replicate the manual changes that you may have done in this file in the past before applying this patch.
- Connect Server services are running.
- Connect Portal service is stopped.
- Ensure that you have followed the Prerequisites' instructions given on the Upgrade page.
Anchor |
---|
| Applying the patch |
---|
| Applying the patch |
---|
|
Applying the patch
...
In this release, some manual changes are required in Connect Portal. The changes differ based on which version you are upgrading from – AC v3.5.24, v3.6.11, or v3.7.
Expand |
---|
title | When upgrading from AC v3.7 |
---|
|
Upgrading from AC v3.7Changes in launcher.propertiesGo to …<ConnectPortalInstallFolder>\ConnectPortal\conf location. - Copy the launcher.properties file from patch location, and paste it at …<ConnectPortalInstallFolder>\ConnectPortal\conf location.
- Open the copied file and make the same manual changes in the file that you have done in your previous launcher.properties file (that you had saved as a backup).
Save the file.
|
Expand |
---|
title | When upgrading from AC v3.6.11 |
---|
|
Upgrading from AC v3.6.11Changes in securityContext.xmlGo to …<ConnectPortalInstallFolder>\ConnectPortal\resources_config\saml location. Open securityContext.xml file. Update the xsi:schemaLocation attribute as shown in the following code snippet. Code Block |
---|
| xsi:schemaLocation="http://www.springframework.org/schema/beans classpath:org/springframework/beans/factory/xml/spring-beans.xsd
http://www.springframework.org/schema/security classpath:org/springframework/security/config/spring-security-5.7.xsd
http://www.springframework.org/schema/context classpath:org/springframework/context/config/spring-context.xsd"> |
- Save the file.
Changes in launcher.propertiesGo to …<ConnectPortalInstallFolder>\ConnectPortal\conf location. - Copy the launcher.properties file from patch location, and paste it at …<ConnectPortalInstallFolder>\ConnectPortal\conf location.
- Open the copied file and make the same manual changes in the file that you have done in your previous launcher.properties file (that you had saved as a backup).
Save the file.
|
Expand |
---|
title | When upgrading from AC v3.5.24 |
---|
|
Upgrading from AC v3.5.24Changes in apps.properties fileGo to …<ConnectPortalInstallFolder>\resources_config location. - Open apps.properties file.
Below the Facebook section in the file, add the following code block for Microsoft Azure. Code Block |
---|
| microsoftazure.appKey=
microsoftazure.appKeySecret=
microsoftazure.oauthVersion=2.0
microsoftazure.oauth20.refreshToken=https://login.microsoftonline.com/{domain}/oauth2/v2.0/token
microsoftazure.oauth20.authorize=https://login.microsoftonline.com/{domain}/oauth2/v2.0/authorize
microsoftazure.oauth20.accessToken=https://login.microsoftonline.com/{domain}/oauth2/v2.0/token
microsoftazure.SecretId=
microsoftazure.scope=openid offline_access https://storage.azure.com/user_impersonation
microsoftazure.enableProduction=true |
- Save the file.
- Restart the Connect Portal.
Changes in Web.xml file- Go to the location …<ConnectPortal>\conf.
- Open the web.xml file in a text editor.
In the filter section, add the following code snippet just after the </init-param> tag that follows <param-value>SAMEORIGIN</param-value>. Code Block |
---|
| <init-param>
<param-name>hstsMaxAgeSeconds</param-name>
<param-value>31536000</param-value>
</init-param>
<init-param>
<param-name>hstsIncludeSubDomains</param-name>
<param-value>true</param-value>
</init-param> |
- Save the file.
Changes in securityContext.xmlGo to …<ConnectPortalInstallFolder>\ConnectPortal\resources_config\saml location. Open securityContext.xml file. Update the xsi:schemaLocation attribute as shown in the following code snippet. Code Block |
---|
| xsi:schemaLocation="http://www.springframework.org/schema/beans classpath:org/springframework/beans/factory/xml/spring-beans.xsd
http://www.springframework.org/schema/security classpath:org/springframework/security/config/spring-security-5.7.xsd |
|
...
http://www.springframework.org/schema/context classpath:org/springframework/context/config/spring-context.xsd"> |
- Save the file.
Changes in launcher.propertiesGo to …<ConnectPortalInstallFolder>\ConnectPortal\conf location. - Copy the launcher.properties file from patch location, and paste it at …<ConnectPortalInstallFolder>\ConnectPortal\conf location.
- Open the copied file and make the same manual changes in the file that you have done in your previous launcher.properties file (that you had saved as a backup).
Save the file.
|
Anchor |
---|
| Verifying Connect Portal patch |
---|
| Verifying Connect Portal patch |
---|
|
Verifying Connect Portal patch
...
- Click Configure > Developer Studio > Proceed.
If you are able to interact with the Connect Server interface, it indicates that the Connect Server is updated.
Tip |
---|
In case you need to recover the patch, refer to this page. |