FIMS Media SOA Framework - AMWA

More documents

Recommendations

Info

QuickTime and adecompressorare needed to see this picture.QuickTime and adecompressorare needed to see this picture.QuickTime and adecompressorare needed to see this picture.QuickTime and adecompressorare needed to see this picture.QuickTime and adecompressorare needed to see this picture.QuickTime and adecompressorare needed to see this picture.FIMS Media SOA Framework Phase1 (Preliminary)Web Service Client / Business ProcessLong-running Web ServiceClientRequest- correlationID- replyToAckServiceAsync Operations PortSOAP/HTTPNotificationConsumercorrelationIDSOAP/HTTP-correlationID-replyToPersistentStore / DBNotificationNotification Producer8.3.1 OperationsFigure 1: Request/response with asynchronous notification patternEach FIMS service shall implement a notification producer as a client stub using the message format defined forthe notification message. Furthermore, each FIMS service shall support polling with the operations using theManageJobRequestType and ManageJobResponseType as request and response messages.8.3.2 SchemaThe types used for the notification and polling operations have been described in sections xxx. The operationsshall use the following types:• Notification operation: shall use an input message based on the types BaseResponseType,MediaResponseType or their extended types.• Polling operation: shall use an input message based on the type ManageJobRequestType and itshall use an output message based on the ManageJobResponseType.8.3.2.1 EventsFIMS services can generate events to indicate job or queue relates state changes, or system / service statuschanges. FIMS service events are based on a publish-subscribe pattern. As mentioned earlier, this sectionfocuses on the structure of the types used by the messages and not on the specified bindings, however it isworth mentioning that for SOAP/HTTP binding FIMS service shall adopt the Web Services Brokered Notification1.3 (WS-BrokeredNotification) OASIS standard. Since the WS-BrokeredNotification standard does not addressthe container used for transporting the event or the event content, this section focuses on the definition of theevent container and of the event payload.8.3.2.1.1 Event ContainerThe event container is based on the WSDM Event Format defined in the Web Services Distributed Management:Management Using Web Services (MUWS 1.1) Part 1 OASIS Standard, 1 August 2006. The WSDM Event Formatdefines an XML format to carry management event information. The format defines a set of basic, consistentdata elements that allow different types of management event information to be carried in a consistent manner.The WSDM Event Format provides a basis for programmatic processing, correlation, and interpretation of eventsfrom different products, platforms, and management technologies.Private committee documentWorking Draft for review by FIMS Rev v1, Nov-16-2010 Page 68 of 89
FIMS Media SOA Framework Phase1 (Preliminary)The event payload shall be inserted in the “any” element of the ManagementEventType.8.3.2.1.2 MediaServiceEventTypeThis type represents a FIMS event payload sent from a service to the framework. The information in this type iswrapped by the event container specified by the WSDM Event Format. This base type is extended to providespecific events types:- SystemEventType- QueueEventType- JobEventType- ServiceEventType8.3.2.1.2.1 Event Types8.3.2.1.2.1.1 SystemEventTypeThis type represents a system-level event. It extends the base MediaServiceEventType.8.3.2.1.2.1.1.1 ParametersParameter Type DescriptionCode SystemEventCodeType The code for this system event,enumerated in SystemEventCodeType(e.g. low disk space).eventData xsd:string Optional element, which provides detailson the event.8.3.2.1.2.1.2 QueueEventTypeThis type represents a queue-level event. It extends the base MediaServiceEventType.Private committee documentWorking Draft for review by FIMS Rev v1, Nov-16-2010 Page 69 of 89
Page 1 and 2:
FIMS Media SOA FrameworkAMWA Specif
Page 3 and 4:
FIMS Media SOA Framework Phase1 (Pr
Page 5 and 6:
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18: FIMS Media SOA Framework Phase1 (Pr
Page 67: FIMS Media SOA Framework Phase1 (Pr
Page 89: FIMS Media SOA Framework Phase1 (Pr
show all

FIMS Media SOA Framework - AMWA

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?