Updating licenses for all nodes in an instance - assure_mimix - Latest

Assure Unified Interface Guide

Product type
Software
Portfolio
Integrate
Product family
Assure
Product
Assure MIMIX™ Software for AIX
Version
Latest
Language
English
Product name
Assure Unified Interface
Title
Assure Unified Interface Guide
Copyright
2021
First publish date
2010
Last updated
2024-02-09
Published on
2024-02-09T05:11:34.582000

You can update licenses for all nodes within an instance of a product in one action.

Do the following from the Home page:

  1. Select License Summary from the global action menu from the Portal Connections portlet.

  2. From the License Summary window, select Update Instance Licenses from the global menu.

  3. A wizard opens, prompting you to select an instance, then click Next. Only instances of products that support portal license management through portal applications deployed on the Assure UI server are available for selection.

  4. If you are prompted to select a portal connection, the default value is the primary portal connection for the instance. Click Next.

    Note: Note:For products such as MIMIX that limit communications among nodes based on their node roles, the instance should be configured so that the primary portal connection in the instance domain is also a management node. If you select a portal connection that is a network node, you will only be able to update the licenses on that node and on management nodes.
  5. If you are prompted to log in to a node, provide a password for the ID specified in the portal connection.

  6. The Options panel prompts you to either get keys from Precisely or use existing keys and identify a location where the license key package (LKP) exists. Make your selection, then click Next.

  7. The Summary panel lists the products whose license from the LKP were applied to the nodes in the instance. The list of licenses displayed may not identify all of the updated licenses if the wizard has not received details about which licenses were updated. For a MIMIX license, this can occur if a system manager process between the node to which you are connected and another node in the MIMIX instance has a backlog or is not active. Click Finish.