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 » Migration to V5.0 - Doesn't like component names

Post new topic  Reply to topic
 Migration to V5.0 - Doesn't like component names « View previous topic :: View next topic » 
Author Message
mehedi
PostPosted: Tue Aug 10, 2004 12:03 pm    Post subject: Migration to V5.0 - Doesn't like component names Reply with quote

Centurion

Joined: 11 Nov 2001
Posts: 102
Location: PSTech
Hi,
(1)
This is the name (EA.ErrorHandler.Input.Node.xml)
of a sub-message flow used in many(actually all our message flows).
The mqsimigratemsgflows doesn't like the dots in the name and replaces them(see report from below).
===============
Report from the mqsimigratemsgflows logs
BIP0859W The message flow name EA.ErrorHandler.Input.Node is invalid.
The migrate command cannot use the flow name as the file name.
The flow name has been changed to EAX2eErrorHandlerX2eInputX2eNode.
You may later rename the flow from the WebSphere Studio.
=================
I tried to create a flow using the "broker application deveopment" view and it doesn't like names with '.' in them.

(2)
There are also instances where code is flagged as having syntax errors in WMQI 5.0 but not in MQSI 2.1.


Does anyone have suggestions(tried & tested) on how to move forward with this ?
I guess we are alarmed by the prospect of having to modify code as
part of the migration process.

Thanks

Mehedi
Back to top
View user's profile Send private message MSN Messenger
fitzcaraldo
PostPosted: Tue Aug 10, 2004 3:26 pm    Post subject: Reply with quote

Voyager

Joined: 05 May 2003
Posts: 98
Be alarmed.

There are two approaches to this.

1. Modify 2.1 flows before migrating to remove all illegal characters from ALL attribute names before migration. This includes the Names of Compute nodes as these become the Compute module names after migration. "Set RFH2" becomes "SetX20RFH2" It also applies to any promoted properties from a subflow. Use underscores instead of dots and remove spaces!

2. Modify the names post migration.
I prefer this approach as you will probably rework the code anyway. Shared ESQL modules can greatly decrease code duplication but you will need to refactor to take advantage of it.

V5.0 is syntactically tighter than v2.1 One that got me was including a label on an "end while" statement - mandatory in 5 and not required in 2.1
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 » Migration to V5.0 - Doesn't like component names
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.