Versions Compared

Version Old Version 8 New Version Current
Changes made by

Ashhad Alam

Ashhad Alam

Saved on

Key

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

...

There are two methods to activate the license – automatic and manual. Before you activate the license, make sure that you have placed the valid License.jar in the shared/ext license folder.

Automatic Activation

...

Info
You must have at least one machine outside the cluster on which the Adeptia License server (license.adeptia.com) is whitelisted and accessible.
  1. Log in Go to Adeptia Connect Portal. 
    This will open a Manual License Activation page.

  2. Generate the token.
  3. Copy the token, and do the following.
    1. Open internet browser and visit https://license.adeptia.com/#activate.
    2. Provide your name and email id.
    3. Paste the token in the Activation token box.
    4. Click Submit to generate the Activation Key.
    5. Copy the generated Activation Key.
    6. Paste the Activation Key on the Manual License Activation page in step 3.
  4. Click Submit.

...

CategoryScenarioEffect
Hard violation
  • The license has expired
  • The installation date has been modified
  • The license authentication has failed (License server call)
  • The runtime container count has exceeded the set limit
  • The runtime core for a container has exceeded the set limit
  • The Soft violation grace period is over

  1. All runtime pods/containers pause the process flow execution.

    Warning
    titleException
    • If the runtime container count exceeds the set limit, the execution of the process flows on the latest container is paused. The execution of the process flows in the remaining containers that do not violate the set runtime container count is not paused.
    • If the runtime core exceeds for a container, the process flows being executed on that container will be paused. The execution of the process flows in the remaining containers that do not violate the set runtime core is not paused.


  2. Webrunner shows the relevant message in the "Notification Message Center".
  3. The application logs the message in the microservices logs.
Soft violation

The Soft violation occurs when any of the following parameters exceeds its set limit:

  • The user count
  • The Process Flow count
  • The Activities count
  • The Group count
  • The Trading Partner count
  • The Relationship count
  • The Data Interface
  • The Hub user count
  • The Partner user count
  • Partner count
  1. Webrunner shows the relevant message in "Notification Message Center".
  2. The application logs the message in the microservices logs.

...