Service Provider Properties

To view or edit a service provider's properties, double-click its Browser or list entry. The property sheet tabs and fields listed here are those available by default, before any customization of the interface by you or an administrator.

The General tab contains the following properties:

Property	Description
Name/Code/Comment	Identify the object. The name should clearly convey the object's purpose to non-technical users, while the code, which is used for generating code or scripts, may be abbreviated, and should not normally include spaces. You can optionally add a comment to provide more detailed information about the object. By default the code is generated from the name by applying the naming conventions specified in the model options. To decouple name-code synchronization, click to release the = button to the right of the Code field.
Stereotype	Extends the semantics of the object. You can enter a stereotype directly in this field, or add stereotypes to the list by specifying them in an extension file.
Filename	Specifies the path to the file that contains the whole service definition. The path is set during import and used during file generation. Use the tools to the right of the box to select a WSDL file or open the currently selected WSDL file.
Endpoint URL	Specifies the address at which the service can be reached.
Target namespace	Specifies a URI (Uniform Resource Identifier) reference that uniquely identifies the web service and avoids conflicts with other web services with the same name. By default, it is: urn:<Service Provider Code>.
Prefix	Specifies a prefix for the target namespace. All the schema elements with this prefix in their start-tag will be associated with the namespace. The default value is: "tns" that stands for "This NameSpace". For example: <tns:invoice>, where "tns" is the prefix associated with the XSD document that describes the "invoice" markup.
Implementation	Specifies a link between the service provider and an OOM component or a PDM database web service. Use the tools to the right of the box to select an implementation object, view the properties of the currently selected object, or remove it.
Keywords	Provide a way of loosely grouping objects through tagging. To enter multiple keywords, separate them with commas.

Service Interfaces Tab

This tab displays a list of service interfaces associated with the service provider (see Service Interfaces (BPM)).

XSD Documents Tab

This tab displays a list of XSD documents that define the data schemas describing the service provider (see XSD Documents).

XML Namespaces Tab

This tab displays a list of XML namespaces prefixes used by the WSDL file. An XML namespace is a URI (Uniform Resource Identifier) reference used in XML documents, which indicates a location where element and attribute names are declared. An XML document can contain element or attribute names from more than one XML vocabulary. If each vocabulary is given a namespace, then the ambiguity between identically named elements or attributes can be resolved.

For example, an XML document can contain references to a customer and an ordered product. Both the customer element and the product element can have a child element named "ID_number". If you declare a namespace (i.e. which vocabulary an element or attribute name comes from) you differentiate them, and avoid ambiguity.

An XML namespace can be created in a choreography diagram with any orchestration languages.

The namespace declaration syntax is the following:

xmlns:prefix="namespaceURI"

An XML namespace contains the following parameters:

Parameter	Description
xmlns	Stands for XML Namespace. Indicates an XML namespace declaration.
:prefix	[optional] Shorthand for the full name of the namespace. It qualifies elements belonging to that namespace. You use it when you need to differentiate same namespace references.
namespaceURI	Uniquely identifies a namespace in the XML document.

The XML namespace can be defined in the XML Namespaces tab for each service provider and XSD document in your model.

In the following example, bk is used as a shorthand for the full name of its respective namespace:

<BOOKS>
  <bk:BOOK xmlns:bk="urn:example.tyler.com:BookInfo"
  <bk:TITLE>Funny Words</bk:TITLE>
</bk:BOOK>
</BOOKS>

Data Schema Tab

This tab contains the data schema of the service provider, which can be created manually or come from:

The imported WSDL
The XSD document associated with an XML model. If there are more than one XSD document, data schemas are concatenated

The Data Schema tab contains the following properties:

Property	Description
Language	Specifies the type of schema language used for message parts. You can enter your own type of language or choose one of the following XML document languages: DTD XML Schema RELAX NG
Data Schema (text box)	Specifies the message part definition details. You can enter any appropriate information in this field, as well as open, insert and save text files.