This describes how to create a new message
definition from WSDL using the New Message Definition File wizard in the workbench.
Before you start:
You must have
completed the following tasks:
Before you begin this task you should note the following points:
- To ensure the highest interoperability of your web services you should:
- Use the document style of WSDL whenever possible
- Where the use of rpc style WSDL is necessary, use literal encoding
- Where the use of rpc style with SOAP encoding is necessary, ensure that
the WSDL operation definitions are qualified by a valid namespace attribute
- WSDL definitions can optionally be split into multiple files. The typical
arrangement would be that a top-level service definition file imports a binding
file, the binding file imports an interface file and this finally imports
or includes schema definition files.
- When you create a new message definition file from a WSDL file, the WSDL
file must already be present in your message set project. If the WSDL is split
into multiple files as described above then you can import either the top-level
service definition file or the binding file. In this case the file you import
and any files it refers to using a relative location must be in the workspace
before the WSDL import is run.
- Where you are importing two or more WSDL files that share common schema
definitions, you should import them into separate message set projects to
avoid the likelihood of any name clashes.
- You should add an XML physical format layer and enable namespace support
for the message set that you are adding the new message definition file to.
In order to improve web services interoperability, you should avoid unnecessary
customization of the XML physical format layer for messages participating
in web services processes.
Important: Note that the extension to the file must be .wsdl in
lower case.
The following steps cover creating a completely
new message definition file and also overwriting the contents of an existing
file.
To create a message definition from a WSDL file or files:
When you have completed the WSDL import using
the wizard:
- Carefully check for any errors in the report that is created when the
file is imported. You can find this report in the log directory
within the project containing the message definition that you have attempted
to create. The report has a <wsdl-file-name>.wsdl.report.txt file
descriptor, where <wsdl-file-name> is the name of
the WSDL definition you are importing.
- Review the messages shown in the workbench task
list to check whether any new warnings or errors have appeared.
Note: Any required SOAP Envelope and SOAP encoding message definitions
are automatically added to your message set during the import. If required,
you can also import these manually via the New Message Definition File wizard
by selecting the new option IBM supplied message.