Licensing in MobileFirst Server

improve this page | report issue


The IBM MobileFirst Server supports two different licensing methods based on what you have purchased.

If you have purchased Perpetual licenses, you can consume what you have purchased and verify your usage and compliance through the License tracking page in the MobileFirst Operations Console and through License Tracking report. If you have purchased Token licenses, configure your MobileFirst Server to communicate with a remote token license server.

Application or Addressable Device licenses

If you have purchased Application or Addressable Device licenses, you can consume what you have purchased and verify your usage and compliance through the License tracking page in the MobileFirst Operations Console and through License Tracking report.

Virtual Processor Cores (VPC Licensing)

Mobile Foundation is also available with capacity-based licensing called Virtual Processor Cores (VPC). VPC is a unit of measurement that is used to determine the licensing cost for Mobile Foundation and is based on the number of cores that are available. Currently, this metric is available only for Cloud Pak for Applications.

The features of this metric are as follows,

  • Clients can run any number of applications and devices. Hence this form of license would be beneficial compared to Application license in scenarios where customers have many apps in their deployment.

  • Aligned with other products in the portfolio and provide flexibility to clients for hybrid cloud deployments.

Token Licensing

In a token environment, every product consumes a predefined token value per license, compared to a traditional floating environment where a predefined quantity per license is consumed. The license key has a pool of tokens from which the license server calculates the tokens that are checked in and checked out. Tokens are either consumed or released when a product checks in or checks out licenses from the license server.

Your licensing contract defines whether you might be able to use token licensing, the number of tokens available, and features that are validated by tokens. See Token license validation.

If you have purchased token-based licenses, install a version of the MobileFirst Server that supports token licenses and configure your application server so that your server can communicate with the remote token server. See Installing and configuring for token licensing.

With token licensing, you can specify the license app type in the application descriptor of each one of your apps before deploying them. The license app type can be either APPLICATION or ADDITIONAL_BRAND_DEPLOYMENT. For testing, you can set the value of the license app type to NON_PRODUCTION. For more information, see Setting the application license information.

The Rational License Key Server Administration and Reporting tool that is released with Rational License Key Server can administer and generate reports for the license consumed by Mobile Foundation. You can identify the relevant parts of the report by the following display names: MobileFirst Platform Foundation Application or MobileFirst Platform Additional Brand Deployment. These names refer to the license app type for which the tokens are consumed. For more information, see Rational License Key Server Administration and Reporting Tool overview and Rational License Key Server Fix Pack 9 (

For information on planning to use token licensing with MobileFirst Server, see Planning for the use of token licensing.

To obtain the license keys for Mobile Foundation, you need to access IBM Rational License Key Center. For more information about generating and managing your license keys, see IBM Support - Licensing.

Inclusive terminology note: The Mobile First Platform team is making changes to support the IBM® initiative to replace racially biased and other discriminatory language in our code and content with more inclusive language. While IBM values the use of inclusive language, terms that are outside of IBM's direct influence are sometimes required for the sake of maintaining user understanding. As other industry leaders join IBM in embracing the use of inclusive language, IBM will continue to update the documentation to reflect those changes.
Last modified on November 04, 2019