MQSeries.net :: View topic - Message Broker- Deployment of BAR- problem- BIP1536S-

siva_chenn · Posted: Wed Oct 31, 2007 6:47 am Post subject:

Hi,

I need a help on the issue, mentioned in subject.......

I tried to create sample Message Broker application using Mappings, for
_ Defining the logic of a message flow using mappings
_ Inserting data into a database DB2 using a message flow
_ Transforming a message from one XML structure to another

I used default broker setup, configured previously.. I have updated my MB Tool Kit to latest Interim Fix 009 also..

I am able to successfully, create a sample Message Set project with XML wire format, with one definition for a XML message.. and also a Message Flow Project, with appropriate mapping from one queue to another and for, a sample XML for transformation..

Later, I created a Broker Archive file by including that sample Message Set and Message Flow project and both Definition and CMF files were successfully created..

When I tried, to deploy it on to a Broker, by creating a test execution group, its going unsuccessful.. I am just pasting the errors, both in Event-viewer of Configuration manager and also Windows event log..
----------------------------------------------------------------------------------------------------------------------------------------

Event Viewer of Configuration Manager:

BIP1536S: The Configuration Manager was unable to register for internal subscriptions with broker WBRK6_DEFAULT_BROKER.

Although the preceding deploy operation was successful, a subsequent attempt by the Configuration Manager to register for internal subscriptions with broker WBRK6_DEFAULT_BROKER 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 WBRK6_DEFAULT_BROKER.

Look in the system log for messages that indicate the cause of this problem. Correct the cause and redeploy to this broker. If this problem persists, contact your IBM support center.

Windows Event Log:

1)

( WBRK6_DEFAULT_CONFIGURATION_MANAGER ) Source field ''410064006d0069006e006900730074007200610074006f007200'' is too long for a target field of length ''12'' when converting from unicode to codepage ''5348''.

When the character data in the source field is converted to the target codepage, the resulting character string was longer than the defined length of the target field.

Correct the application or compute expression that generated the message. Ensure that the definition of the field in the output message is correctly specified bearing in mind the codepage required for the message and check that the origin of the data within the source field is providing correct data.

2)

( WBRK6_DEFAULT_CONFIGURATION_MANAGER ) Invalid configuration message. See the following messages for details of the error.

The publish/subscribe function of the broker has received an invalid configuration message and has not updated its configuration. This can arise as a result of errors in the specification of the broker topology or topics which the Configuration Manager was unable to detect. It can also result from the broker having become out of step with the configuration repository or from other applications sending extraneous messages to the configuration queues of the broker (SYSTEM.BROKER.ADMIN.QUEUE and SYSTEM.BROKER.EXECUTIONGROUP.QUEUE).

Check the relevant topology and topic definitions, perform a complete redeploy of the configuration and ensure that no applications are writing to the configuration queues.

3)
( WBRK6_DEFAULT_CONFIGURATION_MANAGER ) Broker 'WBRK6_DEFAULT_BROKER' 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. Analyze all of the following messages to determine why the internal configuration message could not be processed.

4)

( WBRK6_DEFAULT_CONFIGURATION_MANAGER ) The Configuration Manager was unable to register for internal subscriptions with broker 'WBRK6_DEFAULT_BROKER'.

Although the preceding deploy operation was successful, a subsequent attempt by the Configuration Manager to register for internal subscriptions with broker 'WBRK6_DEFAULT_BROKER' 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 'WBRK6_DEFAULT_BROKER'.

Look in the system log for messages that indicate the cause of this problem. Correct the cause and redeploy to this broker. If this problem persists, contact your IBM support center.
----------------------------------------------------------------------------------------------------------------------------------------

Here, for trying to fix the above problem, even I tried to create, a Test Broker configuration like configuration manager, broker, database, queue manager with listener etc manually from scratch also.. and I tried to deploy , a fresh BAR, created after modifying corresponding properties of nodes in Message Flow.. both using Mapping (with one message definition), also ESQL with out using any message definition.. But, at that time also, I got same problem, in both the cases, with manual broker configuration

Anybody, please provide me, the resolution, for this issue.....

Thanks in advance,
Siva