The rapid deployment configuration tool reference

You can use the rapid deployment configuration tool (wrd-config.bat or wrd-config.sh) from a command line to configure rapid deployment projects, such as free-form or automatic installation projects. The wrd-config command is run in a non-graphical command line interface.

Requirements

.

Before using the wrd-config command you need to set up a workspace environment variable. For more information, see the related topic about setting up a rapid deployment environment. After you have set up your command line, you can use the following syntax and arguments to run the tool.

Syntax

For Windows wrd-config.bat -project <"project_name"> -style <"freeform"|"autoappinstall"> [<optional parameters>]
For UNIX wrd-config.sh -project <"project_name"> -style <"freeform"|"autoappinstall"> [<optional parameters>]

Mandatory parameters:

-project <"project_name">
The name of the rapid deployment project that you want to create. The project name needs to be unique in your workspace.
-style <"freeform"|"autoappinstall">
The deployment approach - either the free-form or automatic application installation project is used as the deployment style.

The free-form project ("freeform") allows you to create or drop in your J2EE artifacts (such as servlet source, JSP, static Web content, EJB classes or source files, Java™ class files, and all other generic files) into the free-form project. These resources are automatically placed in the appropriate location in the J2EE project structure.

The automatic installation project ("autoappinstall") creates a single project that listens for fully composed EAR or module files. If EAR files are placed inside this project, the EAR file is automatically deployed to the server. If the EAR file is deleted, then that application is uninstalled from the server. If you place WAR or EJB jar files in a automatic installation project, the rapid deployment tool generates the necessary EAR wrapper and then publishes that EAR file on the server. For RAR files, a wrapper is not created. The standalone RAR files are published to the server.

Optional parameters:

-rebuild
Cleans and rebuilds the contents of the rapid deployment project.
-configure
Opens an interactive console session to modify any available parameters.
-runtime <"was51"|"was60">
Targeting your runtime will configure which JRE library to use, based on the runtime location, and configure the project's classpath to contain the WebSphere runtime libraries. Specify as an identifier if either WebSphere Application Server v5.1 ("was51") or WebSphere Application Server v6.0 ("was60") is used as the target run-time environment for rapid deployment processing. If this parameter is not specified, the default setting is WebSphere Application Server v6.0. This parameter is only used with -runtimePath parameter.
-runtimePath <"x:\WebSphere\AppServer">
Where x:\WebSphere\AppServer is the directory where WebSphere Application Server is installed. This runtimePath parameter specify the directory path to where the target runtime is installed and is used in conjunction with -runtime parameter.
-j2eeVersion <"1.3"|"1.4">
Specifies either J2EE version 1.3 or 1.4 is used for development and deployment.
-configPath "x:\filename.xml"
The destination file path for the configuration file, where x is the temporary directory. This file persists the configuration data to an XML file, which can later be used to drive other rapid deployment configuration sessions. If this path is not specified, the default location is in the root of the rapid deployment workspace.
-configData "x:\filename.xml"
The path of an existing XML configuration file that is used to drive the configuration session. If this path is not specified, the default location of the XML configuration file is in the root of the rapid deployment workspace with the naming convention projectName_headlessconfig.xml, where projectName is the value specified in the -project parameter.
-listStyles
The available deployment styles and their descriptions.
-listServers
The available runtime server targets.
-properties
Lists the properties for a given deployment project. This parameter is only used with -project.
-buildMode
Specify to disable all console outputs. You find this useful for silent builds.
-usage
Displays the optional and required parameters for this command.

Examples of running the WRD-config command

To create a new free-form project:
WRD-config.bat -project "MyProject" -style "freeform" -runtime "was60" -runtimePath "c:\WebSphere\AppServer"
To create a new automatic application installation project:
WRD-config.bat -project "MyProject" -style "autoappinstall"
To persist configuration data to an XML file:
WRD-config.bat -project "MyProject" -style "freeform" -runtime "was60" -runtimePath "c:\WebSphere\AppServer" -configPath "c:\configData\myHeadlessConfig.xml"
To create a new rapid deployment project using an existing XML configuration file:
WRD-config.bat -configData "c:\configData\myHeadlessConfig.xml"
To clean and rebuild an existing rapid deployment project:
WRD-config.bat -project "MyProject" -rebuild
To modify available deployment parameters:
WRD-config.bat -project "MyProject" -configure
To query properties of an existing rapid deployment project:
WRD-config.bat -project "MyProject" -properties
To query available rapid deployment styles and run-time targets:
WRD-config.bat -listStyles -listServers
Related tasks
Setting up a rapid deployment environment
Feedback
(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.