Online Help for Administrators > Administering SHR > Configuring downtime in reports > Syntax for downtime schedule with one occurrence

Syntax for downtime schedule with one occurrence

To create a downtime schedule that occurs only once, you can use one of the following XML syntax:

Syntax 1

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<downtime>

<name>Sample1</name>

<category>Other</category>

<schedule >

<type>ONCE</type>

<startDate>2012-02-07 10:00:00</startDate>

<endDate>2012-02-07 22:00:00</endDate>

</schedule>

<instances type="system">

<instance>

<attribute name="CI_UID" value="c2fa6553dd16af591b128e19feec3d49"/>

</instance>

</instances>

</downtime>

Syntax 2

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<downtime>

<name>Sample1</name>

<category>Application maintenance</category>

<schedule >

<type>ONCE</type>

<startDate>2012-02-07 10:00:00</startDate>

<endDate>2012-02-07 22:00:00</endDate>

</schedule>

<selectedCIs>

<ci>

<id>ciid_bizsvc1</id>

</ci>

<ci>

<id>ciid_bizsvc2</id>

</ci>

</selectedCIs>

</downtime>

The following table provides a description of the tags used in the above sample.

Tag Description
<name> Provide a name for the downtime in the tag.
<category>

The category assigned to the downtime. Options include:

  • Application installation
  • Application maintenance
  • Hardware installation
  • Hardware maintenance
  • Network maintenance
  • Operating system reconfiguration
  • Other
  • Security issue
<schedule> Define the downtime schedule in this section of the XML.
<type> Define the type of downtime schedule that you want to create. The values can be ONCE, WEEKLY, or MONTHLY.
<startDate> Specify the starting date and time of the scheduled downtime for the monitored component or CI. The date format is yyyy-mm-dd hh:mm:sis. You can change this value at any time. However, data that is enriched with downtime information will not be reprocessed.
<endDate> Specify the ending date and time of the scheduled downtime for the CI. The date format is yyyy-mm-dd hh:mm:ss. You can change this value at any time. However, data that is enriched with downtime information will not be reprocessed.
<instances type> In this section, you define the CI type that will be affected by downtime such as node, CPU, Disk, Web server, application, event, and so on. The downtime XML that you create is applicable for one CI type only. For additional CIs, you must create additional XML files.
<instance>

Each instance of the CI type must be defined in a separate <instance> tag. The attribute name refers to the instance metric and the value refers to the value of that metric. If a particular CI instance is defined by more than one metric, additional instances must also be defined by the same number and type of metrics. For the CI parameters, see the Model Automation XSD.

<selectedCIs> In this section, you can directly define multiple CIs that will be affected by downtime. You can refer to these CIs by using their unique IDs. This section is applicable if SHR is deployed in the SaOB and APM deployment scenarios where RTSM is the topology source.


© 2010 - 2013 Hewlett-Packard Development Company, L.P.