How can I view the License Metric Calculation script for Oracle Per Processor License Metric?

Steve H2
Kilo Expert

We need to create a custom license metric for an Oracle license metric that is based on 2 core per processor, instead of the single core per processor that is part of the Oracle Publisher Pack. To create this custom license metric we need to look at the Calculation script that is part of the Oracle Publisher Pack Per Processor License Metric. We want to use that script as a model for our custom license metric calculation.
When we view the Oracle Per Processor license metric record the calculation script is not viewable, even when we add the script field to the form layout. So how can we see the calculation script?

 
2 ACCEPTED SOLUTIONS

Daniel Slocum
ServiceNow Employee
ServiceNow Employee

Hi Steve,

Did you create your software model manually or via entry of a Publisher part number on the software entitlement record?  If use did the latter, check the Metric Attributes related list on the Software Model.  You may be able to simply mark the number of cores to count there, which would result in the system calculating 2 cores per one license using the out of box metric.

If you choose the Common Metric group and specify Per Core as the license metric, you'll note a Metric Attribute is added to the Software Model, metric attribute related list that allows you to specify two cores, or even more to consume a license. 

Hope this is helpful and precludes you from needing to create a custom license metric.

Regards. 

View solution in original post

Glad I could help Steve,

I actually deleted my comment, to preclude confusion among Community members.  Very glad it worked for you with a Microsoft product.  Metric attributes cannot be added manually.  They are added by ServiceNow based on the license metric chosen on the related software entitlement records. 

View solution in original post

7 REPLIES 7

mikewhalley
ServiceNow Employee
ServiceNow Employee

Just to be clear - are you saying that Oracle's Core Processing Factor is 2 ? If so, what is the processor in question ?

My apologies. I was mistaken in saying Oracle. This is actually a Microsoft License Metric, which is based on 2 core instead of a single core count.

What I am looking for is some example code/scripts for license metrics on which I could build the code/script for this custom license metric. Any thoughts on how to view the scripts/code for the OOB Microsoft License Metrics? Does anyone have code/scripts for custom license metrics you have built, and that you wouldn't mind sharing as an example?

Daniel Slocum
ServiceNow Employee
ServiceNow Employee

Hi Steve,

Did you create your software model manually or via entry of a Publisher part number on the software entitlement record?  If use did the latter, check the Metric Attributes related list on the Software Model.  You may be able to simply mark the number of cores to count there, which would result in the system calculating 2 cores per one license using the out of box metric.

If you choose the Common Metric group and specify Per Core as the license metric, you'll note a Metric Attribute is added to the Software Model, metric attribute related list that allows you to specify two cores, or even more to consume a license. 

Hope this is helpful and precludes you from needing to create a custom license metric.

Regards. 

Daniel Slocum
ServiceNow Employee
ServiceNow Employee

Hi Steve,

A bit more input.  I asked our Dev team about your question.  The following is the response.  Can you reply with additional details?

For Oracle Per Core License Metric, the Oracle Core Factor comes into play which is a multiplier on top of the core count determined based on the processor.  samp_processor_factor_map is the table which stores the values of the Oracle Core Factor.  It's the "Processor Factors" table.  So the customer's question is not fully clear since the Oracle Per Core cost factor is preset based on the processor identified on the ci record and it would be taken care of automatically.  In this case, they are trying to have a multiplier of 2 so it is not clear if its a matter of incomplete information or a new requirement for ServiceNow to consider.