Creating or calling a web service

Web services are self-contained applications that perform business functions, ranging from a simple query to complex business process interactions. You can call an existing web service or you can develop a new web service to fit your needs. This scenario will describe the steps and point you to additional information.

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:

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.

Exports, imports and bindings

IBM Integration Designer allows you to import standard web services and make use of these services in your composite applications.

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.

  1. Create an export to publish the module's service for use by other modules.
  2. Generate a binding for the export.
  3. 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 see the Confirm Enablement window, which displays the following information:
This action requires the enablement of "Web Services Deployment".
Enable the required capability?

IBM Integration Designer provides a filtering function known as capabilities. In the Preferences settings, functions and tools are categorized into capabilities and you can enable and disable categories of capabilities or the subset functions of any category. See Capabilities for more information.