Importing XSD files

An XSD (XML Schema Definition) file defines the structure of the data, which a data object contains. You import an XSD file in your project if you want to set a data type that is different from the primitive ones to a data object.

The data mapping in the process composer does not support all data types. For more information about all limitations on data types, see the SAP Note 1468084 .

Your process model does not directly use the XSD documents that you import and are contained in your project. The documents are first imported into the Enterprise Service Modeling (ESM) repository, which saves the imported data in its own proprietary format. The repository is seamlessly integrated into your project and the import takes place in the background.

When you import or reimport XSD documents into your project, it is possible that one and the same entity, meaning an entity with the same qualified name has a different definition in the document that you are trying to import, compared to the definition already existing in the project and defined by other documents. Such different definitions of the same entity are not allowed because of the qualified name uniqueness concept. If such a conflict occurs, you have the following options in the dialog comparing the two definitions:

• Update the files

  If you choose the Update Files >> pushbutton, the entity definition that comes from the document you are trying to import overrides the old entity definition both in the repository and in the files of the already imported documents. The new document is imported. You must use this option carefully because it can have a severe impact at runtime. Choose this option only if you are sure that all existing documents that contain this entity have changed and use the new entity definition. If you are not sure, get the latest versions of these documents, reimport them, and if you still get this conflict, reject the import.

• Reject the import

  If you choose the Reject pushbutton, the document that you are trying to import is not imported into the repository and appears only in your project with an error marker. If you still want to use this document, you must import it into another project.

  You can check all the documents that define a conflicting entity when you choose the Show/Hide Affected Schemas button, located in the top-left corner of the dialog.

You have opened the Process Development perspective in the SAP NetWeaver Developer Studio and have expanded your project in Project Explorer view.

1. Expand Process Modeling , then expand Data Types .

2. In the context menu of the XSD Files folder, choose Import XSD... .

3. Choose the Browse pushbutton to define an output folder for the XSD source file. Choose the OK pushbutton.

   We recommend that you select the src\wsdl folder in your project for an output folder.

4. Select Remote Location / File System from the Available XSD sources and choose the Next pushbutton.

5. Select an XSD file to import.

   To do that, choose one of the following options:

   • Choose the Browse pushbutton and navigate through the file system to select the XSD file you want to import.

   • Enter a URL to import the XSD file from.

6. Choose the Finish pushbutton.

   The XSD file appears in your project, in  Process Modeling  Data Types  XSD Files  folder. The XSD source file appears in the output folder you defined.