div.collapsecontent{display:block;}

Express (Distributed operating systems), v8.0 > Develop and deploying applications > Rapid deployment of J2EE applications > Automatically installing applications on WAS v6.0 or later


Create an automatic installation project in your workspace

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 administering the application on a server.


About this task

The initial configuration of the automatic installation project in your workspace creates an automatic installation project. After we 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: We 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 (or later) nor J2EE 1.2 specification-level. For tools support of deploying Java EE 5 and later modules, you can use the monitored directory starting in WAS V8.0 release. For more details about the monitored directory, see Ways to install enterprise applications or modules and Installing enterprise application files by adding them to a monitored directory topics. Prerequisite


Procedure

  1. From the command prompt, change to the x:/profiles/ <profileName>/bin directory, where x is the directory where WAS is installed.

  2. Type the following at the prompt:

    • WRD-config.bat -project "project_name" -style "autoappinstall"
    • WRD-config.sh -project "project_name" -style "autoappinstall"

    
    
    
    

  3. 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 to publish the application. For example, server1. For WAS 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 WAS 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 Protocol (SOAP) connector port. This port is used for making JMX connections with the server. For example, 8880. For WAS 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.


Results

The automatic installation project is created with the naming convention project_name, where project_name is the string value provided for the -project parameter.

Previous topic: Set up a WebSphere rapid deployment environment

Next topic: Start a WebSphere rapid deployment session


Feedback

+

Search Tips   |   Advanced Search