Chapter 19 Working with Sybase Unwired Orchestrator
The XSD schema files contain the definition of the complex data types used within the business process. These data types are used to define context variables that are accessible by the different activities. Each XSD file is a set of elements and complex types that can be used as a data type of a variable. PowerDesigner Business Process Model does not support the extraction of elements and complex types by parsing the content of the file. However, you can use the XML model to reverse engineer XSD files and obtain a graphical view of these files.
| Unwired Orchestrator concept | PowerDesigner concept |
|---|---|
| XSD schema | Message format with XSD stereotype (not mandatory) |
Within Orchestrator, a service interaction activity is an invocation of one WSDL operation. The input or output message of this operation is defined within the WSDL file. When this message is complex, the Schema section in the WSDL file defines this complex type. Orchestrator always extracts the schema section of the WSDL file as an XSD file that defines a variable used to receive an input message or to send an output message.
PowerDesigner imports WSDL files as service providers. The Schema section defined within the WSDL file is imported as DataSchema attribute of the service provider. The input/output messages of the different operations are imported as message formats containing parts. These message formats are used as data types of context variables, which are used to receive or send messages.
So for these variables, the XSD definition file is extracted and generated from the service provider DataSchema attribute. When the DataSchema is empty the following extended attribute is available from the message format with message parts property sheet:
| Extended attribute | Description |
|---|---|
| XSD location | Location of the XSD file that contains the definition of the types used by the parts of the message |
| Copyright (C) 2007. Sybase Inc. All rights reserved. |
| |