The automatic installation project automates the installation,
modification, and uninstallation of J2EE compliant applications (EAR files)
or modules (WAR, JAR, or RAR files) on a server. Automatic application installation
releases you from the complexity of administrating your application on a server.
The initial configuration of the automatic installation project
in your workspace creates an automatic installation project. After you have
configured the workspace to contain an automatic installation project, you
can launch a rapid deployment session. Launching a rapid deployment session
indicates that you want the project to start listening for your EAR or module
files. If you place an EAR file in the automatic application installation
project, the EAR file is automatically deployed to the server. If you delete
EAR files from the project, the application is uninstalled from the server.
If you place a new copy of the same EAR file in the automatic application
installation project, the application is either reinstalled or the server
restarts to pick up the modifications. If you place module files in the project,
a supporting EAR wrapper is generated, and then that EAR file is deployed
to the server.
Restriction: You
can use the rapid deployment tools for packaging applications at J2EE 1.3
or 1.4 specification-levels. However, the rapid deployment tools do not support
Java EE 5.0 nor J2EE 1.2 specification-level.
Prerequisite
To configure a new automatic installation workspace:
- From the command prompt, change to the x:/profiles/<profileName>/bin
directory, where x is the directory where WebSphere Application
Server is installed.
- Type the following at the prompt:
WRD-config.bat
-project "project_name" -style "autoappinstall"
WRD-config.sh
-project "project_name" -style "autoappinstall"
- In the Parameter Configuration Settings dialog
box, specify the value for one or more of the following settings:
Option |
Description |
Enter the server name* (server1) |
The
name of the server process you want to publish your application. For example,
server1. For WebSphere Application
Server Network Deployment, the server name is in the form <cell
name>/<node name>/<server name>.
To publish to a cluster, the server name is in the form <cell
name>/<cluster name> |
Enter the server JMX host name* (localhost) |
The
host name of the machine containing the server you want to make a connection
to. For example, localhost. For WebSphere Application Server Network
Deployment, type the host name of the Network Deployment Manager. |
Enter the server JMX port number* (8880) |
This
is a required field. The server administrative port number, also known as
the Simple Object Access Protocal (SOAP) connector port. This port is used
for making JMX connections with the server. For example, 8880. For WebSphere Application
Server Network Deployment, type the SOAP port number of the Network Deployment
Manager, default is 8879. |
Enter your server username |
(Optional) If
security is enabled, specify the user name for current active authentication
settings defined in the server configuration. |
Enter your server password |
(Optional) If
security is enabled, specify the password for current active authentication
settings defined in the server configuration. |
The automatic installation project is created with the naming convention project_name,
where project_name is the string value provided for the -project parameter.