| Author |
Message
|
| iyerhari |
 Posted: Mon Apr 22, 2002 1:58 am Post subject: |
 |
|
Novice
Joined: 25 Feb 2002
Posts: 13
|
Hello,
I have created 2 brokers on 2 separate queue managers. I also created a config mgr on one of the queue managers which also houses one of the broker. When I try to deploy the configuration through the control center I am getting an error
" BIP1533E: Unable to deploy configuration data: unknown MQSeries queue manager COMP2 associated with broker COMP2_SAMPLE_BROKER.
An attempt was made to deploy configuration data to one or more brokers. The MQSeries queue manager COMP2 associated with broker COMP2_SAMPLE_BROKER is not known to the Configuration Manager's MQSeries queue manager. The deploy operation was not performed.
Check that the name of the queue manager is spelled correctly. Note that MQSeries queue manager names are case-sensitive. If the spelling is correct, make sure that either a queue manager alias definition for queue manager COMP2, or a transmission queue called COMP2, is defined to the Configuration Manager's queue manager. For more information on this error see the MQSeries Application Programming Reference manual, code 2087. "
I am using WMQI 2.1 on Windows NT.
If anyone has got idea about this please help.
Thanks in advance.
Regards,
Hari Iyer. |
|
| Back to top |
|
 |
| RichA |
| Posted: Mon Apr 22, 2002 2:12 am Post subject: |
|
|
Centurion
Joined: 14 Mar 2002
Posts: 102
|
| Have you created listeners for both broker queue managers and do they have different ports and are they started? |
|
| Back to top |
|
|
| iyerhari |
| Posted: Mon Apr 22, 2002 2:21 am Post subject: |
|
|
Novice
Joined: 25 Feb 2002
Posts: 13
|
Hello,
The queue managers are running on ports 1414 and 1415 respectively. They are both running.
Regards,
Hari Iyer. |
|
| Back to top |
|
|
| RichA |
| Posted: Mon Apr 22, 2002 3:25 am Post subject: |
|
|
Centurion
Joined: 14 Mar 2002
Posts: 102
|
| Is there anything more in your event viewer application log? |
|
| Back to top |
|
|
| iyerhari |
| Posted: Mon Apr 22, 2002 3:33 am Post subject: |
|
|
Novice
Joined: 25 Feb 2002
Posts: 13
|
Hello,
The event viewer does not give any error message.
Regards,
Hari Iyer. |
|
| Back to top |
|
|
| kirani |
| Posted: Mon Apr 22, 2002 5:58 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Hari,
You need to create communication link between two queue managers. For example, you have two queue managers named COMP1 and COMP2, and Your brokers are created on these two queue managers, and COMP1 is being shared by Configuration manager.
In this case, you must define communication link between two queue managers COMP1 and COMP2.
Define following channels,
On COMP1
--------
A transmission queue named COMP2
A sender channel (e.g. TO.COMP2)
A receiver channel (e.g. TO.COMP1)
On COMP2
--------
A transmission queeu named COMP1
A Sender channel (e.g. TO.COMP1)
A receiver channel (e.g. TO.COMP2)
After you start these pair of channels your queue manager COMP1 and COMP2 can communicate with each other! Before you deploy a message flows to any of these brokers you must create a reference to these brokers in your configuration repository.
For more information on how to define channels refer to MQSeries Intercommunication book. For any WMQI administration please refer to WMQI Administration/Installation guide.
_________________
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 |
|
|
| iyerhari |
| Posted: Tue Apr 23, 2002 2:24 am Post subject: |
|
|
Novice
Joined: 25 Feb 2002
Posts: 13
|
Hello,
Thanks for the help. I was able to deploy the configuration. But still there is a problem. I had to delete the older brokers because they were yielding some problems. But when I deploy the newer configuration the older broker still persists.
It reads an error message
"BIP1533E: Unable to deploy configuration data: unknown MQSeries queue manager COMP2 associated with broker COMP2_SAMPLE_BROKER.
An attempt was made to deploy configuration data to one or more brokers. The MQSeries queue manager COMP2 associated with broker COMP2_SAMPLE_BROKER is not known to the Configuration Manager's MQSeries queue manager. The deploy operation was not performed.
Check that the name of the queue manager is spelled correctly. Note that MQSeries queue manager names are case-sensitive. If the spelling is correct, make sure that either a queue manager alias definition for queue manager COMP2, or a transmission queue called COMP2, is defined to the Configuration Manager's queue manager. For more information on this error see the MQSeries Application Programming Reference manual, code 2087."
How do I remove the reference of the older brokers when they are not at all present with the present configuration.
Regards,
Hari Iyer. |
|
| Back to top |
|
|
| Cliff |
| Posted: Tue Apr 23, 2002 3:19 am Post subject: |
|
|
Centurion
Joined: 27 Jun 2001
Posts: 145
Location: Wiltshire
|
When you say you deleted the broker, do you mean just from the Topology or did you also do mqsideletebroker?
MQSI is sensitive to the order of events - look at 'Deleting Components From the Broker Domain' in Chapter 3 of the Administration Guide for the full low-down on how to do it correctly.
Regards - Cliff |
|
| Back to top |
|
|
| iyerhari |
| Posted: Wed Apr 24, 2002 3:49 am Post subject: |
|
|
Novice
Joined: 25 Feb 2002
Posts: 13
|
Hello,
I was able to successfully deploy the Broker. But after deploying it is giving the following errors in my "DataUpdate"node.
1. BIP2491E: (1, 33) : Illegal argument (value 'integer WHERE') to function SET; character string required.
The argument must be a character string value. The function was called with the value 'integer WHERE'.
Ensure the argument passed to SET is a character string.
2. BIP4181E: Syntax error in SQL statements in database node '{2}'.
The configuration of database node {2} failed due to errors in the SQL statement text. See the following messages for details of the error. The statement text was 'TestFlow.DataUpdate1.Database1'.
The next error message will give specific details of where the error occurred in the statement text. Check the correct syntax for database node SQL statements in the WebSphere MQ Integrator publications. Correct the statements and re-deploy the configuration.
3. BIP4041E: Execution group 'default' received an invalid configuration message. See the following messages for details of the error.
The message broker received an invalid configuration message and has not updated its configuration. This can arise as a result of errors in the specification of either message flows or message sets which the configuration manager was unable to detect. It can also result from a message flow requiring a type of node that is not supported by the broker installation, from the broker having become out of step with the configuration database or from other applications sending extraneous messages to the broker's configuration queues (SYSTEM.BROKER.ADMIN.QUEUE & SYSTEM.BROKER.EXECUTIONGROUP.QUEUE).
Check the relevant message flow and message set definitions, check that all necessary plug-ins are installed, perform a complete redeploy of the broker's configuration and ensure that no applications are writing to the broker's configuration queues.
4. BIP2086E: Broker BROKER1 could only process parts of the internal configuration message.
Parts of the internal configuration message were not processed successfully.
This response indicates that one or more Execution Groups could not process the internal configuration message. Analyse all of the following messages to determine why the internal configuration message could not be processed.
I did check my Database fields as well as the fields in my Message Set. They do not contain any integer value. All of them declared as String in the Message Set andVarchar in the DB2 database.
Regards,
Hari Iyer. |
|
| Back to top |
|
|
| gabbar |
| Posted: Wed Jan 01, 2003 8:01 pm Post subject: Iyer |
|
|
Acolyte
Joined: 10 Dec 2002
Posts: 50
|
| Could you solve your problem. I am facing exactly the same situation. |
|
| Back to top |
|
|
|
|
