| Author |
Message
|
| solomita |
 Posted: Fri Jun 24, 2005 2:28 pm Post subject: BIP133E when trying to add linux broker to toolkit |
 |
|
Voyager
Joined: 06 May 2003
Posts: 94
|
I recently created a broker on linux and my chls are running between the broker and the configmgr. Both my config mgr and broker are running and it says "Broker not running" in toolkit as well - But when I went to add to the toolkit, this is what happened - any ideas? I have verified the info that it suggests.
BIP1533E: Unable to deploy configuration data: unknown WebSphere Business Integration queue manager WBRKLXDB associated with broker WBRKLXDB.
An attempt was made to deploy configuration data to one or more brokers. The WebSphere Business Integration queue manager WBRKLXDB associated with broker WBRKLXDB is not known to the Configuration Manager's WebSphere Business Integration queue manager. The deploy operation was not performed.
Check that the name of the queue manager is spelled correctly. Note that WebSphere Business Integration queue manager names are case-sensitive. If the spelling is correct, make sure that either a queue manager alias definition for queue manager WBRKLXDB, or a transmission queue called WBRKLXDB, is defined to the Configuration Manager's queue manager. For more information on this error see the WebSphere Business Integration Application Programming Reference manual, code 2087.
_________________
IBM Certified Specialist - WebSphere MQ Integrator
IBM Certified System Administrator - WebSphere MQ V5.3
IBM Certified System Administrator - WebSphere Business Integration Message Broker V5 |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Fri Jun 24, 2005 2:38 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Have you previously established proper MQ network connectivity between the ConfigMgr queue manager and the broker queue manager? And is it working?
Because the error says that it is not working or has not been set up.
You need a two sender-receiver pairs between the queue managers and two transmission queues, or you need to cluster the two queue managers together.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| solomita |
| Posted: Tue Jun 28, 2005 3:19 pm Post subject: |
|
|
Voyager
Joined: 06 May 2003
Posts: 94
|
I have made the necessary changes and have chls up and running between my config mgr and broker. When I deploy, I now get these errors:
BIP2066E: Broker LINUX3 (UUID 2c6ffcc4-0401-0000-0080-8258071abfb5) was unable to retrieve an internal configuration response message for execution group '$SYS_mqsi' within the 360 second Configuration Timeout.
The execution group did not respond within the Configuration Timeout period. A negative response is returned to the Configuration Manager for this execution group. The Configuration Timeout is the maximum length of time that an execution group is allowed to apply a deployed configuration change. By default the Configuration Timeout period is 300 seconds. You can increase (or decrease) the timeout by using the mqsichangebroker option, ConfigurationTimeout. This will not resolve any underlying problem with the deployed message, but can be used to reduce the response turnaround time or increase it to allow for large and complex deployments.
Investigate why the execution group was unable to respond before being timed out. Use the system log messages to determine if there is a problem with the execution group. You should check that your system is not running short of resources, for example, you may need to increase the WebSphere MQ log size. Reducing the complexity of the deploy by reducing the number of execution groups may also help to alleviate this problem. Correct the problem and redeploy the broker's configuration from the Message Brokers Toolkit. If there are no other failure diagnostics then you should consider increasing the Configuration Timeout, increase this value in units of 300 until this message no longer occurs. Contact your IBM support center if you are unable to resolve the problem.
BIP1536S: Configuration Manager unable to register for internal subscriptions with broker LINUX3.
Although the preceding deploy operation was successful, a subsequent attempt by the Configuration Manager to register for internal subscriptions with broker LINUX3 was not successful. This means that the Message Brokers Toolkit may not reliably show the correct status of the resources assigned to broker LINUX3. The Configuration Manager also writes this message to the system event log, accompanied by other messages giving details of the problem.
Look at the messages for this problem in the system event log. Determine and correct the cause of the problem before attempting to deploy to this broker again. If this problem persists, contact your IBM support center.
And in /var/log/messages:
Jun 28 19:02:43 localhost MQSIv500[3587]: (LINUX3)[32771]BIP2811E: The broker was unable to receive a 'stopped' publish event response. : LINUX3.agent: /build/S500_P/src/AdminAgent/ImbAdminAgent.cpp: 670: ImbAdminAgent::monitorAdminAgentParentProcess: :
Jun 28 19:02:45 localhost MQSIv500[3567]: (LINUX3)[16384]BIP2002W: The WebSphere Business Integration Message Brokers service has stopped. : LINUX3.service: /build/S500_P/src/AdminAgent/ControlProcess/Linux/ImbControlService.cpp: 522: ImbControlService::CleanUp: :
Jun 28 19:02:58 localhost MQSIv500[4647]: (LINUX3)[16384]BIP2001I: The WebSphere Business Integration Message Brokers service has started, process ID 4650. : LINUX3.service: /build/S500_P/src/AdminAgent/ControlProcess/Linux/ImbControlService.cpp: 342: ImbControlService::StartNewAA: :
Jun 28 19:03:00 localhost MQSIv500[4666]: (LINUX3.$SYS_mqsi)[16384]BIP2201I: Execution Group started: process '4666'; thread '16384'; additional information: brokerName 'LINUX3'; executionGroupUUID '82a6e590-12b3-11d3-81a2-00203506a68e'; executionGroupLabel '$SYS_mqsi'; defaultExecutionGroup 'true'; queueManagerName 'LINUX3'; trusted 'false'; dataSourceName 'LINUX3'; userId 'db2inst1'; migrationNeeded 'false'; brokerUUID '2c6ffcc4-0401-0000-0080-8258071abfb5'; filePath '/opt/mqsi'; workPath '/var/mqsi'. : LINUX3.82a6e590-12b3-11d3-81a2-00203506a68e: /build/S500_P/src/DataFlowEngine/ImbMain.cpp: 235: main: :
Jun 28 19:03:01 localhost MQSIv500[4665]: (LINUX3)[65541]BIP2060W: The broker has detected that the Execution Group $SYS_mqsi, process ID 4666, has shutdown. : LINUX3.agent: /build/S500_P/src/AdminAgent/ImbAdminAgent.cpp: 3876: ImbAdminAgent::startAndMonitorADataFlowEngine: :
Jun 28 19:03:01 localhost MQSIv500[4669]: (LINUX3.$SYS_mqsi)[16384]BIP2201I: Execution Group started: process '4669'; thread '16384'; additional information: brokerName 'LINUX3'; executionGroupUUID '82a6e590-12b3-11d3-81a2-00203506a68e'; executionGroupLabel '$SYS_mqsi'; defaultExecutionGroup 'true'; queueManagerName 'LINUX3'; trusted 'false'; dataSourceName 'LINUX3'; userId 'db2inst1'; migrationNeeded 'false'; brokerUUID '2c6ffcc4-0401-0000-0080-8258071abfb5'; filePath '/opt/mqsi'; workPath '/var/mqsi'. : LINUX3.82a6e590-12b3-11d3-81a2-00203506a68e: /build/S500_P/src/DataFlowEngine/ImbMain.cpp: 235: main: :
Jun 28 19:03:02 localhost MQSIv500[4665]: (LINUX3)[65541]BIP2060W: The broker has detected that the Execution Group $SYS_mqsi, process ID 4669, has shutdown. : LINUX3.agent: /build/S500_P/src/AdminAgent/ImbAdminAgent.cpp: 3876: ImbAdminAgent::startAndMonitorADataFlowEngine: :
Jun 28 19:03:03 localhost MQSIv500[4674]: (LINUX3.$SYS_mqsi)[16384]BIP2201I: Execution Group started: process '4674'; thread '16384'; additional information: brokerName 'LINUX3'; executionGroupUUID '82a6e590-12b3-11d3-81a2-00203506a68e'; executionGroupLabel '$SYS_mqsi'; defaultExecutionGroup 'true'; queueManagerName 'LINUX3'; trusted 'false'; dataSourceName 'LINUX3'; userId 'db2inst1'; migrationNeeded 'false'; brokerUUID '2c6ffcc4-0401-0000-0080-8258071abfb5'; filePath '/opt/mqsi'; workPath '/var/mqsi'. : LINUX3.82a6e590-12b3-11d3-81a2-00203506a68e: /build/S500_P/src/DataFlowEngine/ImbMain.cpp: 235: main: :
Jun 28 19:03:03 localhost MQSIv500[4665]: (LINUX3)[65541]BIP2060W: The broker has detected that the Execution Group $SYS_mqsi, process ID 4674, has shutdown. : LINUX3.agent: /build/S500_P/src/AdminAgent/ImbAdminAgent.cpp: 3876: ImbAdminAgent::startAndMonitorADataFlowEngine: :
Jun 28 19:03:03 localhost MQSIv500[4679]: (LINUX3.$SYS_mqsi)[16384]BIP2201I: Execution Group started: process '4679'; thread '16384'; additional information: brokerName 'LINUX3'; executionGroupUUID '82a6e590-12b3-11d3-81a2-00203506a68e'; executionGroupLabel '$SYS_mqsi'; defaultExecutionGroup 'true'; queueManagerName 'LINUX3'; trusted 'false'; dataSourceName 'LINUX3'; userId 'db2inst1'; migrationNeeded 'false'; brokerUUID '2c6ffcc4-0401-0000-0080-8258071abfb5'; filePath '/opt/mqsi'; workPath '/var/mqsi'. : LINUX3.82a6e590-12b3-11d3-81a2-00203506a68e: /build/S500_P/src/DataFlowEngine/ImbMain.cpp: 235: main: :
Jun 28 19:03:04 localhost MQSIv500[4665]: (LINUX3)[65541]BIP2060W: The broker has detected that the Execution Group $SYS_mqsi, process ID 4679, has shutdown. : LINUX3.agent: /build/S500_P/src/AdminAgent/ImbAdminAgent.cpp: 3876: ImbAdminAgent::startAndMonitorADataFlowEngine: :
Jun 28 19:03:05 localhost MQSIv500[4684]: (LINUX3.$SYS_mqsi)[16384]BIP2201I: Execution Group started: process '4684'; thread '16384'; additional information: brokerName 'LINUX3'; executionGroupUUID '82a6e590-12b3-11d3-81a2-00203506a68e'; executionGroupLabel '$SYS_mqsi'; defaultExecutionGroup 'true'; queueManagerName 'LINUX3'; trusted 'false'; dataSourceName 'LINUX3'; userId 'db2inst1'; migrationNeeded 'false'; brokerUUID '2c6ffcc4-0401-0000-0080-8258071abfb5'; filePath '/opt/mqsi'; workPath '/var/mqsi'. : LINUX3.82a6e590-12b3-11d3-81a2-00203506a68e: /build/S500_P/src/DataFlowEngine/ImbMain.cpp: 235: main: :
Jun 28 19:03:05 localhost MQSIv500[4665]: (LINUX3)[65541]BIP2060W: The broker has detected that the Execution Group $SYS_mqsi, process ID 4684, has shutdown. : LINUX3.agent: /build/S500_P/src/AdminAgent/ImbAdminAgent.cpp: 3876: ImbAdminAgent::startAndMonitorADataFlowEngine: :
Jun 28 19:03:06 localhost MQSIv500[4689]: (LINUX3.$SYS_mqsi)[16384]BIP2201I: Execution Group started: process '4689'; thread '16384'; additional information: brokerName 'LINUX3'; executionGroupUUID '82a6e590-12b3-11d3-81a2-00203506a68e'; executionGroupLabel '$SYS_mqsi'; defaultExecutionGroup 'true'; queueManagerName 'LINUX3'; trusted 'false'; dataSourceName 'LINUX3'; userId 'db2inst1'; migrationNeeded 'false'; brokerUUID '2c6ffcc4-0401-0000-0080-8258071abfb5'; filePath '/opt/mqsi'; workPath '/var/mqsi'. : LINUX3.82a6e590-12b3-11d3-81a2-00203506a68e: /build/S500_P/src/DataFlowEngine/ImbMain.cpp: 235: main: :
Jun 28 19:03:07 localhost MQSIv500[4665]: (LINUX3)[65541]BIP2060W: The broker has detected that the Execution Group $SYS_mqsi, process ID 4689, has shutdown. : LINUX3.agent: /build/S500_P/src/AdminAgent/ImbAdminAgent.cpp: 3876: ImbAdminAgent::startAndMonitorADataFlowEngine: :
Jun 28 19:03:07 localhost MQSIv500[4695]: (LINUX3.$SYS_mqsi)[16384]BIP2201I: Execution Group started: process '4695'; thread '16384'; additional information: brokerName 'LINUX3'; executionGroupUUID '82a6e590-12b3-11d3-81a2-00203506a68e'; executionGroupLabel '$SYS_mqsi'; defaultExecutionGroup 'true'; queueManagerName 'LINUX3'; trusted 'false'; dataSourceName 'LINUX3'; userId 'db2inst1'; migrationNeeded 'false'; brokerUUID '2c6ffcc4-0401-0000-0080-8258071abfb5'; filePath '/opt/mqsi'; workPath '/var/mqsi'. : LINUX3.82a6e590-12b3-11d3-81a2-00203506a68e: /build/S500_P/src/DataFlowEngine/ImbMain.cpp: 235: main: :
Jun 28 19:03:08 localhost MQSIv500[4665]: (LINUX3)[65541]BIP2060W: The broker has detected that the Execution Group $SYS_mqsi, process ID 4695, has shutdown. : LINUX3.agent: /build/S500_P/src/AdminAgent/ImbAdminAgent.cpp: 3876: ImbAdminAgent::startAndMonitorADataFlowEngine: :
Jun 28 19:03:19 localhost kernel: application bug: bipservice(4651) has SIGCHLD set to SIG_IGN but calls wait().
Jun 28 19:03:19 localhost kernel: (see the NOTES section of 'man 2 wait'). Workaround activated.
Jun 28 19:04:19 localhost kernel: application bug: bipservice(4651) has SIGCHLD set to SIG_IGN but calls wait().
Jun 28 19:04:19 localhost kernel: (see the NOTES section of 'man 2 wait'). Workaround activated.
Jun 28 19:05:20 localhost kernel: application bug: bipservice(4651) has SIGCHLD set to SIG_IGN but calls wait().
Jun 28 19:05:20 localhost kernel: (see the NOTES section of 'man 2 wait'). Workaround activated.
_________________
IBM Certified Specialist - WebSphere MQ Integrator
IBM Certified System Administrator - WebSphere MQ V5.3
IBM Certified System Administrator - WebSphere Business Integration Message Broker V5 |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Jun 28, 2005 4:40 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| solomita wrote: |
I have made the necessary changes and have chls up and running between my config mgr and broker. When I deploy, I now get these errors:
BIP2066E: Broker LINUX3 (UUID 2c6ffcc4-0401-0000-0080-8258071abfb5) was unable to retrieve an internal configuration response message for execution group '$SYS_mqsi' within the 360 second Configuration Timeout. |
Most likely you have a permissions problem with the queues or channels.
Examine the DLQ on the broker queue manager for messages that should have gone to the configmgr. Look at the DLQ Header for the DLQ Reason Code - this will tell you why the configmr did not receive the response it wanted from the broker.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| solomita |
| Posted: Wed Jun 29, 2005 3:30 am Post subject: |
|
|
Voyager
Joined: 06 May 2003
Posts: 94
|
Right now my DLQ is empty - probably b/c I shut down the machine and stopped the qmgrs. What can I look for and on what queues/channels in the meantime?
_________________
IBM Certified Specialist - WebSphere MQ Integrator
IBM Certified System Administrator - WebSphere MQ V5.3
IBM Certified System Administrator - WebSphere Business Integration Message Broker V5 |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Jun 29, 2005 3:52 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
If the broker machine is shut down, then you won't get any response from the broker.
And if it's shut down, then there is nothing you can look at - as the problem is only with messages coming FROM the broker, not going to it.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| solomita |
| Posted: Wed Jun 29, 2005 4:14 am Post subject: |
|
|
Voyager
Joined: 06 May 2003
Posts: 94
|
The broker machine was up but when I went to look at the DLQ, it had no messages in it and I thought it was b/c the qmgr was stopped and restarted but once again I am getting the same messages in the event log of the toolkit as well as the /var/log/messages on linux. And there are no messages on the DLQ of the broker queue manager. I am assuming that it shouldnt matter that my config mgr on windows was created with a different id than the broker on linux as both are part of mqm and mqbrkrs and the id the config mgr was created with is also part of administrator as well as the other mqbr* groups. I am really at a loss here. I am running linux and the broker on windows on 2 separate VMWARE images so not sure if they requires anything additional.
_________________
IBM Certified Specialist - WebSphere MQ Integrator
IBM Certified System Administrator - WebSphere MQ V5.3
IBM Certified System Administrator - WebSphere Business Integration Message Broker V5 |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Jun 29, 2005 4:55 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Nothing on the broker dlq?
ERm.
Maybe it's on the configmgr dlq...?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| solomita |
| Posted: Wed Jun 29, 2005 5:30 am Post subject: |
|
|
Voyager
Joined: 06 May 2003
Posts: 94
|
nothing there either 
_________________
IBM Certified Specialist - WebSphere MQ Integrator
IBM Certified System Administrator - WebSphere MQ V5.3
IBM Certified System Administrator - WebSphere Business Integration Message Broker V5 |
|
| Back to top |
|
|
| vennela |
| Posted: Wed Jun 29, 2005 5:49 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
| as well as the /var/log/messages on linux. |
Anything of interest there in the MQ errors ? |
|
| Back to top |
|
|
| JT |
| Posted: Wed Jun 29, 2005 5:49 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
Are there any messges in the SYSTEM.BROKER.* queues on the broker queue manager?
If so, which ones? |
|
| Back to top |
|
|
| solomita |
| Posted: Thu Jun 30, 2005 2:35 pm Post subject: |
|
|
Voyager
Joined: 06 May 2003
Posts: 94
|
There are messages on the following SYSTEM.BROKER queues:
CONTROL.QUEUE
EXECUTIONGROUP.QUEUE
It appears as though the broker starts up ok but as soon as I deploy it from the toolkit, all of those messages I previously posted appear.
Also, there is now a message on the DLQ of the ConfigMgr which is as follows:
44 4C 48 20 00 00 00 01 DLH ....
00 00 00 00 53 59 53 54 ....SYST
45 4D 2E 42 52 4F 4B 45 EM.BROKE
52 2E 41 44 4D 49 4E 2E R.ADMIN.
52 45 50 4C 59 00 00 00 REPLY...
00 00 00 00 00 00 00 00 ........
00 00 00 00 00 00 00 00 ........
00 00 00 00 47 43 53 43 ....GCSC
46 47 57 31 00 00 00 00 FGW1....
00 00 00 00 00 00 00 00 ........
00 00 00 00 00 00 00 00 ........
00 00 00 00 00 00 00 00 ........
00 00 00 00 00 00 00 00 ........
00 00 00 00 00 00 02 22 ......."
00 00 04 B8 20 20 20 20 ...∏
20 20 20 20 00 01 00 00 ....
4D 51 53 65 72 69 65 73 MQSeries
49 6E 74 65 67 72 61 74 Integrat
6F 72 32 00 00 00 00 00 or2.....
00 00 00 00 32 30 30 35 ....2005
30 36 33 30 31 38 30 39 06301809
35 36 30 30 3C 42 72 6F 5600<Bro
6B 65 72 20 75 75 69 64 ker uuid
3D 22 35 66 30 63 34 36 ="5f0c46
63 66 2D 30 34 30 31 2D cf-0401-
30 30 30 30 2D 30 30 38 0000-008
30 2D 38 66 30 37 38 33 0-8f0783
35 33 34 32 38 35 22 20 534285"
6C 61 62 65 6C 3D 22 47 label="G
43 53 42 52 4B 4C 31 22 CSBRKL1"
20 76 65 72 73 69 6F 6E version
3D 22 31 22 3E 3C 4F 76 ="1"><Ov
65 72 61 6C 6C 43 6F 6D erallCom
70 6C 65 74 69 6F 6E 43 pletionC
6F 64 65 20 72 65 73 75 ode resu
6C 74 3D 22 66 61 69 6C lt="fail
75 72 65 22 3E 3C 4C 6F ure"><Lo
67 45 6E 74 72 79 20 63 gEntry c
61 74 61 6C 6F 67 3D 22 atalog="
42 49 50 76 35 30 30 22 BIPv500"
20 6E 75 6D 62 65 72 3D number=
22 32 30 38 37 22 3E 3C "2087"><
49 6E 73 65 72 74 20 74 Insert t
79 70 65 3D 22 73 74 72 ype="str
69 6E 67 22 20 74 65 78 ing" tex
74 3D 22 47 43 53 42 52 t="GCSBR
4B 4C 31 22 2F 3E 3C 49 KL1"/><I
6E 73 65 72 74 20 74 79 nsert ty
70 65 3D 22 73 74 72 69 pe="stri
6E 67 22 20 74 65 78 74 ng" text
3D 22 35 66 30 63 34 36 ="5f0c46
63 66 2D 30 34 30 31 2D cf-0401-
30 30 30 30 2D 30 30 38 0000-008
30 2D 38 66 30 37 38 33 0-8f0783
35 33 34 32 38 35 22 2F 534285"/
3E 3C 2F 4C 6F 67 45 6E ></LogEn
74 72 79 3E 3C 2F 4F 76 try></Ov
65 72 61 6C 6C 43 6F 6D erallCom
70 6C 65 74 69 6F 6E 43 pletionC
6F 64 65 3E 3C 43 6F 6E ode><Con
74 72 6F 6C 47 72 6F 75 trolGrou
70 43 6F 6D 70 6C 65 74 pComplet
69 6F 6E 43 6F 64 65 20 ionCode
75 75 69 64 3D 22 22 20 uuid=""
72 65 73 75 6C 74 3D 22 result="
75 6E 6B 6E 6F 77 6E 22 unknown"
3E 3C 4C 6F 67 45 6E 74 ><LogEnt
72 79 20 63 61 74 61 6C ry catal
6F 67 3D 22 42 49 50 76 og="BIPv
35 30 30 22 20 6E 75 6D 500" num
62 65 72 3D 22 32 30 36 ber="206
36 22 3E 3C 49 6E 73 65 6"><Inse
72 74 20 74 79 70 65 3D rt type=
22 73 74 72 69 6E 67 22 "string"
20 74 65 78 74 3D 22 47 text="G
43 53 42 52 4B 4C 31 22 CSBRKL1"
2F 3E 3C 49 6E 73 65 72 /><Inser
74 20 74 79 70 65 3D 22 t type="
73 74 72 69 6E 67 22 20 string"
74 65 78 74 3D 22 35 66 text="5f
30 63 34 36 63 66 2D 30 0c46cf-0
34 30 31 2D 30 30 30 30 401-0000
2D 30 30 38 30 2D 38 66 -0080-8f
30 37 38 33 35 33 34 32 07835342
38 35 22 2F 3E 3C 49 6E 85"/><In
73 65 72 74 20 74 79 70 sert typ
65 3D 22 73 74 72 69 6E e="strin
67 22 20 74 65 78 74 3D g" text=
22 24 53 59 53 5F 6D 71 "$SYS_mq
73 69 22 2F 3E 3C 49 6E si"/><In
73 65 72 74 20 74 79 70 sert typ
65 3D 22 73 74 72 69 6E e="strin
67 22 20 74 65 78 74 3D g" text=
22 33 36 30 22 2F 3E 3C "360"/><
2F 4C 6F 67 45 6E 74 72 /LogEntr
79 3E 3C 2F 43 6F 6E 74 y></Cont
72 6F 6C 47 72 6F 75 70 rolGroup
43 6F 6D 70 6C 65 74 69 Completi
6F 6E 43 6F 64 65 3E 3C onCode><
43 6F 6E 74 72 6F 6C 47 ControlG
72 6F 75 70 2F 3E 3C 2F roup/></
42 72 6F 6B 65 72 3E Broker>
_________________
IBM Certified Specialist - WebSphere MQ Integrator
IBM Certified System Administrator - WebSphere MQ V5.3
IBM Certified System Administrator - WebSphere Business Integration Message Broker V5 |
|
| Back to top |
|
|
| solomita |
| Posted: Thu Jul 07, 2005 10:10 am Post subject: SOLVED: Problem with deploying a LINUX broker to the toolkit |
|
|
Voyager
Joined: 06 May 2003
Posts: 94
|
Here are the things that need to be done for a Linux installation:
1. LD_ASSUME_KERNEL must be set to 2.4.19 while WMQ and WBI-MB are installed
2. Only IBM Java versions are supported and can be downloaded from the link on the SOE Pg (http://www-306.ibm.com/software/integration/wbimessagebroker/requirements/)
3. Make sure you follow the instructions in the link 'Please see the Technical Details for further information' in the above page.
4. After installation, backup the product supplied JRE in /opt/mqsi/jre and replace this directory with a soft link to the JRE 1.4.2 installation. For example, "ln -s /opt/IBMJava2-142/jre /opt/mqsi/jre".
To ensure that the link is correct if you issue ls -l in /opt/mqsi the jre should show a link to /opt/IBMJava-142/jre
(NOTE that once you backup the /opt/mqsi/jre directory, REMOVE the jre sub-directory before creating the soft link or you will end up with /opt/mqsi/jre/jre which is what happened to me)
5. LANG and LC_ALL must be set to en_US in the profile
6. Make sure that the PATH environment variable references IBM Java 1.4.2 before any other java version. You can check this by issuing 'java -version' and 'which java'. The java version should be 1.4.2 and which java should point to /opt/IBMJava-1.4.2/bin'
7. Ensure that LD_LIBRARY_PATH contains /opt/IBMJava-1.4.2/jre/bin/classic directory or whichever directory contains libjvm.so otherwise you will get errors related to libjvm.so
_________________
IBM Certified Specialist - WebSphere MQ Integrator
IBM Certified System Administrator - WebSphere MQ V5.3
IBM Certified System Administrator - WebSphere Business Integration Message Broker V5 |
|
| Back to top |
|
|
|
|
