Web Service Hosting Operations

Mode

The web service mode:

• Use SOAP body contents as Rhapsody message body (default).
• Use entire SOAP envelope as Rhapsody message body.
• Extract contents from SOAP message into Rhapsody message body and properties.

XML Namespace Mapping

Used to handle clients that use unexpected prefixes for the incoming messages. The namespace mapping automatically defines the prefix ns1 to the web service namespace. The prefix soapenv is also automatically defined (internally) as the namespace of the SOAP envelope. This will differ depending on whether the SOAP 1.1 or SOAP 1.2 binding is used.

If you define the soapenv prefix, then your setting overrides the internal setting.

This field is only available if the mode is Extract contents from SOAP message into Rhapsody message body and properties.

Content Extraction

Uses XPaths to extract some content into message properties, and other content into the message body. The message body and each property can only be used once.

This field is only available if the mode is Extract contents from SOAP message into Rhapsody message body and properties.

Mode

The web service mode:

• Use the Rhapsody message body as the contents of the SOAP body (default).
• Use the Rhapsody message body as the entire SOAP envelope.
• Construct the contents of the SOAP body using a template and values from the Rhapsody message body and properties.

Template

The XML template to use to build the contents of the SOAP body:

• To view the default template for the operation, select the View Template button.
• To set the template to the default, select the Reload Template button.

This field is only available if the mode is Construct the contents of the SOAP body using a template and values from the Rhapsody message body and properties.

Content Insertion

Allows values to be inserted into the template that are retrieved from message properties or the entire message body.
Unlike the Input tab, each property and the message body can be used more than once. There is also no need to define namespace mappings as the user controls the template, and hence the prefixes in use.

The Content Type determines whether the value should be treated as Text or XML. If treated as text, then any embedded XML special characters will be escaped, however, if it is treated as XML then it is inserted as an XML structure at the indicated location (that is, the XML tags will not be escaped).

This field is only available if the mode is Construct the contents of the SOAP body using a template and values from the Rhapsody message body and properties.

Mode

The web service mode:

• Use the Rhapsody message body as the contents of the SOAP body (default).
• Use the Rhapsody message body as the entire SOAP envelope.
• Construct the contents of the SOAP body using a template and values from the Rhapsody message body and properties.

Template

The XML template to use to build the contents of the SOAP body.

This field is only available if the mode is Construct the contents of the SOAP body using a template and values from the Rhapsody message body and properties.

Content Insertion

Allows values to be inserted into the template that are retrieved from message properties or the entire message body.

Unlike the Input tab, each property and the message body can be used more than once. There is also no need to define namespace mappings as the user controls the template, and hence the prefixes in use.

The Content Type determines whether the value should be treated as Text or XML. If treated as text, then any embedded XML special characters will be escaped, however, if it is treated as XML then it is inserted as an XML structure at the indicated location (that is, the XML tags will not be escaped).

This field is only available if the mode is Construct the contents of the SOAP body using a template and values from the Rhapsody message body and properties.