we use the java task:

  <target name="deploy" depends="init">
    <java fork="true" classname="weblogic.Deployer">
      <classpath refid="classpath"/>
      <arg line="-verbose -noexit -name ${DEPLOY_NAME} -nostage -source
${DEPLOY_SOURCE}  -targets ${TARGET_SERVER}  -adminurl
t3://localhost:${Server.Admin.ListenPort} -user ${Server.Admin.Username}
-password ${Server.Admin.Password} -deploy"/>
    </java>             
  </target>

  <target name="deploy.beans" description="deploys ejb ear">
        <antcall target="deploy">
      <param name="DEPLOY_NAME" value="${BEAN_APPLICATION_NAME}"/>
      <param name="DEPLOY_SOURCE" value="${APPLICATION_DIR}/myEar.ear"/>
      <param name="TARGET_SERVER" value="${APP_SERVER_NAME}"/>

        </antcall>
  </target>


we have 3 servers under the domain, admin, web, and "app" server where
the beans are deployed. a little ant scripting and this could probably
be made a bit more generic. currently we have a separate target for each
component we need to deploy.

> -----Original Message-----
> From: Andreas Bothner [ MTN - Innovation Centre ]
> [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, October 20, 2004 7:28 AM
> To: Ant Users List
> Subject: RE: Any recommended methods for build and deployment in
> weblogic and jboss servers?
> 
> 
> Which ant tasks are you using to deploy to weblogic? 
> 
> -----Original Message-----
> From: Mark Lybarger [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, 20 October 2004 13:23
> To: Ant Users List
> Subject: RE: Any recommended methods for build and deployment 
> in weblogic
> and jboss servers?
> 
> we use ant for building and deploying to weblogic.  we have a 
> fragmented
> process. one build process to build an archive for deployment 
> which is sent
> (via ftp) to a holding area.  there's quite a few steps in there, but
> basically, it's pull from cvs, compile the code, build the 
> ear and web app,
> and package it up into an archive file (we're using .tar 
> unfortunately atm).
> 
> deploying then happens also via ant tasks.  tech services has 
> a shell script
> that basically just calls our deploy script to deploy when 
> it's convenient
> for them.  our deploy script does several things to get 
> deployed to wls.  it
> first undeploys the existing apps from the running server (to 
> clean out
> cached WEB-INF/lib jar files). then it shuts down the servers 
> using ant java
> tasks. next, it copies in our versioned config.xml using ant 
> filters to set
> it up for the needed environment.  finally, it starts the 
> servers again
> using ant java tasks, and then deploys the components to the various
> servers.
> 
> backing out right now is as simple as running the deploy 
> process on the
> previous version.  all wls config changes are accounted for, 
> and any library
> changes are cleaned up and ready to go.
> 
> now, if we could only find time to include a method to 
> inteligently handle
> database changes as well.
> 
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, October 19, 2004 2:36 PM
> > To: Ant Users List
> > Subject: Any recommended methods for build and deployment 
> in weblogic 
> > and jboss servers?
> > 
> > 
> > Hi all,
> > 
> > I know that this is a rather open question.
> > 
> > Are there any recommended ways of building and deploying 
> application 
> > to weblogic and jboss servers?
> > 
> > For example, in build, using Ant in only the build server, 
> then create 
> > packages (what type of format for weblogic and jboss?) then deliver 
> > (rsync?
> > ftp?) and deploy (stop and start the server, what is the 
> best way? run 
> > some ant scripts? or?)
> > 
> > 
> > Thanks
> > 
> > B.
> > 
> > 
> > 
> ---------------------------------------------------------------------
> > 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]
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to