| Author |
Message
|
| bobgosling |
 Posted: Wed Jan 26, 2005 9:33 am Post subject: Parser Implementation Libraries |
 |
|
Novice
Joined: 16 Jan 2004
Posts: 12
Location: London , UK
|
Trying to install a Win-XP ConfigMgr with a Solaris Broker.
The 2 QMs can talk to each other OK, I tested with a localQ on each pointing to a remoteQ on the other and can drop a message in one Q and read it in the counterpart so I'm sure comms between the 2 is working OK
Trying to deploy one of the sample flows to check it all works but I get :
BIP2293E: Invalid configuration message containing attribute value 'MRM': not valid for target attribute 'messageDomainProperty' on object 'TextMessenger.TEXTMESSENGER'.
The message broker received a configuration message containing an attribute value which is not valid for the target attribute 'messageDomainProperty' on an object on this broker. The value is case sensitive and must match one of the parsers registered with this broker.
Ensure that the value of the attribute is correct and that all the required parser implementation libraries have been installed, then redeploy the message flow.
+++++++++++++++++++++++++++++++++++
I have been unable to find any info in the docs about "parser implementation libraries". Can anyone help with what they are and where they are installed ? I'm guessing that something was not installed correctly.
Yes, I am running with the latest versions/CSDs/fixpaks of everything !
Unimpressed with this product so far. It's about as user friendly as a cornered rat .... |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Jan 26, 2005 9:41 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Did you successfully register the broker with the configuration manager?
Does it show up in your Domain view?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kirani |
| Posted: Wed Jan 26, 2005 11:52 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Please post WMQI related questions into WMQI forum,
[Moving to WMQI Support forum]
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| bobgosling |
| Posted: Thu Jan 27, 2005 2:11 am Post subject: |
|
|
Novice
Joined: 16 Jan 2004
Posts: 12
Location: London , UK
|
Sorry, I originally posted this to the install forum because I thought was probably an installation issue.
In the Toolkit I can see DBRK_QM@localhost:1414 and I can Connect to it.
Broker Topology then shows Broker=DBROKER with Execution Group=default and I get an alert saying "Execution Group is not running", which is unsuprising as I haven't deployed anything to it yet.
I get no other errors ( nothing in Event Log and no timestamps updated on any files in the Solaris Broker directory ).
I have very little hair left. Someone please help before I need to buy a wig ... |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Jan 27, 2005 5:19 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
This may be an installation issue.
It may be a deployment issue.
But it's still a WBIMB issue... 
What are you putting into the BAR file?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| bobgosling |
| Posted: Thu Jan 27, 2005 5:40 am Post subject: headbutting brick wall |
|
|
Novice
Joined: 16 Jan 2004
Posts: 12
Location: London , UK
|
The TextMessenger & Pager example from the Help / Help Contents / Explore the Getting started samples.
I manually created the required queues on my Broker QM as local queues.
Interestingly we tried a bog-standard InputNode to OutputNode with no Message Domain defined ( i.e. defaulting to BLOB ) and this works OK so we are now convinced that we do not have any permission or comms issues. We can deploy a simple message flow OK but trying the same thing with the IBM examples gives us the BIP2293E message Invalid configuration message containing attribute value 'MRM' etc ( see original post for full text )
I am going to try uninstalling & reinstalling the Solaris WBIMB as a last resort but our sys admin won't have time to do it this week so if in the meantime anyone has any suggestions I will happily try them.
Its a lot of money to pay for something that just copies between queues ... |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Jan 27, 2005 5:40 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Are you including the message set as well as the message flows?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kirani |
| Posted: Fri Jan 28, 2005 12:13 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Try to create a small message flow with simple message set and see if that deploys ok.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| bobgosling |
| Posted: Fri Jan 28, 2005 1:08 am Post subject: Please close this thread now. |
|
|
Novice
Joined: 16 Jan 2004
Posts: 12
Location: London , UK
|
A reinstall fixed it so obviously something was not quite right after the original install.
Thanks to everyone who tried to assist with this.
Next time I'll try a reinstall first ...
There is one other thing I noticed during this debacle which I will mention here so searches pick it up. It seems that the default "lil" path in the mqsicreatebroker command on Solaris may be incorrect ( or maybe just a symptom of our failed install ?). I had to set it via a "mqsichangebroker {brokername} -l /opt/mqsi/lil " because I was getting a BIP2241E error. Anyway that just made the problem move downstream and the reinstall appears to have fixed the problem. |
|
| Back to top |
|
|
|
|
