| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Issue On Migration of Message Set to WMB 6.0. |
« View previous topic :: View next topic » |
| Author |
Message
|
| Ranodip Basu |
 Posted: Thu Sep 07, 2006 5:00 am Post subject: Issue On Migration of Message Set to WMB 6.0. |
 |
|
Apprentice
Joined: 23 Sep 2004
Posts: 48
|
Hi All,
We are in a process of migration from WMQI 2.1 (CSD level 11) to WMB 6.0.1. Our v2.1 broker is running in HP-UX 11i whereas WMB config manager on windows 2003 and broker on SUSE-Linux.
We are facing a problem for migrating a particular message set to v6.0. This particular message set is created in v2.1 and running fine in v2.1 and after migration in v5.0(config manager in windows 2000 and broker in HP-UX 11i).
This message set has input message format in XML and output in TDS(space delimited).We have imported the migrated version of this message flow from 5.0 workspace to v6.0 workspace using the "File->Import-> Existance Project Into WorkSpace" way. We have successfully created the .bar file and getting the errors as in below while deploying to execution group:
| Quote: |
BIP5347E: MtiImbParser2: RM has thrown an unknown exception.
Returned by the RM when an unknown exception is thrown. This is an internal error.
Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem still continues to occur contact your IBM support center providing system trace files where possible. |
| Quote: |
BIP5145E: Error setting up runtime dictionary resource using message set identifier 'E01DD5O0BM001'.
An error was detected when trying to deploy message set. Use the Message Brokers Toolkit to match the message set Identifier : E01DD5O0BM001, to a message set name.
Check that you have a valid broker installation. If the problem persists, contact your IBM support center.
|
| Quote: |
BIP4041E: Execution group 'ABCD_EXEC_GRP1' 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 user-defined extensions are installed, perform a complete redeploy of the broker's configuration and ensure that no applications are writing to the broker's configuration queues. |
We have againg create a separate message set in v2.1 with same structure of the above one and found to be running fine. But when migrated it to v6.0 directly got the same errors again.
We have used mqsiimpexpmsgset and mqsimigratemsgsets for migration purpose.
Thanks & Regards,
Ranodip |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Sep 07, 2006 5:08 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Did you confirm that the ID of the imported message set is the same?
Did you confirm that the message set compiles properly, and has no warnings in the Toolkit?
Did you try doing what the BIP5145 says?
Did you try creating a new message set in v6 and confirming that it can deploy?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu Sep 07, 2006 6:24 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
From the migration topics in the docs ( for 5.0 -> 6.0 )
| Quote: |
To migrate the Version 5.0 Message Brokers Toolkit to Version 6.0, complete the following steps:
1. Install WebSphere Message Broker Version 6.0 in a different location from WebSphere Business Integration Message Broker Version 5.0.
2. Migrate any Version 5.0 mappings using the mqsimigratemfmaps command. (There is no migration tool to migrate a mapping that is called from ESQL.)
3. When you start the Version 6.0 Message Brokers Toolkit for the first time, you are prompted to enter a workspace location. Enter the directory where the Version 5.0 or Version 5.1 Message Brokers Toolkit workspace that you want to migrate is located. In Version 5.0, the default location is <BrokersInstallPath>/eclipse/workspace.
* Version 5.0 message flows are converted to the Version 6.0 format automatically when you save them for the first time. The Version 5.0 Message Brokers Toolkit cannot read message flows that have been saved in Version 6.0 format.
* If your message flows use MQe nodes, follow the instructions in Migrating a message flow that contains WebSphere MQ Everyplace nodes. If your message flows use XML style sheets, follow the instructions in Migration of style sheets and XML files.
* Version 5.0 message sets are converted to the Version 6.0 format automatically when you save them for the first time. The Version 5.0 Message Brokers Toolkit cannot read message sets that have been saved in Version 6.0 format.
4. Clean and rebuild your workspace.
... |
1. What you are describing sounds different from this advice.
2. Is there a good reason why you are migrating via v5.0? You could migrate directly from v2.1 to v6. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
