Defining Web Services

To describe your service, you need to create a set of WSDL and XSD files.

For example, a Web Service called AdditionServices would require the following files:

  • AdditionServices.wsdl – describes the address at which the service is available and that is appropriate for the transport binding chosen. This WSDL also describes the operations and the messages used in operations.
  • Addition.xsd – describes the data types used in the messages that will be included by the extension.xsd file.

You can follow the pattern in the existing Web Services WSDL and XSD files. For each new transaction that you create, you must add the following:

  • A Web Service operation.
  • One input, one output, and between zero and many fault messages.
  • One part per message only (required when the service style and encoding are document literal wrapped).
  • One element per part. The types used to describe the element are defined in the XSD files (either Additions.xsd or other XSD files).
  • For the fault message, you can reuse the ProcessingFault element type defined in MDMWSDLCommon.xsd.

Once you have described your new Web Service and its data types in XSD schema, you do not need to take any further steps to enable InfoSphere® MDM to support it. New Web Services are automatically supported by the single service provider entry point.