Automated building and deployment framework for WebSphere Commerce products based on Agile mode (1)

Introduction to Automatic Build and deployment framework for incremental code

Introduction to Concepts and tools

Agile and Delta Code

agile-Agile Development. In recent years, people have been widely concerned. It advocates dividing a complete software version into multiple iteration cycles. Each iteration implements a different attribute. Significant, high priority features are first implemented, and high-risk features are first implemented. The prototype of the software is developed early in the project and is refined in subsequent iterations based on this prototype.

Delta code-Delta code. In the Agile development model, developers are constantly improving and expanding their code based on the software prototype. This code is called incremental code.

The automation framework described in this article is built and deployed primarily for incremental code. Continuous integration and daily build capacity are strong enough to be an important foundation for the success of iterative development. This article describes how to implement rapid incremental code building on the RAD development platform.

WebSphere Commerce Build and Deployment Tool (WCBD)

The WebSphere Commerce build and Deployment Tool is a compilation and deployment tool that is included in the WebSphere Commerce product to support customer customization. The WCBD consists of an Ant script file and various templates. Provides a standardized and controllable automated build and deployment process for users. Users can choose the appropriate template to customize according to their own needs, and generate the exclusive script package. Users can also add scripts that they write themselves. It consists primarily of building code and deployment code, and users can customize the processes themselves. This tool provides a quick way to continuously integrate and build on a daily basis. This article will focus on the deployment features of WCBD and how to deploy user-defined resources through this feature. WCBD is mainly applied to various applications using was as a middleware. Can be used to deploy a single file, multiple files, or the overall deployment of application modules and support local and remote deployments. Users need to be configured according to their environment when they are in use. The configuration for the WCBD deployment will be covered in part 3rd of this series.

Build Utility Plugin

Build Utility is a plug-in integrated into the Rational application Development Tool (RAD) product. The expansion of the Ant scripting language enables an automated build of various applications on the IBM software development platform. The various projects developed in the work platform will be entered as build Utility. Build Utility outputs the compiled engineering files and packs them into Jar,war and EAR files according to the project type. Build Utility also adds additional special tasks to support working platform operations such as: Projectimport, Projectbuild, Workspacebuild, Ejbdeploy, and Earexport. The Ant tasks supported by the simple Eclipse platform are much richer. As with the Ant tool, you also need to enter XML-formatted build scripts to perform a variety of tasks when using the Builds Utility plug-in. The build script used for build Utility can be made up of tasks that are customized by the client, Ant itself contains tasks, and the special tasks contained in the build Utility.

Build Utility is supported on the working platform or on a command-line basis. On the work platform, the user simply clicks on the build script and then executes the run as-> Ant construct. There are two ways to use build Utility from the command line. The user can start the plug-in to execute a custom build script from the Runant.bat file in the bin directory under the RAD installation path, or through the headless to enable the Ant task Multithreading by launching the plug-in in an ant script. The following are detailed instructions for both of the above methods.

Executing build Utility under the window platform can be done in the following way. This method invokes the RunAnt in the Bin folder in the RAD installation directory, which is used to configure environment variables and invoke application Com.ibm.etools.j2ee.ant.RunAnt start build Utility.

Open the Command Line window.

Enter set Workspace=<rad_workspace root>.

Navigate to the <rad_install_root>\bin directory in the command Line window.

Run command: Runant-buildfile myscript.xml (Myscirpt.xml Custom build script for user).

The command line implementation of Headless's direct launch com.ibm.etools.j2ee.ant.RunAnt is shown in Listing 1 of the code example. This article uses the Headless method to start Built Utility by default.

Listing 1. Headless Start Build Utility

<property name= "Classpath" value= "&quot;${developement.environment.full.path} 
\plugins\ org.eclipse.equinox.launcher_1.0.101.r34x_v20081125.jar;&quot; " /> 
<exec executable= "${developement.environment.full.path}/jdk/bin/java"
        resultproperty= " ReturnCode "errorproperty=" Runanterr "
        output=" ${build.scripts.log.path}/${args}.log "> 
<arg line="- ms256m "/> <arg line="-mx1024m "/> <arg line= 
"-xj9 "/> <arg line= 
"-classpath ${ Classpath} "/> 
<arg line=" Org.eclipse.equinox.launcher.Main "/> <arg line= 
"-application Com.ibm.etools.j2ee.ant.RunAnt "/> 
<arg line="-dosgi.adaptor= Org.eclipse.core.runtime.adapter.EclipseAdaptor "/> 
<arg line="-dwtp.autotest.noninteractive=true " > 
<arg line= "-data ${workspace.full.path}"/> <arg line= 
"-buildfile ${buildfile}" 
/> <arg line= "${args}"/> 
</exec>