This section discusses how you can activate Adeptia Connect by registering a valid license.

Activating license

License activation is required when you purchase a license for the first time or renew an expired license.

Adeptia Connect is installed with 60 days trial license. After 60 days of using the trial license, you need to purchase the license according to your requirement for using the application.

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/license folder.

Automatic activation

If Adeptia License server (license.adeptia.com) is whitelisted and accessible in your cluster, you need to restart the license microservice, and the license will be assigned/registered automatically.

Manual activation

If Adeptia License server (license.adeptia.com) is not whitelisted and accessible in your cluster, follow the steps given below to activate the license manually.

You must have at least one machine outside the cluster on which the Adeptia License server (license.adeptia.com) is whitelisted and accessible.

Go to Connect Portal.
This will open a Manual License Activation page.
Generate the token.
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.
Click Submit.

License violation

The following table encapsulates the scenarios of license violation and their effects. The violations can fall under either Hard or Soft violation category.

Category

Scenario

Effect

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

All runtime pods/containers pause the process flow execution.
Exception
- 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.
Webrunner shows the relevant message in the "Notification Message Center".
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

Webrunner shows the relevant message in "Notification Message Center".
The application logs the message in the microservices logs.

Soft violation has a grace period of 15 days. If it is not resolved in limit, it is treated as Hard violation.
The Message Center may continue to show the warning regarding Soft and Hard violation of license for up to one hour of resolving the violation.

Browser not supported