| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Msg flow Naming Convensions(standards) for WIB 5.0 |
« View previous topic :: View next topic » |
| Author |
Message
|
| chanduy9 |
 Posted: Wed Jan 21, 2004 2:15 pm Post subject: Msg flow Naming Convensions(standards) for WIB 5.0 |
 |
|
Disciple
Joined: 28 Nov 2001
Posts: 177
Location: USA
|
Hi,
Is there any naming convensions for Msg flows and Msg sets in WIB5.0. I migrated from WMQI2.1 where the msg flows are having . , - and blank space, when I rename the msg flows in V5.0 with the .,- or blank it is not accepting....
Any thoughts,
Thanks in Advace,
Chandra. |
|
| Back to top |
|
 |
| JLRowe |
| Posted: Wed Jan 21, 2004 3:53 pm Post subject: |
|
|
Yatiri
Joined: 25 May 2002
Posts: 664
Location: South East London
|
Some tips:
Only project and schema names can contain a full stop/period.
As for flow names, I found that only the flow name is displayed in the editor tab, the schema name is only displayed if you hover over it. For me, it made sense to give each flow a unique and meaningful name so I can distinguish them when multiple editor windows are open.
Be careful with having the same schema name in multiple projects, flows may deploy OK when only one project is open, but may fail with duplicate symbol names when all the projects are open.
Take care in how you split the artifacts over projects, if you're not doing source control now, play with it so you can see how your structure fits in (grab a free CVS server).
If you are doing source control, qualify your project names to distinguish between those under source control (Message flow and message set projects), and those you wish to keep local only (Local test server projects, Local config scripts etc). |
|
| Back to top |
|
|
| jfluitsm |
| Posted: Sun Jan 25, 2004 2:42 am Post subject: |
|
|
Disciple
Joined: 24 Feb 2002
Posts: 160
Location: The Netherlands
|
Chandra,
There is a naming convention in that only the characters a - z, A - Z, 0 - 9 and _ are allowed in MsgFlow and MsgSet names It is stated somewhere in the docs, but I don't know exactly where.
I suggest not to use the _ as this is also used as seperator in ESQL module names: <MsgFlowName>_<NodeName>.
Although the docs state that you can change the 'Xnn' values after migration, doing this before migration might be more feasible.
Renaming before migration:
- Rename flow
Renaming after migration:
- Rename flow (.msgflow and .esql files)
- When a sub-flow, rename all references to the flow from higher-level flows.
- Rename all ESQL modules in the .esql file
- Change all nodes with references to the ESQL modules
Any one already come up with a tool for renaming?
I am thinking about writing a script to rename the flows in a 2.1 export file according to some predefined rules, for instance proper naming (removing special chars and first letter capital: MY MAIN_FLOW --> MyMainFlow.
_________________
Jan Fluitsma
IBM Certified Solution Designer WebSphere MQ V6
IBM Certified Solution Developer WebSphere Message Broker V6 |
|
| Back to top |
|
|
| jfluitsm |
| Posted: Sun Feb 22, 2004 5:29 am Post subject: |
|
|
Disciple
Joined: 24 Feb 2002
Posts: 160
Location: The Netherlands
|
Some more additons:
- Deploying is done per main message flow, i.e. containing any of the 'input' nodes (not the InputTerminal) within the flow or any contained sub-slows. You have to take care to deploy all main flows that contain a changed sub-flow.
- Flow linking is done by name instead of UUID, using version numbers in the name will result in 'new' flows with every new version.
_________________
Jan Fluitsma
IBM Certified Solution Designer WebSphere MQ V6
IBM Certified Solution Developer WebSphere Message Broker 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
|
|
|
|
