| Author |
Message
|
| protocol |
 Posted: Tue Aug 02, 2005 1:20 am Post subject: RM Descriptor Not Found |
 |
|
Apprentice
Joined: 25 Feb 2005
Posts: 41
|
Hi All,
I am having a simple flow in which i am trying to map from a TDS to CWF using the Mapping node.
This is failing with the following error
'RM Descriptor Not Found'.
When i try the same thing using a Compute node and mapping using ESQL it seems to be working fine.
Why am i getting this RM Descriptor Error ?
I am on CSD 5.
[/b] |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Aug 02, 2005 3:19 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
What is the rest of the error message?
What is the BIP number? Did you look the BIP number up to see what the documentation says?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| protocol |
| Posted: Tue Aug 02, 2005 5:10 am Post subject: |
|
|
Apprentice
Joined: 25 Feb 2005
Posts: 41
|
Hi Jeff,
The following is the error message i see in the Event Viewer :
( BROKER1.default ) Message Format 'TDS1' does not match a Wire Format Identifier or a Format Name.
The Message Format is used to identify a Physical Format layer in the message set (via the Wire Format Identifier of the layer).
Message Set HEDEMJO002001 did not contain any Physical Format layer with a Wire Format Identifier of 'TDS1'.
The Message Format can also identify a bitstream worker by its name, but 'TDS1' is not a valid name for a bitstream worker. 'xml','cwf','tds' and 'pdf' are valid names, and others may be available on your system.
If the Message Format was intended to identify a Physical Format layer, check that the Message Format has been specified correctly, and check that the message set has been deployed successfully.
If the Message Format was intended to refer to a bitstream worker, check that the appropriate bitstream worker file (dll or shared object) exists in the correct directory.
E.g. On NT if we send an XML message to the broker we should have the file bipxmlworker.wrk in the <MQSI dir>/bin directory. Other platforms should have the .wrk files in the <MQSI dir>/lib directory.
Ensure that all the required workers are available and have loaded without error.
I am confused.
Message Set HEDEMJO002001 did not contain any Physical Format layer with a Wire Format Identifier of 'TDS1'.
The above line does not seem to make sense as the Set HEDEMJO002001 is the target CWF message set. Why should it have a TDS Wire Format Identifier ?
Does this mean that i cannot use the mapping node to map from TDS to CWF ?
Can anybody please clarify ? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Aug 02, 2005 5:30 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
If your TDS structure is in a different message description file, then you need to ensure that you correct the OutputRoot.Properties.MessageSet to indicate the proper message set ID.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mqsidude |
| Posted: Tue Aug 02, 2005 12:25 pm Post subject: |
|
|
Centurion
Joined: 22 Jan 2004
Posts: 148
|
I strongly suspect that you are not setting the 'MessageFormat' property of Properties tree correctly. When you are mapping TDS to CWF, i guess that 'MessageFormat' property is still set to 'TDS1' which is the TDS layer ID of your message set. Set this property to the CWF layer ID value, probably something like 'CWF1'
Cheers!
Crony |
|
| Back to top |
|
|
| protocol |
| Posted: Tue Aug 02, 2005 9:37 pm Post subject: |
|
|
Apprentice
Joined: 25 Feb 2005
Posts: 41
|
Hi Guys,
Thanks for your replies.
| Quote: |
When you are mapping TDS to CWF, i guess that 'MessageFormat' property is still set to 'TDS1' which is the TDS layer ID of your message set. Set this property to the CWF layer ID value, probably something like 'CWF1'
|
| Quote: |
If your TDS structure is in a different message description file, then you need to ensure that you correct the OutputRoot.Properties.MessageSet to indicate the proper message set ID.
|
But i am using a mapping node and so cannot modify the Properties Tree. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Aug 03, 2005 3:18 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| protocol wrote: |
| But i am using a mapping node and so cannot modify the Properties Tree. |
But an RCD should do just fine.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
