This documentation supports the 21.05 version of Action Request System.
To view an earlier version, select the version from the Product version menu.

Application licensing example

In this example, XYZ Corporation, an ISV, created an application, MusicManager, that they want to license for sale. The following steps describe the process to license their application. Typically, ISVs perform step 1 through step 3. Customers who purchase the application perform steps 4 and 5.

  1. Create the MusicManager application with its accompanying forms.
  2. Register your application name with BMC.
    BMC applications must have unique names. To avoid potential licensing conflicts, use this naming convention:
    vendorName:applicationName
    In this example, the name is XYZ:MusicManager.
    Usually, you do not need to worry about conflicts with naming conventions for your application. Even if XYZ has a competitor with its own MusicManager application, the vendor name prefix guarantees uniqueness in most cases.
    If you have questions, go to the Customer Support website ( http://www.bmc.com/support Open link ) and verify that the application name is unique or has not been used by another application developer in your company.
  3. Designate the application as licensable.
    You can make your application Application licensable or Application and form licensable, as described in Making applications licensable for integration system vendors:
    • Customers need application licenses to access the form data in the application.
    • Customers need user fixed or user floating licenses based on individual forms to access form data.
      In this example, XYZ Corporation makes the MusicManager application licensable and user licensable. The MusicManager application includes these forms: MusicManager Configuration, MusicManager Songs, and MusicManager Singers. When customers try to access data in any of these forms, they receive an error if they do not have a valid MusicManager application license.
      Further, XYZ Corporation makes only the MusicManager Songs form user licensable (shown in Making applications licensable for integration system vendors). If users try to submit or modify data in this form, they receive an error if they do not have a MusicManager user license (fixed or floating). Because the ISV does not make the MusicManager Singers form user licensable, any user can create or modify MusicManager Singers without a MusicManager user license.
  4. (Customers only) In the AR System Administration Console, click System > General > Add or Remove Licenses to add the license to your AR System server .
  5. (Customers only) If your application is user licensable, assign application user licenses to your users so that they can access the user licensable portions of the application (the user licensable forms).
    To do this, open the User form in the AR System Administration Console and assign licenses to specific users. After users are given the appropriate application user licenses, they can access the application and its forms in the usual manner. For information, see Assigning application licenses to users.
Was this page helpful? Yes No Submitting... Thank you

Comments