Article ID: 115690, created on Mar 11, 2013, last review on Feb 18, 2015

  • Applies to:
  • Operations Automation

Synchronize resource usage for instances of APS applications

An APS application can count and report usage of particular resources (e.g. traffic, diskpace, number of mailboxes and so on) using special resource scripts defined by APS specification:

The periodic POA task 'Synchronize resource usage for instances of APS applications' looks for applications that can report resource usage and then for each application instance calls script defined in the APP-META.xml file of an APS package. The script reports usage which must conform XML schema defined by APS format specification. POA parses XML output provided by resource script and then update resource usage in own database.

If APS application instance does not update its resource usage, check the following things:

  • Make sure that resource is correctly defined in the APP-META.xml file in the APS application in accordance with the APS specification.

  • The periodic task 'Synchronize resource usage for instances of APS applications' is active and is being executed in accordance with schedule defined in POA Task Manager. The proper status for the task is Rescheduled.

  • Proper execution period is set for the task, the default period is 180 seconds.

  • Check task history (the Task log tab in POA Task Manager), make sure task does not fail to be executed.

  • Make sure that resource script provides output in accordance with above mentioned XML schema, otherwise POA will not be able to process received data.

  • Check poa.debug.log on POA Management Node for the moment when task was executed last time and see, whether it processed the problem application instance or no.

The periodic POA task which collects resource usage may fail with the error message Document not well-formed, see Parallels Knowledgebase article #115033 for troubleshooting.

See also the KB article APS: General information, Best Practices and Troubleshooting

caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF