After you confirm your WSDL document sources, the WSDL ODA generates the
business objects and meta-objects for the web service you wish to invoke or
for the collaboration you want to expose as a web service. See Figure 68 and follow the steps below for saving objects.
- Note:
- The WSDL ODA cannot automatically select a key attribute for the top-level
business object. For business objects at all other levels, the WSDL ODA
sets the first attribute as the key. Accordingly, when you save WSDL
ODA-generated objects in Business Object Designer, an error message informs
you that the top-level object is missing a key attribute. Assign a key
attribute that reflects your business data and business object requirements,
then re-save the objects. Use caution when selecting the key
attribute; it is used in event sequencing and may lead to performance
issues if not selected carefully.
- Check Save business objects to a file, or check Open the business objects
in separate windows. The latter choice launches the Business Object
Designer and opens the business objects in that application.
- If you do not want the ODA to continue to run, check Shutdown ODA and
click Finish. Otherwise, just click Finish, and the ODA will be ready
for the next business object generation.
Figure 68. Save window

For request processing, the call to the web service must have a request
and, if synchronous, a response and fault messages. For event
processing, the collaboration exposed must have a request and, if synchronous,
a response and fault messages. The WSDL ODA generates business objects
for each of these including the application-specific information (ASI) at
every level as well as SOAP data handler, and protocol Config MOs. The
SOAP bindings in WSDL document determine the structure of SOAP message.
For more on business object structure, see Business object requirements.
