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 » Single Project for Messageflows and Message Sets

Post new topic  Reply to topic
 Single Project for Messageflows and Message Sets « View previous topic :: View next topic » 
Author Message
SOAIntegration
PostPosted: Tue Dec 07, 2010 10:44 am    Post subject: Single Project for Messageflows and Message Sets Reply with quote

Newbie

Joined: 07 Dec 2010
Posts: 7

Hi,
Right now we have all main flows in one Message flow project, similarly subflows and Message sets in MessageSet project. We are planning to combine Message Sets, Main flows, subflows and java components (jars or classess) related to one service in single folder so that we can have bundles based on service and from there we can create bar files.

Though able to put them in single folder (simple project type) while creating bar it is not allowing to add message sets and flows as they are not belong right project type.

Is there any other approach where by i can combine all the components to single folder?

thanks in advance
Back to top
View user's profile Send private message
mqjeff
PostPosted: Tue Dec 07, 2010 10:48 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

You can't have Message Sets in the same Project as Message Flows, and neither can be in a "simple" project.

You need Message Sets to be in Message Set Projects and Message Flows to be in Message Flow projects.

Otherwise Eclipse doesn't know anything about the contents of the files or what builders to use to process the projects or how to resolve project dependencies.

You should have one Message Set Project for each Message Set. You should have one Message Flow project for each set of logically related Message Flows.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Wed Dec 08, 2010 12:36 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

Look at your source control hierarchy and organize message flow and message set projects accordingly.
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
lancelotlinc
PostPosted: Wed Dec 08, 2010 7:05 am    Post subject: Reply with quote

Jedi Knight

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

Think of your grouping mechanism as the Bar file, not the project. A Bar file can, usually does, contain several projects.

Seems as though you are trying to over-engineer your source code control system.

Most ESB teams have one or more "Build Engineers" whose primary focus is to build and deploy bar files, usually with the help of a Continuous Integration tool like Hudson. What does your Build Engineer say about your proposal?
_________________
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
mqjeff
PostPosted: Wed Dec 08, 2010 7:10 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

lancelotlinc wrote:
Most ESB teams have one or more "Build Engineers"


You have missed the word "Should".

Most do not. Most should.

Especially given things like SOXLEY and PCI.

It's fairly clear that SOAIntegration is trying to get to the point where they do have one, and have a structure that is configured to assist using something like Hudsen or ANT or Maven or etc. But also fairly clear that they don't have sufficient understanding to do it correctly.

The structure being looked for should be done at the source control level, not at the workspace or project level.
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed Dec 08, 2010 8:22 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

lancelotlinc wrote:
Most ESB teams have one or more "Build Engineers" whose primary focus is to build and deploy bar files


Hah!

lancelotlinc wrote:
usually with the help of a Continuous Integration tool like Hudson.


Hah squared.

You've clearly been fortunate in your experiences.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
lancelotlinc
PostPosted: Wed Dec 08, 2010 8:28 am    Post subject: Reply with quote

Jedi Knight

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

Last year, the US Govt gave away free golf carts to anyone who wanted one. As long as the golf cart was electric, it qualified for a $4,650 green energy tax credit. The cost of electric golf carts magically became $4,650. 7,211 electric golf carts were bought and paid for with US Treasury money.

So, I am thinking, we can get Congress to approve a Build Engineer tax credit so all Banks, Stock Brokers, and Electric Companies can afford to hire Build Engineers. Ya think?
_________________
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
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Single Project for Messageflows and Message Sets
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.