Data Mapping

Data mapping defines the relationships between field-value pairs in external

systems and
property-value pairs on Process Commander clipboard pages. Before you continue
reading this section, read Chapter 5 (Data Mapping) in PegaRULES Process Commander
Integrating with External Systems.
A SOAP service rule form has two tabs for mapping data:
■ Request — use this tab to specify how to map the arguments from incoming SOAP
messages to properties on the clipboard (Map To).
■ Response — use this tab to specify how the service rule constructs the response
to be
sent from Process Commander in reply to the request (Map From).
To determine how to configure the data mapping for a SOAP service rule, consider
how
you want to work with the data in the SOAP client application. For example, will
the
client application work with simple string or numeric values? Will the client
application
work with XML data or complex object values? Your assessment reveals which of the
following data mapping options you must use for each argument included in the SOAP
message:
■ Simple argument-property mapping – used when the data in the SOAP message
arguments can be mapped directly to and from clipboard properties or activity
parameter values.
■ XML parse and stream rules – used to parse or assemble string argument values
that
contain XML data and the SOAP operation style is RPC.
■ Model rules – used to describe the schema of the message when the message
contains an XML object and the SOAP operation style is document.
■ Special parameters – used to map authentication values for a stateful service
when a
SOAP client does not support HTTP Basic Authentication, or to map the requestor
ID for a stateful service when the SOAP client does not support cookies.
For information about using XML parse and stream rules, and model rules that are
used
to define schema, see the document Data Mapping XML posted on the Integration
Services pages of the Pega Developer Network. For information about the data types
for
simple argument-property mapping, see the Application Developer help system.

Special Parameters
The SOAP service allows values for user name and password to be sent directly to
PRSOAPServlet through HTTP Basic Authentication. During a stateful session, the
Requestor ID is automatically sent to the SOAP client as a token in a cookie. In
certain
cases, however, you cannot take advantage of these built in features. For those
cases, the
SOAP service rule supports three default parameters that appear as options in the
Map To
field on the Request tab:
■ Username
■ Password
■ Requestor ID
For example, if the SOAP client does not support HTTP Basic Authentication but the
service must run as an authenticated user, create data mapping entries for the
Username
and Password parameters on the Request tab of the service rule. If the SOAP client
does
not support cookies and the session is stateful, create a data mapping entry for
the
Requestor ID parameter on the Response tab of the service rule. In both cases, you
select
the parameter from the list in the Map To or Map From field and leave the Map To
Key
or Map From Key field blank.
Process Commander and the PRSOAPServlet manage these default parameters
automatically. Yo