Databases Reference
In-Depth Information
The following diagram shows a simple
Composite
service that is invoked by a
Client
, which in turn invokes two services before the
Composite
completes:
The details of the composite service are not relevant at this point, and the composite
could consist of a Service Bus pipeline, a Mediator, a BPEL process, or all three. Note
that the nature of the composite defines several interfaces; the composite exposes a
client interface, and in turn makes use of interfaces exposed by the two services. We
will use this simple example (previously shown) to explore how to perform different
levels of the test.
One-off testing
Within a development environment, it is very useful to run a quick test of a
composite or interaction to ensure that it behaves as expected. These one-off tests can
be run from the
Enterprise Manager
(
EM)
Console and the Service Bus Console, as
explained in the next section,
Testing composites
.
Testing composites
All deployed composites have a test client created for them. This is accessed by
clicking on the composite in the EM Console and selecting the
Test
tab. The test
client in the EM Console is very good when you want to quickly test whether the
composite you have deployed is behaving as expected. It allows you to specify the
input parameters through the web interface, including a choice of Tree or XML input
formats. When switching between views, the data entered will be preserved. The
next example from the EM console shows how the Tree format makes it very easy to
focus on just the input fields required, rather than having to be concerned with the
exact XML format required by the composite.
