Ant Script deployment in weblogic 10.3.6(11g)?

By -

Step 1:Create build.xml file

<project name="testapp" default="deploy">
<property name="wls.username" value="weblogic"/>
<property name="wls.password" value="weblogic"/>
<property name="wls.hostname" value="localhost"/>
<property name="wls.port" value="7001"/>
<property name="admin.server.name" value="AdminServer"/>
<property name="deploy.targets" value="ms1,ms2"/>
<property name="deploy.name1" value="jsf"/>
<property name="deploy.name2" value="jstl"/>
<property name="deploy.name3" value="bstr"/>
<property name="deploy.name4" value="medrec"/>
<property name="deploy.name5" value="physician"/>
<property name="deploy.source.jsf" value="C:\bea\wlserver_10.3\common\deployable-libraries\jsf-1.2.war"/>
<property name="deploy.source.jstl" value="C:\bea\wlserver_10.3\common\deployable-libraries\jstl-1.2.war"/>
<property name="deploy.source.browserstarter" value="C:\bea\wlserver_10.3\samples\server\medrec\modules\browser-starter\target\browser-starter.war"/>
<property name="deploy.source.medrec" value="C:\bea\wlserver_10.3\samples\server\medrec\modules\medrec\assembly\target\medrec.ear"/>
<property name="deploy.source.physician" value="C:\bea\wlserver_10.3\samples\server\medrec\modules\physician\assembly\target\physician.ear"/>
<taskdef name="wldeploy" classname="weblogic.ant.taskdefs.management.WLDeploy">
<classpath>
<pathelement location="C:\bea\wlserver_10.3\server\lib\weblogic.jar"/>
</classpath>
</taskdef>
<target name="deploy">

<wldeploy action="deploy"
        name="${deploy.name1}"
        source="${deploy.source.jsf}"
        user="${wls.username}"
       nostage="true"
        password="${wls.password}"
        verbose="true
        library="true"
        adminurl="t3://${wls.hostname}:${wls.port}"
        targets="${deploy.targets}"/>
<wldeploy action="deploy"
        name="${deploy.name2}"
        source="${deploy.source.jstl}"
        user="${wls.username}"
       nostage="true"
        password="${wls.password}"
        verbose="true"
        library="true"
        adminurl="t3://${wls.hostname}:${wls.port}"
        targets="${deploy.targets}"/>

<wldeploy action="deploy"
        name="${deploy.name4}"
        source="${deploy.source.medrec}"
        user="${wls.username}"
       nostage="true"
        password="${wls.password}"
        verbose="true"
        library="false"
        adminurl="t3://${wls.hostname}:${wls.port}"
        targets="${deploy.targets}"/>

<wldeploy action="deploy"
        name="${deploy.name5}"
        source="${deploy.source.physician}"
        user="${wls.username}"
       nostage="true"
        password="${wls.password}"
        verbose="true"
        library="false"
        adminurl="t3://${wls.hostname}:${wls.port}"
        targets="${deploy.targets}"/>

<wldeploy action="deploy"
        name="${deploy.name3}"
        source="${deploy.source.browserstarter}"
        user="${wls.username}"
       nostage="true"
        password="${wls.password}"
        verbose="true"
        library="false"
        adminurl="t3://${wls.hostname}:${wls.port}"
        targets="${deploy.targets}"/>
 </target>
<target name="undeploy">
<wldeploy action="undeploy"
        name="${deploy.name5}"
        failonerror="false"
         user="${wls.username}"
         password="${wls.password}"
         verbose="true"
         adminurl="t3://${wls.hostname}:${wls.port}"
 targets="${deploy.targets}"/>
<wldeploy action="undeploy"
        name="${deploy.name4}"
        failonerror="false"
        user="${wls.username}"
        password="${wls.password}"
        verbose="true"
        adminurl="t3://${wls.hostname}:${wls.port}"
        targets="${deploy.targets}"/>
<wldeploy action="undeploy"
        name="${deploy.name3}"
        failonerror="false"
        user="${wls.username}"
       password="${wls.password}"
       verbose="true"
       adminurl="t3://${wls.hostname}:${wls.port}"
       targets="${deploy.targets}"/>
<wldeploy action="undeploy"
        name="${deploy.name2}"
        failonerror="false"
        user="${wls.username}"
        password="${wls.password}"
        verbose="true"
        adminurl="t3://${wls.hostname}:${wls.port}"
      targets="${deploy.targets}"/>
<wldeploy action="undeploy"
        name="${deploy.name1}"
        failonerror="false"
        user="${wls.username}"
        password="${wls.password}"
        verbose="true"
       adminurl="t3://${wls.hostname}:${wls.port}"
       targets="${deploy.targets}"/>
</target>
</project>

Step 2: Set the classpath
 Execute setDomainEnv.sh script.

Step3: Execute the below command for deployment

ant -f build.xml deploy

Step4: Execute the below command for undeploying the application

ant -f build.xml undeploy

Comments

Post a Comment

Popular posts from this blog

Interview question for File and FTP Adapter

By -
1)  Why File Adapter is used in SOA Suite tool ?.  File adapter is used to read and write file from and to local system. 2)  Why FTP Adapter is used in SOA Suite tool ?. FTP adapter is similar to File adapter with one difference that this adapter is used to read/write the file from/to remote system. 3)  What all differences we have between File and FTP adapters.  Following are the major differences between File and FTP adapter. File Adapter 1. It is used to deal with local systems only. 2. Do not require any configuration to make this adapter work. FTP Adapter 1. It is used to deal with remote systems. 2. Outbound Connection Pool needs to be configured with FTP details to make this adapter work. 4)  File & FTP adapters are known and Transactional or Non-Transactional adapters?.  These adapters are known as non-transactional adapters as these adapters does not support transactions. 5)  Can we read flat files using these adapter...
Read more

What is boot.properties file and how to create

By -
Boot.properties is a file, it containing  weblogic server username and password . If your server is in production mode then only you have to create manually this boot.properties file. If your server is in Development then you no need to create this file because server it self create this file while creating Domain. A boot identity file contains the user credentials for starting and stopping an instance of WebLogic Server. An administration server or managed server can refer to this file for user credentials instead of prompting at the command line to provide them. To Create boot.properties: Go to below location Win :   C:\Oracle\Middleware\user_projects\domains\test_domain\servers\AdminServer\ Linux : Oracle\Middleware\user_projects\domains\test_domain\servers\AdminServer\ 1.First you have to create security folder under AdminServer 2.Create boot.properties file under security folder. 3.Open notepad and write the below two lines username=********** password=*****...
Read more

SSL Exceptions in Admin Server and Node Manager.

By -
javax.net.ssl.SSLKeyException: [Security:090482]BAD_CERTIFICATE alert was received from oracle.test.com – xx.xxx.xx.xx. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected. <WARNING> <Uncaught exception in server handlerjavax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake>javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:849) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1170) The above exceptions are  the most common exceptions encountered during the setup of Weblogic Server in an environment. The stack does suggest what could be the reasons but the diagnostics are not mentioned. To debug this issue, first we need...
Read more