Understanding Upstream Interface Parameters

After the initial translation has occurred, the contents of messages sent from upstream systems are analyzed by the SRT at run time. After initial translation, the service bundle configuration enables the SRT to analyze the contents of messages from upstream. To accomplish this, you map the parameters that the messages contain to those required by the service actions that have been associated with the service bundle.

Note:

Some upstream interface parameters may not be used in the provisioning process. Upstream interface parameters can be mapped to lookups for further processing, for example to split parameters apart or to concatenate them together.

To map upstream interface parameters to service action parameters, you add the parameters to the Upstream Interface list:

Automatically based on service action labels. When you associate service actions with the service bundle, Design Studio asks you whether you want to use the service action labels to populate the upstream interface parameter list. If you elect to do so, Design Studio places the parameters in the parameter list on the Service Bundle editor Upstream Interface tab.
Manually in the Service Bundle editor. If you know what the upstream labels will be but do not have a sample XML document that can be imported, the parameters can be added in manually.
Import the upstream parameters from a sample upstream service request (in XML format). Using this method, Design Studio runs a transformation against the upstream XML file and extracts the interface parameters. The XSLT that implements the transformation must first be created by a technical resource such as a developer. See "Configuring Translations" for more information.