Convert Deployment profile to ant tasks

There is any utility to convert deployment profiles (.deploy files) to ant tasks? We are working with Jdev 10.1.3.2
Thank's in advance.
Julio.

Julio,
Nope. 11g has a nice utility called "ojdeploy" that can be called from ANT, but no help in 10g.
John

Similar Messages

Deploy and Bind ant tasks

Re,
I am using the 10.1.3 beta of oc4j and we are starting to run into some problems with using the oracle deploy and bind ant tasks provided. As our application is growing, the deploy task is taking longer and longer (which by itself is not really a problem since that is to be expected, and when I say long it is only a few seconds so it is tolerable). The problem (I think) lies in the ant tasks. Our "bind" tasks depends on the "deploy" task. But, it seems that sometimes the bind task actually starts before the deploy task is finished. So, we are wondering if there is something wrong with the deploy task. Either oc4j is sending a signal that the deploy is complete before it actually is or the deploy ant task is just waiting a few seconds and then assuming it is complete.
The only way for us to make this problem go away is to run the deploy ant task, look at the console to see that the deploy is finished and then run the bind task separately. Needless to say, that is a bit annoying and hard to automate.
Any ideas?

Chris,
Thanks. I dont think that is it. The process waits a while (so maybe they are the ones doing a sleep).
I am hoping to find out what is actually happening under the hood and if there is in fact a 'wait' giong on, implore to the development staff that they fix that issue before things are GA. Or, if something else is going on ... maybe I can fix it on my end.
Thanks,
Greg

Execute deployment profile in ant

Hi,
is it possible to execute a deployment profile create in JDeveloper in ant?
Thanks,
Koen
[edit]
Started topic before searching the forum.
Re: How can I integrate JDeveloper Deployment profiles into an Ant build sc
Does not seems to work.
[edit]

Hi Koen,
Although there is no way to maintain/generate the ant buildfile directly, it is not too hard to write a buildfile that can build the war/ear and then deploy it. On these links you can find some information on how to do that:
* [Using OC4J Ant tasks for deployment|http://download.oracle.com/docs/cd/E12524_01/web.1013/e12289/anttasks.htm#BEIGEEID]
* [Deploying your webcenter app with ant tasks|http://download.oracle.com/docs/cd/B32110_01/webcenter.1013/b31074/jpsdg_deploy.htm#BGBIIFCC]
Basically, you can use <oracle:deploy/> and alike tasks to deploy your app, and other ant tasks to create datasources and shared libraries.
Regards,
Jeroen van Veldhuizen

Error during deploying using sapdeploy ant task

I am attempting to deploy a simple service which I have created using Dev studio. Instead of deploying using Dev studio, I want to use ant task for the same.
This is the output I see in the console:
deploy:
[sapdeploy] Starting deployment with the following properties:
[sapdeploy] Version Handling Rule: all
[sapdeploy] Error Handling Strategies: [error action: 'prerequisites', error strategy: 'stop', error action: 'deploy', error strategy: 'stop']
[sapdeploy] The targeted SAP J2EE Engines are: [server host: 'myhost', server port '50000', user name 'J2EE_ADMIN'.]
[sapdeploy] Starting to validate the data...
[sapdeploy] Validation ended
[sapdeploy] root dir C:\temp\HelloWorldEAR
[sapdeploy] Selected archives for deployment:
[sapdeploy] 1: 'C:\temp\HelloWorldEAR\HelloWorldEAR.ear'
[sapdeploy] Starting validation for the engine 'server host: 'myhost', server port '50000', user name 'J2EE_ADMIN'.'
[sapdeploy] Engine data validated successfully
[sapdeploy] Starting deployment for the engine 'server host: 'myhost', server port '50000', user name 'J2EE_ADMIN'.'
[sapdeploy] An error occured during the deployment.
[sapdeploy] The result of the deployment is: Error
[sapdeploy] Deployment ended
Where can I get more details of what might be wrong with the deploy process? I tried "-v" flag but to no avail. Syslog of the server shows nothing of interest.
Thanks in advance for any help.
Regards,
Sameer

Logs will be in log\dc_log folder.

LDAP Broken Pipe exception when deploying processes via ant task

Hi,
Has anyone experienced this and can offer a fix? We are publishing/deploying our processes using the fuego:publish task in Fuego 5.7 (we are migrating our system from 5.1) and one of the publish tasks for a large project always fails with the following exception:
Caused by: fuego.directory.CommunicationException: Cannot connect to the Directory Service at: [iplanet://zion:28899/o=nexagent.com].
Detail:The Directory Service could not be reached. Either the Directory Service is down, the host where it resides is unavailable, a network problem exists, or there is no Directory Service at the specified location.
at fuego.directory.provider.ldap.LDAPPersistenceManager.createEntry(LDAPPersistenceManager.java:465)
at fuego.directory.provider.ldap.LDAPPersistenceManager.createEntry(LDAPPersistenceManager.java:489)
at fuego.directory.provider.ldap.LDAPProjectAccessor.createCatalogJar(LDAPProjectAccessor.java:160)
at fuego.directory.DirCatalogJar.create(DirCatalogJar.java:257)
at fuego.directory.DirCatalogJar.create(DirCatalogJar.java:46)
at fuego.mami.CatalogPublisher.store(CatalogPublisher.java:369)
at fuego.mami.ProjectPublisher.storeCatalog(ProjectPublisher.java:1631)
at fuego.mami.ProjectPublisher.storeProject(ProjectPublisher.java:1653)
at fuego.mami.ProjectPublisher.publish(ProjectPublisher.java:854)
at fuego.tools.ant.enterprise.impl.PublishProjectTaskImpl.execute(PublishProjectTaskImpl.java:377)
... 23 more
Caused by: javax.naming.CommunicationException: Broken pipe [Root exception is java.net.SocketException: Broken pipe]; remaining name 'cn=catalogJar-3,cn=fuego-dirCatalogJars,cn=fuego-directoryRoot'
at com.sun.jndi.ldap.LdapCtx.c_createSubcontext(LdapCtx.java:803)
at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_createSubcontext(ComponentDirContext.java:319)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.createSubcontext(PartialCompositeDirContext.java:248)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.createSubcontext(PartialCompositeDirContext.java:236)
at javax.naming.directory.InitialDirContext.createSubcontext(InitialDirContext.java:178)
at fuego.jndi.FaultTolerantDirContext.createSubcontext(FaultTolerantDirContext.java:413)
at fuego.directory.provider.ldap.LDAPPersistenceManager.createNestedEntry(LDAPPersistenceManager.java:1744)
at fuego.directory.provider.ldap.LDAPPersistenceManager.createEntry(LDAPPersistenceManager.java:455)
... 32 more
Caused by: java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at java.io.BufferedOutputStream.write(BufferedOutputStream.java:105)
at com.sun.jndi.ldap.Connection.writeRequest(Connection.java:389)
at com.sun.jndi.ldap.Connection.writeRequest(Connection.java:364)
at com.sun.jndi.ldap.LdapClient.add(LdapClient.java:1007)
at com.sun.jndi.ldap.LdapCtx.c_createSubcontext(LdapCtx.java:766)
... 39 more
Looking at the LDAP access log the error code is B1 which means that the client closed the connection without sending an unbind request or it could also mean that the client sent a malformed request to the server. The project being deployed is quite big and fails when storing the catalog, could the size have something to do with it (this worked in v5.1) is this a bug in 5.7?
Any help would be greatly appreciated!
regards,
Mike

Hi,
Has anyone experienced this and can offer a fix? We are publishing/deploying our processes using the fuego:publish task in Fuego 5.7 (we are migrating our system from 5.1) and one of the publish tasks for a large project always fails with the following exception:
Caused by: fuego.directory.CommunicationException: Cannot connect to the Directory Service at: [iplanet://zion:28899/o=nexagent.com].
Detail:The Directory Service could not be reached. Either the Directory Service is down, the host where it resides is unavailable, a network problem exists, or there is no Directory Service at the specified location.
at fuego.directory.provider.ldap.LDAPPersistenceManager.createEntry(LDAPPersistenceManager.java:465)
at fuego.directory.provider.ldap.LDAPPersistenceManager.createEntry(LDAPPersistenceManager.java:489)
at fuego.directory.provider.ldap.LDAPProjectAccessor.createCatalogJar(LDAPProjectAccessor.java:160)
at fuego.directory.DirCatalogJar.create(DirCatalogJar.java:257)
at fuego.directory.DirCatalogJar.create(DirCatalogJar.java:46)
at fuego.mami.CatalogPublisher.store(CatalogPublisher.java:369)
at fuego.mami.ProjectPublisher.storeCatalog(ProjectPublisher.java:1631)
at fuego.mami.ProjectPublisher.storeProject(ProjectPublisher.java:1653)
at fuego.mami.ProjectPublisher.publish(ProjectPublisher.java:854)
at fuego.tools.ant.enterprise.impl.PublishProjectTaskImpl.execute(PublishProjectTaskImpl.java:377)
... 23 more
Caused by: javax.naming.CommunicationException: Broken pipe [Root exception is java.net.SocketException: Broken pipe]; remaining name 'cn=catalogJar-3,cn=fuego-dirCatalogJars,cn=fuego-directoryRoot'
at com.sun.jndi.ldap.LdapCtx.c_createSubcontext(LdapCtx.java:803)
at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_createSubcontext(ComponentDirContext.java:319)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.createSubcontext(PartialCompositeDirContext.java:248)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.createSubcontext(PartialCompositeDirContext.java:236)
at javax.naming.directory.InitialDirContext.createSubcontext(InitialDirContext.java:178)
at fuego.jndi.FaultTolerantDirContext.createSubcontext(FaultTolerantDirContext.java:413)
at fuego.directory.provider.ldap.LDAPPersistenceManager.createNestedEntry(LDAPPersistenceManager.java:1744)
at fuego.directory.provider.ldap.LDAPPersistenceManager.createEntry(LDAPPersistenceManager.java:455)
... 32 more
Caused by: java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at java.io.BufferedOutputStream.write(BufferedOutputStream.java:105)
at com.sun.jndi.ldap.Connection.writeRequest(Connection.java:389)
at com.sun.jndi.ldap.Connection.writeRequest(Connection.java:364)
at com.sun.jndi.ldap.LdapClient.add(LdapClient.java:1007)
at com.sun.jndi.ldap.LdapCtx.c_createSubcontext(LdapCtx.java:766)
... 39 more
Looking at the LDAP access log the error code is B1 which means that the client closed the connection without sending an unbind request or it could also mean that the client sent a malformed request to the server. The project being deployed is quite big and fails when storing the catalog, could the size have something to do with it (this worked in v5.1) is this a bug in 5.7?
Any help would be greatly appreciated!
regards,
Mike

How to build ear files for ADF application using Ant task

How to build ear files for ADF applications using Ant. The ojdeploy ant task can not find application-level deployment profiles. I am trying to automated build and release for ADF application.
Any help is highly appreciated.
Thanks
Shiva

Hi Timo
Thanks for your reply.
I have successfully created ear file using ojdeploy on jenkins. however when am trying to auto deploy using WLDeploy ant task am getting the following
error :
weblogic.application.ModuleException: :oracle.mds.config.MDSConfigurationException:MDS-01335: namespace "/oracle/webcenter/quicklinks/scopedMD" mapped to metadata-store-usage "WebCenterFileMetadataStore" but its definition was not found in MDS configuration
Please advise how to handle this.
As am a newbie to ADF, could you please advise if it is possible for the ADF application deployments can be automated for different environments using jenkins due to this MDS dependencies.
Appreciate your help.
Thanks
Shiva

Does anyone know how to convert the .deploy file to ant script

hi guys ,
I am doing some work relate to J2EE/ADF application deployment. I need ant script to compile/ear and remote deploy.
Does anyone know how to generate the ant script based on the .deploy file (eg.ejb.deploy and webservice.deploy ).
although I can generate the ant script with creating buildfile from project ,but all the ant tasks are just compile ,no other deploy task...
I much appreciate if anyone can give me a clue
Kevin

I don't know how to convert a .deploy file but you may use below commands to remotely deploy an ear file
To compile
c:\Oracle\Middleware\jdeveloper\jdev\bin\ojdeploy -profile EarProfile -workspace MyApp\MyApp.jws
To Deploy
c:\Oracle\Middleware\wlserver_10.3\server\bin\setWLSEnv.cmd
java weblogic.Deployer -adminurl http://localhost:7101 -user weblogic -password weblogic1 -deploy -upload MyApp\deploy\EarProfile.earMore Details
http://edocs.bea.com/wls/docs100/deployment/understanding.html#wp1057841

Deploying bpm 11g project sar file using ant task

I am trying to deploy the bpm project using ant task file. The status I get is [deployComposite] ---->Deploying composite success. However when I check the deployments, they are not there. If I try to deploy this using Jdeveloper it works correctly. I need to get this to work for production deployments. Any suggestions?
C:\Oracle\Middleware\Oracle_SOA1\bin>ant -f ant-sca-deploy.xml -DserverURL=http:
//10.140.183.71:7001 -DsarLocation=N:\RuleBasedProjectInitiate\deploy\RequestPro
ject.ear -Doverwrite=true -Duser=weblogic
Buildfile: C:\Oracle\Middleware\Oracle_SOA1\bin\ant-sca-deploy.xml
[echo] oracle.home = C:\Oracle\Middleware\Oracle_SOA1\bin/..
deploy:
[input] skipping input as property serverURL has already been set.
[input] skipping input as property sarLocation has already been set.
[deployComposite] created temp dir =C:\DOCUME~1\azeltov\LOCALS~1\Temp\deploy_cli
ent_1279894885343
[deployComposite] Creating HTTP connection to host:10.140.183.71, port:7001
[deployComposite] Enter username and password for realm 'default' on host 10.140
.183.71:7001
[deployComposite] Authentication Scheme: Basic
[deployComposite] Username:
weblogic
[deployComposite] Password:
[deployComposite] Received HTTP response from the server, response code=200
[deployComposite] clean up temp dir: C:\DOCUME~1\azeltov\LOCALS~1\Temp\deploy_cl
ient_1279894885343
[deployComposite] ---->Deploying composite success.
BUILD SUCCESSFUL
Total time: 4 seconds
C:\Oracle\Middleware\Oracle_SOA1\bin>

You can always deploy the ADF web apps from the Application (top menu) deploy option. Just make sure you're deploying the EAR profile for the project. Deploying the web projects from the composite deployment wizard can be convenient. But I think it's often the case that you deploy them (the composite and forms) separately (e.g. you make a series of changes to the composite without needed to redeploy the UI projects).
Bottom line is you don't have to delete the projects to be able to modify/deploy them.

Weblogic 9.1 Deployment errors using the ANT task wldeploy

I am not able to deploy applicatons using the ANT task. The same works with Weblogic 8.1. It is throwing a NoClassDefFoundError. It is looking for a class by name javax/management/InvalidAttributeValueException.
This class file is shipped as part of jmx.jar. I tried to include it and then there was another NoClassDefFoundError that occured.
The problem is I don't want to keep adding these different jars to make the ant deployment work. Can anyone please let me know what could be the problem.
I am using a Windows XP OS and 1.4.2_10 as java version.
I have added all the jars in the weblogic91\server\lib directory to the classpath.
Also I have my apache ant tasks set in the classpath.
Thanks
Shankar Chandrasekaran

Have had a bit of these CLASSPATH issues when jumping versions.
Have had the best success when I create a different profile for each one, making sure the version you want is the only one defined. the main thing my profile sets is
unset PATH
unset CLASSPATH
unset JAVA_HOME
then
export PATH=
export CLASSPATH= the weblogic 9 one
export JAVA_HOME= the one with 9
or however they do it in windows, but make sure you CLASSPATH is only refencing the 9 jars

ANT task wsgen error while deploying RPC style web service

Hi
I am trying to assemble/deploy an rpc style weblogic web service using the 'wsgen'
Ant task and the build.xml scripts provided with the samples. I get this error:
Please help
Thanks,
Praveen
C:\test>ant
Buildfile: build.xml
webservice:
clean:
[delete] Deleting directory C:\test\build
init:
[mkdir] Created dir: C:\test\build
[mkdir] Created dir: C:\test\build\META-INF
[copy] Copying 5 files to C:\test\build\META-INF
compile_ejb:
[javac] Compiling 5 source files to C:\test\build
jar_ejb:
[jar] Building jar: C:\test\a_statelessSession.jar
ejbc:
all:
wsgen:
Error at line:8 col:12 ':' Already got a ':' in name
at weblogic.xml.babel.baseparser.SAXElementFactory.createSAXParseExc
on(SAXElementFactory.java:60)
at weblogic.xml.babel.parsers.StreamParser.<init>(StreamParser.java:
at weblogic.xml.babel.parsers.BabelXMLEventStream.startDocument(Babe
EventStream.java:28)
at weblogic.soap.WebServiceProxy.getXMLStream(WebServiceProxy.java:6
at weblogic.soap.WebServiceProxy.getXMLStream(WebServiceProxy.java:5
at weblogic.soap.WebServiceProxy.getServiceFrom(WebServiceProxy.java
at weblogic.ant.taskdefs.ejb.WSGenHelper.writeClientJar(WSGenHelper.
:1125)
at weblogic.ant.taskdefs.ejb.WSGenHelper.writeWSDL(WSGenHelper.java:
at weblogic.ant.taskdefs.ejb.WSGenHelper.saveDescriptors(WSGenHelper
a:1415)
at weblogic.ant.taskdefs.ejb.WSGenHelper.output(WSGenHelper.java:148
at weblogic.ant.taskdefs.ejb.WSGenHelper.doit(WSGenHelper.java:1517)
at weblogic.ant.taskdefs.ejb.WSGen.execute(WSGen.java:93)
at org.apache.tools.ant.Target.execute(Target.java:153)
at org.apache.tools.ant.Project.runTarget(Project.java:898)
at org.apache.tools.ant.Project.executeTarget(Project.java:536)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:213)
at org.apache.tools.ant.Target.execute(Target.java:153)
at org.apache.tools.ant.Project.runTarget(Project.java:898)
at org.apache.tools.ant.Project.executeTarget(Project.java:536)
at org.apache.tools.ant.Project.executeTargets(Project.java:510)
at org.apache.tools.ant.Main.runBuild(Main.java:421)
at org.apache.tools.ant.Main.main(Main.java:149)
BUILD SUCCESSFUL
Total time: 34 seconds
C:\test>

WLS6.1, service pack 2? I didn't know there were any service packs for 6.1 and
6.0 didn't support wsgen and web services??
simon.
manoj cheenath <[email protected]> wrote:
>
>
This is a known bug which is fixed in WLS 6.1 SP2.
The workaround is to change the complex data types
to have more than one level package names.
for eg: change ....
package foo;
class Data{}
to :
package foo.bar;
class Data{}
-manoj
Praveen wrote:
Hi
I am trying to assemble/deploy an rpc style weblogic web service usingthe 'wsgen'
Ant task and the build.xml scripts provided with the samples. I getthis error:
Please help
Thanks,
Praveen
C:\test>ant
Buildfile: build.xml
webservice:
clean:
[delete] Deleting directory C:\test\build
init:
[mkdir] Created dir: C:\test\build
[mkdir] Created dir: C:\test\build\META-INF
[copy] Copying 5 files to C:\test\build\META-INF
compile_ejb:
[javac] Compiling 5 source files to C:\test\build
jar_ejb:
[jar] Building jar: C:\test\a_statelessSession.jar
ejbc:
all:
wsgen:
Error at line:8 col:12 ':' Already got a ':' in name
at weblogic.xml.babel.baseparser.SAXElementFactory.createSAXParseExc
on(SAXElementFactory.java:60)
at weblogic.xml.babel.parsers.StreamParser.<init>(StreamParser.java:
at weblogic.xml.babel.parsers.BabelXMLEventStream.startDocument(Babe
EventStream.java:28)
at weblogic.soap.WebServiceProxy.getXMLStream(WebServiceProxy.java:6
at weblogic.soap.WebServiceProxy.getXMLStream(WebServiceProxy.java:5
at weblogic.soap.WebServiceProxy.getServiceFrom(WebServiceProxy.java
at weblogic.ant.taskdefs.ejb.WSGenHelper.writeClientJar(WSGenHelper.
:1125)
at weblogic.ant.taskdefs.ejb.WSGenHelper.writeWSDL(WSGenHelper.java:
at weblogic.ant.taskdefs.ejb.WSGenHelper.saveDescriptors(WSGenHelper
a:1415)
at weblogic.ant.taskdefs.ejb.WSGenHelper.output(WSGenHelper.java:148
at weblogic.ant.taskdefs.ejb.WSGenHelper.doit(WSGenHelper.java:1517)
at weblogic.ant.taskdefs.ejb.WSGen.execute(WSGen.java:93)
at org.apache.tools.ant.Target.execute(Target.java:153)
at org.apache.tools.ant.Project.runTarget(Project.java:898)
at org.apache.tools.ant.Project.executeTarget(Project.java:536)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:213)
at org.apache.tools.ant.Target.execute(Target.java:153)
at org.apache.tools.ant.Project.runTarget(Project.java:898)
at org.apache.tools.ant.Project.executeTarget(Project.java:536)
at org.apache.tools.ant.Project.executeTargets(Project.java:510)
at org.apache.tools.ant.Main.runBuild(Main.java:421)
at org.apache.tools.ant.Main.main(Main.java:149)
BUILD SUCCESSFUL
Total time: 34 seconds
C:\test>
-----------------------------------------------------------------<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
This is a known bug which is fixed in WLS 6.1 SP2.
The workaround is to change the complex data types
 to have more than one level package names.
for eg: change ....
package foo;
 class Data{}
to :
package foo.bar;
 class Data{}
-manoj
Praveen wrote:
<blockquote TYPE=CITE>Hi
 I am trying to assemble/deploy an rpc style weblogic web service
using
the 'wsgen'
 Ant task and the build.xml scripts provided with the samples. I get
this error:
 Please help
 Thanks,
 Praveen
 -----------------------------------------------------------------
 C:\test>ant
 Buildfile: build.xml
webservice:
clean:
 [delete] Deleting directory C:\test\build
init:
 [mkdir] Created dir: C:\test\build
 [mkdir] Created dir: C:\test\build\META-INF
 [copy] Copying 5 files to C:\test\build\META-INF
compile_ejb:
 [javac] Compiling 5 source files to C:\test\build
jar_ejb:
 [jar] Building jar: C:\test\a_statelessSession.jar
ejbc:
all:
wsgen:
 Error at line:8 col:12 ':' Already got a ':' in name
 at weblogic.xml.babel.baseparser.SAXElementFactory.createSAXParseExc
 on(SAXElementFactory.java:60)
 at weblogic.xml.babel.parsers.StreamParser.<init>(StreamParser.java:
 at weblogic.xml.babel.parsers.BabelXMLEventStream.startDocument(Babe
 EventStream.java:28)
 at weblogic.soap.WebServiceProxy.getXMLStream(WebServiceProxy.java:6
 at weblogic.soap.WebServiceProxy.getXMLStream(WebServiceProxy.java:5
 at weblogic.soap.WebServiceProxy.getServiceFrom(WebServiceProxy.java
 )
 at weblogic.ant.taskdefs.ejb.WSGenHelper.writeClientJar(WSGenHelper.
 :1125)
 at weblogic.ant.taskdefs.ejb.WSGenHelper.writeWSDL(WSGenHelper.java:
 )
 at weblogic.ant.taskdefs.ejb.WSGenHelper.saveDescriptors(WSGenHelper
 a:1415)
 at weblogic.ant.taskdefs.ejb.WSGenHelper.output(WSGenHelper.java:148
 at weblogic.ant.taskdefs.ejb.WSGenHelper.doit(WSGenHelper.java:1517)
 at weblogic.ant.taskdefs.ejb.WSGen.execute(WSGen.java:93)
 at org.apache.tools.ant.Target.execute(Target.java:153)
 at org.apache.tools.ant.Project.runTarget(Project.java:898)
 at org.apache.tools.ant.Project.executeTarget(Project.java:536)
 at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:213)
 at org.apache.tools.ant.Target.execute(Target.java:153)
 at org.apache.tools.ant.Project.runTarget(Project.java:898)
 at org.apache.tools.ant.Project.executeTarget(Project.java:536)
 at org.apache.tools.ant.Project.executeTargets(Project.java:510)
 at org.apache.tools.ant.Main.runBuild(Main.java:421)
 at org.apache.tools.ant.Main.main(Main.java:149)
BUILD SUCCESSFUL
Total time: 34 seconds
C:\test>
 -----------------------------------------------------------------</blockquote>
</html>

Wldeploy Ant task deploys app in 'New' state

I am trying to deploy a web application in WL 10.0 using the wldeploy Ant task. However, everytime the application is deployed, the consolidated state is 'New' (or deferred deployment). I have to bounce the servers everytime to bring the app in the Active state.
Here is my code:
<target name="undeployWeb">
 
 <wldeploy action="undeploy" verbose="true" debug="false" name="${deploymentName}" user="${weblogicUsername}" password="${weblogicPassword}" adminurl="${weblogicAdminURL}" targets="${weblogicTargetServers}" failonerror="false" />
</target>

<target name="deployWeb">
 
 <wldeploy action="deploy" stage="stage" usenonexclusivelock="true" source="${weblogicDeploymentLocation}/${deploymentName}.war" remote="true" name="${deploymentName}" upload="false" user="${weblogicUsername}" password="${weblogicPassword}" verbose="true" adminurl="${weblogicAdminURL}" debug="true" targets="${weblogicTargetServers}" />
</target>
Is there any way to avoid the bounce of the target servers? I wish to activate the web app straightaway. Please help.
~hartbrekk

Thanks user10939158, for looking into this.
Reason I am saying network is not an issue here because the artifact copy to the remote servers and deployment happens fast, it is just at the step of closing DM connection, it is waiting for a long time (>5 mins). I am guessing that the Deployment Manager message exchanges with the server (internally) has something to do with LAN vs WAN. And, I would expect deployment over WAN take a minute extra as opposed to 5-9 minutes extra what we are seeing now.
Yes, I tried running the wlst script on the remote server and it is fast as well.
Just to clarify, I do not have a local server. I run the plain simple ant script on a build box(lean linux box) which is in the US.
Thanks for your help again.
- Kris
Edited by: kris_2000 on May 25, 2010 2:08 PM

How do I get Ant task deploy to fail on error within an ojdeploy-build ?

I am calling ojdeploy on an xml file with several <deploy> tasks within the <ojdeploy-build> task.
FYI this dramatically increases performance when doing several deployments.
I want to find a way to have the script stop with an error as soon as one of the <deploy> tasks fails with an error (such as a compile error). It does not currently do this.
Is there a way to get the script to stop as soon as a <deploy> task fails within the outer <ojdeploy-build> task?
(eg. could I somehow check the return code for each deploy explicitly and do an exit if the deploy fails)
My Ant book claims that Ant tasks normally fail on error, and when one task fails the Ant script stops at that point. Some Ant tasks (such as exec) have an explicit failonerror attribute which can change this behavior to ignore a non-zero return code from the task and continue executing the Ant script.
It seems to me that the <ojdeploy-build> task has a serious bug where it (probably using java try-catch) ignores the error from <deploy> and keeps going to the next <deploy>, violating a basic design principle of a proper Ant task.
Where can I find the java code for <ojdeploy-build> to confirm my suspicion and then report the bug officially?
Meanwhile, I am very interested in finding some workaround for this bug that preserves having several <deploy> in one script. If I put just one <deploy> in each <ojdeploy-build>, the huge performance improvement is lost.

I played with it some more and it seems that failonerror and resultproperty actually work in JDev 11.1.1.4.0 They are inherited from the [url http://ant.apache.org/manual/Tasks/exec.html]Ant Exec task and work, you just have to set failonerror="true", e.g.
<ora:ojdeploy xmlns:ora="oraclelib:OJDeployAntTask"
 executable="${oracle.jdeveloper.ojdeploy.executable}"
 failonerror="true"
 resultproperty="ojdeploy.exit.code"
 ora:buildscript="${oracle.jdeveloper.deploy.dir}/ojdeploy-build.xml"
 ora:statuslog="${oracle.jdeveloper.deploy.dir}/ojdeploy-statuslog.xml">
...Note that resultproperty is useful only if failonerror="false", use one or the other.

Sun-appserv-deploy cutom Ant task

Hi
I wanted to use sun-appserv-deploy custom ant task in my build file to deploy an archive. But the file attribute requires EXISTING file which is constantly being deleted and recreated during development...
 <taskdef name="sun-appserv-deploy" classname="org.apache.tools.ant.taskdefs.optional.sun.appserv.DeployTask">
 <classpath refid="j2ee.classpath"/>
 </taskdef>
 <sun-appserv-deploy
 file="webapp1.war"
 contextroot="/webapp1"
 name="webapp1WAR
 force="true"
 precompilejsp="false"
 verify="false"
 upload="true"
 user="admin"
 passwordfile="${passwordfile}"
 host="localhost"
 port="4848"
 asinstalldir="${j2ee.home}"/>
Unless the "webapp1.war" exists the enitre build.xml file invalidates (in eclipse)
How do I use this custom task during my development time (obviously when I run clean the WAR file is removed which invalidates my build.xml)
Is there a workaround for this?
Thanks
Z...

You have to include an additional attribute in the task:
<sun-appserv-deploy ... generatermistubs="true" />Edited by: sjfischli on May 15, 2008 8:54 AM

Ant tasks for creating ADF Library

Created an ADF declarative component, exported it as an ADF library and got it working fine. The ADF Library jar was created within JDeveloper by setting up a Deployment profile. The created ADF Library file has the TLD file and TagHandler / Component class files created on the fly and packaged.
Not sure of how We could get the same ADF library created by an Ant task. Are there Ant tasks for creating ADF library available? http://www.connotea.org/user/jdeveloper/tag/ant has some details on the JDeveloper based ant tasks but doesn't have details on creating ADF library.

You can use the ojdeply executable to create and deploy your ADF Library from the commandline:
<Jdev-install-location>/jdeveloper/jdev/bin/ojdeploy -workspace /mydirectory/yourworkspace.jws -profile yourprofile -project yourproject.jpr

Built-in wlst ant task does not work in weblogic 10.3.1

Hi,
We have an installer script that deploys an ear file to a weblogic managed server. The script also invokes the build-tin wlst ant task to bounce the managed server. However, in version 10.3.1 the wlst task seems to be broken. I get this error:
[echo] [wlst] sys-package-mgr: can't create package cache dir, '/u00/webadmin/product/10.3.1/WLS/wlserver_10.3/server/lib/weblogic.jar/./java
tmp/wlstTemp/packages'
[echo] [wlst] java.io.IOException: No such file or directory
[echo] [wlst] at java.io.UnixFileSystem.createFileExclusively(Native Method)
[echo] [wlst] at java.io.File.checkAndCreate(File.java:1704)
[echo] [wlst] at java.io.File.createTempFile(File.java:1792)
[echo] [wlst] at java.io.File.createTempFile(File.java:1828)
[echo] [wlst] at com.bea.plateng.domain.script.jython.WLST_offline.getWLSTOfflineInitFilePath(WLST_offline.java:240)
[echo] [wlst] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[echo] [wlst] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[echo] [wlst] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[echo] [wlst] at java.lang.reflect.Method.invoke(Method.java:597)
[echo] [wlst] at weblogic.management.scripting.utils.WLSTUtil.getOfflineWLSTScriptPath(WLSTUtil.java:63)
[echo] [wlst] at weblogic.management.scripting.utils.WLSTUtil.setupOffline(WLSTUtil.java:214)
[echo] [wlst] at weblogic.management.scripting.utils.WLSTInterpreter.<init>(WLSTInterpreter.java:133)
[echo] [wlst] at weblogic.management.scripting.utils.WLSTInterpreter.<init>(WLSTInterpreter.java:75)
[echo] [wlst] at weblogic.ant.taskdefs.management.WLSTTask.execute(WLSTTask.java:103)
[echo] [wlst] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
Obviously that is not a valid directory...so I am wondering what it is trying to do, and why. The wlst task worked perfectly in 10.3.0. No changes were made when attempting to run the script against 10.3.0 and 10.3.1, which tells me that something is different with the 10.3.1 setup. Here is the ant code I am running:
<target name="init-taskdefs">
<taskdef resource="net/sf/antcontrib/antcontrib.properties">
<classpath>
<pathelement location="ant-ext/ant-contrib.jar" />
</classpath>
</taskdef>
<taskdef name="wldeploy" classname="weblogic.ant.taskdefs.management.WLDeploy" />
<taskdef name="wlst" classname="weblogic.ant.taskdefs.management.WLSTTask" />
</target>
<macrodef name="wlShutdownServer">
<attribute name="adminUser" default="${deploy.admin.username}" />
<attribute name="adminPassword" default="${deploy.admin.password}" />
<attribute name="adminUrl" default="${deploy.admin.url}" />
<attribute name="serverTarget" />
<sequential>
<trycatch property="server.error">
<try>
<wlst failonerror="true"
arguments="@{adminUser} @{adminPassword} @{adminUrl} @{serverTarget}">
<script>
adminUser=sys.argv[0]
adminPassword=sys.argv[1]
adminUrl=sys.argv[2]
serverTarget=sys.argv[3]
connect(adminUser,adminPassword,adminUrl)
target=getMBean("/Servers/"+serverTarget)
if target == None:
target=getMBean("/Clusters/"+serverTarget)
type="Cluster"
else:
type="Server"
print 'Shutting down '+serverTarget+'...'
shutdown(serverTarget,type,'true',15,force='true')
print serverTarget+' was shut down successfully.'
</script>
</wlst>

<echo message="Deleting any lok files that have not been removed..." />
<delete failonerror="false">
<fileset dir="${env.DOMAIN_HOME}/servers/@{serverTarget}" includes="**/*.lok"/>
</delete>
</try>
<catch>
<fail message="@{serverTarget} shutdown failed. ${server.error}" />
</catch>
<finally/>
</trycatch>
</sequential>
</macrodef>
Any help would be appreciated. Thanks!

Well, it looks like passing something like "-Djava.io.tmpdir=/var/tmp/javatmp/`date +%Y%m%d`" to ant did the trick. I had to make sure that directory existed first, otherwise it threw a java ioexception.
I still don't understand what changes between 10.3.0 and 10.3.1 to necessitate this change.

Convert Deployment profile to ant tasks

Similar Messages

Maybe you are looking for