Hi folks, Tuesday (16 Sept 2003)
Per my WBMM action item, I have written a prototype Schedule XML Schema
v0.10, following the well-tested IETF Schedule MIB v2 (RFC 3231) model.
This Schedule XML Schema validates without warnings using XSV 2.5 (the
free XML Schema Validator) and is posted at:
ftp://ftp.pwg.org/pub/pwg/wbmm/schemas/schedule-20030916.xsd
Comments?
Cheers,
- Ira McDonald
High North Inc
------------------------------------------------------------------------
[use models]
Use Model 1 (Passive - Required):
A WBMM managed device (or service) creates an HTTP connection (OUTBOUND
across the enterprise network's firewall) to a WBMM management station.
The WBMM managed device (or service) immediately sends a Get-Schedule
request (packaged in a SOAP/1.1 envelope). The WBMM management station
sends a Get-Schedule response containing an XML Schedule object (a list
of scheduled operations and times/intervals).
Later, as each scheduled operation is performed, the WBMM managed device
(or service) may create another HTTP connection to the WBMM management
station and send Send-Report (normal) and/or Send-Alert (exception)
requests, as needed.
Use Model 2 (Active - Optional):
A WBMM management station sends an Execute (or SetSchedule) request
(containing a Schedule object) directly to a WBMM managed device (or
service), for example, by sending a SOAP/1.1 request over email (SMTP).
Later, each scheduled operation is performed by the WBMM managed device
(as described in Use Model 1 above).
------------------------------------------------------------------------
[defined operations]
None - no operation
Other - vendor extension with parameter named 'Operation'
Disable
Enable
Pause
Resume
PauseAndDisable
ResumeAndEnable
PurgeJobs
Restart - reset to same, previous, or factory configuration
Shutdown - stop instance of service/device entirely
Startup - start new instance of service/device
GetElements
SetElements
GetResource
SetResource
Subscribe - for notifications
Unsubscribe
Wakeup - wakeup service/device, which then performs Get-Schedule
------------------------------------------------------------------------
[excerpted definition of 'SchedEntry' (row in a schedule)]
<xsd:element name="SchedEntry">
<!-- entry for a scheduled management operation -->
<!-- note that some elements may be multi-valued -->
<!-- see individual element descriptions for their cardinality -->
<!-- and REQUIRED versus OPTIONAL presence in a schedule entry -->
<!-- see schedEntry - section 4 [RFC3231] -->
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="SchedIndex" minOccurs="1" maxOccurs="1"/>
<xsd:element ref="SchedDescription" minOccurs="0"/>
<xsd:element ref="SchedState" minOccurs="1" maxOccurs="1"/>
<xsd:element ref="SchedStateReason" minOccurs="0"/>
<xsd:element ref="SchedStateMessage" minOccurs="0"/>
<xsd:element ref="SchedOperation" minOccurs="1" maxOccurs="1"/>
<xsd:element ref="SchedParameter" minOccurs="0"/>
<xsd:element ref="SchedTargetURI" minOccurs="0"/>
<xsd:element ref="SchedObject" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="SchedElement" minOccurs="0"/>
<xsd:element ref="SchedMode" minOccurs="1" maxOccurs="1"/>
<xsd:element ref="SchedInterval" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="SchedWeekDay" minOccurs="0" maxOccurs="7"/>
<xsd:element ref="SchedMonth" minOccurs="0" maxOccurs="12"/>
<xsd:element ref="SchedDay" minOccurs="0" maxOccurs="31"/>
<xsd:element ref="SchedHour" minOccurs="0" maxOccurs="24"/>
<xsd:element ref="SchedMinute" minOccurs="0" maxOccurs="60"/>
<xsd:element ref="SchedTriggers" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="SchedFailures" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="SchedLastError" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="SchedErrorDate" minOccurs="0" maxOccurs="1"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
This archive was generated by hypermail 2b29 : Tue Sep 16 2003 - 16:33:11 EDT