Skip to main content

How Do I: Use a Custom Ant Build for an Application in Weblogic?


WebLogic Workshop uses a standard Ant build process for all applications. You can create a custom Ant build file for an application that extends the standard build process or uses different build targets altogether. If you want to extend or modify the standard build process, you should first export the standard application build file and begin by modifying that file.
To Export the Standard Application Build File
1.    Choose Tools-->Application Properties to display the Application Properties dialog.
2.    In the left-hand pane, select Build.
3.    In the Build Type pane, click Export to Ant File. A dialog appears informing that the exported_build.xml file has been stored in the root of the application folder. Click OK.
The exported Ant file contains a set of standard tasks and targets for managing the build for your application.
Note the class workshop.core.WlwBuildTask called by the "wlwBuild" task is the same class called by the command line tool wlwBuild.cmd.
 <taskdef name="wlwBuild" classname="workshop.core.WlwBuildTask"
            classpath="${weblogic.home}/workshop/wlw-ide.jar"/>
The most important target in the Ant file is the "build" target.
<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}"/>
    </wlwBuild>
  </target>
Note that the following parameters are available for the "build" target:
project: String. Name of a specific project within the application to build. If omitted, the entire application will be built.
outputdir: String file path. Directory where build output file(s) will be placed. Defaults to application directory. May not be applicable for some types of project build.
outputfilename: String file path. Filename to use for output archive. Defaults to appname.ear. May not be applicable for some types of project build.
nodebug: Boolean value. Turns debugging information on or off. If no value is specified, the value is set to false.
noear: Boolean value. Specifies whether an EAR file should be generated for the application build. If no value is specified, the value is set to false. Not applicable for a project build.
To Create a Custom Ant Build File
You can use the standard exported build task and add additional build (sub)targets, or you can create a new ant file. To add a new task, you must use the <taskdef> element:
<taskdef name="myTask" classname="myTask" classpath="AllMyClass.jar"/>
Use the classpath attribute to specify the physical location of the JAR file as shown above, or you can specify the location when you change the project properties to use the custom build file as is described next.
You can also create a custom build process for an individual project within your application. Again, you should begin by exporting the standard build file and modifying that file.
To Export the Standard Project Build File
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, e.g., BEA_HOME/weblogic81/samples/workshop/SamplesApp/WebServicesexported_build.xml.
To Use the Project Build File
1.    Choose Tools-->Project Properties--><projectname> to display the Project Properties dialog.
2.    In the left-hand pane, select Build.
3.    In the Ant Settings area, click Browse, navigate to the new build file and click Open.
4.    If your build file contains a new task definition without a classpath attribute, click Add JAR to specify the location of the Ant task. Navigate and select the file, then click Select JAR.
5.    In the Build Type area, select Use Ant Build.
6.    From the Build Target drop-down list, select the build target.
7.    Click OK.
The Ant window will now appear in WebLogic Workshop, listing the various targets. From this window you can run a target by double-clicking it.

Comments

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

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...

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...