Services interface business processes with applications and other systems within and outside your enterprise. Unwired Orchestrator provides features for working with the following kinds of services:
Messaging Services, which enable interaction with messaging systems such as WebSphere MQ and JMS.
Database Services, which enable interaction with databases such as Sybase ASE, ASA, Oracle, MS SQL Server, and DB2.
Replication Event Services, which enables database event management implementation.
Web Services, which enable interaction with HTTP or SOAP Web services.
Unwired Orchestrator provides tools for defining or discovering services, working with service endpoints, and adding services to business processes. Services are defined or discovered and then used in the business process. Configuration of the endpoint allows communication between the external systems and the business process. The discovery or definition of the service includes the identification of the service operations that are used in the business process. The service interaction represents a specific invocation of a service operation.
The types of external services that are defined or discovered at design time must either reside on or be accessible to the server for successful communication between the source and target systems at runtime. Even though there may be no identified errors during the design of the services, the engine can be suspended at runtime as a result of missing or inaccurate service definitions or endpoint connection problems.
Although the discovery and definition of the service information is associated with design time, it is the deployment to the runtime machine that enables the runtime engine to connect to the physical endpoints. The design information must be tied to the physical configuration of the runtime machine. Assigning the physical port and connectivity information to each service used in business processes ensures communication between the correct devices at runtime.