A web service operation is an interface to public Web service operations. Unwired Orchestrator allows you to use standard SOAP Web services in business processes. When you reference a Web service, you are not accessing the actual service but the WSDL for that service. Those WSDLs that do not have an associated extracted schema in XSD format cannot be used in Unwired Orchestrator.
You do not define Web services in Unwired Orchestrator like you do database and messaging services. Instead, you discover existing Web services in UDDI registries or other locations and then add them to a project. The Service Search Wizard explores the Universal Description, Discovery, and Integration (UDDI) registry for all available types of resources. You can then store the information for each resource in the Endpoint Manager or Service Library by dragging and dropping. This information is then available for use in a business process.
After Web services are added to a project, you use them the same as database and messaging services. You use the default .iface file or create a new .iface file to define the service interaction for each Web service operation to be used in a business process, extract the schema for the operation, and then drop the service interaction into the business process.
When searching the UDDI repository, you are searching each business and service to find a match with the metadata you entered. Services that are stored in a UDDI registry must contain at least a schema specification, an application specification, and an operator's specification. Eligible Web services must employ a SOAP/HTTP transport.
Web services technology is based on a service-oriented architecture with the following components:
Service provider
Service requester
Service broker, for example, UDDI or IBM or Microsoft .net , which facilitates matching requesters and providers
Unwired Orchestrator supports Web services used as One-Way or Request/Reply operations. One-Way operations are used when the engine must send a message to a Web service and no response is expected. Request/reply operations are used when the Web service sends request and then waits for a response. All transactions are treated as sequential.