My Notes - SOA for Dummies Part 7



Chapter 8: The Registry and the Broker
-          SOA Registry key functionality
o   Publish webservices and enable their discovery
o   Collect and maintain metadata about webservices
o   Govern webservice usage
-          What is metadata
o   Data to describe the webservices
o   Business rules
o   Rules used to access those WS.
-          Brokering Services
o   It’s about finding services and connecting consumer service and producer service as per the rules specified policy engine (visualize as a component of the registry) to invoke target service.
o   In order to achieve this, services must be published to registry.
-          Registry – what’s inside?
o   Webservices component description – Rules about the service itself, follows UDDI standard
o   Legacy component description – if webservice is a legacy service, rules that govern to invoke such service
o   Business process definition – Holds a map of complete business process in order to orchestrate the services invocation in a given business process.   It’s broader than just webservices.
o   Business process rules – Rules that applies business process wide, like security it is another webservice component in itself.
o   Performance rules – what are the performance requirements in order to invoke the service at the outset.  ( SOA supervisor does same at runtime)
o   Governance rules – to handle change management of contents of registry like webservices rules



-          Service Broker – What it does? – It works with Service Registry and connects all services needed and uses information stored in registry to invoke the business process.    So how it does this?

  • When application is requested, broker gets notification.
  •    Consults registry, what needs to be done and whether it can be invoked at this time.
  • Broker checks
  • All components are working and if not it starts them.
  • Interfaces between components and what information those interfaces need to know, as all adapters get connected to execute requested business process.
  • If any rules associated with the connection between components (or adapters).  So components get them from Rules Engine associated with registry.
  • Based on rules if required, broker checks and gets the connection with other components.



        

No comments:

Post a Comment