| Author |
Message
|
| abs_cal |
 Posted: Thu Nov 10, 2005 2:18 pm Post subject: Remote Broker Connection |
 |
|
Acolyte
Joined: 18 Aug 2005
Posts: 62
|
Anyone can please help me to find the steps to connect to a remote broker(AIX) to the local broker domain. I have broker installed in AIX but getting error always during deployment. This seem to me, i am missing something during addition of the remote broker.
I have given only Broker name(created in AIX) and associated QMGR for this broker during addition of this broker in WBIMB toolkit domain.
Is this only info, you need to provide for adding a Broker installed in AIX?
Thanks in advance. |
|
| Back to top |
|
 |
| EddieA |
| Posted: Thu Nov 10, 2005 3:47 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
What error.
Do you have channels set up between the broker and the ConfigMgr.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| dipankar |
| Posted: Thu Nov 10, 2005 11:41 pm Post subject: |
|
|
Disciple
Joined: 03 Feb 2005
Posts: 171
|
try this
System A(local) - X (QMGR)--queue manager of configmgr
System B(Remote) - Y (QMGR)--queue manager of Broker
1. create transmission queue in A under X ---Y
2. create transmission queue in B under Y ---X
3. create channel in X
a) sender channel 'X2Y' with transmission Q Y
b)receiver channel 'Y2X'
4.create channel in Y
a) sender channel 'Y2X' with transmission Q X
b)receiver channel 'X2Y'
5) start all channels.
now add the broker in ur toolkit. |
|
| Back to top |
|
|
| abs_cal |
| Posted: Fri Nov 11, 2005 8:11 am Post subject: Here is the error |
|
|
Acolyte
Joined: 18 Aug 2005
Posts: 62
|
Even, i deployed a tiny msgflow..i find below error
BIP1510E: Unable to deploy configuration data.
An attempt was made to deploy configuration data to one or more brokers,
ut the Configuration Manager is already deploying to broker ESBDE01WBRK2.
You can not deploy to a set of brokers if there is an earlier deploy outstanding
to any broker in the set. The deploy operation was not performed.
Wait for the outstanding deploy to complete before retrying the operation.
The Event Log Editor may be used to check that all responses to the outstanding
deploy have been received and processed. If the outstanding deploy does not fully
complete in a suitable period of time, check that all brokers exist and are running,
all WebSphere MQ queue managers are running, and that all channels between queue
managers are started. Also check that deploy messages have been correctly delivered
to the target brokers, and have not been put to the dead letter queue. Correct any
problems you find. If it still does not complete, then cancel the deploy operation
by specifying the 'Cancel' option in the Message Brokers Toolkit Note that 'Cancel'
affects all outstanding deployment operations throughout the domain, so you may not
have the authority to perform this. |
|
| Back to top |
|
|
| jhosie |
| Posted: Fri Nov 11, 2005 8:59 am Post subject: |
|
|
Apprentice
Joined: 12 May 2005
Posts: 28
|
In the Domains view of the Broker Administration perspective, you can right click on your config mgr connection and select "Cancel Deployment".
This will allow you to deploy without this error.
However, you are probably getting this error because the configmgr did not receive a response from the broker for a previous deploy. This is the real problem.
Check the syslog on the brokers machine to see if there are any clues as to why the deploy did not complete.
Verify that your MQ Channels are working okay. Try manually sending messages in both directions between the 2 queue managers. If one of the channels has problems, then either a) the broker will never see the deploy message or b) the broker processes the deploy but the configmgr will never see the response. In either case, that would explain you error message. |
|
| Back to top |
|
|
| abs_cal |
| Posted: Fri Nov 11, 2005 9:07 am Post subject: |
|
|
Acolyte
Joined: 18 Aug 2005
Posts: 62
|
Jhosie..thanks..i checked Chl..and did with cancel deployment..
plz tell me the broker m/c syslog path. Broker in running in AIX box.
Other thing i have noticed, afte cancel deployement, i tried to deploy a tiny(in->out) flow..i was getting those error...
thanks.. |
|
| Back to top |
|
|
| jhosie |
| Posted: Fri Nov 11, 2005 9:23 am Post subject: |
|
|
Apprentice
Joined: 12 May 2005
Posts: 28
|
|
| Back to top |
|
|
| jhosie |
| Posted: Fri Nov 11, 2005 9:26 am Post subject: |
|
|
Apprentice
Joined: 12 May 2005
Posts: 28
|
| you should also take a look at the syslog/eventvwr on the configmgr machine. |
|
| Back to top |
|
|
| abs_cal |
| Posted: Fri Nov 11, 2005 11:30 am Post subject: Here is the error |
|
|
Acolyte
Joined: 18 Aug 2005
Posts: 62
|
Even, i deployed a tiny msgflow..i find below error
BIP1510E: Unable to deploy configuration data.
An attempt was made to deploy configuration data to one or more brokers,
ut the Configuration Manager is already deploying to broker ESBDE01WBRK2.
You can not deploy to a set of brokers if there is an earlier deploy outstanding
to any broker in the set. The deploy operation was not performed.
Wait for the outstanding deploy to complete before retrying the operation.
The Event Log Editor may be used to check that all responses to the outstanding
deploy have been received and processed. If the outstanding deploy does not fully
complete in a suitable period of time, check that all brokers exist and are running,
all WebSphere MQ queue managers are running, and that all channels between queue
managers are started. Also check that deploy messages have been correctly delivered
to the target brokers, and have not been put to the dead letter queue. Correct any
problems you find. If it still does not complete, then cancel the deploy operation
by specifying the 'Cancel' option in the Message Brokers Toolkit Note that 'Cancel'
affects all outstanding deployment operations throughout the domain, so you may not
have the authority to perform this. |
|
| Back to top |
|
|
| abs_cal |
| Posted: Fri Nov 11, 2005 11:32 am Post subject: Now getting DB2 warning.. |
|
|
Acolyte
Joined: 18 Aug 2005
Posts: 62
|
DB2 ERROR---
2005-11-10-19.34.23.178000 Instance:DB2 Node:000
PID:1324(db2fmp.exe) TID:1688 Appid:none
Health Monitor HealthIndicator::update Probe:500
ADM10500E Health indicator "Log Filesystem Utilization" ("db.log_fs_util")
breached the "upper" alarm threshold of "85 %" with value "88 %" on "database"
"DB2.WBRKCMDB". Calculation: "((os.fs_used/os.fs_total)*100);" =
"((17569644544 / 20011589632) * 100)" = "88 %". History (Timestamp, Value,
Formula): "()"
tell me how to increase space!! |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Fri Nov 11, 2005 9:24 pm Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
I'm not sure, but just check......
Use the command below
get db cfg for <DB NAME>
If the propery that u need is listed then increase using......
get dbm cfg => parameter <Property Name> (total number)
Regards. |
|
| Back to top |
|
|
| abs_cal |
| Posted: Mon Nov 14, 2005 9:03 am Post subject: BROKER not running |
|
|
Acolyte
Joined: 18 Aug 2005
Posts: 62
|
I have created new config db and new configmgr to remove earlier error. Connected Remote(AIX) broker into local domain. But warnings are there-broker is not running as well as Execution Gr.(default) is not running. I know execution Gr. is not running because no msgflow was deployed.
Do you know why "broker is not running" warning is coming...??
Second, i tired to deploy a tiny msgflow into the Broker. Successful message came but nothing came out inside execution Gr. --Any Idea??
Channels are running and i started broker..
bye |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Nov 14, 2005 9:08 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Broker doesn't enter "running" state until at least one execution group enters "running" state. EGs don't enter "running" state until at least one flow is deployed.
If flow claims to be deployed, but no flows appear in broker domain, then something is odd. You'll need to troubleshoot to find out what.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| abs_cal |
| Posted: Mon Nov 14, 2005 9:42 am Post subject: |
|
|
Acolyte
Joined: 18 Aug 2005
Posts: 62
|
jefflowrey--Thanks for your remark..First time i am doing this one...that's why i am bit concern whether i am missing any step.
Please check and let me know steps are right..
channels are working as i have sent dummy message from one QMgr to Another.
Then, i have added Remote Broker into domain with add->new->Broker.
Given broker QMGR and broker name.
Is this sufficient step to add a remote broker? Is there anything to check or add?
thanks |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Nov 14, 2005 10:05 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You'll need to check the Event Log in the domain connection to ensure things worked properly.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
