Information Technology Reference
In-Depth Information
As the development goes on, we are interested in learning about the
following: import of simulation data, preselection of branching, timer
control, and moreover how typical grid requirements can be supported
in cases where scaled-down versions are not sufi cient to evaluate a work-
l ow design.
8.15
BPEL Designer comes with a general Web service client. This is of immedi-
ate demand after process deployment. The Web Tools Platform (WTP) is an
extension platform of Eclipse for developing Web and J2EE applications. It
provides essential data models, APIs, and tools that are relied on by many
derivative Eclipse projects and products, including BPEL Designer. The
Web Standard Tools (WST) subproject supports the processing of a wide
range of popular Web standards, like HTML, XML, XSD, XSLT, SOAP,
WSDL, UDDI, and so on. The Web Service Explorer (WSE) is a tool with
which users can interact with Web services and UDDI registries through
Web interfaces.
In order to invoke a Web service, WSE uses the full WSDL description of
a service to dynamically generate the Web form that needs to be i lled out
by a user to initialize the service request body. WSDL i les may be located
either locally or remotely. Associated XML schemas will be parsed to sup-
port form generation. The user coni rms and submits a form by clicking a
button. Request data will be validated before sending out. Errors detected
during the invocation will be reported in the status window in which for-
matted response data of successful invocation will be displayed. Both
request and response messages in raw SOAP can be viewed in a separate
page, in which SOAP segments can be edited directly, or even saved or
loaded if necessary. OMII-BPEL has integrated OMII security support into
WSE. OMII users can invoke services hosted by OMII servers, whether
BPEL processes or not, seamlessly and safely.
In order to work with UDDI registries, WSE allows users to specify the
registry they want to create, update, delete, and query for services. Without
going into too much detail, a typical scenario of using the UDDI registry is
that a user can log in to the registry to search for services; for example, using
keywords of service descriptions. The WSDL i le of the returned service can
then be saved directly into the current project space, and used in the part-
ner link declaration as we have mentioned before. OMII distribution ships
its own UDDI registry, Grimories, which implements the standard UDDI
specii cation. It can be simply deployed to register and manage service
information, including BPEL processes. The registry itself is a Web service,
and the access from within WSE is secured in a similar way. Finally, WSE
Web Service Client
Search WWH ::
Custom Search