Author |
Message
|
elvis_gn |
Posted: Tue Feb 28, 2006 1:17 am Post subject: |
|
|
 Padawan
Joined: 08 Oct 2004 Posts: 1905 Location: Dubai
|
Hi nik_iway,
Are you saying that your message set it not added to the execution group if u use the Bar and it is if you use the RAD...??
Is the message set added to your Bar atleast...?
If this is your situation, then there has to be a problem somewhere....you should try making the Bar work, as production environments look better with Bar and not RAD...
Regards. |
|
Back to top |
|
 |
kimbert |
Posted: Tue Feb 28, 2006 1:17 am Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
Quote: |
Can a message set name contain whitespace within its name? |
Yes
Quote: |
Why is it not working wen i am creating the bar file and deploying it to the execution group... wat is the difference? |
The difference is that when you use RAD to do the deployment, the message set gets deployed! You must explicitly add the message set to the BAR file - just checking the tick box 'Include Message Flow/Set source' is not enough. All that does is put a copy of the projects into the BAR file. Also, if a message flow project references a message set project, that does not mean that the message set will automatically get added to the BAR file along with the message flow. |
|
Back to top |
|
 |
nik_iway |
Posted: Tue Feb 28, 2006 1:27 am Post subject: |
|
|
Centurion
Joined: 21 Jul 2005 Posts: 115
|
Hi Elvis,
messageset.msgset - messageset file
BookStoreOrder.mxsd - Message Definition File
are added to the bar file, Still the same error why?
Kimbert,
You must explicitly add the message set to the BAR file - kimbert
How can we acheive that............
Regards
Nik |
|
Back to top |
|
 |
elvis_gn |
Posted: Tue Feb 28, 2006 1:31 am Post subject: |
|
|
 Padawan
Joined: 08 Oct 2004 Posts: 1905 Location: Dubai
|
Hi nik_iway,
nik_iway wrote: |
You must explicitly add the message set to the BAR file - kimbert
How can we acheive that............ |
When you add files to the Bar, select the message flow AND select the message set (actually select the Set project itself).
You MUST see a dictionary file, along with the msgflow file, after the addition....
If it is not seen, then there is a prolem in the message set.
Regards. |
|
Back to top |
|
 |
nik_iway |
Posted: Tue Feb 28, 2006 1:34 am Post subject: |
|
|
Centurion
Joined: 21 Jul 2005 Posts: 115
|
Hi Kimbert,
I got it, i need to checkin message set explicitly while creating the bar file the that belongs to the message flow, but i am getting the following output :
<?xml version="1.0"?>
<MRM xmlns="www.mrmnames.net/KTI2KM8002001">
<ShippingDetails>
<CustomerDetails>
<FirstName>Sandra</FirstName>
<LastName>Postlethwaite</LastName>
<Address>7 Mycenae Street</Address>
<ZipCode>SO21 2JN</ZipCode>
</CustomerDetails>
<BookDetails>
<Title>Sitting Pretty</Title>
<Author>Tim Gordon</Author>
<Price>1.5E+1</Price>
</BookDetails>
</ShippingDetails>
</MRM>
if i want the XML to be :
<?xml version="1.0"?>
<ShippingDetails>
<CustomerDetails>
<FirstName>Sandra</FirstName>
<LastName>Postlethwaite</LastName>
<Address>7 Mycenae Street</Address>
<ZipCode>SO21 2JN</ZipCode>
</CustomerDetails>
<BookDetails>
<Title>Sitting Pretty</Title>
<Author>Tim Gordon</Author>
<Price>1.5E+1</Price>
</BookDetails>
</ShippingDetails>
what needs to be done??
regards
Nik |
|
Back to top |
|
 |
dipankar |
Posted: Tue Feb 28, 2006 1:41 am Post subject: |
|
|
Disciple
Joined: 03 Feb 2005 Posts: 171
|
Nik,
I told u before this
Quote: |
Have you added your message set project into your bar file? |
_________________ Regards |
|
Back to top |
|
 |
elvis_gn |
Posted: Tue Feb 28, 2006 1:41 am Post subject: |
|
|
 Padawan
Joined: 08 Oct 2004 Posts: 1905 Location: Dubai
|
Hi nik_iway,
Look at supress Doctype in message set properties.
Regards. |
|
Back to top |
|
 |
kimbert |
Posted: Tue Feb 28, 2006 1:51 am Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
Quote: |
Look at supress Doctype in message set properties. |
I think nik will be more interested in the 'Root Tag Name' property. It defaults to 'MRM', but most people need it to be empty. |
|
Back to top |
|
 |
nik_iway |
Posted: Tue Feb 28, 2006 1:54 am Post subject: |
|
|
Centurion
Joined: 21 Jul 2005 Posts: 115
|
Hi Elvis,
In the Message Set Phyisical Properties - XML1
I cheked the Suppress XML Declarations and
I checked the Suppress DOCTYPE settings but still i am getting the
The following XML as Output:
<MRM xmlns="www.mrmnames.net/KTI2KM8002001">
<ShippingDetails>
<CustomerDetails>
<FirstName>Sandra</FirstName>
<LastName>Postlethwaite</LastName>
<Address>7 Mycenae Street</Address>
<ZipCode>SO21 2JN</ZipCode>
</CustomerDetails>
<BookDetails>
<Title>Sitting Pretty</Title>
<Author>Tim Gordon</Author>
<Price>1.5E+1</Price>
</BookDetails>
</ShippingDetails>
</MRM>
Any suggestions...
Nik |
|
Back to top |
|
 |
dipankar |
Posted: Tue Feb 28, 2006 2:01 am Post subject: |
|
|
Disciple
Joined: 03 Feb 2005 Posts: 171
|
I am not very sure. It may work
the default value Root tag name is MRM. Just make it null. _________________ Regards |
|
Back to top |
|
 |
nik_iway |
Posted: Tue Feb 28, 2006 2:05 am Post subject: |
|
|
Centurion
Joined: 21 Jul 2005 Posts: 115
|
Hi Dipankar,
It worked making the Root Tag Name Null
Thank you all for ur valuable advices
Regards
Nik |
|
Back to top |
|
 |
elvis_gn |
Posted: Tue Feb 28, 2006 2:07 am Post subject: |
|
|
 Padawan
Joined: 08 Oct 2004 Posts: 1905 Location: Dubai
|
Hi,
kimbert:
For me the Root Tag Name is always blank anyway
But I agree that even if we supress the Doctype..the MRM tag will appear...i think
nik_iway:
Uncheck the supress Doctype, make the DOCType system Id blank and then check it again....Now try
Regards. |
|
Back to top |
|
 |
kimbert |
Posted: Tue Feb 28, 2006 5:18 am Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
Quote: |
For me the Root Tag Name is always blank anyway |
That's because you're using v6. In earlier versions, it defaults to 'MRM' |
|
Back to top |
|
 |
raja_no_1 |
Posted: Sun May 21, 2006 11:29 am Post subject: |
|
|
 Apprentice
Joined: 05 Sep 2005 Posts: 34
|
I am trying the same sample that is mentioned in this post and from the red book "message broker basics". I am following the step by step as is mentioned in the doc on page 116.
I am using Broker -V6.
Message defn contains two messages BookStoreOrder and ShippingDetails.
Flow MQInput --> Tracing1-->Mapping --> Tracing2--> MQOutput
Output of Trace1
Code: |
(0x01000021):MRM = (
(0x01000013):CustomerDetails = (
(0x0300000B):FirstName = 'Sandra'
(0x0300000B):LastName = 'Postlethwaite'
(0x0300000B):Address = '7 Mycenae Street'
(0x0300000B):ZipCode = 'SO21 2JN'
)
(0x01000013):Book = (
(0x0300000B):Title = 'Sitting Pretty'
(0x0300000B):Author = 'Tim Gordon'
(0x0300000B):Edition = 1
(0x0300000B):Date = DATE '1976-05-23'
(0x0300000B):Publisher = 'Hamble and Bursledon'
(0x0300000B):ISBN = 'FT03449302 0'
(0x0300000B):Genre = 'Thriller'
)
(0x01000013):BookOrder = (
(0x0300000B):Format = 'Hardback'
(0x0300000B):Price = 1.5E+1
|
Output of Trace2:
Code: |
(0x01000021):MRM = (
(0x01000000):CustomerDetails = (
(0x03000000):FirstName = 'Sandra'
(0x03000000):LastName = 'Postlethwaite'
(0x03000000):Address = '7 Mycenae Street'
(0x03000000):ZipCode = 'SO21 2JN'
)
(0x01000000):BookDetails = (
(0x03000000):Title = 'Sitting Pretty'
(0x03000000):Author = 'Tim Gordon'
(0x03000000):Price = 1.5E+1
)
)
)
|
But the message goes to the failure Queue.
Trace output which occurs before the failure queue:
Code: |
(0x0100001B):MRM = (
(0x01000013):CustomerDetails = (
(0x0300000B):FirstName = 'Sandra'
(0x0300000B):LastName = 'Postlethwaite'
(0x0300000B):Address = '7 Mycenae Street'
(0x0300000B):ZipCode = 'SO21 2JN'
)
(0x01000013):Book = (
(0x0300000B):Title = 'Sitting Pretty'
(0x0300000B):Author = 'Tim Gordon'
(0x0300000B):Edition = 1
(0x0300000B):Date = DATE '1976-05-23'
(0x0300000B):Publisher = 'Hamble and Bursledon'
(0x0300000B):ISBN = 'FT03449302 0'
(0x0300000B):Genre = 'Thriller'
)
(0x01000013):BookOrder = (
(0x0300000B):Format = 'Hardback'
(0x0300000B):Price = 1.5E+1
)
)
|
Which is same as the input message.
The input xml which I am using is
Code: |
<BookStoreOrder><CustomerDetails>
<FirstName>Sandra</FirstName>
<LastName>Postlethwaite</LastName>
<Address>7 Mycenae Street</Address>
<ZipCode>SO21 2JN</ZipCode>
</CustomerDetails>
<Book>
<Title>Sitting Pretty</Title>
<Author>Tim Gordon</Author>
<Edition>1</Edition>
<Date>1976-05-23T01:00:00</Date>
<Publisher>Hamble and Bursledon</Publisher>
<ISBN>FT03449302 0</ISBN>
<Genre>Thriller</Genre>
</Book>
<BookOrder>
<Format>Hardback</Format>
<Price>15.00</Price>
</BookOrder>
</BookStoreOrder>
|
The error which I am getting is the following:
Code: |
2006-05-21 20:15:46.322921 3796 RecoverableException BIP2488E: ('.IBM_WBIMB_BookStoreFLow_Mapping.MAIN', '3.1') Error detected whilst executing the SQL statement ''BookStoreFLow_Mapping(InputRoot, OutputRoot, InputLocalEnvironment, OutputLocalEnvironment);''.
The message broker detected an error whilst executing the given statement. An exception has been thrown to cut short the SQL program.
See the following messages for details of the error.
2006-05-21 20:15:46.322959 3796 RecoverableException BIP2934E: Error detected whilst executing the function or procedure ''BookStoreFLow_Mapping''.
The message broker detected an error whilst executing the function or procedure ''BookStoreFLow_Mapping''. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2006-05-21 20:15:46.322982 3796 RecoverableException BIP2488E: ('.BookStoreFLow_Mapping', '121.2') Error detected whilst executing the SQL statement ''PROPAGATE FINALIZE DEFAULT DELETE DEFAULT;''.
The message broker detected an error whilst executing the given statement. An exception has been thrown to cut short the SQL program.
See the following messages for details of the error.
2006-05-21 20:15:46.323001 3796 RecoverableException BIP2230E: Error detected whilst processing a message in node 'BookStoreFLow.MQOutput'.
The message broker detected an error whilst processing a message in node 'BookStoreFLow.MQOutput'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2006-05-21 20:15:46.323020 3796 ParserException BIP5136E: Invalid Wire Format Identifier ''''.
When processing an MRM message the broker requires a valid wire format identifier.
Check that you have packaged the message correctly and set the correct message properties then resubmit the message.
2006-05-21 20:15:46.323520 3796 UserTrace BIP2539I: Node 'BookStoreFLow.Trace3': Evaluating expression ''Root'' at ('', '1.3'). This resolved to ''Root''. The result was ''ROW... Root Element Type=16777216 NameSpace='' Name='Root' Value=NULL''.
|
Please can someone guide me. Thanks in advance. |
|
Back to top |
|
 |
kimbert |
Posted: Sun May 21, 2006 12:38 pm Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
This exception is the key:
Quote: |
ParserException BIP5136E: Invalid Wire Format Identifier ''''. |
It's saying that Properties.MessageFormat is set to the empty string. You might want to check your message flow and ensure that you are setting all of the critical MRM parser properties ( Domain [must be 'MRM'], MessageSet, MessageType, MessageFormat ). Otherwise you might find that you end up solving this in three or four stages.
If the RedBook is giving incomplete or inaccurate instructions, please post again, so that we can get the situation sorted. |
|
Back to top |
|
 |
|