| Author |
Message
|
| au@kosa |
 Posted: Wed Jan 10, 2007 9:36 pm Post subject: CEP Node with MB 6.0 |
 |
|
Centurion
Joined: 04 Jan 2007
Posts: 103
Location: pune
|
I am having a serious problem with CEP plugin node with MB 6.0. After installing the IAOS support pac with find and install feature in MB 6.0 Toolkit i can see the detector nodes (Situation Manager and Intelligent router) inside the toolkit palete.
Also the CEP_*.par has been moved ../MQSI/6.0/ Jplugin folder to support the runtime env.
After importing a sample message flow for situation manager, we depolyed the bar file. I am getting the following error in the EVENT log
[
BIP1536S: The Configuration Manager was unable to register for internal subscriptions with broker MB_BRK.
Although the preceding deploy operation was successful, a subsequent attempt by the Configuration Manager to register for internal subscriptions with broker MB_BRK was not successful. This means that Message Brokers Toolkit and Config Manager Proxy applications may not show the correct status of the resources assigned to broker MB_BRK.
]
could any one please help me.
Regards,
au Kosa |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Jan 10, 2007 11:13 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
... Did everything work fine before you deployed this flow?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| au@kosa |
| Posted: Wed Jan 10, 2007 11:32 pm Post subject: |
|
|
Centurion
Joined: 04 Jan 2007
Posts: 103
Location: pune
|
jefflowrey
I imported the Sample Project Bank_project1 in to the toolkit.
It Consists of MQInputNode->Situationmanager Node-> MQoutput Node
The required i/p and o/p queue had been created for the purpose.
It looks the broker is not able to recognise the situation manager node. I do not why? I kept the CEP_*.par file at MQSI/6.0/Jplugin folder. Is there some thing i missed or i need to install some fix pack.
Regards,
au@kosa |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Jan 11, 2007 4:10 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Your initial problem posted was that the configmgr was not able to register for publications with the broker - and this happened after you tried to deploy a flow with the CEP plugin.
That's the question I'm trying to help you with, when I asked "Did this work before you tried to deploy the flow with the CEP Plugin?"
Now you're saying that the CEP plugin hasn't loaded.
These are entirely different problems. Which one do you want to solve first?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| au@kosa |
| Posted: Thu Jan 11, 2007 9:03 pm Post subject: |
|
|
Centurion
Joined: 04 Jan 2007
Posts: 103
Location: pune
|
Thanks Jef,
it seems the documentation file ia0s.pdf page 8
[
copy/move ’/6.0.0.1/bin/cep_6.0.0.1.par’ to the directory ‘<mqsi_root>/6.0/jplugin’ unless this property was changed for a broker
]
is wrong it should be
copy/move ’/6.0.0.1/bin/cep_6.0.0.1.par’ to the mqsi_root>/6.0/bin’
Now i am able to deploy the message flow with out any error but input message lost when it hits the Situation manager node. Nothing appears in the out queue,SIT queue and log file. I tried to catch the exception but nothing appears there too.
My bar file contains only the message flow, no message set right now. If some thing is wrong an exception should be raised, the message should not be lost without any notification.
Desperatly looking for the help here.
Regards,
au kosa |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Jan 12, 2007 2:35 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The SituationManager node should always pass the message from it's input terminal to it's output terminal unchanged.
It's not clear to me how you have your flow wired - I guess you're using a sample flow, but I don't have those samples directly in front of me so I don't want to guess.
If you're not seeing a message on the output terminal of the SituationManager node, then something is wrong.
But if you're simply not seeing any situations detected, that may be normal. You just might not have deployed the situations correctly.
This is a Cat 3 Support pack, so you can open a PMR for it if you have to. But I'll try and find some time to dig in a little more and see what I can see.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| au@kosa |
| Posted: Tue Feb 13, 2007 3:37 am Post subject: CEP problem solved |
|
|
Centurion
Joined: 04 Jan 2007
Posts: 103
Location: pune
|
After installing the fixpack 3 the problem has been fixed
_________________
Regards,
au@kosa
IBM Certified SOA Solution Designer/Associate |
|
| Back to top |
|
|
|
|
