WBMM> Posted Schedule schema v0.50 (27 Jan 2004)

WBMM> Posted Schedule schema v0.50 (27 Jan 2004)

WBMM> Posted Schedule schema v0.50 (27 Jan 2004)

McDonald, Ira imcdonald at sharplabs.com
Tue Jan 27 19:00:46 EST 2004


Hi folks,                                      Tuesday (27 January 2004)

[Per our review of the Schedule schema during the December PWG in Provo
and most recent draft of WBMM Protocol spec 'wd-wbmm10-20040126.pdf'.]

I have just posted a revised Schedule XML Schema v0.50, which validates
without warnings using XML SPY 2004, XRay 2.0, and XSV 2.5 (the free XML
Schema Validator) and is posted at:

    ftp://ftp.pwg.org/pub/pwg/wbmm/schemas/schedule-20040127.xsd

Below are: (a) change log; (b) use models; and (c) defined actions.

Note that the use models have been rewritten for completeness.

Cheers,
- Ira McDonald
  High North Inc

------------------------------------------------------------------------
[changes from v0.40 to v0.50]

(1) Minor editorial fixups;
(2) Deleted the redundant compound actions 'PauseAndDisable' and
    'ResumeAndEnable', not needed in a multiple-action Schedule,
    per review at December 2003 PWG Meeting in Provo, UT;
(3) Deleted the redundant action 'DeleteElements', not needed with
    'SetElements' (but kept 'DeleteResources' which removes objects),
    per review at December 2003 PWG Meeting in Provo, UT;
(4) Renamed the tickle action 'Wakeup' to 'UpdateSchedule', for clarity,
    per review at December 2003 PWG Meeting in Provo, UT;
(5) Renamed the complementary actions 'Subscribe/Unsubscribe' to
    'Subscribe/UnsubscribeForalerts', for clarity,
    per review at December 2003 PWG Meeting in Provo, UT;
(6) Renamed the complementary operations 'Register/Unregister' to
    'Regsiter/UnregisterForManagement', for clarity,
    per review at December 2003 PWG Meeting in Provo, UT;
(7) Added 'ActionResetMode' parameter to 'SetElements' action, for
    per review at December 2003 PWG Meeting in Provo, UT;
(8) Changed 'service or device' to 'legacy or managed entity',
    per recent review of WBMM Protocol spec;
(9) Changed 'management station' to 'management proxy/station',
    per recent review of WBMM Protocol spec.

------------------------------------------------------------------------
[use models]

Use Model 1 (Passive Mode):

(1a) If SOAP over HTTP is the active WBMM transport binding, then the
WBMM Managed Entity (service or device) starts an HTTP connection to an
administratively configured or dynamically discovered:
(a) WBMM Management Proxy (inside or outside enterprise firewall); or
(b) WBMM Management Station (inside or outside enterprise firewall).

(1b) WBMM Management Proxy or WBMM Management Station authenticates the
calling WBMM Managed Entity and accepts the incoming HTTP connection.

(2a) If this is the first contact, then the WBMM Managed Entity sends a
RegisterForManagement request (packaged in a SOAP/1.1 envelope), to
establish a management association.

(2b) The WBMM Management Proxy or WBMM Management Station (optionally)
further authenticates and authorizes the calling WBMM Managed Entity and
sends a RegisterForManagement response back to the WBMM Managed Entity.

(3a) The WBMM Managed Entity sends a GetSchedule request (packaged in a
SOAP/1.1 envelope), to solicit management directions.

(3b) The WBMM Management Proxy or WBMM Management Station sends back a
GetSchedule response containing an XML Schedule object (a list of
planned actions and their timetables).

(4a) Later, as each planned action is performed, the WBMM Managed Entity
then creates other HTTP connections sends SendReport (normal) or
SendAlert (exception) requests, as needed.

(4b) The WBMM Management Proxy or WBMM Management Station sends back
SendReport or SendAlert responses, as needed.

Use Model 2 (Active Mode):

(1) Out-of-band management association is created between a WBMM Managed
Entity and a WBMM Management Proxy or WBMM Management Station, or a
passive mode RegisterForManagement operation is completed successfully.

(2a) The WBMM Management Proxy or WBMM Management Station sends an
SetSchedule request (containing an XML Schedule object) directly to the
WBMM Managed Entity, for example, by sending a SOAP/1.1 request over
email (SMTP).

(2b) The WBMM Managed Entity sends a SetSchedule response back to the
WBMM Management Proxy or WBMM Management Station, by the same transport.

(3) Later, each planned action is performed by the WBMM Managed Device
(as described in steps 4a and 4b of Use Model 1 above).

------------------------------------------------------------------------
[defined actions]

Vendor - vendor extension action with any parameters
Disable
Enable
Pause
Resume
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
DeleteResources
SetResource
SubscribeForAlerts
UnsubscribeForAlerts
UpdateSchedule - wakeup service/device, which then performs GetSchedule

------------------------------------------------------------------------

Ira McDonald (Musician / Software Architect)
Blue Roof Music / High North Inc
PO Box 221  Grand Marais, MI  49839
phone: +1-906-494-2434
email: imcdonald at sharplabs.com



More information about the Wims mailing list