Services allow business processes to interact with external systems. Unwired Orchestrator provides tools for discovering or defining, editing, sharing, and deploying services. A service can be as simple as a credit check process that one company has developed and is willing to share. In Unwired Orchestrator, services are stored in Web Services Description Language (WSDL) files.
Services can also be used to perform a Request/Reply such as a call for information from a database or Web service. Services can also be used to start a process, to receive information from a messaging system, and to send information to another messaging system. Messaging systems are configured as endpoints to external services. For example, an Unwired Orchestrator business process could be defined with two messaging systems having endpoint connections to SAP and PeopleSoft external services. In this scenario, information could be delivered from SAP to PeopleSoft using the two messaging systems.
Business processes are built using a building-block approach. In Unwired Orchestrator, each service is one block that provides some interaction with an external system. For example, these blocks can be used to build order entry or inventory control processes, and then those processes can be combined into large entities that ultimately may be end-to-end business processes such as supply chain management.
Note: This version of Unwired Orchestrator supports only those schema that conform to the final recommendations of W3C for schemas. Specifically, Unwired Orchestrator checks to be sure the namespace of the WSDL file includes the 2001 W3C schema URI: http://www.w3.org/2001/XMLSchema.
A service contains a port type, operations, and ports.