Composite Operation and Input Mapping Terminology and Configuration Guidelines

Understand composite operation related terminology to better understand how to configure composite operation input mappings.

The example MBO project used to illustrate the following terminology is located at the SAP® Community Network: http://scn.sap.com/docs/DOC-8803.

  • EIS operations accept one or more EIS arguments – an EIS argument is conceptually similar to a parameter accepted by a Java method call. The physical representation of an EIS argument varies with each endpoint type. For example, the interface to a REST Web service is defined via an XSD and each root element contained in the XSD represents an EIS argument.
  • EIS arguments have one or more levels such that child levels are nested under parent levels – EIS arguments are represented as a hierarchy consisting of one or more levels:


    eisArguments

  • Top level EIS argument – the root level of the EIS argument hierarchy:


    topLevelEisArgument

  • Repeating MBO – an MBO which is on the many side of a relationship in the composite graph, or which has an ancestor in the composite graph which is on the many side of a relationship.


    repeatingMBO

  • Input source – the input source is one of the following: an MBO composite graph, a client parameter, or a personalization key.


    inputSource

    Client parameters can be mapped only to the top level (not fields in the top level) of an EIS argument:


    validInputMappingClientParameter

    To map a personalization key into a repeating argument element, there must be an attribute mapped into the same level.

    For example, using the REST example MBO model, with the arguments required by an operation on the Order MBO: A personalization key cannot be mapped into items.item.productid unless some repeating attribute is mapped into one of the other primitives contained by items.item:


    validInputMappingPersonalizationKey

    Note: Sybase Unwired WorkSpace version 2.2 SP01 and later does not allow manually adding links from personalization keys and client parameters into the same remote operation argument. If a migrated project includes that scenario, Sybase Unwired WorkSpace maintains the linking but generates a warning message similar to:
    Client parameter 'parameterName' might not be used,
 as the mapped argument has 'Fill from Attribute' or 
'Personalization Key' specified."
    After migrating the project, remove the additional link (either the personalization key or the client parameter) from the input mapping. In cases where both a client parameter and personalization key are mapped, the personalization key value is used. Sybase Unwired WorkSpace no longer allows mapping attributes into arguments that are already mapped to personalization keys or client parameters.
Parent topic: Composite Operation and Input Mapping Validation Rules and Error Messages