Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
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.<strong>FIMS</strong> <strong>Media</strong> <strong>SOA</strong> <strong>Framework</strong> Phase1 (Preliminary)Web Service Client / Business ProcessLong-running Web ServiceClientRequest- correlationID- replyToAckServiceAsync Operations Port<strong>SOA</strong>P/HTTPNotificationConsumercorrelationID<strong>SOA</strong>P/HTTP-correlationID-replyToPersistentStore / DBNotificationNotification Producer8.3.1 OperationsFigure 1: Request/response with asynchronous notification patternEach <strong>FIMS</strong> service shall implement a notification producer as a client stub using the message format defined forthe notification message. Furthermore, each <strong>FIMS</strong> 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,<strong>Media</strong>ResponseType 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 Events<strong>FIMS</strong> services can generate events to indicate job or queue relates state changes, or system / service statuschanges. <strong>FIMS</strong> 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 <strong>SOA</strong>P/HTTP binding <strong>FIMS</strong> 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 <strong>FIMS</strong> Rev v1, Nov-16-2010 Page 68 of 89
Change language