ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » XML Tranformation Issue

Post new topic  Reply to topic Goto page 1, 2  Next
 XML Tranformation Issue « View previous topic :: View next topic » 
Author Message
rsmile
PostPosted: Wed Feb 13, 2008 11:11 pm    Post subject: XML Tranformation Issue Reply with quote

Apprentice

Joined: 13 Feb 2008
Posts: 38

Hi All,

We have a message flow where we are using XML Tranformation Node to apply a XSL transformation to a given inut XML message.

We need to use XML Tranformation twice in the same flow on the same input message as per our business logic.

The first time we apply the Tranformation we were able to apply XSL succesfully,thena again we are reconstructing the original message and passing it to the 2nd XMLT Node.

When the message reaches the 2nd XMLT node we are getting an Error as follows:

Quote:
XML Writing Errors have occurred <com.ibm.broker.plugin.MbParserException class:JNI method:ImbGenericXmlParser::refreshBitStreamFromElements source:BIPv600 key:5010>


When we verify the input message it is being the same for the 2nd time.We are not understanding why we are getting this error.

Could some one help us? Any help is appreciated.
Back to top
View user's profile Send private message
AJStar
PostPosted: Thu Feb 14, 2008 12:21 am    Post subject: Reply with quote

Acolyte

Joined: 27 Jun 2007
Posts: 64

Why / How are you re-constructing your message?

Can't you use a FlowOrder node?
_________________
Regards
AJ
Back to top
View user's profile Send private message
rsmile
PostPosted: Thu Feb 14, 2008 12:54 am    Post subject: Reply with quote

Apprentice

Joined: 13 Feb 2008
Posts: 38

As the tranformation applies the transformation through XSL we will get the tranformed output from the 1st Tranfromation node.We need to reconstruct the message as we need the actual message after the transformation.

We are reconstructing the message by retaining the actual message in the environment root & then copying it back.

How does flow order node help us in this situation?
Back to top
View user's profile Send private message
AJStar
PostPosted: Thu Feb 14, 2008 1:21 am    Post subject: Reply with quote

Acolyte

Joined: 27 Jun 2007
Posts: 64

Just look up FlowOrder node in the documentation.

FlowOrder node sends the original message through path2, even if the message is altered in path1.
_________________
Regards
AJ
Back to top
View user's profile Send private message
kimbert
PostPosted: Thu Feb 14, 2008 1:35 am    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton

So the product has issued an error message, but it does not contain enough information.
Q: How can you get the product to give more diagnostic info?
A: User trace is your friend. Get into the habit of using it as a debugging tool.

http://publib.boulder.ibm.com/infocenter/wmbhelp/v6r1m0/topic/com.ibm.etools.mft.doc/au14220_.htm
Back to top
View user's profile Send private message
rsmile
PostPosted: Thu Feb 14, 2008 1:44 am    Post subject: Reply with quote

Apprentice

Joined: 13 Feb 2008
Posts: 38

Here is the user trace, now can we get any help?

I had observed the path that says:

Quote:
ParserException BIP5005E: No valid body of the document could be found.
There should be one, and only one, top level element of type Element or EmptyElement and this is not the case for the current message.
Check that the XML message being passed in is a well formed XML message that adheres to the XML specification and that only one of the above exists as a child of the root.


Probably this is what is the problem,I'm working on it, but please provide any inputs if you have any!!

Quote:
Timestamps are formatted in local time, 330 minutes past GMT.
Trace written by version 6003; formatter version 6003

2008-02-14 15:03:12.589947 3340 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'TranformSalesList.MQInput'.
2008-02-14 15:03:12.590170 3340 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node 'TranformSalesList.MQInput' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2008-02-14 15:03:12.590201 3340 UserTrace BIP6061I: Parser type ''MQMD'' created on behalf of node 'TranformSalesList.MQInput' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value ''MQHMD'' from previous parser.
2008-02-14 15:03:12.590231 3340 UserTrace BIP6061I: Parser type ''XMLNSC'' created on behalf of node 'TranformSalesList.MQInput' to handle portion of incoming message of length '4700' bytes beginning at offset '364'. Parser type selected based on value ''XMLNSC'' from previous parser.
2008-02-14 15:03:15.624952 3340 UserTrace BIP4007I: Message propagated to 'out' terminal of node 'TranformSalesList.CopyXSLT2Environment'.
2008-02-14 15:03:15.958836 3340 UserTrace BIP3904I: Invoking the evaluate() method of node (class='ComIbmXslMqsiNode', name='TranformSalesList#FCMComposite_1_3').
About to pass a message to the evaluate() method of the specified node.
No user action required.
2008-02-14 15:03:16.171710 3340 UserTrace BIP4201I: Message propagated to out terminal from node 'TranformSalesList.ResetContentDescriptor'.
A reset content descriptor node has received a message and is propagating it to any nodes connected to its out terminal.
No user action required.
2008-02-14 15:03:16.383953 3340 UserTrace BIP4008I: Message propagated to '''out1''' terminal of node 'TranformSalesList.Propagate'.
2008-02-14 15:03:16.581277 3340 UserTrace BIP2638I: The MQ output node 'TranformSalesList.MQOutput2' attempted to write a message to queue ''OT.SUB_VALIDATION'' connected to queue manager ''DIDEV''. The MQCC was '0' and the MQRC was '0'.
2008-02-14 15:03:16.581298 3340 UserTrace BIP2622I: Message successfully output by output node 'TranformSalesList.MQOutput2' to queue ''OT.SUB_VALIDATION'' on queue manager ''DIDEV''.
2008-02-14 15:03:16.581476 3340 UserTrace BIP4007I: Message propagated to 'out' terminal of node 'TranformSalesList.Propagate'.
2008-02-14 15:03:17.289657 3340 UserTrace BIP4007I: Message propagated to 'out' terminal of node 'TranformSalesList.XSL_SUBFLOW.Compute'.
2008-02-14 15:03:17.789432 3340 UserTrace BIP3904I: Invoking the evaluate() method of node (class='ComIbmXslMqsiNode', name='TranformSalesList#FCMComposite_1_8.XSL_SUBFLOW#FCMComposite_1_1').
About to pass a message to the evaluate() method of the specified node.
No user action required.
2008-02-14 15:03:17.790006 3340 UserTrace BIP2231E: Error detected whilst processing a message in node 'TranformSalesList.XSL_SUBFLOW.Transformation'.
The message broker detected an error whilst processing a message in node 'TranformSalesList.XSL_SUBFLOW.Transformation'. The message has been augmented with an exception list and has been propagated to the node's failure terminal for further processing.
See the following messages for details of the error.
2008-02-14 15:03:17.790018 3340 RecoverableException BIP5010E: XML Writing Errors have occurred.
Errors have occurred during writing of XML.
Review further error messages for an indication to the cause of the errors.
2008-02-14 15:03:18.457138 3340 Error BIP2232E: Error detected whilst handling a previous error in node 'TranformSalesList.MQOutput1'.
The message broker has detected an error in node 'TranformSalesList.MQOutput1' whilst handling a previous error.
See the following messages for details of the exception list associated with the original error. Thereafter messages will be associated with the new error.
2008-02-14 15:03:18.457155 3340 RecoverableException BIP2230E: Error detected whilst processing a message in node 'TranformSalesList.XSL_SUBFLOW.Transformation'.
The message broker detected an error whilst processing a message in node 'TranformSalesList.XSL_SUBFLOW.Transformation'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2008-02-14 15:03:18.457162 3340 RecoverableException BIP5010E: XML Writing Errors have occurred.
Errors have occurred during writing of XML.
Review further error messages for an indication to the cause of the errors.
2008-02-14 15:03:18.457437 3340 UserTrace BIP2231E: Error detected whilst processing a message in node 'TranformSalesList.Validation'.
The message broker detected an error whilst processing a message in node 'TranformSalesList.Validation'. The message has been augmented with an exception list and has been propagated to the node's failure terminal for further processing.
See the following messages for details of the error.
2008-02-14 15:03:18.457447 3340 RecoverableException BIP2230E: Error detected whilst processing a message in node 'TranformSalesList.MQOutput1'.
The message broker detected an error whilst processing a message in node 'TranformSalesList.MQOutput1'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2008-02-14 15:03:18.457452 3340 ParserException BIP5010E: XML Writing Errors have occurred.
Errors have occurred during writing of XML.
Review further error messages for an indication to the cause of the errors.
2008-02-14 15:03:18.457462 3340 ParserException BIP5005E: No valid body of the document could be found.
There should be one, and only one, top level element of type Element or EmptyElement and this is not the case for the current message.
Check that the XML message being passed in is a well formed XML message that adheres to the XML specification and that only one of the above exists as a child of the root.
2008-02-14 15:03:18.719110 3340 UserTrace BIP2638I: The MQ output node 'TranformSalesList.MQOutput1' attempted to write a message to queue ''WEB.OUT'' connected to queue manager ''DIDEV''. The MQCC was '0' and the MQRC was '0'.
2008-02-14 15:03:18.719127 3340 UserTrace BIP2622I: Message successfully output by output node 'TranformSalesList.MQOutput1' to queue ''WEB.OUT'' on queue manager ''DIDEV''.

Threads encountered in this trace:
3340
[/quote]
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Thu Feb 14, 2008 1:54 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

rsmile wrote:

ParserException BIP5005E: No valid body of the document could be found.
There should be one, and only one, top level element of type Element or EmptyElement and this is not the case for the current message.
Check that the XML message being passed in is a well formed XML message that adheres to the XML specification and that only one of the above exists as a child of the root.

You cannot move an MRM body to an XMLNS or XMLNSC body without adding the xml root tag.
The xml root tag is implied in MRM and defined as per the message type.

Enjoy
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
jefflowrey
PostPosted: Thu Feb 14, 2008 2:24 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

fjb_saper wrote:
You cannot move an MRM body to an XMLNS or XMLNSC body without adding the xml root tag.
The xml root tag is implied in MRM and defined as per the message type.


While that's all true, it's irrelevant to the situation, as the usertrace clearly shows that the XMLNSC parser is being used.

It appears that the XSLT is producing a bad message, or an empty output.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
rsmile
PostPosted: Thu Feb 14, 2008 2:47 am    Post subject: Reply with quote

Apprentice

Joined: 13 Feb 2008
Posts: 38

Thank you for the responses.

In Debugger, I 'm able to see the message being constructed properly.But still goes to failure terminal.

Any Clues?
Back to top
View user's profile Send private message
AJStar
PostPosted: Thu Feb 14, 2008 3:11 am    Post subject: Reply with quote

Acolyte

Joined: 27 Jun 2007
Posts: 64

Can you post that message?
_________________
Regards
AJ
Back to top
View user's profile Send private message
kimbert
PostPosted: Thu Feb 14, 2008 3:45 am    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton

Quote:
Here is the user trace, now can we get any help?
Now that help is possible, I will gladly give it.

You are giving a badly-constructed message tree to the XMLNSC parser. It cannot output a well-formed XML message using that message tree. Insert a Trace node before the second XMLT node, and look carefully at the children of Root.XMLNSC.

Quote:
In Debugger, I 'm able to see the message being constructed properly
How do you define 'properly'?
Back to top
View user's profile Send private message
rsmile
PostPosted: Thu Feb 14, 2008 3:48 am    Post subject: Reply with quote

Apprentice

Joined: 13 Feb 2008
Posts: 38

Here is the output:

Quote:
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xml" href="#arrestssId" ?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:web="http://datashare.nyc.gov/schema/webservice" xmlns:arr="http://datashare.nyc.gov/schema/exchange/arrestreport" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<soapenv:Header>
.....................
</soapenv:Header>
<soapenv:Body>
</soapenv:Body>
</soapenv:Envelope>
Back to top
View user's profile Send private message
kimbert
PostPosted: Thu Feb 14, 2008 3:54 am    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton

Thanks for posting that, but I'm not sure it helps very much. The problem is in the structure of the message tree. The only useful thing to post at this point is a trace of that message tree.
Back to top
View user's profile Send private message
rsmile
PostPosted: Thu Feb 14, 2008 4:13 am    Post subject: Reply with quote

Apprentice

Joined: 13 Feb 2008
Posts: 38

Thank you again.

Here is the output from the Trace node:

Quote:

(
(0x01000000):Properties = (
(0x03000000):MessageSet = ''
(0x03000000):MessageType = ''
(0x03000000):MessageFormat = ''
(0x03000000):Encoding = 273
(0x03000000):CodedCharSetId = 437
(0x03000000):Transactional = TRUE
(0x03000000):Persistence = FALSE
(0x03000000):CreationTime = GMTTIMESTAMP '2008-02-14 12:09:59.090'
(0x03000000):ExpirationTime = -1
(0x03000000):Priority = 0
(0x03000000):ReplyIdentifier = X'000000000000000000000000000000000000000000000000'
(0x03000000):ReplyProtocol = 'MQ'
(0x03000000):Topic = NULL
(0x03000000):ContentType = ''
)
(0x01000000):MQMD = (
(0x03000000):SourceQueue = 'Input'
(0x03000000):Transactional = TRUE
(0x03000000):Encoding = 273
(0x03000000):CodedCharSetId = 437
(0x03000000):Format = 'MQSTR '
(0x03000000):Version = 2
(0x03000000):Report = 0
(0x03000000):MsgType = 8
(0x03000000):Expiry = -1
(0x03000000):Feedback = 0
(0x03000000):Priority = 0
(0x03000000):Persistence = 0
(0x03000000):MsgId = X'414d5120444944455620202020202020921db4472000140f'
(0x03000000):CorrelId = X'000000000000000000000000000000000000000000000000'
(0x03000000):BackoutCount = 0
(0x03000000):ReplyToQ = ' '
(0x03000000):ReplyToQMgr = 'DIDEV '
(0x03000000):UserIdentifier = 'rcherukuri '
(0x03000000):AccountingToken = X'16010515000000dbeb0c503b245e6907e53b2bf003000000000000000000000b'
(0x03000000):ApplIdentityData = ' '
(0x03000000):PutApplType = 11
(0x03000000):PutApplName = 'ava\jdk1.5.0_14\bin\java.exe'
(0x03000000):PutDate = DATE '2008-02-14'
(0x03000000):PutTime = GMTTIME '12:09:59.090'
(0x03000000):ApplOriginData = ' '
(0x03000000):GroupId = X'000000000000000000000000000000000000000000000000'
(0x03000000):MsgSeqNumber = 1
(0x03000000):Offset = 0
(0x03000000):MsgFlags = 0
(0x03000000):OriginalLength = -1
)
(0x01000000):XMLNSC = (
(0x01000000):XmlDeclaration = (
(0x03000000):Version = '1.0'
(0x03000000):Encoding = 'UTF-8'
)
(0x01000000)http://schemas.xmlsoap.org/soap/envelope/:Envelope = (
(0x03000000)http://www.w3.org/2000/xmlns/:soapenv = 'http://schemas.xmlsoap.org/soap/envelope/'
(0x03000000)http://www.w3.org/2000/xmlns/:web = 'http://datashare.nyc.gov/schema/webservice'
(0x03000000)http://www.w3.org/2000/xmlns/:arr = 'http://datashare.nyc.gov/schema/exchange/arrestreport'
(0x03000000)http://www.w3.org/2000/xmlns/:xsl = 'http://www.w3.org/1999/XSL/Transform'
(0x01000000)http://schemas.xmlsoap.org/soap/envelope/:Header = (
(0x01000000)http://schemas.xmlsoap.org/soap/envelope/:DoittHeader = (
(0x03000000):version = '1.0'
(0x01000000):service = (
(0x03000000):version = '1.0'
(0x03000000):serviceId = 'ARRESTREPORT'
)
(0x01000000):user = (
(0x03000000):userId = 'User01'
(0x01000000):securityToken =
)
(0x01000000):context = (
(0x03000000):externalId = 'NYPD'
(0x03000000):instanceId = 'Instanceid01'
)
(0x03000000):audit = 'true'
(0x03000000):logLevel = '1'
)
(0x01000000)http://schemas.xmlsoap.org/soap/envelope/:ExchangeHeader = (
(0x03000000):version = '1.0'
(0x01000000):description = (
(0x03000000):version = '1.0'
(0x03000000):id = 'id'
(0x03000000):name = 'name'
(0x03000000):group = 'group'
)
(0x01000000):validation = (
(0x03000000):validate = 'true'
(0x03000000):id = '10'
)
(0x01000000):transformation = (
(0x03000000):transform = 'true'
(0x03000000):id = '20'
)
(0x01000000):persistence = (
(0x03000000):persist = 'false'
(0x03000000):id = '30'
)
(0x01000000):publication = (
(0x03000000):publish = 'true'
(0x03000000):id = '10'
)
)
(0x01000000)http://schemas.xmlsoap.org/soap/envelope/:ValidationHeader = (
(0x03000000):id = '10'
(0x03000000):version = '1.0'
(0x03000000):type = 'XSLT'
(0x01000000):xsltContext = (
(0x03000000):version = '1.0'
(0x03000000):source = 'INLINE'
(0x01000000):file = (
(0x03000000):name = 'arrestReport.xsl'
(0x03000000):directory = 'InputValidation'
)
(0x01000000):db = (
(0x03000000):name = 'XSLT'
(0x03000000):xsltId = 'REPORT1'
)
(0x01000000):xslt = (
(0x01000000)http://www.w3.org/1999/XSL/Transform:stylesheet = (
(0x03000000):id = 'arrestssId'
(0x03000000):version = '1.0'
(0x03000000)http://www.w3.org/2000/xmlns/:soapenv = 'http://schemas.xmlsoap.org/soap/envelope/'
(0x03000000)http://www.w3.org/2000/xmlns/:arr = 'http://datashare.nyc.gov/schema/exchange/arrestreport'
(0x03000000)http://www.w3.org/2000/xmlns/:xsl = 'http://www.w3.org/1999/XSL/Transform'
(0x01000000)http://www.w3.org/1999/XSL/Transform:template = (
(0x03000000):match = '/'
(0x01000000):ValidationResult = (
(0x01000000)http://www.w3.org/1999/XSL/Transform:if = (
(0x03000000):test = 'string-length(/soapenv:Envelope/soapenv:Body/arr:ArrestReportDocument/arrestee/id/arrestId) <13'
(0x01000000)http://www.w3.org/1999/XSL/Transform:value-of = (
(0x03000000):select = '/soapenv:Envelope/soapenv:Body/arr:ArrestReportDocument/arrestee/id/firstName'
)
)
(0x01000000)http://www.w3.org/1999/XSL/Transform:if = (
(0x03000000):test = 'string-length(/soapenv:Envelope/soapenv:Body/arr:ArrestReportDocument/arrest/location/state) > 2'
(0x03000000)http://www.w3.org/1999/XSL/Transform:message = 'State value can not be greater than 2 characters'
)
)
)
)
)
)
(0x01000000):wsContext = (
(0x03000000):version = '1.0'
(0x03000000):operation = '/ArrestReportValidation/ArrestReportInterfaceImpl'
(0x03000000):url = '192.168.41.24:7001'
)
(0x01000000):mrmContext = (
(0x03000000):version = '1.0'
(0x03000000):messageSet = 'messageSet'
(0x03000000):messageType = 'messageType'
(0x03000000):messageFormat = 'messageFormat'
)
)
(0x01000000)http://schemas.xmlsoap.org/soap/envelope/:TransformationHeader = (
(0x03000000):id = '20'
(0x03000000):version = '1.0'
(0x03000000):type = 'XSLT'
(0x01000000):xsltContext = (
(0x03000000):version = '1.0'
(0x03000000):source = 'DB'
(0x01000000):file = (
(0x03000000):name = 'arrestReport.xsl'
(0x03000000):directory = 'InputValidation'
)
(0x01000000):db = (
(0x03000000):name = 'XSLT'
(0x03000000):xsltId = 'REPORT2'
)
(0x01000000):xslt = (
(0x01000000)http://www.w3.org/1999/XSL/Transform:stylesheet = (
(0x03000000):id = 'arrestssId1'
(0x03000000):version = '1.0'
(0x03000000)http://www.w3.org/2000/xmlns/:soapenv = 'http://schemas.xmlsoap.org/soap/envelope/'
(0x03000000)http://www.w3.org/2000/xmlns/:arr = 'http://datashare.nyc.gov/schema/exchange/arrestreport'
(0x03000000)http://www.w3.org/2000/xmlns/:xsl = 'http://www.w3.org/1999/XSL/Transform'
(0x01000000)http://www.w3.org/1999/XSL/Transform:template = (
(0x03000000):match = '/'
(0x01000000):ValidationResult = (
(0x01000000)http://www.w3.org/1999/XSL/Transform:if = (
(0x03000000):test = 'string-length(/soapenv:Envelope/soapenv:Body/arr:ArrestReportDocument/arrestee/id/arrestId) <13'
(0x01000000)http://www.w3.org/1999/XSL/Transform:value-of = (
(0x03000000):select = '/soapenv:Envelope/soapenv:Body/arr:ArrestReportDocument/arrestee/id/lastName'
)
)
(0x01000000)http://www.w3.org/1999/XSL/Transform:if = (
(0x03000000):test = 'string-length(/soapenv:Envelope/soapenv:Body/arr:ArrestReportDocument/arrest/location/state) > 2'
(0x03000000)http://www.w3.org/1999/XSL/Transform:message = 'State value can not be greater than 2 characters'
)
)
)
)
)
)
(0x01000000):wsContext = (
(0x03000000):version = '1.0'
(0x03000000):operation = '/ArrestReportValidation/ArrestReportInterfaceImpl'
(0x03000000):url = '192.168.41.24:7001'
)
(0x01000000):mrmContext = (
(0x03000000):version = '1.0'
(0x03000000):messageSet = 'messageSet'
(0x03000000):messageType = 'messageType'
(0x03000000):messageFormat = 'messageFormat'
)
)
(0x01000000)http://schemas.xmlsoap.org/soap/envelope/:PersistanceHeader = (
(0x03000000):id = '10'
(0x03000000):version = '1.0'
(0x03000000):content = 'BINARY'
(0x01000000):storagetype = (
(0x01000000):dbStorage = (
(0x03000000):dbURL = 'dbURL'
(0x03000000):dbName = 'dbName'
)
(0x01000000):queueStorage = (
(0x03000000):queueName = 'queueName'
(0x03000000):queueManager = 'queueManager'
)
(0x01000000):fileStorage = (
(0x03000000):fileName = 'fileName'
(0x03000000):directory = 'directory'
)
)
(0x03000000):binaryContentType = 'PDF'
(0x01000000):pocketContentType = (
(0x03000000):pocketSize = '1'
(0x03000000):docType = 'BINARY'
)
)
(0x01000000)http://schemas.xmlsoap.org/soap/envelope/:PublicationHeader = (
(0x03000000):id = '10'
(0x03000000):version = '1.0'
)
)
(0x01000000)http://schemas.xmlsoap.org/soap/envelope/:Body = (
(0x03000000)http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd:Id = 'Body-6d6012b1-c7a8-425f-b3e8-cfcf082a823d'
(0x03000000)http://www.w3.org/2000/xmlns/:wsu = 'http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd'
(0x01000000)http://datashare.nyc.gov/schema/exchange/arrestreport:ArrestReportDocument = (
(0x01000000):arrestee = (
(0x01000000):id = (
(0x03000000):arrestId = 'NYC-ARRA4-01'
(0x03000000):firstName = 'Siva'
(0x03000000):lastName = 'Natarajan'
)
(0x03000000):gender = 'Male'
(0x03000000):age = '30'
(0x03000000):alias = 'God'
)
(0x01000000):arrest = (
(0x01000000):location = (
(0x03000000):street = 'Wall Street'
(0x03000000):city = 'New York'
(0x03000000):state = 'NY'
(0x03000000):zip = '19380'
)
(0x03000000):processingType = 'Testing'
(0x03000000):isFingerPrintable = 'true'
(0x03000000):isCopySent = 'false'
(0x01000000):incidentData = (
(0x03000000):comment = 'Incident1'
)
(0x01000000):deskAppearanceData = (
(0x03000000):comment = 'Desk1'
)
(0x01000000):bookingData = (
(0x03000000):comment = 'Booking Comment1'
)
(0x03000000):topChargeMethodType = 'TopCharge'
(0x03000000):crimeEventCode = 'CrimeEvent'
)
(0x01000000):arrestingOfficer = (
(0x03000000):firstName = 'Farhan'
(0x03000000):lastName = 'Abbasi'
(0x03000000):internalRank = 'Officer'
(0x03000000):command = 'Command01'
(0x03000000):shieldNo = '2343'
)
(0x01000000):charges = (
(0x01000000):chargeCode = (
(0x03000000):code = '200'
(0x03000000):class = 'Roe'
(0x03000000):title = 'Test'
(0x03000000):counts = '1'
(0x03000000):attemptedFlag = 'true'
(0x03000000):legalLanguage = 'Y'
)
)
)
)
)
)
)

Back to top
View user's profile Send private message
rsmile
PostPosted: Thu Feb 14, 2008 4:24 am    Post subject: Reply with quote

Apprentice

Joined: 13 Feb 2008
Posts: 38

How can I format this log into an understandable format ?

I tried using mqsiformatlog -i input.log -o formattedTrace.log, but I'm getting the output like below:

Quote:
BIP5004E: XML parsing error ('An exception occurred! Type:RuntimeException, Message:The primary document entity could not be
d. Id=E:/IBM/MQSI/6.0/logs/Tranform_Trace.log ') encountered on line 0 column 0 while parsing element ''.
The above error was reported by the generic XML parser.
This message is usually caused by a badly-formed XML message. Check that the XML message being passed in is a well-formed XML
age that adheres to the XML specification. Note that the line number and column number quoted above give the position where t
rser discovered the problem. The actual error may be earlier in the message. Internal error codes : (-1), ('').

BIP8047E: Unable to parse the data received, exception caught 'ImbException'.
The command uses parser functions to analyze XML data, the parser has detected an error in the format of the XML data being p
. Use the line number and column number to locate the XML causing the problem.
Check that the data being parsed is correctly formatted. The command may produce partial output. It may also be possible to m
the XML data that the command is parsing so that the error does not occur.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page 1, 2  Next Page 1 of 2

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » XML Tranformation Issue
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.