Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Corrected links that should have been relative instead of absolute.

New features and improvements

...

  • REST API requests and responses logging 
    You can now configure the application to log the REST API requests and responses. To enable this, set the property logging.api.enabled to true. You can find this property by navigating as follows:
    Account > Microservice Settings > RESTAPIService > Logging.

  • User-friendly names for microservices 
    Names of the following microservices have been modified to make them more user-friendly. 

    Sl. No.Old nameNew name
    1webrunnerac-webrunner
    2portalac-portal
    3eventac-event
    4listenerac-listener
    5webapp-gatewayac-webapp-gateway
    6aimapac-aimap
    7api-gatewayac-api-publisher-gateway
    8rest-apiac-rest-api-publisher
    9soap-apiac-soap-api-publisher
    10licenseac-license
    11runtimeac-runtime
    12archival-and-cleanupac-archive-and-cleanup
    13autoscalerac-autoscaler
    14rabbitmqac-rabbitmq


  • Updated keystore
    The bundled keystore adeptiaBPM.keystore is now updated to remove some of the unsupported algorithms.

  • Improved application monitoring
    Latest environment variables required for Adeptia Connect application monitoring through the Datadog are added in the helm chart.

  • Support for zip and perl commands
    The application now supports the use of zip and perl commands in the runtime container.

...

  • In case of Synchronous API requests, you can make Adeptia Connect to first check if the runtime pod has enough CPU, or memory, or both available to be considered ready to accept any more request. The application performs this check by using the following two configurable threshold properties for runtime. For more details, click here.

    • readiness.probe.cpu.threshold
    • readiness.probe.memory.threshold
  • Adeptia Connect now allows you to define whether you want the pod autoscaling to happen based on cpu or memory or both. To achieve this, you need to set the value for the variables, type and RUNTIME_AUTOSCALING_TYPE in the global values.yaml file. For more details, click here.

Bug fixes

  • The Azure Blob Event picked up all the files even when its Trigger Type was set to "new and updated files".

...