Proper license types are not generated

Issue Symptom

The license job is not running properly.

Issue Scope

When you use the license type wizard to create a license type, a set of rules is generated in the License Engine forms and stored as metadata. These forms start with a prefix of RLE. When License Engine runs, it executes these rules.

Resolution

• Make sure the rules have been properly set up; see Configuring-license-types.
• Ensure that the correct qualifications have been defined; see Managing-jobs-that-automatically-attach-CIs-to-license-certificates. 
• Make sure that the fields are mapped correctly; see Create license type examples.
• Make sure that the correct scope for the job is defined; see Managing-jobs-that-automatically-attach-CIs-to-license-certificates.

Debugging tips for troubleshooting the issues in license types

Before you begin debugging, ensure that you back up the license type forms. License type forms can be backed up to ensure there is no loss of data that prevents you from using your existing license types.

For more details, see To debug license type.
To back up the forms, before you begin troubleshooting, export the following license type forms by using Developer Studio. Then you can import them if you need to recover them at a later time.

List of license type forms

• AST:ConfigAction_CalculateSpecificData
• AST:ConfigAction_GetSpecificData
• AST:Config_ActionBase
• AST:ConfigCompliance_RuleReference
• AST:ConfigConnection_RuleFieldMapping
• AST:ConfigCompliance_RuleDefinition
• AST:ConfigBasicQuestionRegistry_DispProp
• AST:ConfigBasicQuestionRegistry_Base
• AST:ConfigLicenseTypeRegistry_DispProp
• RLE:ComplexRuleSpecificData
• RLE:CalculationRuleSpecificData
• RLE:GetRuleSpecificData
• RLE:LoopRuleSpecificData
• AST:ConfigLicenseTypeRegistry_Base
• AST:ConfigCompliance_ActionSelectList
• AST:ConfigAction_UpdateSpecificData
• AST:ConfigRuleSet
• RLE:RuleSet
• RLE:RuleSetType
• RLE:BaseRule
• RLE:UpdateRuleSpecificData
• AST:ConfigAction_CompareSpecificData

To help debug problems, you can turn logging on at the engine level:

1. To log all of the rules as they execute, set the log level to debug.
2. Examine the rules to determine whether they are being translated to the correct fields, are returning the correct results, and so on.

The log file is in the DB directory of the AR System server  and is called arjavaplugin.log.

For more information about setting the log level, see Configuring-the-license-engine.

Every license type created by the license type wizard creates a corresponding set of rules that are stored in the license engine rule forms and start with a prefix of RLE:.

The corresponding rules created are as follows:

• Query operations translate into GET rules.
• Create/modify operations translate into UPDATE rules.
• Computational operations translate into CALCULATE rules.
• Comparison operations translate into COMPARE rules.
  
  

The following list describes some of the RLE forms and the system rules that they contain:

• The RLE:RunTag form has a system rule for the LIVE RunTag.
• The RLE:RuleSetType form has two system data rules: one for CONNECTION jobs and the other one for COMPLIANCE jobs.
• The RLE:RuleSet, RLE:GetRuleJoin, RLE:UpdateRuleJoin, and RLE:LoopRuleJoin forms have two rulesets called GetScope and CommitData. These are used to process connection rules for all rules.
• Several other RLE forms are also installed with all the default license types that are shipped with the BMC Helix ITSM: Asset Management application. Do not modify any of this data in these forms. Only modify or delete license types using the license type wizard.

To debug license types