info@techygeekhub.com
+011-40071137,+91-9310947352

Blog Post

Boomi
_ _ Sowjanya gurrala

BOOMI LICENSING

Integration Editions:

Boomi offers different tiers of subscriptions called Integration Editions. When you purchase integration, you have a choice of these editions to choose from.

The following editions are available:

  • Personal Edition (30day free trial)
  • Base Edition
  • Professional Edition
  • Professional Plus Edition
  • Enterprise Edition
  • Enterprise Plus Edition

Note: The Integration Edition doesn’t change how the licensing works but it may affect services that can be available with the particular edition.

To know in detail about Integration Editions go through the link below

https://help.boomi.com/bundle/integration/page/c-atm-AtomSphere_Editions.html

Licensing:

What is Licensing?

 In the context of Boomi, Licensing refers to the process of obtaining the legal rights to use the Boomi integration platform and its associated services.

How licenses are calculated?

  • In Boomi, licensing is calculated based on 3 categories
  1. Connections
  2. Cloud Usage
  3. API Usage
  • The licenses are calculated only upon deployment.
  • You can have as many connections in the build tab as you want, they are not counted since they are not deployed. 
  • Your account will be provisioned with some number of connection licenses based on how many you purchased while creating a subscription.
  • The number of licenses you have is the number of connections you can deploy across all of your integration processes. 
  • Licenses are calculated separately for Test and Production environment.

To view the licensing details in Boomi:

Step 1: Log onto the Boomi platform (https://platform.boomi.com/) with the required credentials (Email Address and Password).

Step 2: Under Services choose Integration

Step 3: Go to settings tab and choose Account Information and setup

Step 4: click on licensing tab. Here we can see different tabs (Connections, Cloud Usage, API Usage).

This page allows us to view all licenses that have been purchased. We can view the number of deployed and available connections along with details of cloud usage and API usage.

Now we discuss in detail about each category.

1. Connections:

 The rule of thumb is one license per unique connection per runtime (atom, molecule, or cloud). A unique connection is determined by the component ID.

  • Under the connections tab, we can see the Connection licenses for a particular account including how many were deployed and how many are available.
  • In order to identify the Production and Test environment licenses uniquely, Test environment licenses are indicated as (Test).
  • Under connections tab, we can see connections by class and connector class.

About connector class:

  • Connection licenses are categorized and provisioned by connector classes: Small Business, Standard, Enterprise, and Trading Partner.
  • The class doesn’t change how licenses work, they would just be counted under that specific class pool if they fall into that category. Examples of classes:
  • Small Business – QuickBooks, Sage 50/Peachtree

          2.Standard – the majority of connections fall under this category, SFTP,                                                       .                              Disk, Mail, Salesforce, NetSuite, HTTP Client, Web Services.                              server, database, web services SOAP Client.

3.Enterprise – SAP, Oracle E-Business

           4.Trading Partner – your trading partners’ profiles, each trading partner             .                      component is counted as a license not each of the communication                              .                     types inside of it

  • According to the requirement we have to purchase the licenses separately for each connector class.

Example Scenario1:

As here we are using a database connector, when we deploy this process then

the licenses are calculated from standard connector class.

Scenario2:

Suppose we want to deploy a process having SAP connector. But we haven’t purchased the licenses for Enterprise connector class. Then in this scenario deployment will not be successful.

Note: There are certain connectors that do not affect your license count. You can deploy the following connectors an unlimited number of times across different atoms and environments.

  • AS2 Shared Server connector
  • Boomi Atom Queue connector
  • Atmosphere API connector
  • Atmosphere Partner API connector
  • Boomi Master Data Hub connector
  • Boomi Master Data Hub Listener connector
  • Flow Services Server connector
  • MLLP Server connector
  • Web Services Server connector

Trading Partner:

  • Trading Partner is used to manage B2B requirements. It’s a way to conduct Direct EDI or point-to-point e-business transactions by designating a host partner and a remote partner who connect through an agreed-upon communication protocol.
  • We have different configurations in which a start shape can be configured. One of them is Trading Partner. We can see in the below image.
  • We can see there are different options like communication method,

My Standards and Trading Partner list.

Note: Licensing will not depend on Communication method.

  • In Trading partner, we will configure My Standards and Trading Partner list.
  • Licensing is calculated per unique partner connection.

Example 1:

In the below image, we have configured one my company under My Standards and one Trading Partner under Trading Partner List.

So, in this scenario it will cost only one License.

    Example 2:

    In My Standards we have configured one My company and under Trading            

     Partner List we have configured two different trading partners.

     In this scenario it will consume 2 licenses. (see the image below)

2. Cloud Usage:

  • The cloud usage tab in Licensing shows your account’s total usage of each Atom Cloud.
  • Each Atom Cloud can process up to 1 GB of volume per month at no charge. Additional charges may be applied when you exceed this limit.
  • Total Usage is calculated using the formula (data in + data out) /2

The following details apply to your volume usage:

  • The sum is the total document size that flows through connector steps. Data flowing through connector call lookups, such as Map functions, are not counted.
  • Each Atom Cloud can process up to 1 GB of volume per month at no charge. Additional charges may be applied when you exceed this limit.
  • Web services listen operations and return document steps, which are treated as inbound and outbound connectors, are counted towards volume usage.
  • Low latency process data is counted towards volume usage even though these executions are not reported in Process Reporting.
  • Local Atoms are not counted in volume usage.

Current Usage

Shows the volume of data in MB processed on the selected Atom Cloud for the account in the current month.

Projected Usage

Shows the current month’s projected usage based on the account’s current monthly volume. This is calculated as: ((current usage/current day of the month) * number of days in the month).

Usage History

Shows by year and by month the volume of data in MB processed on the selected Atom Cloud for the account.

3.API Usage

  • The API Usage tab in Licensing shows your account’s total number of API calls.
  • For each year, you can view the usage by month.
  • We can make 10 API calls per/sec for free. If we exceed this limit we need to pay.

References:

♥152

Author

Sowjanya gurrala

Leave a comment

Your email address will not be published. Required fields are marked *