ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Deploy to AIX broker box from W2K

Post new topic  Reply to topic
 Deploy to AIX broker box from W2K « View previous topic :: View next topic » 
Author Message
Gama
PostPosted: Mon Nov 27, 2006 8:07 am    Post subject: Deploy to AIX broker box from W2K Reply with quote

Centurion

Joined: 11 Jan 2005
Posts: 103
Location: Portugal

Hello all,

I need to attach to my config manager on W2k one broker that it is an AIX.

I already create de QueueManager, BrokerDB and the Broker.

crtmqm..... QUEUEMANAGER
mqsicreatedb BROKERDB
mqsicreatebroker BROKERNAME

I create the Sender and Receiver Channel's between the Windows QM and AIX QM, then Transmissions Queue they have then name of the destination queue mananger.


On my Control Center (WMQI2.1) on tab Topology, i already create the broker, and here everything ran well, but when i attache some flow to the default execution group and then tried to do the deploy, i receive the folow errors.

"BIP1536S: Configuration Manager unable to register for internal subscriptions with broker BROKER_P521_1.

Although the preceding deploy operation was successful, a subsequent attempt by the Configuration Manager to register for internal subscriptions with broker BROKER_P521_1 was not successful. This means that the Control Center Operations view may not reliably show the correct status of the resources assigned to broker BROKER_P521_1. 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. "

"BIP2087E: Broker WMQIBRKP521_1 was unable to process the internal configuration message.

The entire internal configuration message failed to be processed successfully.

The internal configuration message failed to be processed, use the messages following this message to determine the reasons for the failure. "

"BIP2047E: Broker WMQIBRKP521_1 (UUID 93cbeb29-0f01-0000-0080-f1e6b88f711a) could not process an internal configuration message because the broker name received in the message (BROKER_P521_1) did not match that of this broker.

An internal configuration message could not be processed and was rejected. Each broker is given a name when the Control Center user creates a definition for the broker. This name must match the name supplied on the mqsicreatebroker command used to create the broker itself. Although the configuration message received contained the correct broker identity (UUID), it contained a broker name, BROKER_P521_1, that did not match the name of this broker, WMQIBRKP521_1. The probable cause is that a Control Center user has incorrectly renamed the broker in the broker definition.

Use the Control Center to rename the broker back to the name specified on the mqsicreatebroker
command. This name can be found using the mqsilist command. "

Can Any one help-me?

Thanks a lot
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Mon Nov 27, 2006 8:10 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

I bet you'll have a lot less trouble doing this on a supported version of the product, rather than building an unsupported and new 2.1 infrastructure.

Otherwise, look at MQ security.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
Gama
PostPosted: Mon Nov 27, 2006 9:03 am    Post subject: Reply with quote

Centurion

Joined: 11 Jan 2005
Posts: 103
Location: Portugal

jefflowrey wrote:
I bet you'll have a lot less trouble doing this on a supported version of the product, rather than building an unsupported and new 2.1 infrastructure.

Otherwise, look at MQ security.


jefflowrey, You are right, but whe are migrating from the 2.1 to the version 6 and we have to pass all of the developments for another aix server.

any more help?
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Mon Nov 27, 2006 10:40 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Look at MQ security.

Look at channel configuration between both queue managers.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Mon Nov 27, 2006 2:09 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

Quote:
Although the configuration message received contained the correct broker identity (UUID), it contained a broker name, BROKER_P521_1, that did not match the name of this broker, WMQIBRKP521_1. The probable cause is that a Control Center user has incorrectly renamed the broker in the broker definition.


How about looking into this and trying to find a solution to it??
Looks like your broker and configmgr are out of synch?
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Gama
PostPosted: Tue Nov 28, 2006 7:16 am    Post subject: Reply with quote

Centurion

Joined: 11 Jan 2005
Posts: 103
Location: Portugal

fjb_saper wrote:
Quote:
Although the configuration message received contained the correct broker identity (UUID), it contained a broker name, BROKER_P521_1, that did not match the name of this broker, WMQIBRKP521_1. The probable cause is that a Control Center user has incorrectly renamed the broker in the broker definition.


How about looking into this and trying to find a solution to it??
Looks like your broker and configmgr are out of synch?


Yes fjb_saper, you are absolutlly sure, but after recreate the broker over de Control Center the problem steel the same.

BIP1536S: Configuration Manager unable to register for internal subscriptions with broker WMQIBRKP521_1.

Although the preceding deploy operation was successful, a subsequent attempt by the Configuration Manager to register for internal subscriptions with broker WMQIBRKP521_1 was not successful. This means that the Control Center Operations view may not reliably show the correct status of the resources assigned to broker WMQIBRKP521_1. The Configuration Manager also writes this message to the system event log, accompanied by other messages giving details of the problem.
Back to top
View user's profile Send private message
Gama
PostPosted: Tue Nov 28, 2006 8:23 am    Post subject: Reply with quote

Centurion

Joined: 11 Jan 2005
Posts: 103
Location: Portugal

Thanks jefflowrey and fjb_saper,

My Problem was related to UUID of Broker,

I run the mqsiservice ${BrokerName} -r BrokerUUID=${UUID_CfgMgrExpect} and the config managar deploy successfully.

BIP4045I: Configuration changed successfully. [/b]
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Deploy to AIX broker box from W2K
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.