You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Evise <ev...@mail.ru> on 2008/06/05 10:40:39 UTC
SA deploy\undeploy automation using Ant tasks
Good day.
I try to automate SA deploy-start procedure using SM Ant tasks.
Initial conditions:
SA that could be frequently regenerated with different settings for some SU
and should be deployed-started after each changing under SM
If there is a first SA deployment (no such SA under SM yet) it is enough
deploy and start Ant tasks.
If there is a not first SA deployment (SA already exist and started under SM
) shutdown, undeploy, deploy and start Ant task should be used.
The question is: how do I (script ) know is there SA with such name exist or
not under SM.
Because if I try to do for e.g. shutdown Ant task for unexisted SA the
NullPointerException shown and script finished.
Or may be it is possible some how to force deployment even if SA already
exist under SM?
I also see a "list-service-assemblies " Ant task at servicemix-ant-task.xml,
but it looks like only print a number of SA under SM to console traces and
I can't imagine how to use it in my situation.
Thank you.
--
View this message in context: http://www.nabble.com/SA-deploy%5Cundeploy-automation-using-Ant-tasks-tp17664921p17664921.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: SA deploy\undeploy automation using Ant tasks
Posted by Evise <ev...@mail.ru>.
bsnyder wrote:
>
> On Thu, Jun 5, 2008 at 2:40 AM, Evise <ev...@mail.ru> wrote:
>>
>> Good day.
>> I try to automate SA deploy-start procedure using SM Ant tasks.
>> Initial conditions:
>> SA that could be frequently regenerated with different settings for some
>> SU
>> and should be deployed-started after each changing under SM
>> If there is a first SA deployment (no such SA under SM yet) it is enough
>> deploy and start Ant tasks.
>> If there is a not first SA deployment (SA already exist and started under
>> SM
>> ) shutdown, undeploy, deploy and start Ant task should be used.
>> The question is: how do I (script ) know is there SA with such name exist
>> or
>> not under SM.
>> Because if I try to do for e.g. shutdown Ant task for unexisted SA the
>> NullPointerException shown and script finished.
>> Or may be it is possible some how to force deployment even if SA already
>> exist under SM?
>> I also see a "list-service-assemblies " Ant task at
>> servicemix-ant-task.xml,
>> but it looks like only print a number of SA under SM to console traces
>> and
>> I can't imagine how to use it in my situation.
>
> There is no reason to shut down ServiceMix every time you need to
> redeploy a SA as SAs can be hot deployed in ServiceMix via either the
> hotdeploy directory or via JMX (the Ant tasks use JMX).
>
> Bruce
> --
> perl -e 'print
> unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
> );'
>
> Apache ActiveMQ - http://activemq.org/
> Apache Camel - http://activemq.org/camel/
> Apache ServiceMix - http://servicemix.org/
> Apache Geronimo - http://geronimo.apache.org/
>
> Blog: http://bruceblog.org/
>
>
I did not shutdown SM, as I wrote, I shutdown SA using ant tasks. I know
about deployment SA by copy it to hotdeploy folder, but is not suitable for
me.
Anyway I decide to use for this purpose not one build\deploy script, because
if some task failed script stop their work, but 2 additional scripts with
"stop" and "undeploy" ant task and call this scripts from main script. In
this case if some of task failed main scenario will be continue.
--
View this message in context: http://www.nabble.com/SA-deploy%5Cundeploy-automation-using-Ant-tasks-tp17664921p17797131.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: SA deploy\undeploy automation using Ant tasks
Posted by Bruce Snyder <br...@gmail.com>.
On Thu, Jun 5, 2008 at 2:40 AM, Evise <ev...@mail.ru> wrote:
>
> Good day.
> I try to automate SA deploy-start procedure using SM Ant tasks.
> Initial conditions:
> SA that could be frequently regenerated with different settings for some SU
> and should be deployed-started after each changing under SM
> If there is a first SA deployment (no such SA under SM yet) it is enough
> deploy and start Ant tasks.
> If there is a not first SA deployment (SA already exist and started under SM
> ) shutdown, undeploy, deploy and start Ant task should be used.
> The question is: how do I (script ) know is there SA with such name exist or
> not under SM.
> Because if I try to do for e.g. shutdown Ant task for unexisted SA the
> NullPointerException shown and script finished.
> Or may be it is possible some how to force deployment even if SA already
> exist under SM?
> I also see a "list-service-assemblies " Ant task at servicemix-ant-task.xml,
> but it looks like only print a number of SA under SM to console traces and
> I can't imagine how to use it in my situation.
There is no reason to shut down ServiceMix every time you need to
redeploy a SA as SAs can be hot deployed in ServiceMix via either the
hotdeploy directory or via JMX (the Ant tasks use JMX).
Bruce
--
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
Apache ActiveMQ - http://activemq.org/
Apache Camel - http://activemq.org/camel/
Apache ServiceMix - http://servicemix.org/
Apache Geronimo - http://geronimo.apache.org/
Blog: http://bruceblog.org/