Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

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

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. 

Prerequisites

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

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

Applying the patch

 For 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-x.x/ConnectPortal"
     
    Once the patch is applied, a confirmation message will be displayed. 
 For 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.

After applying this patch, refer to post patch deployment section for manual changes.

Post patch deployment steps

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.

 When upgrading from AC v3.7

Upgrading from AC v3.7

Changes in launcher.properties

  1. Go to …<ConnectPortalInstallFolder>\ConnectPortal\conf location.

  2. Copy the launcher.properties file from patch location, and paste it at …<ConnectPortalInstallFolder>\ConnectPortal\conf location.
  3. 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).

  4. Save the file.

 When upgrading from AC v3.6.11

Upgrading from AC v3.6.11

Changes in securityContext.xml

  1. Go to …<ConnectPortalInstallFolder>\ConnectPortal\resources_config\saml location.

  2. Open securityContext.xml file.

  3. Update the xsi:schemaLocation attribute as shown in the following code snippet. 

    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">
  4. Save the file.

Changes in launcher.properties

  1. Go to …<ConnectPortalInstallFolder>\ConnectPortal\conf location.

  2. Copy the launcher.properties file from patch location, and paste it at …<ConnectPortalInstallFolder>\ConnectPortal\conf location.
  3. 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).

  4. Save the file.

 When upgrading from AC v3.5.24

Upgrading from AC v3.5.24

Changes in apps.properties file

  1. Go to …<ConnectPortalInstallFolder>\resources_config location.

  2. Open apps.properties file.

  3. Below the Facebook section in the file, add the following code block for Microsoft Azure.

    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
  4. Save the file.
  5. Restart the Connect Portal.

Changes in Web.xml file

  1. Go to the location …<ConnectPortal>\conf.
  2. Open the web.xml file in a text editor.

  3. In the filter section, add the following code snippet just after the </init-param> tag that follows <param-value>SAMEORIGIN</param-value>. 

    <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>
  4. Save the file.

Changes in securityContext.xml

  1. Go to …<ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\etc\saml location.

  2. Open securityContext.xml file.

  3. Update the xsi:schemaLocation attribute as shown in the following code snippet. 

    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">
  4. Save the file.

Changes in launcher.properties

  1. Go to …<ConnectPortalInstallFolder>\ConnectPortal\conf location.

  2. Copy the launcher.properties file from patch location, and paste it at …<ConnectPortalInstallFolder>\ConnectPortal\conf location.
  3. 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).

  4. Save the file.

Verifying Connect Portal patch

To verify if the Connect Portal has been deployed successfully, login to the portal and check the build tag of the Connect Portal.

Follow the steps below to check the build tag:

  1. Click Help > About.
  2. On the About screen, check the Connect Portal tag. 
    If the build tag matches the tag of the Connect Portal, it indicates that the Connect Portal patch is deployed successfully.

Additionally, to verify if the user interface of the Connect Server is working as expected, follow the steps below:

  • Click Configure > Developer Studio > Proceed.
    If you are able to interact with the Connect Server interface, it indicates that the Connect Server is updated.


In case you need to recover the patch, refer to this page.




  • No labels