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 » Convert base64binary to a MRM

Post new topic  Reply to topic
 Convert base64binary to a MRM « View previous topic :: View next topic » 
Author Message
giorginus80
PostPosted: Wed Aug 06, 2008 5:36 am    Post subject: Convert base64binary to a MRM Reply with quote

Centurion

Joined: 08 Jul 2008
Posts: 124
Location: Rome, Italy

Hi,
I'm trying to convert a field of a xmlnsc field, uploaded by a webservice exposed by the broker 6.1, into a mrm.
Initially for testing I was using a mq input with blob parser and the using an esql node to convert it into a mrm like this

Code:

      DECLARE parseOptions INTEGER BITOR(FolderBitStream, ValidateContent,
      ValidateValue, ValidateLocalError);      

      CREATE FIELD OutputRoot.MRM.io:body;
      DECLARE bodyRef REFERENCE TO OutputRoot.MRM.io:body;      
      
      CREATE LASTCHILD OF bodyRef
      PARSE ( msgBitStream
      OPTIONS parseOptions
      SET inMessageSet
      TYPE inMessageType
      FORMAT inMessageFormat);


msgBitStream is a shared variable which contains the message in BLOB format got from queue with blob parsing.
If I got from webservice I need to give the base64binary, so I don't know if it's the right way, then I convert the base64binary to blob, but in this way it doesn't parse with no errors.
What can I do to have from a base64binary a field like a blob like I get it from a queue with blob parser?
Back to top
View user's profile Send private message
kimbert
PostPosted: Wed Aug 06, 2008 6:15 am    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton

http://publib.boulder.ibm.com/infocenter/wmbhelp/v6r1m0/topic/com.ibm.etools.mft.doc/ac67201_.htm

No point in using the MRM for this. Use XMLNSC in validating mode, and tick the box on the Parser Options page of the input node which says 'Build tree using XML Schema'.

Alternatively, search this forum for 'base64 java' and find out how to do it quite easily with a Java method call direct from ESQL.
Back to top
View user's profile Send private message
giorginus80
PostPosted: Wed Aug 06, 2008 6:27 am    Post subject: Reply with quote

Centurion

Joined: 08 Jul 2008
Posts: 124
Location: Rome, Italy

Quote:
tick the box on the Parser Options page of the input node which says 'Build tree using XML Schema'.


Ok now I try, but I have the httpInputnode and this option is disabled!!! is it the same?
Back to top
View user's profile Send private message
giorginus80
PostPosted: Wed Aug 06, 2008 6:32 am    Post subject: Reply with quote

Centurion

Joined: 08 Jul 2008
Posts: 124
Location: Rome, Italy

Exscuse for me I had a bug in my workspace. Ok I add the options in my httpinputnode but now I got this exception:

Code:

ExceptionList
   RecoverableException
         File:CHARACTER:/build/S610_P/src/DataFlowEngine/ImbDataFlowNode.cpp
         Line:INTEGER:739
         Function:CHARACTER:ImbDataFlowNode::createExceptionList
         Type:CHARACTER:ComIbmWSInputNode
         Name:CHARACTER:it/capgemini/emsg/EMessageFlow#FCMComposite_1_6
         Label:CHARACTER:it.capgemini.emsg.EMessageFlow.HTTP Input
         Catalog:CHARACTER:BIPv610
         Severity:INTEGER:3
         Number:INTEGER:2230
         Text:CHARACTER:Node throwing exception
         RecoverableException
               File:CHARACTER:/build/S610_P/src/DataFlowEngine/PluginInterface/ImbJniNode.cpp
               Line:INTEGER:1021
               Function:CHARACTER:ImbJniNode::evaluate
               Type:CHARACTER:ComIbmJniNode
               Name:CHARACTER:it/capgemini/emsg/EMessageFlow#FCMComposite_1_7.gen/it/capgemini/emsg/EMessageSerieService_EMessageFlow#FCMComposite_1_1
               Label:CHARACTER:it.capgemini.emsg.EMessageFlow.EMessageSerieService.Extract
               Catalog:CHARACTER:BIPv610
               Severity:INTEGER:3
               Number:INTEGER:2230
               Text:CHARACTER:Caught exception and rethrowing
               ParserException
                     File:CHARACTER:/build/S610_P/src/MTI/MTIforBroker/GenXmlParser4/ImbXMLNSCParser.cpp
                     Line:INTEGER:858
                     Function:CHARACTER:ImbXMLNSCParser::parseFirstChild
                     Type:CHARACTER:
                     Name:CHARACTER:
                     Label:CHARACTER:
                     Catalog:CHARACTER:BIPv610
                     Severity:INTEGER:3
                     Number:INTEGER:5009
                     Text:CHARACTER:XML Parsing Errors have occurred
                     ParserException
                           File:CHARACTER:/build/S610_P/src/MTI/MTIforBroker/GenXmlParser4/ImbXMLNSCDocHandler.cpp
                           Line:INTEGER:527
                           Function:CHARACTER:ImbXMLNSCDocHandler::handleParseErrors
                           Type:CHARACTER:ComIbmWSInputNode
                           Name:CHARACTER:it/capgemini/emsg/EMessageFlow#FCMComposite_1_6
                           Label:CHARACTER:it.capgemini.emsg.EMessageFlow.HTTP Input
                           Catalog:CHARACTER:BIPv610
                           Severity:INTEGER:3
                           Number:INTEGER:5025
                           Text:CHARACTER:A schema validation error has occurred while parsing the XML document
                           Insert
                                 Type:INTEGER:2
                                 Text:CHARACTER:5032
                           Insert
                                 Type:INTEGER:2
                                 Text:CHARACTER:2
                           Insert
                                 Type:INTEGER:2
                                 Text:CHARACTER:1
                           Insert
                                 Type:INTEGER:2
                                 Text:CHARACTER:234
                           Insert
                                 Type:INTEGER:5
                                 Text:CHARACTER:Unexpected root tag. Element "soapenv:Envelope" is not a global element.
                           Insert
                                 Type:INTEGER:5
                                 Text:CHARACTER:/Root/XMLNSC


It is strange, because I did the wsdl from message format, and then I drag and dropped wsdl to have httpinputnode.
Back to top
View user's profile Send private message
giorginus80
PostPosted: Wed Aug 06, 2008 6:55 am    Post subject: Reply with quote

Centurion

Joined: 08 Jul 2008
Posts: 124
Location: Rome, Italy

Ok Thanks....I used resetcontentdescritor node after remove the soapenvelope, so putting validation and build tree to resetcontentdescriptor it worked. Thanks
Back to top
View user's profile Send private message
kimbert
PostPosted: Wed Aug 06, 2008 11:05 am    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton

I should have explained that 'Build tree using XML Schema' is disabled if Validation is set to 'None'. The reason should be fairly obvious : unless the XML parser is using an XML schema, it does not know which XML schema types to put into the message tree.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Convert base64binary to a MRM
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.