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 » mqsipackagebar with independent resources

Post new topic  Reply to topic
 mqsipackagebar with independent resources « View previous topic :: View next topic » 
Author Message
scravr
PostPosted: Thu Aug 01, 2013 9:19 am    Post subject: mqsipackagebar with independent resources Reply with quote

Partisan

Joined: 03 Apr 2003
Posts: 391
Location: NY NY USA 10021

Can mqsipackagebar build from flows on independent resources, or all must be on Apps+Libs?
Back to top
View user's profile Send private message Send e-mail MSN Messenger
lancelotlinc
PostPosted: Thu Aug 01, 2013 9:36 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

Yo can do either, but only independent when your nature has not been converted to Apps.

See RFEs: 37692 IIB/WMB build environment needs to be automatable.
and
37693 : Provide way to indicate design time dependencies
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
scravr
PostPosted: Thu Aug 01, 2013 12:59 pm    Post subject: Reply with quote

Partisan

Joined: 03 Apr 2003
Posts: 391
Location: NY NY USA 10021

in independent resources I have:
MainFlows project with 30 main flows. Each main flow has few "subflows" which are in a 2nd project that has 50 flows.
Each "subflow" point to an ESQL project, JAVA project and 2 msgset projects.
all are in independent resources V7 style.

I "buildformqsipackagebar" the JAVA and both msg-sets project.
The when creating new BAR for one of Mainflows I need to check the "compile and in-line resources". the Manage tab says "You cannot create this BAR file by using mqsipackagebar because it contains a .cmf file."
How do I fix this to get the mqsipackagebar CMD format ?
Back to top
View user's profile Send private message Send e-mail MSN Messenger
scravr
PostPosted: Thu Aug 01, 2013 1:10 pm    Post subject: Reply with quote

Partisan

Joined: 03 Apr 2003
Posts: 391
Location: NY NY USA 10021

I am trying not to change v7 "subflows" to V8 SUBFLOWS
Back to top
View user's profile Send private message Send e-mail MSN Messenger
lancelotlinc
PostPosted: Fri Aug 02, 2013 3:27 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

Are you following these steps to migrate your V7 development to V8?

http://publib.boulder.ibm.com/infocenter/wmbhelp/v8r0m0/topic/com.ibm.etools.mft.doc/bh23410_.htm
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
scravr
PostPosted: Fri Aug 02, 2013 5:06 am    Post subject: Reply with quote

Partisan

Joined: 03 Apr 2003
Posts: 391
Location: NY NY USA 10021

Please answer only if you really now the subject.

I have V7 style independent resources. Can I use mqsipackagebar without changing flows to " Message Broker projects " and without changing V7 "subflows" to V8 subflows, etc. ?
Back to top
View user's profile Send private message Send e-mail MSN Messenger
lancelotlinc
PostPosted: Fri Aug 02, 2013 5:12 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

scravr wrote:
Please answer only if you really now the subject.

I have V7 style independent resources. Can I use mqsipackagebar without changing flows to " Message Broker projects " and without changing V7 "subflows" to V8 subflows, etc. ?


Yes. In fact, that was my answer earlier. You seem to not believe the answer.

To use mqsipackagebar with independent resources, you need to list out each resource independently and leave your nature as Independent rather than Application. You also need to follow the migration steps outlined in the above link.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
scravr
PostPosted: Fri Aug 02, 2013 5:26 am    Post subject: Reply with quote

Partisan

Joined: 03 Apr 2003
Posts: 391
Location: NY NY USA 10021

what is that I am missing...
this link to "Migrating the WebSphere Message Broker Toolkit development resources to Version 8.0" says to migrate to V8 Appls, libs, and Message Broker projects .

I HAVE NO INTEREST changing V7 to V8 artifacts. I am on V8 in last 18months and all is working great. Just like to use mqsipackagebar since its much faster and creates smaller BARs.

when using V7 style BAR and check the "compile and in-line resources". the Manage tab says "You cannot create this BAR file by using mqsipackagebar because it contains a .cmf file."
Back to top
View user's profile Send private message Send e-mail MSN Messenger
mqjeff
PostPosted: Fri Aug 02, 2013 5:31 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

scravr wrote:
what is that I am missing...
this link to "Migrating the WebSphere Message Broker Toolkit development resources to Version 8.0" says to migrate to V8 Appls, libs, and Message Broker projects .

I HAVE NO INTEREST changing V7 to V8 artifacts. I am on V8 in last 18months and all is working great. Just like to use mqsipackagebar since its much faster and creates smaller BARs.

when using V7 style BAR and check the "compile and in-line resources". the Manage tab says "You cannot create this BAR file by using mqsipackagebar because it contains a .cmf file."


that's got *nothing* to do with independent resources.

That's got *everything* to do with "compile and in-line resources".

That's what that checkbox does - makes it impossible to use mqsipackagebar. It uses Toolkit to compile everything before deployment, and thus you have to use mqsiCREATEbar, which is a TOOLKIT command.

mqsipackagebar is a runtime command that does not use Toolkit, and thus does not compile anything, and thus can be run anywhere that runtime is installed.

BAR files built by mqsipackagebar are compiled by the runtime DURING DEPLOYMENT.

BAR files built by mqsicreatebar are compiled by THE TOOLKIT during BAR FILE BUILD.

Don't use "compile and in-line resources" unless you have a specific and identified need to do so.
Back to top
View user's profile Send private message
scravr
PostPosted: Fri Aug 02, 2013 5:46 am    Post subject: Reply with quote

Partisan

Joined: 03 Apr 2003
Posts: 391
Location: NY NY USA 10021

Thanks mqjeff.

I understand the diif's between mqsipackagebar and mqsicreatebar and where each is executed.

I need to use "compile and in-line resources" without it I get errors on toolkit build bar.

So the bottom line is:
1. we cannot use mqsipackagebar with V7 style artifacts,
2. stay with V7 and check "compile and in-line resources"
3. just try using mqsipackagebar on broker and type all 50-70 artifacts that need to be added to BAR !!!
Back to top
View user's profile Send private message Send e-mail MSN Messenger
mqjeff
PostPosted: Fri Aug 02, 2013 6:09 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

scravr wrote:
Thanks mqjeff.

I understand the diif's between mqsipackagebar and mqsicreatebar and where each is executed.

I need to use "compile and in-line resources" without it I get errors on toolkit build bar.

So the bottom line is:
1. we cannot use mqsipackagebar with V7 style artifacts,

No.

scravr wrote:
2. stay with V7 and check "compile and in-line resources"

No.

scravr wrote:
3. just try using mqsipackagebar on broker and type all 50-70 artifacts that need to be added to BAR !!!

Or move to a v8 application and libraries, and type one thing.
Back to top
View user's profile Send private message
lancelotlinc
PostPosted: Fri Aug 02, 2013 6:28 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

mqjeff wrote:
scravr wrote:
2. stay with V7 and check "compile and in-line resources"

No.

scravr wrote:
3. just try using mqsipackagebar on broker and type all 50-70 artifacts that need to be added to BAR !!!

Or move to a v8 application and libraries, and type one thing.


There is a bug with both mqsicreatebar and mqsipackagebar in that it includes all files in your project whether you need them or not if on Application nature. So be aware if you change natures, and you specify the application name to include in the bar, you might get unexpected other files there also. It doesn't cause any errors, just bloats bar size.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
scravr
PostPosted: Fri Aug 02, 2013 7:13 am    Post subject: Reply with quote

Partisan

Joined: 03 Apr 2003
Posts: 391
Location: NY NY USA 10021

Have been through all these problems in last 18months.

will stay with V7 style artifacts and not be using mqsipackagebar !!!
Back to top
View user's profile Send private message Send e-mail MSN Messenger
ghoshly
PostPosted: Tue May 27, 2014 7:19 am    Post subject: Reply with quote

Partisan

Joined: 10 Jan 2008
Posts: 333

When we are trying to create bar files using toolkit, mqsicreatebar, mqsipackagebar command each generating different bar file for same code.

While WMB Toolkit is able to add all artifacts for an application; mqsipackagebar command is unable to add artifacts through indirect references. Though mqsicreatebar command is able to add artifacts through indirect reference it misses artifacts other than flows and jars, i.e. esql files.

Just wanted to know if you have noticed any such discrepancy?

WMB 8.0.0.2 - Windows where both runtuime and toolkit is installed.

Lets say trying to build bar file for App 'A'
'A' has references to Lib 'B' and Lib 'B' has reference to Lib 'C'
Unless we update project reference of 'A' to include 'C' directly, mqsipackage bar is unable to add the same in the bar file.
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 » mqsipackagebar with independent resources
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.