See information about the latest product version
Generating a service SOAP/HTTP binding
Learn the steps to generate a binding for your service.
Create a service, and implement the operations defined in the service interface. See Service creation workflow overview.
When you create a service in WebSphere Message Broker, the service opens in the service editor. The service endpoint and binding are shown on the left of the service overview. The Service Input node represents the service endpoint. A default SOAP over HTTP binding is generated, shown next to the Service Input node icon.
You can also create your own binding. First, you delete the default binding, and then you can generate a new binding.
The service binding can be created and configured before or after you define and implement your operations.
Complete the following steps to generate a binding:
- Open your service in the Service editor by double-clicking the Service Description in the Broker Development view, or by right-clicking and selecting Open. Select the Service tab to see the service overview.
- Delete the default SOAP/HTTP binding. Right-click the binding name and select Delete. The existing binding is deleted. The service SOAPInput node icon changes to an Input node, and the binding name is replaced with the action Generate binding.
- Click the Generate binding action. The Generate HTTP Binding wizard launches.
- Select a SOAP/HTTP binding type of either SOAP 1.1 or SOAP 1.2.
- Enter the URL for the binding. Click Finish.
A SOAP over HTTP binding is generated. The service input node icon is updated to a SOAPInput node icon, and the name of the binding is displayed next to it.
The properties of the binding are shown in the Properties view when the binding is selected in the Service editor. You can view and edit the binding properties in the Properties view.
Consumers can query your deployed service using a ?wsdl query string to return the service interface. To disable this behavior, select the SOAP/HTTP binding in the Services editor, and clear Enable support for ?wsdl in the HTTP transport tab of the SOAP/HTTP service binding properties.
Deploy the service to an execution group. For more information, see Packaging and deploying.