First off, we actually use 10.1.2, not 10.1.3, but I'm pretty sure this will
work for you... A while back I actually downloaded and installed 10.1.3 and
started testing our deployment on it, but never finished it as more important
issues came up, and 10.1.2 is working OK for us right now so there's no
pressing reason to move.
You need to realize the difference between an OC4J deployment and an IAS/OAS deployment.
In short, OC4J is the actual app server which receives the deployment and runs your
EAR/WAR. IAS/OAS is a bundle of administrative tools etc "around" OC4J that
serves as a container for one or more OC4J instances. This is important because we use
different scripts for deployment to OC4J or IAS/OAS.
build.properties file (customized for various environments):
#build.properties file for xyz server
ias.host=blah.xyz.com
ias.em.port=1825
ias.admin=name
ias.admin.password=pass
ias.dcmservlet=Oc4jDcmServletAPI
ias.oracle.home=/orahome/app/oracle/product/OAS10g1012
ias.oc4j.instance=app212
app.name=app
app.web.context=/app212
Generic build.xml content:
<property name="ear.dir" value="${basedir}/ProjectEar"/>
<available file="${ear.dir}/target/project-ear-2.1.2-SNAPSHOT.ear" type="file"
property="ear.present"/>
Stand-alone OC4J is what we generally use for deployment on our
developer workstations.
<target name="oc4jDeploy" depends="oc4jUndeploy" if="ear.present" description="Deploy Application">
<java jar="${basedir}/lib/jdev/j2ee/home/admin.jar" fork="true"
failonerror="true">
<arg value="ormi://${oc4j.host}:${oc4j.ormi.port}/"/>
<arg value="${oc4j.admin}"/>
<arg value="${oc4j.admin.password}"/>
<arg value="-deploy"/>
<arg value="-file"/>
<arg
value="${basedir}/ProjectEar/target/project-ear-2.1.2-SNAPSHOT.ear"/>
<arg value="-deploymentName"/>
<arg value="${app.name}"/>
</java>
<java jar="${basedir}/lib/jdev/j2ee/home/admin.jar" fork="true"
failonerror="true">
<arg value="ormi://${oc4j.host}:${oc4j.ormi.port}/"/>
<arg value="${oc4j.admin}"/>
<arg value="${oc4j.admin.password}"/>
<arg value="-bindWebApp"/>
<arg value="${app.name}"/>
<arg value="project-web-2.1.2-SNAPSHOT"/>
<arg value="${oc4j.web.site}"/>
<arg value="${app.web.context}"/>
</java>
</target>
<target name="oc4jUndeploy" depends="" description="Undeploy Application">
<java jar="${basedir}/lib/jdev/j2ee/home/admin.jar" fork="true"
failonerror="true">
<arg value="ormi://${oc4j.host}:${oc4j.ormi.port}/"/>
<arg value="${oc4j.admin}"/>
<arg value="${oc4j.admin.password}"/>
<arg value="-undeploy"/>
<arg value="${app.name}"/>
</java>
</target>
IAS/OAS is what we use on our real production servers.
<target name="iasDeploy" depends="iasUndeploy" description="Deploy Application">
<java jar="${basedir}/lib/jdev/jdev/lib/oc4j_remote_deploy.jar"
fork="true">
<arg
value="http://${ias.host}:${ias.em.port}/${ias.dcmservlet}/"/>
<arg value="${ias.admin}"/>
<arg value="${ias.admin.password}"/>
<arg value="redeploy"/>
<arg value="${ias.oracle.home}"/>
<arg
value="${basedir}/ProjectEar/target/project-ear-2.1.2-SNAPSHOT.ear"/>
<arg value="${app.name}"/>
<arg value="${ias.oc4j.instance}"/>
</java>
</target>
<target name="iasUndeploy" depends="" description="Undeploy Application">
<java jar="${basedir}/lib/jdev/jdev/lib/oc4j_remote_deploy.jar"
fork="true">
<arg
value="http://${ias.host}:${ias.em.port}/${ias.dcmservlet}/"/>
<arg value="${ias.admin}"/>
<arg value="${ias.admin.password}"/>
<arg value="undeploy"/>
<arg value="${ias.oracle.home}"/>
<arg value="${app.name}"/>
<arg value="${ias.oc4j.instance}"/>
</java>
</target>
Obviously you'll need to do some customizations to the properties file, but
otherwise, this should do it for you. ;-)
Tell me if you have any problems running this on 10.1.3... In the meantime,
I'll try to confirm it works for us at least on 10.1.3 too...
Wayne
On 9/19/06, Alexandre Poitras <[EMAIL PROTECTED]> wrote:
Cargo doesn't support yet oc4j 10.1.3.
On 9/19/06, Mick Knutson <[EMAIL PROTECTED]> wrote:
> That would be great. Would love to see it. I just really want to stop
using
> the web console. Too many issues....
>
>
>
> On 9/18/06, Wayne Fay <[EMAIL PROTECTED]> wrote:
> >
> > I actually use Maven to package my EAR, and then Ant to actually deploy
> > it.
> >
> > But you could certainly use something like Cargo to deploy it from
> > Maven, I'd expect. I just haven't ever had time/reason to bother
> > implementing it. ;-)
> >
> > If you would like, I can certainly send you instructions on deploying
via
> > Ant...
> >
> > Wayne
> >
> > On 9/18/06, Mick Knutson <[EMAIL PROTECTED]> wrote:
> > > I am just starting to use oas 10.1.3 and we want to stop using the web
> > > console and start deploying with maven. Can anyone help us on how to
do
> > > this?
> > >
> > >
> > > --
> > >
> > > Thanks
> > >
> > > DJ MICK
> > > http://www.djmick.com
> > > http://www.myspace.com/mickknutson
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
>
> Thanks
>
> DJ MICK
> http://www.djmick.com
> http://www.myspace.com/mickknutson
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
