| Author |
Message
|
| EZHIL MALAR |
 Posted: Wed Aug 13, 2008 3:02 am Post subject: Get name of bar file or message flow deployed in the EG |
 |
|
Newbie
Joined: 20 Mar 2007
Posts: 8
|
I have a problem here..
I need to retrieve the name of the bar files or all the message flows deployed in the execution Groups from the ESQL code of the message flows.
I cannot use a JCN as extra load is not allowed.
How can i do it from ESQl.
Can anybody suggest please ? |
|
| Back to top |
|
 |
| AkankshA |
| Posted: Wed Aug 13, 2008 3:15 am Post subject: Re: Get name of bar file or message flow deployed in the EG |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
| EZHIL MALAR wrote: |
I have a problem here..
I need to retrieve the name of the bar files or all the message flows deployed in the execution Groups from the ESQL code of the message flows.
I cannot use a JCN as extra load is not allowed.
How can i do it from ESQl.
Can anybody suggest please ? |
even JCN would not return you all the message flows deployed in the bar file...
_________________
Cheers |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Wed Aug 13, 2008 3:22 am Post subject: Why do you need this? |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
It would help everyone here if you would provide an explanation of why you need this information.
In my opinion, BAR files are just transport containers for deployable objects. There isn't a STRICT 1:1 relationship between a bar file and a message flow or a message model.
Personally, I prefer the 1:1 method but I know of other sites where they package every deployable item into one bar file.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| EZHIL MALAR |
| Posted: Wed Aug 13, 2008 3:50 am Post subject: |
|
|
Newbie
Joined: 20 Mar 2007
Posts: 8
|
I need the BAR File name that contains the message flows deployed in the EG from the ESQL because depending on that we have to decide the suitable course of action for different project instances on different project servers.
Since ESQL has a way to know the broker name, execution group and message flow name that hosts the ESQL code.
I wanted to know whether there is any means to know the bar file also deployed in the EG. |
|
| Back to top |
|
|
| AkankshA |
| Posted: Wed Aug 13, 2008 3:52 am Post subject: |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
we package it wrt functionality and sometimes even wrt teams..
I am curious to know the requirement for knowing all the flow names deployed in a bar file and also for knowing the bar name,, .. does it relate to logging in some way ?? 
_________________
Cheers |
|
| Back to top |
|
|
| EZHIL MALAR |
| Posted: Wed Aug 13, 2008 3:55 am Post subject: |
|
|
Newbie
Joined: 20 Mar 2007
Posts: 8
|
yes you got it right 
We are trying to identify differnt project instances on our visual tracking tool using our logging framework. |
|
| Back to top |
|
|
| AkankshA |
| Posted: Wed Aug 13, 2008 4:26 am Post subject: |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
Well,,, why do you want to log all the flow names then,, and also why bar file name...
I feel is should only log the flow name ....
are you trying to deploye one flow in 2 or more bar files...
May be its the time to question the requirements.. 
_________________
Cheers |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Wed Aug 13, 2008 4:40 am Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi EZHIL MALAR,
If you look at the Message Broker Toolkit Administrative perspective, you'll find that on clicking any deployed flow, you are shown the name of the bar file it was deployed from.
So if the toolkit can display it then surely it is available somewhere. could be the broker database.
If eventually this information is not available anywhere and you want it logged, then have only one tool do the deployment always and have it store this information too somewhere.
Regards. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Aug 13, 2008 2:16 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
The information should be available using the java toolkit proxy...
So you can program and store it wherever you want...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| sandeep9678 |
| Posted: Wed Aug 13, 2008 9:24 pm Post subject: |
|
|
Apprentice
Joined: 04 Aug 2008
Posts: 41
Location: India
|
Hi EZHIL MALAR,
If you want the flow name for Logging and you have your own Logging Framework, why you need .bar file name. You can very well use ESQL node through which you can get the messageFlow name at runtime.
Use this flowname which you got at runtime to log the details.
Another point about different environments, then if you want to log differently according to the environment type, then get the Broker Name / execution group. It must be different with specific pattern. Use that to differentiate the logging level.
You can use UDP on message flow as well. This will help you in deciding the logging environment and logging level as well.
_________________
Cheers,
Sandeep |
|
| Back to top |
|
|
|
|
