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 14 Current »

This section helps you upgrade from Adeptia Connect version 3.7.1 to Adeptia Connect version 3.7.2. Patch details applicable for this upgrade are discussed in the Patch details section that follows.

To upgrade, you need to apply the following patches in the sequence given below. Before you apply the patch, make sure that you have met the prerequisites discussed on this page.

  1. Connect Server patch
  2. Connect Portal patch 

Important

  1. As this patch includes a major JRE upgrade (JRE v17), it is recommended that you apply this patch to a test environment before applying it to production.
  2. The upgrade to Java 17 may require you to handle the conflicts that may occur with custom jars or custom classes. You may come across the following scenarios wherein you need to take the necessary actions to address the conflicts. 

    1. Java packages used in the custom plugins, custom jars, or custom classes may have changed. To address this issue, you need to change the custom plugins, custom jars, and the custom classes accordingly.

    2. Classes used in custom plugins, custom jars, or custom classes may have been deprecated or their implementation may have changed. To address this issue, you need to change the custom plugins, custom jars, and the custom classes accordingly.

    3. Although Java 17 is backward compatible – code compiled with Java 8 continues to run on Java 17 most of the time – there are certain restrictions implemented in Java 17, for example, Java 17 restricts the use of certain packages and reflections. However, you can override these restrictions by adding the required entries in the launcher.properties file.

    4. External jar(s) in the ext folder may not be compatible with the upgraded versions of the framework. In this case, jars need to be upgraded accordingly.

  3. With an upgrade to JRE v17,

    1. The SAML implementation in Adeptia Connect has got configuration changes. To learn more about SAML in Adeptia Connect, refer to this document.

    2. The JMS provider that connects to Apache Active MQ JMS server uses the two jars activemq-core-5.7.0.jar and geronimo-j2ee-management_1.1_spec-1.0.1.jar. Ensure that:

      1. You use these two jars when you create a JMS provider that connects to Apache Active MQ JMS server.

      2. You have updated any existing JMS provider that connects to Apache Active MQ JMS server to use these two jars.
        For more details, refer to this page.

  4. This patch can be applied only to Adeptia Connect version 3.7.1. If you are using product version 3.7 or earlier, you should upgrade to v3.7.1 before applying this patch. Click here to upgrade Adeptia Connect to version 3.7.1.

Patch details

Adeptia Connect Patch Name:  AdeptiaConnect_3_7_2_04June2023.zip   

Connect Server Build Tag:        Release_AC_3_7_2_01June2023        

Connect Portal Build Tag:        Release_AC_Web_3_7_2_01June2023     

                              

This patch can be applied on the following Build Tags: 

Connect Server

  • Release_AC_3_7_01_03Nov2022
  • Release_AC_3_7_01_01_16Dec2022
  • Release_AC_3_7_01_02_11Jan2023
  • Release_AC_3_7_01_03_31Jan2023
  • Release_AC_3_7_01_04_22Feb2023
  • Release_AC_3_7_01_05_14Mar2023
  • Release_AC_3_7_01_06_06Apr2023
  • Release_AC_3_7_01_07_26Apr2023

Connect Portal 

  • Release_AC_Web_3_7_01_03Nov2022
  • Release_AC_Web_3_7_01_01_16Dec2022
  • Release_AC_Web_3_7_01_02_11Jan2023
  • Release_AC_Web_3_7_01_03_31Jan2023
  • Release_AC_Web_3_7_01_04_22Feb2023
  • Release_AC_Web_3_7_01_05_14Mar2023
  • Release_AC_Web_3_7_01_06_06Apr2023
  • Release_AC_Web_3_7_01_07_26Apr2023


  • No labels