License expiry scenario
  • 25 Apr 2022
  • 1 Minute to read
  • Dark
    Light
  • PDF

License expiry scenario

  • Dark
    Light
  • PDF

In the license expiry scenario, we recommend the user to perform the following actions, if you are not using Atomic Scope.

1. BizTalk Artifacts:

Whenever a message is passed through atomic scope pipeline, it will try to track the transaction.
In this license expiry case, it won't track the messages & will log license invalid error in log table in atomic scope.

  • Remove the Atomic Scope Pipelines and Atomic Scope Activities in your custom pipeline from BizTalk Applications and use the BizTalk pipelines.
  • Replace the Atomic Scope pipelines from your ports with your own pipelines
  • In Visual Studio, remove Atomic Scope pipeline components from your custom pipelines (and redeploy)
  • In Visual Studio, remove calls to the Atomic Scope .NET classes from your orchestrations (and redeploy)
  • Make sure your applications are running without any Atomic Scope components and confirm if all the integrations are working fine.
  • Completely uninstall the Atomic Scope (Web, Atomic Scope Services) and delete the Atomic Scope database.

2. Azure Entities:

Whenever a message is available in queue, atomic scope will try to process & track it.
But if license is expired, then message won't be tracked & license invalid error will be logged in log table in atomic scope. So it is advisable to remove the atomic scope connectors & replace it with custom connectors in logic apps or disable the atomic scope connectors in the stages in the logic apps.

  • Remove the Atomic Scope connectors in the Logic Apps workflow.
  • Delete the Atomic Scope Service Bus that are used to process the messages

Was this article helpful?