Database Reference
In-Depth Information
The SQL implementation of the service taxonomy (example)
As an outcome of the realization of the service taxonomy, we can now demonstrate the
Enterprise Service Repository database schema, which is quite simple but fully functional
and capable of supporting runtime and design-time Discoverability for practically any line
of business (not only telcommunication). You can use it as an example for your own im-
plementation. Relations between entities are clearly visible and very suitable for exposure
by quick JAX-WS Service Inventory Endpoint. But we do not need to do that for our ag-
nostic controller. It will be no problem to modify
ExecutionPlanlooupService
for
the extraction of EP information from DB. We will have to add the DB adapter and use it
instead of the rule component. The SQL query in the adapter will be based on the view
built around the relational model presented earlier, where the composition linking the
table is the cornerstone. The view will isolate the
select
statement in the adapter from
further development in the Custom ER schema.
Custom SR DB-schema
The XML implementation of Execution Plan
Finally, the Execution Plan (synonymous with Task List or Service Routing Slip) is the
XML representation of the service composition we described earlier. It's a sequence of the
tasks with Endpoint URLs, where a task can have steps for synchronous MEPs and the
definition of Service Engines responsible for task execution (Oracle OSB in the following
example).
As you can see in the following working example, a list of the actual task's operation is
rather limited: invoke and transform. You can add your operation, but this minimal set for
Service Broker functionality is quite enough as we do not have any plans to create another
BPEL. For error handling, task pairs can have the rollback or compensation part, which
will be executed by Service Broker if the response from the first execution is negative. In
general, compensation can be another execution plan, that is, if the rollback scenario is
complex.
Search WWH ::
Custom Search