Troubleshooting
Problem
When creating business objects in WebSphere Integration Developer, in versions 6.0 through to and including 6.2.0.1, global complex types are created in an XML schema file.
Cause
This is working as designed. However, some other products such as IBM WebSphere Transformation Extender, instead require a global element in the XML schema file. While WebSphere Integration Developer does not generate this element, you can add it manually and it will be preserved.
Resolving The Problem
To manually add and preserve an element in an XML schema file, choose one of the following options.
Option A
Using the following example, there is a library named CommonLibrary with a business object named Address, as shown here:

To manually add the element, right click on the business object in the Business Integration view and select Open With -> Text Editor. From the text editor, insert a namespace prefix declaration "tns" for the target namespace and a global element referring to the existing global complex type.
Using the Address business object as shown above, the XSD file would look like this before editing:

This is the same example after adding the "tns" declaration and the global element referring to the existing global complex type:

The additions are lines 3 and 5. Note that the element can have the same name as the complex type, such as "Address". However, from release V6.1.0 and on, in some WebSphere Integration Developer selection lists, you will see one entry for the element and one for the type. Therefore, if they have the same name it might be difficult to distinguish them. As of release V6.2.0.1, in such selection lists, the icons for elements are differentiated from the icons for types, as shown here in the interface editor:

Option B
An alternative option is to turn the complex type into an anonymous type, so that only one entry shows in WebSphere Integration Developer selections lists in version 6.1.0 and above, as shown here:

In this case, lines 4 and 18 have been added. Line 5 has also been changed to remove the name attribute from the complex type definition. This has been cut and pasted into the new element definition in line 4.
When choosing this approach, be aware that you cannot create a new business object that inherits from (or "extends" in XML schema terms) this business object due to XML schema specification rules.
Note that using either one of these options ensures that the new element will be preserved by WebSphere Integration Developer when you edit the business object in the business object editor.
Was this topic helpful?
Document Information
More support for:
WebSphere Integration Developer
Software version:
6.2.0.1, 6.2, 6.1.2, 6.1.0.1, 6.1, 6.0.2.2, 6.0.2, 6.0.1.2, 6.0.1.1, 6.0.1, 6.0
Operating system(s):
Linux, Windows
Document number:
396221
Modified date:
15 June 2018
UID
swg21399071