Skip to main content

How Do I: Call wlwBuild.cmd from an Ant build.xml file in Weblogic?

How Do I: Call wlwBuild.cmd from an Ant build.xml file?

 

The following topic explains how to create an Ant task that calls the command line tool wlwBuild.cmd. wlwBuild.cmd is used to create application-level EAR files or project-level JAR files for deployment to a production server.

To create an Ant build.xml file, you can either auto-generate a build.xml file or you can write the file by hand.

To auto-generate an Ant build.xml file for the application

1.    Open the target application in WebLogic Workshop.

2.    From the Tools menu, select Application properties.

3.    In the Application Properties dialog, from the left-side navigation panel, select the Build node.

4.    In the section labeled Export, click the Export to Ant file button.

5.    An Ant file named exported_build.xml is generated and placed in the application's root directory, e.g., BEA_HOME/weblogic81/samples/workshop/SamplesApp/exported_build.xml.

The generated Ant file contains two tasks by default: "build" and "clean". When calling the build file from the command line, use the -f flag to name the file exported_build.xml:

    C:\bea\weblogic81\samples\workshop\SamplesApp>ant -f exported_build.xml build

To build selected projects with the application, modify the <build> element within the exported_build.xml file. By adding the attribute project="Schemas", only the Schemas project will be build:

  <target name="build">

    <!-- Builds the full application creating an ear at the specified location.

         The server classpath parameter is used, but may be omitted if the server home directory

         configured in Workshop is accessible. -->

    <wlwBuild work="${app.dir}/${work.file}" serverclasspath="${server.classpath}">

       <build outputdir="${output.dir}" outputfilename="${output.file}" project="Schemas"/>

    </wlwBuild>

  </target>

See the documentation within the exported_build.xml file for more information about specifying output directories, output file names, etc.

You can also export an Ant build.xml file for building an individual project in much the same way as you do for the application.

To auto-generate an Ant build.xml file for a project

1.    Open the target application in WebLogic Workshop.

2.    From the Tools menu, select Project properties, then the target project name.

3.    In the Project Properties dialog, from the left-side navigation panel, select the Build node.

4.    In the section labeled Build Type, click the Export to Ant file button.

5.    An Ant file named exported_build.xml is generated and placed in the project's root directory,

 

Labels:

Comments

Post a Comment

Popular posts from this blog

Java Health Center - Overview and Features

This video highlights the features available in Health Center. Health Center is a low-processor and memory usage diagnostic tool for monitoring the status of a running IBM Java Virtual Machine (JVM). Health Center provides live information and recommendations in each of the following areas: - Classes: information about classes being loaded - Environment: details of the configuration and system of the monitored application - Garbage Collection: information about the Java heap and pause times - Locking: information about contention on inflated locks - Profiling: sampling profile of Java methods including call paths
Post a Comment
Continue Reading >>>>

WebSphere MQ Interview Questions

What is MQ and what does it do? Ans. MQ stands for MESSAGE QUEUEING. WebSphere MQ allows application programs to use message queuing to participate in message-driven processing. Application programs can communicate across different platforms by using the appropriate message queuing software products. What is Message driven process? Ans . When messages arrive on a queue, they can automatically start an application using triggering. If necessary, the applications can be stopped when the message (or messages) have been processed. What are advantages of the MQ? Ans. 1. Integration. 2. Asynchrony 3. Assured Delivery 4. Scalability. How does it support the Integration? Ans. Because the MQ is independent of the Operating System you use i.e. it may be Windows, Solaris,AIX.It is independent of the protocol (i.e. TCP/IP, LU6.2, SNA, NetBIOS, UDP).It is not required that both the sender and receiver should be running on the same platform What is Asynchrony? Ans. With messag...
11 comments
Continue Reading >>>>

Java Garbage Collection

Explain Garbage collection mechanism in Java? Garbage collection is one of the most important features of Java. The purpose of garbage collection is to identify and discard objects that are no longer needed by a program so that their resources can be reclaimed and reused. A Java object is subject to garbage collection when it becomes unreachable to the program in which it is used. Garbage collection is also called automatic memory management as JVM automatically removes the unused variables/objects (value is null) from the memory. Every class inherits finalize() method from java.lang.Object, the finalize() method is called by garbage collector when it determines no more references to the object exists. In Java, it is good idea to explicitly assign null into a variable when no more in use. In Java on calling System.gc() and Runtime.gc(), JVM tries to recycle the unused objects, but there is no guarantee when all the objects will garbage collected. Garbage collection is an automatic pro...
Post a Comment
Continue Reading >>>>