You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Robert Thullner <rt...@gmx.at> on 2007/12/20 19:27:25 UTC
Manageability in ServiceMix
Hi
I have now been playing and working with ServiceMix a few weeks. But I still
have one question targeting the manageability and maintainability of my
configurations.
Assuming that I have 20 or more service units in my service assembly, so
that I would also have 20 xbeans.xml, pom.xml, etc. files where my service
units are configured (services, endpoints, routes, etc.). For me that would
lead into a real mass of configuration files that have to be managed and
maintained somehow. However I find it painful to keep the overview of such a
mass of files.
Do you advises a way or a tool how to keep the management complexity of huge
service assemblies low so that I do not have to keep track of and maintain a
lot of xml files if any changes in an environment occur?
Thanks for any thoughts and suggestions
Robert
Re: AW: Manageability in ServiceMix
Posted by rgavlin <rg...@yahoo.com>.
You might consider using a single service unit per service engine/binding
component. This might be a sensible way to decompose the service assembly
into manageable pieces.
- Ron
Robert Thullner wrote:
>
> I was already thinking of this. But again I have to state if I have 20
> service units in one file it would also get pretty huge and maintaining
> such
> huge files is also not easy. But of course I have everything defined in
> one
> file.
>
> For me having 20 different xml files or having one huge xml files are the
> two extremes. I am wondering if there is "a way in the middle" or some
> best
> practices to handle a lot of service units in one assembly?
>
> Greetings
> Robert
>
>
> -----Ursprüngliche Nachricht-----
> Von: Guillaume Nodet [mailto:gnodet@gmail.com]
> Gesendet: Donnerstag, 20. Dezember 2007 20:02
> An: users@servicemix.apache.org
> Betreff: Re: Manageability in ServiceMix
>
> You can also use a single xml configuration file if you prefer for all
> your
> servicemix endpoints:
>
> http://svn.apache.org/viewvc/incubator/servicemix/trunk/deployables/servicee
> ngines/servicemix-lwcontainer/src/test/resources/org/apache/servicemix/lwcon
> tainer/su2-src/servicemix.xml?revision=584990&view=markup&pathrev=584990
>
> On Dec 20, 2007 7:27 PM, Robert Thullner <rt...@gmx.at> wrote:
>
>> Hi
>>
>> I have now been playing and working with ServiceMix a few weeks. But I
>> still have one question targeting the manageability and
>> maintainability of my configurations.
>>
>> Assuming that I have 20 or more service units in my service assembly,
>> so that I would also have 20 xbeans.xml, pom.xml, etc. files where my
>> service units are configured (services, endpoints, routes, etc.). For
>> me that would lead into a real mass of configuration files that have
>> to be managed and maintained somehow. However I find it painful to
>> keep the overview of such a mass of files.
>>
>> Do you advises a way or a tool how to keep the management complexity
>> of huge service assemblies low so that I do not have to keep track of
>> and maintain a lot of xml files if any changes in an environment
>> occur?
>>
>> Thanks for any thoughts and suggestions Robert
>>
>>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
>
>
>
--
View this message in context: http://www.nabble.com/Manageability-in-ServiceMix-tp14442277s12049p14461696.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
AW: Manageability in ServiceMix
Posted by Robert Thullner <rt...@gmx.at>.
I was already thinking of this. But again I have to state if I have 20
service units in one file it would also get pretty huge and maintaining such
huge files is also not easy. But of course I have everything defined in one
file.
For me having 20 different xml files or having one huge xml files are the
two extremes. I am wondering if there is "a way in the middle" or some best
practices to handle a lot of service units in one assembly?
Greetings
Robert
-----Ursprüngliche Nachricht-----
Von: Guillaume Nodet [mailto:gnodet@gmail.com]
Gesendet: Donnerstag, 20. Dezember 2007 20:02
An: users@servicemix.apache.org
Betreff: Re: Manageability in ServiceMix
You can also use a single xml configuration file if you prefer for all your
servicemix endpoints:
http://svn.apache.org/viewvc/incubator/servicemix/trunk/deployables/servicee
ngines/servicemix-lwcontainer/src/test/resources/org/apache/servicemix/lwcon
tainer/su2-src/servicemix.xml?revision=584990&view=markup&pathrev=584990
On Dec 20, 2007 7:27 PM, Robert Thullner <rt...@gmx.at> wrote:
> Hi
>
> I have now been playing and working with ServiceMix a few weeks. But I
> still have one question targeting the manageability and
> maintainability of my configurations.
>
> Assuming that I have 20 or more service units in my service assembly,
> so that I would also have 20 xbeans.xml, pom.xml, etc. files where my
> service units are configured (services, endpoints, routes, etc.). For
> me that would lead into a real mass of configuration files that have
> to be managed and maintained somehow. However I find it painful to
> keep the overview of such a mass of files.
>
> Do you advises a way or a tool how to keep the management complexity
> of huge service assemblies low so that I do not have to keep track of
> and maintain a lot of xml files if any changes in an environment
> occur?
>
> Thanks for any thoughts and suggestions Robert
>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
Re: Manageability in ServiceMix
Posted by Guillaume Nodet <gn...@gmail.com>.
You can also use a single xml configuration file if you prefer for all your
servicemix endpoints:
http://svn.apache.org/viewvc/incubator/servicemix/trunk/deployables/serviceengines/servicemix-lwcontainer/src/test/resources/org/apache/servicemix/lwcontainer/su2-src/servicemix.xml?revision=584990&view=markup&pathrev=584990
On Dec 20, 2007 7:27 PM, Robert Thullner <rt...@gmx.at> wrote:
> Hi
>
> I have now been playing and working with ServiceMix a few weeks. But I
> still
> have one question targeting the manageability and maintainability of my
> configurations.
>
> Assuming that I have 20 or more service units in my service assembly, so
> that I would also have 20 xbeans.xml, pom.xml, etc. files where my service
> units are configured (services, endpoints, routes, etc.). For me that
> would
> lead into a real mass of configuration files that have to be managed and
> maintained somehow. However I find it painful to keep the overview of such
> a
> mass of files.
>
> Do you advises a way or a tool how to keep the management complexity of
> huge
> service assemblies low so that I do not have to keep track of and maintain
> a
> lot of xml files if any changes in an environment occur?
>
> Thanks for any thoughts and suggestions
> Robert
>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/