Although you may not create all of your services from the ground up using IBM® Integration Designer, some of your services will indeed be created this way. When working with the assembly editor and the business process editor to assemble services into a business process, you are likely to find that some services are missing. It may therefore be helpful to create those missing services using IBM Integration Designer tools. The reverse is also true - after you have created a new process, you may decide that it would be useful to expose all, or some subset of the process operations as a service for others to consume.
Note: This scenario applies to users of IBM Integration Designer for IBM Process Server and WebSphere® Enterprise Service Bus.
There are several reasons for developing Web services using IBM Integration Designer:
- Creating services in IBM Integration Designer allows you to implement the service using business rules.
- Developing in IBM Integration Designer allows you to develop a Java service and expose it as both a Web service and through SCA.
- Interface mapping without having to code is an advantage. You can take all of the data mappings out of the Java code leaving a simple black box Java program for the Java developer.
- IBM Integration Designer shows all of the services and relationships in one place.
- The ability to refactor will also aid in the development of Web services using IBM Integration Designer.
Keep in mind that Web services should not be regarded as the solution to all of your integration problems. However, just as with any other technology or architectural approach, there are inherent advantages of using Web services in the right place and at the right time.
In IBM Integration Designer, use the assembly editor to develop services. Follow the standard process to create modules, mediation modules, libraries, and components. Then, you can use exports, imports, and bindings to share and access those services. The steps for those basic tasks are listed below and the links lead to more detailed information for each task.
You can use either of two bindings for Web services - a Web service binding or an HTTP binding. A Web service binding provides a specification for transmitting messages to and from a Web service. The tools help you to generate a Web service binding automatically. An HTTP binding is a standard request-and-response protocol between clients and server as defined by the HTTP protocol published by the World Wide Web consortium (W3C). You will need to provide some initial binding configuration information if you use an HTTP binding.
- Create an export to publish the module's service for use by other modules.
- Generate a binding for the export.
- Create an import to call an existing service that is not part of the module that you are assembling.
Read the linked topic if you want to invoke a Web service from JavaServer Pages.
Web services development capabilities
When opening an editor associated with the Web services creation process, you might encounter the following error:
For training on IBM Lombardi mail us at firstname.lastname@example.org