Unsupported content

 

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Example - Creating a site license type (basic mode)

This procedure provides an example to show you how to create a custom license type in basic mode based on the default Site license type.

To create a custom license type in basic mode

  1. From the Application Administration Console, click the Custom Configuration tab.
  2. From the Application Settings list, choose Asset Management > Advanced Options > Configure License Type, and then click Open.
    The Configure License Type dialog box appears.
  3. Click Create.
    The license type wizard starts.
  4. Update the Create License Type page as follows:
    1. Select Global as the company.
      This makes the license type available to all companies.
    2. Enter Site Example as the name for the license type.

      Note

      Do not name this license type Site because that license type already exists in the system.

    3. Enter the following description for the license type: Example site license that includes all software from a manufacturer being used by a specific site.
      By default, the status is set to Draft.
    4. For Groupable, select No.
    5. For License Type Mode, select Basic.

      Note

      After a license type is created, it has to be enabled. This example shows you how to that in a later step.

      The following figure shows what the Create License Type page should look like:


  5. Click Next.
  6. Update the Connection Questions page as follows:
    1. For Question, enter text that prompts for the product name: Enter certificate site.
    2. For Field Type, select Char.
    3. For the CI Grouping, select Computer System.
      You select Computer System instead of Software because computer systems, and not CIs, are usually updated with Site because there are typically fewer of them.
    4. Click the Sequence up arrow to make the sequence 1.
      The following figure shows what the Connection Questions page should look like with the information filled in:


  7. Click Add.
    The connection question is added to the list.
  8. Click Next.
  9. Update the Map Connection Attributes page of the license type wizard as follows:
    1. For the CI Type, select Computer System.
    2. For the Attribute, select the database name, in this case Site.
      This mapping needs to be made so the system can return the list of computer systems that have a site name that matches the site name entered (in answer to the connection question created earlier) when the certificate is created. The next sections in this example show you how to build the compliance questions and actions that are used to determine compliance.
    3. Click Map Attribute.
      The mapping is added as shown in the following figure:


  10. Click Next.
  11. On the Compliance Questions page that appears, build the first compliance question as follows:
    1. Enter the following question: Number of products deployed.
    2. For Field Type, select Int.
    3. For Sequence, select 1.
      This indicates the sequence in which the question is asked when the license certificate is created.
    4. Since this compliance question is updated later by an update action, select Yes for Computed Value.
    5. For Field Visibility, select Visible Read/Write.
      The field visibility needs to be set to read/write access because this field is updated by a value entered when the license certificate is created.
      The following figure shows how the Compliance Questions page should look:


    6. Click Add.
      The question is added to the list.
  12. Click Next.
    The next section of the example shows how to create the actions that work with the compliance question to determine whether the list of certificates retrieved by the connection question and its mapping are compliant.
  13. On the Compliance Actions page of the create license wizard, select Get in the Action field and then click Create.
    The Get Action dialog box is displayed.
  14. Build the Get action as follows:
    1. Enter the following name for the Get action: Get deployed products. This action retrieves the number of deployed licenses from the list of certificates returned by the connection question and mapping configured earlier.
    2. Select AR as the source from which to retrieve the information.
    3. In the Target field, enter the name of the form from which to retrieve the information: CTR:Contract_Relationship. This form holds all connection information stored for processed connection questions.

      Tip

      You configure a license type with the conditions that will be present at the time the license certificate is created. The CTR:Contract_Relationships form will be populated with the information that this Get action needs at that time.

    4. For this license type, you want to count the number of deployed licenses, so select Count as the type.
    5. From the Rule list, select GetCertificates > instanceId, as shown in the following figure, to start the rule count to retrieve the number of license certificates:


    6. From the Operator list, select =.
    7. From the Value list, select Child Instance ID*.
      The WHERE field now contains GetCertificates.instanceId = 'Child_Instance_ID' as shown in the following figure:


    8. Click Save.
      The Compliance Actions page of the license wizard is redisplayed and the Get action appears in the list:


      In order to display the results of the Get action and set the compliance flag, you must build an update action.
  15. From the Action list, select Update and then click Create.
  16. Build the update action as follows:
    1. Enter the following name: Update Compliance.
    2. For the Source, select Compliance Question.
    3. From the Set list, select Number of products deployed.
      This value indicates that the question field should be updated based on the count retrieved in the Get.
    4. In the Set Value From field, select Rule.
    5. From the Value list, select Get Questions > Number of products deployed, as shown in the following figure:


    6. Click Add.
  17. Create a second update action in which you set the compliance flag to return a true or false to indicate whether the licenses are compliant. Leave the Update dialog box open and complete the rest of the steps.

    Tip

    For the Site default license type, and if a site licenses exists, it is compliant because all of the license certificates fall under the site license. That means the compliance flag can be set to 1, indicating true for compliance.

    1. For the Source, select AR.
    2. From the Set list, select ComplianceFlag.
      This value indicates that the question field should be updated based on the count retrieved in the Get.
    3. In the Set Value From field, select Constant.
    4. In the Value field, enter 1.
      The compliance flag is set to 1 because this is the true setting and the site license is compliant.
      The Update Action dialog box should appear as shown in the following figure:


    5. Click Add.
      Both update actions appear in the list.
  18. Now build the WHERE qualifier for the update action:
    1. In the Matching Requests list, select Modify all matching records.
    2. From the Rule list, select GetCertificates > instanceId.
      This is added to the WHERE field as the clause starts to be built.
    3. From the Operator list, select =.
    4. From the Value list, select Certificate_InstanceId.
      The WHERE qualifier should look like the following figure:


  19. Click Save.
    The Compliance Actions page of the license wizard is redisplayed and all of the compliance actions appear in the list, as shown in the following figure:


  20. Click Done.
  21. At the prompt, click Yes to create the license type.
    The license type is created and displayed in the list in the Configure License Type dialog box, as shown in the following figure:


    By default the license type is created in draft mode.
  22. To enable the license type, select it and click Enable.
  23. Click Close.

Related topic

Default system license types

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments