FIMS Media SOA Framework - AMWA

More documents

Recommendations

Info

FIMS Media SOA Framework Phase1 (Preliminary)The service registry should support the service update lifecycle by allowing specifying the version for eachimported service interface documents and schemas [see 6.2.3].6.1.4.2 New service implementationIn this scenario there is no change in the version of the interface, but the service is replaced with a differentimplementation where some of the features (operations) are implemented or more features (operations) areimplemented. In the latter case, the service is backward compatible. In the former case, there is the issue ofmaking the framework aware that the service is not implementing some features. The current FIMSspecification recommends the following guidelines:• Service description metadata for each service implementation shall bind service operations withproperties (e.g. transcode operation shall bind with a list of supported formats).• Only available operations shall have bindings in the service metadata.• Services are invoked through mediation in the ESB. The mediation is responsible of performing a lookupin the service registry to find the service instance(s) that implement the requested operation.• If no instance with the required operation is found, the mediation shall throw a fault (e.g. service withrequested feature not found)[REF1] Web Services Description Language (WSDL) Version 2.0 Part 0: Primer - W3C Recommendation 26 June2007. Available at http://www.w3.org/TR/wsdl20-primer.6.2 Service behaviorThis section addresses the service behavior that is common to all categories of services. Behavior specific toeach service category will be discussed when describing the service interfaces.6.2.1 Operation Implementation patternsService operations defined by FIMS interfaces provide different types of interactions between the serviceprovider and the service requester. Each one specifies how the result of an operation is made available to therequester. The interface definition along with the input parameters of the operation determines how the serviceshould return the response of the operation.6.2.1.1 Synchronous Request/ResponseIn this interaction mode the service client (e.g. a business process) invokes the service to perform an operationpassing the input parameters (par1, … parN) and receives the response in the same communication session asthe request. Operations that implement this mode of interaction should not be long-running processes to avoidblocking the service client for a long period of time and to prevent timeouts that may occur in thecommunication session.Examples of operations that use this type of interaction are the job and queue management operations.Private committee documentWorking Draft for review by FIMS Rev v1, Nov-16-2010 Page 16 of 89
FIMS Media SOA Framework Phase1 (Preliminary)6.2.1.2 Asynchronous Request/Response with NotificationThis interaction pattern should be used for long running processes. The request and response associated to theoperation are exchanged in two different communication sessions. The request session includes the invocationby the client of an operation passing the input parameters (par1, … parN, jobGUID, notifyAt) and theacknowledgement by the service that the request was received.The jobGUID parameter identifies uniquely the job request from the business process (the service client) pointof view. The notifyAt parameter specifies to the service provider where to send the response message when theoperation execution completes. It also specifies where to send an error notification message if the service failsduring its execution.A separate communication session is used to send the response message to the address specified by thereplyTo element of the notifyAt parameter. If an error occurs during the process of the operation an errornotification should be issued to the endpoint specified by the faultTo element of the notifyAt parameter.An example of operation that employs this interaction mode is the transcode operation of the TransformMediaservice.Private committee documentWorking Draft for review by FIMS Rev v1, Nov-16-2010 Page 17 of 89
Page 1 and 2: FIMS Media SOA FrameworkAMWA Specif
Page 3 and 4: FIMS Media SOA Framework Phase1 (Pr
Page 15: FIMS Media SOA Framework Phase1 (Pr
Page 67 and 68:
FIMS Media SOA Framework Phase1 (Pr
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89:
show all

FIMS Media SOA Framework - AMWA

Create successful ePaper yourself

Delete template?

Save as template?