Data Source

Release Notes > JTGO 4.5 Release Notes > New Features > Data Source

Data Source

Changing Object States using XML

It is now possible to change the object state attribute for the predefined business objects incrementally. States, alarms and traps can be set in the object state without requiring the update of the whole attribute value. The incremental update of the objectState attribute is performed using the new tag <updateState>, as illustrated in the following example.

<cplData xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation = "ilog/cpl/schema/data.xsd">

<updateObject id="NE1">

  <updateState>

    <misc operation="remove">DoorAjar</misc>

    <performance state="Input" operation="remove" />

    <alarms>

      <new severity="Raw.Warning" operation="add">1</new>

      <ack severity="Raw.Major" operation="remove">2</ack>

    </alarms>

    <availability operation="remove">Degraded</availability>

    <procedural operation="remove">Initializing</procedural>

  </updateState>

</updateObject>

</cplData>

For more information, see Data Sources, Adding Business Objects from XML, Adding Predefined Business Objects in the Business Objects and Data Sources section of the User's Documentation.

Alarms and traps can be set, added or removed from the object state using the operation attribute in the alarm or trap tag:

To add alarms or traps, use operation="add"
To remove alarms or traps, use operation="remove"
To set alarms or traps, use operation="set" (default)

<cplData xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation = "ilog/cpl/schema/data.xsd">

<updateObject id="NE1">

  <updateState>

    <alarms>

      <new severity="Raw.Warning" operation="add">1</new>

      <ack severity="Raw.Major" operation="remove">2</ack>

    </alarms>

  </updateState>

</updateObject>

</cplData>

OSI, Bellcore, Miscellanous, Performance, and SAN secondary states can be added or removed from the object state using the operation attribute in the state tag:

To remove secondary states, use operation="remove"
By default, if the operation attribute is not defined, the secondary states are set in the object

<cplData xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation = "ilog/cpl/schema/data.xsd">

<updateObject id="NE1">

  <updateState>

    <misc operation="remove">DoorAjar</misc>

    <availability operation="remove">Degraded</availability>

    <procedural operation="remove">Initializing</procedural>

  </updateState>

</updateObject>

</cplData>

SONET protections can be removed by setting the attributes from or/and to to false.

<cplData xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation = "ilog/cpl/schema/data.xsd">

<updateObject id="L1">

  <updateState>

    <state>Active</state>

    <protection from="true" to="false">Exercisor</protection>

    <protection from="false" to="true">WaitToRestore</protection>

  </updateState>

</updateObject>

</cplData>

Copyright © Rogue Wave Software, Inc. 1997, 2016. All rights reserved. Legal terms.