Skip to Content
0

PI Operational Mapping Test/Runtime bug?

Nov 22, 2017 at 02:27 PM

34

avatar image

I am wondering if I have uncovered an issue where an operational mapping behaves differently depending on whether unit testing via the Test tab, or using in the runtime.

SAP NetWeaver Enterprise Services Builder version 7.5, dual stack.

The operational map has 3 message maps.

1) an XSLT map to sort the XML input.

2) a validation map that modifies one field based on values in other fields.

3) a message split that outputs 2 message types (one an aggregation and a second a filter of incoming records).

The input and output of the XSLT and validation mappings should be the same message type. The input of the split should be that same type.

Here starts the issues:

The message splitting map creates Messages/Message{1..n} envelopes on the output, and requires a Messages/Message1 envelope on the input.

Neither the Test tab, nor testing in run time will work unless the validation map outputs the Messages/Message1 envelopes, so I "hacked" the solution by changing the validation mapping to be a 1:0..1 cardinality.

Now the Test tab is failing because the XSLT is not adding the Messages/Message1 envelopes. So I coded them into the XSLT.

Now my Test tab works.

Except my run time does not.

If I remove the Messages/Message1 envelopes from the XSLT output, the Test tab will fail, but the run time will work.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

0 Answers