| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Nomenclature of the Message flows,functions,etc |
« View previous topic :: View next topic » |
| Author |
Message
|
| dprogwmb |
 Posted: Thu Jul 21, 2011 4:30 am Post subject: Nomenclature of the Message flows,functions,etc |
 |
|
Voyager
Joined: 19 Jul 2011
Posts: 96
|
Hi all,
I wonder if any of you have a generic document (may be from IBM... but I couldn´t find it), for the nomenclature of the development artifacts for Websphere Message Broker (v 7.0.2)... for example: How to name a main flow, a subflow depending of the main flow, how to name a generic function, how to name a Message Set, how to name an adapter, etc...
I have been looking also in this forum and I couldn't find anything for Message Broker (for MQ there are some best practices, but it's not usefull in my case)
I am very grateful for what you can provide to me (and for all) !!!
Thanks a lot!!! |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Thu Jul 21, 2011 4:35 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
This is usually determined locally. Each customer is different.
At my sites, we use <Business_program_name>_<main_upstream_consumer>_<main_downstream_provider> as the name for flows.
For projects, we usually pick <Business_program_name> as the name of the root msgflow project.
Business_program_name is the main cost center on the accountant's balance sheet, not a name for a computer program. Most times, we abbreviate it in two or three characters.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| WGerstma |
| Posted: Thu Jul 21, 2011 7:08 am Post subject: |
|
|
Acolyte
Joined: 18 Jul 2011
Posts: 55
|
|
| Back to top |
|
|
| kimbert |
| Posted: Thu Jul 21, 2011 11:04 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Not sure whether WGerstma's articles will mention this, but you should avoid having two or more nodes with the same name within the same message flow. Similarly, you should avoid having two terminals with the same name on the same node. If you don't follow those rules, you may regret it one day when you try to add business event monitoring to your flows. |
|
| 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
|
|
|
|
