WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Implementing a service operation

Implement the operations that are defined in your service interface.

Before you start:

Create a new service by importing a WSDL, or create a an service and define the service interface. For more information, see Creating a service based on WSDL, or Creating a service and Defining a service interface.

You can use different editors to implement a service operation:
  • You can implement a service operation by using the Service editor. For more information, see Service editor.
  • You can implement an operation by using the Message flow editor. For more information, see Message Flow editor.

Complete the following steps to implement an operation:

  1. Open the service.
    • In the Service editor, double-click the Service Description of the service in the Broker Development view. The service Overview tab opens in the service editor.
    • In the Message flow editor, expand the service resources in the Broker Development view.
  2. Open the operation in an editor.
    • If you are using the Service editor, click an operation to open the embedded subflow editor.
    • If you are using the Message flow editor, double-click the subflow that represents the operation.
  3. Implement the operation as a subflow. For more information, see Creating a subflow.
    • A one-way operation has 1 input node by default.
    • A request-response operation has 1 input node and 1 output node by default.
    • Operation faults are displayed in the subflow as output nodes.
    Note: For the service to be called by using any binding, the response message that is built in the subflow must consist of the service payload in the XMLNSC domain. For example, if you are building a response in a Compute node, then you should write:
    SET OutputRoot.XMLNSC.NS1:echoResponse.data = 'response';
    instead of:
    SET OutputRoot.SOAP.Body.NS1:echoResponse.data = 'response';
  4. Use the breadcrumb navigation at the top of the editor to return to the service overview.
Next steps:

A default HTTP binding is generated when the service is created. To use the default binding, deploy the service when you implement all defined operations of your service. For more information, see Packaging and deploying.

To instead use your own HTTP binding, see Generating a service SOAP/HTTP binding.

Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:47:47


Task topicTask topic | Version 8.0.0.7 | bc19316_