| Author |
Message
|
| shruthi |
 Posted: Fri Sep 24, 2010 4:31 am Post subject: including source code in bar file in V61 WMB |
 |
|
Apprentice
Joined: 04 Apr 2008
Posts: 43
|
Hi ,
Is there any impact on Broker if we deploy the bar file which has source code included in V61 WMB.
Thanks
-Shruthi |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Fri Sep 24, 2010 4:42 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Sep 24, 2010 4:43 am Post subject: Re: including source code in bar file in V61 WMB |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| shruthi wrote: |
| Is there any impact on Broker if we deploy the bar file which has source code included in V61 WMB. |
It'll make the bar file bigger.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| shruthi |
| Posted: Fri Sep 24, 2010 6:01 am Post subject: |
|
|
Apprentice
Joined: 04 Apr 2008
Posts: 43
|
| i mean is there any impact on broker performance or any disadvantages if we deploy with source code in barfile. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Sep 24, 2010 6:16 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| shruthi wrote: |
| i mean is there any impact on broker performance or any disadvantages if we deploy with source code in barfile. |
I repeat, define "impact".
Yes, bigger bar files use more resources. Does that use of resources cause an impact? It depends on how you are measuring the impact, and it depends on how big the bar file is in the first place.
Is it better to NOT deploy source? Yes.
Is it going to cause a problem if you DO deploy source?  |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Sep 24, 2010 6:24 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| shruthi wrote: |
| i mean is there any impact on broker performance or any disadvantages if we deploy with source code in barfile. |
It'll take the broker long to process deploys for one thing.
It depends on a lot of factors. Mostly (as my most worthy associate points out) what you mean by "impact". It also depneds on how much code we're talking about. I have a flow (I use the term guardedly) with a little over 26Mb of ESQL in it. If I was insane enough to put that in a bar file, the impact would be significantly different to a flow with 5 lines in a single compute node.
Here's another good question - why do you want to put source in a bar file? What do you intend to achieve? What do you intend to achieve that you couldn't achieve (and with considerably more benefits) with good source code control?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| shruthi |
| Posted: Fri Sep 24, 2010 8:00 am Post subject: |
|
|
Apprentice
Joined: 04 Apr 2008
Posts: 43
|
Jeff i am not sure what do want to be defined in "impact"
let me put the question in a different way 
What are the disadvantages in including source code in bar file.
does it slow the processing of messages /flow performance ?
does the source code included in bar file is stored some where in broker internal tables or does broker just ignores source code like commented code when deployed .
We use CVS as code repository but just want to understand more about the new recovery feature in V61 . |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Sep 24, 2010 8:56 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| shruthi wrote: |
| just want to understand more about the new recovery feature in V61 . |
Post a link to the features you're trying to use.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| shruthi |
| Posted: Fri Sep 24, 2010 10:41 am Post subject: |
|
|
Apprentice
Joined: 04 Apr 2008
Posts: 43
|
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Sep 24, 2010 11:02 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| shruthi wrote: |
http://publib.boulder.ibm.com/infocenter/wmbhelp/v6r1m0/index.jsp?topic=/com.ibm.etools.mft.doc/ax79999_.htm
Take copies of all your BAR files to back up their contents. Include all the associated source files when you build your broker archive (BAR) files; you can then save all content by saving only the BAR file. To add resources to a BAR file that is ready for deployment, select Include source files, which adds the message flow and message set source files, and the compiled files. |
Ah! That's one of the suggested methods for backing up the broker toolkit. You confused me slightly when you talked about the "new recovery feature in v61", which this really isn't.
However, all the comments about code in bar files apply. IMHO I think having the code in CVS gives you all that source in the bar files would in a better way.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| shruthi |
| Posted: Fri Sep 24, 2010 11:17 am Post subject: |
|
|
Apprentice
Joined: 04 Apr 2008
Posts: 43
|
sorry Vitor i wasnot clear.
i was talking about recovering code from bar file , by building bar file using the 'include source file' option.
is it a good idea to use that option in production ? |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Sep 24, 2010 11:34 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| shruthi wrote: |
| sorry Vitor i wasnot clear. |
No, no, I had the stick by the wrong end.
| shruthi wrote: |
| is it a good idea to use that option in production ? |
IMHO no. You're much better off having good controls & delivery procedures so that you can identify which code version in CVS is the one that's running. This also gets you into the habit of moving associated components (like application or database chages) along with a bar file as a syncronised delivery.
Also if you want to fix producton it's much faster and easier to pull the code out of CVS into a Toolkit project than to extract it from a bar file & reconstruct it.
My 2 cents, other opinions are equally valid.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
