This section outlines some common problems that can arise when using messages. It contains advice for dealing with the problems:
This puts your updated message to the queue.
<?xml version ="1.0" standalone="no"?><!DOCTYPE doc [<!ELEMENT doc (#PCDATA)*>]><doc><I1>100</I1></doc>You apply the ESQL transform:
SET OutputRoot.XML.doc.I1 = 112233;This generates the XML message (after serialization):
<?xml version ="1.0" standalone="no"?><!DOCTYPE doc [<!ELEMENT doc (#PCDATA)*>]<I1>112233<I1>><doc><I1>100</I1></doc>The new value for I1 has been put inside the DOCTYPE, and has not replaced the value of 100, as you expected.
The parser has found the first instance of an element called doc and has created a child I1 with the value 112233.
SET OutputRoot.XML.(XML.tag)doc.I1 = 112233;
<doc><I1>100</I1></doc>The Compute node in the message flow contains the following ESQL:
SET OutputRoot.XML.abc = InputBody;You expect the following output message to be created:
<abc><doc><I1>100</I1></doc></abc>
The Compute node generates error message BIP5005 and does not implement the ESQL.
SET OutputRoot.XML.(XML.Element)abc = InputBody;or:
SET OutputRoot.XML.(XML.tag)abc = InputBody;
Solution 1: Either clear this field, or set it to the root tag used by all your XML messages. If you provide a value in this field, the root tag does not need to be modelled in all your message definitions.
Similarly, if you set XML in the Properties folder for the output message in the Compute node, this value is passed to the parser when it creates the message bit stream from the message tree, usually in the Output node.
XMLWorker::initializeParse file:C:\s000\src\cpi\pwf\xml\xmlworker.cpp line:126 message:5409.BIPv500 No dictionary present have you specified Wire Format 'XML' in error? , UserTrace BIP5409E: XML Worker: Wire Format 'XML' specified. Default MRM XML settings are being used because wire format identifier 'XML' was specified and not found. This can be due to an incorrect setting of the wire format identifier in a message.
Solution 2: If you have incorrectly entered the identifier of the format that you have defined, correct your code and retry. If you do not want the default action to be taken, define a physical layer that produces the required results.
Related concepts
XML parser and domains
Related tasks
Configuring Custom Wire Format (CWF) properties: Message sets
Dealing with problems
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
au16550_ |