Before you start:
If you are not familiar with message flow concepts, message model concepts, and common tasks to manage message flow resources, see Developing message flows and Constructing message models.
In a heterogeneous environment, each service provider has a different syntax and format for describing their service. An application needs a description of the service interfaces to be able to consume, provide, govern, or catalog the service. Service discovery in IBM Integration Bus provides you with a common experience for describing service interfaces.
In IBM Integration Bus, a discovered service is a representation of the external service with which your message flow interacts. This discovered service can be shared with different tools and users. The interface of a discovered service is defined through WSDL.
- A user enters connection details in a service editor.
- The service editor discovers the technical assets.
- A user selects the required technical assets for elaboration.
- The service editor creates a service definition, and optionally stores it in a catalog for later use.
You can use service discovery to connect the following client applications:
- A database: Use a Database Service to make database operations accessible both within a message flow, and to external applications that call a message flow. For more information, see Database Service.
- A WebSphere MQ application: Use the MQ Service to define the interaction between IBM Integration Bus and WebSphere MQ applications. For more information, see MQ Service.
The discovered service can be used internally within a message flow, and can be exposed to service consumers through an integration service. For more information, see Integration services.
Last updated Friday, 21 July 2017