Applying patch on Connect Server

Owned by Akash Kumar Jaiswal (Unlicensed)
Last updated: Sept 23, 2020Version comment

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

Though every release of SecureBridge 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

  • You have Read and Write permissions on all subfolders and files of .../AdeptiaConnect-<Version>.
  • Services such as Kernel, WebRunner, and AIMap are stopped.

Applying the patch

For Windows

  1. Download the latest patch from the provided URL.
  2. Extract the downloaded zip file in a folder.
  3. Open the Command Prompt.
  4. Go to the folder where you have extracted the zip file.
  5. Run the following command to apply the patch:

    Apply-Patch.bat “<Path where Adeptia Connect is installed till AdeptiaServer folder>” 

    For example:

    Apply-Patch.bat "C:/Program Files/AdeptiaConnect/AdeptiaConnect-x.x/ConnectServer/AdeptiaServer"

  6. Once the patch is applied, a confirmation message is displayed.

    Note: While applying the patch you may come across following warning messages that you should ignore.

    Warning: Not deploying connect2.0 accelerator because no change list is present.
    Warning: Not deploying EDI accelerator because no change list is present.

  7. Start the services, i.e. Kernel, WebRunner, and AIMap.

For Linux

  1. Open the Terminal.
  2. Download the latest patch from the provided URL.
  3. Extract the downloaded zip file in a directory.
  4. Go to the directory where you have extracted the zip file.
  5. Run the following command to apply the patch:

    ./Apply-Patch.sh <Path where Adeptia Connect is installed till AdeptiaServer folder> 

    For example:

    ./Apply-Patch.sh /mnt/AdeptiaConnect-x.x/ConnectServer/AdeptiaServer

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

    Note: While applying the patch you may come across following warning messages that you should ignore.

    Warning: Not deploying connect2.0 accelerator because no change list is present.
    Warning: Not deploying EDI accelerator because no change list is present.

  7. Start the services, i.e. Kernel, WebRunner, and AIMap.

After you have applied the patch, PatchApplicationLog_<Date>.log file is created inside the logs folder. The logs folder is available in the same folder from where you have applied the patch. PatchApplicationLog_<Date>.log file contains the logs generated during patch application and can be used to troubleshoot any issue related to the patch application.

Patch application may take some time, in case there are a large number of records in the backend and log database.

The patch will automatically rollback, in case of any error during the deployment.

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

Post patch deployment steps

Changes in AgentContext.xml file

After deploying the patch, update database configuration in AgentContext.xml file to store heartbeat and other agent operation in the database. To update this file, follow the steps below:

  1. Go to …<ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\etc location.
  2. Open AgentContext.xml file.

  3. Set the following properties based on your environment.

    If you are going to use a separate backend database for the Agent, you need to create the database and update this file with new database property. Or, you can use the existing backend database of Adeptia Connect and use its properties to update this file.

    Under "dataSourceAgent" section, update the following properties:



    1. Update the property "jdbcUrl", for example, in case of MySQL being used as a backend database, the format of jdbcUrl will be jdbc:mysql://<hostname>:<port no.>/<DB Name>?useSSL=false.
      Here,
      Hostname: Name/IP address of the database server.
      Port No.: Port number of the database.
      Database name: Name of the database.

      If you are using SQL or Oracle as a backend database, the format of jdbcUrl will be:

      SQL
      jdbc:sqlserver://<hostname>:<port no.>;DataBaseName=<DB Name>

      Oracle
      jdbc:oracle:thin:@<hostname>:<port no.>:<DB Name>

    2. driverClass: Update the driver class name, for example, "com.mysql.cj.jdbc.Driver" if MySQL database is used. 

      If you are using SQL or Oracle as a backend database, update the value of driverClass as:

      SQL
      com.microsoft.sqlserver.jdbc.SQLServerDriver

      Oracle
      oracle.jdbc.OracleDriver

    3. user: Enter the user name.
    4. password: Enter the password.

    5. dataSourceName: Enter the backend database name.

      You can define rest of the properties based on your requirement.

  4. Under "AgentEntityManagerFactory" section, update the "hibernate.dialect" property.

    "hibernate.dialect" property for each database is as follows:

    MySQL
    org.hibernate.dialect.MySQL5InnoDBDialect

    SQL
    org.hibernate.dialect.SQLServerDialect

    Oracle
    org.hibernate.dialect.Oracle10gDialect

  5. Save the file.

Changes in hubConfiguration.properties file

Configure email notification property, recipientsEmail, in hubConfiguration.properties file. 

  1. Go to …<ConnectServerInstallFolder>\AdeptiaServer\ServerKernel\etc location.
  2. Open hubConfiguration.properties file.

  3. Set the "recipientsEmail" property with the email id of the recipient. 



    You can also update other properties like mailBodyContenType, mailSubject, mailBodyHeader, and mailBodyFooter based on your requirements. 
  4. Save the file.

Next

Applying patch on Connect Portal