Search Engine: Elastic

Article ID: 124343, created on Jan 30, 2015, last review on Aug 23, 2016

  • Applies to:
  • Operations Automation
  • Business Automation
  • APS


There are 6 so called "application counters" which function as numeral representation of goods consumed by customer, namely:

  • Application Counter (KB)
  • Application Counter (MB-hours)
  • Application Counter (MHz)
  • Application Counter (MHz-hours)
  • Application Counter (unit)
  • Application Counter (unit-hours)

They are declared in application metadata (schemas), and have OA resources created for them.

The difference between "hours" and "-hours" resources is that the latter is additive.

Typical examples:

  • Counter (unit) - non-additive - diskspace
  • Counter (unit-hour) additive - traffic, MHz.

Note: when configuring Resources in PBA, that are linked to OA RT, BA ignores its own "additive" flag, and uses OA's. This ultimately affects the way customer would be billed for the resource. If traffic would be set to "Application Counter (KB)" - the customer would receive bigger and bigger orders.

Resource synchronization task

There is a periodic task Synchronize resource usage for instances of APS applications that effectively goes through APS2.0 endpoints and calls retrieve() function. In reply the endpoint goes ahead and updates the resource usage in OA. The detailed explanation of how the retrieve() function may function is available at docs at appstandard.

198398b282069eaf2d94a6af87dcb3ff caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 717db81efe94e616312b74fb03a5d474 5356b422f65bdad1c3e9edca5d74a1ae

Email subscription for changes to this article
Save as PDF