Generating WSDL from a COBOL copybook in WMB

Technote (FAQ)


Question

What are the steps in WebSphereMessage Broker (WMB) for generating a WSDL from a COBOL copybook?

Answer

With applications and libraries, generating a WSDL from an existing schema is not supported. This is a known requirement.

There are two possible workarounds:

Option 1: To create the WSDL manually by using the WSDL editor, complete the following steps:
a) To create a new WSDL file in your application or library, click File -> New -> Other... -> Web Services -> WSDL. The WSDL file is created, and the following error is displayed in the Problems view:
"The WSDL file 'NewWSDLFile.wsdl' was not added through the Message
Model wizard. This error can be fixed by invoking the Message Model
wizard and importing this WSDL file as a SOAP XML."

b) Right-click on the error from the previous step, select Quick Fix, Finish, Next, Finish.

c) Delete the <WSDL_FILE_NAME>.xsd file that was generated by the Quick Fix. This file is not required.
d) Close and then re-open your WSDL file.

e) Alter the existing operation that is contained in the WSDL file, and add new operations to use messages that are defined in your DFDL files.

f) If you are not using elements or types that are defined in the <WSDL_FILE_NAME>_InlineSchema1.xsd file, you can delete this schema file, and remove the reference to it from your WSDL file.

Option 2: To create the WSDL by using the Generate -> WSDL Definition message set action:

a) Create a temporary message set project.

b) In your temporary message set project, create message definition files for the following XSD files:
i. DFDL schema
ii. IBM supplied DFDL format schema
(for example, CobolDataDefinitionFormat.xsd)

c) To generate a WSDL from the message definition file created in step b) i, right-click on your message set folder and select Generate -> WSDL Definition -> 'Generate a new WSDL definition from existing message definitions' -> Next. A WSDL file is created.

d) Copy the WSDL file to your application or library project and update the path to the DFDL schema in the WSDL file if necessary.

After coping the WSDL file to an application or library, the following error is displayed in the Problems view:

"The WSDL file 'MsgSet1Service.wsdl' was not added through the
Message Model wizard. This error can be fixed by invoking the
Message Model wizard and importing this WSDL file as a SOAP XML."

e) Right-click on the error from the previous step, select Quick Fix, Finish, Next, Finish.

f) Delete the <WSDL_FILE_NAME>.xsd file that was generated by the Quick Fix. This file is not required.

g) Close and then re-open your WSDL file.

h) Update the WSDL file to point to the DFDL schema instead of the
<WSDL_FILE_NAME>_InlineSchema1.xsd file. You might also need to update
the namespace prefix used for the DFDL schema in the WSDL file.

i) Delete the temporary message set project created in step a).

Product Alias/Synonym

WMB MB WebSphere Message Broker MQ Integrator WBIMB WBI-MB MQSI WMQI

Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere Message Broker
Toolkit

Software version:

8.0

Operating system(s):

Linux, Windows

Reference #:

1619020

Modified date:

2012-12-26

Translate my page

Machine Translation

Content navigation