|This section describes how to generate and deploy the
Enterprise Archive (EAR) file in the WebSphere Application Server (WAS), by
using the WASSetupUI command
to start the Deployment Wizard for V5 Web Applications. You will be presented with two
This scenario does NOT cover all possible deployment scenarios on a WAS ND (Network Deployment) cluster of machines. However, the generated JACL (defined later) can be used if all machines in the cluster have same image (OS, file systems, etc.). WAS ND lets you clone the installation of a single WAS node to all the clusters.
A Few Definitions
WAS is an acronym for WebSphere Application Server, the IBM server infrastructure used to run WebTop applications.
EAR is the short name for Enterprise Archive file. An EAR file contains a subset of the information required to deploy a WebTop application in WebSphere Application server: the application root URI, security on the URL handled by the application, persistency details, path to the ENOVIA installation directory.
WebTop: WebTop applications are applications which are targeted to be used from a web browser, like Microsoft Internet Explorer or Mozilla. WebTop applications can be deployed on WAS or as Microsoft ASP.NET. The WebTop applications involved here is the ENOVIA VPM Lifecycle Navigator.
|For this task, you will need the following:
|If the ENOVIA server host is different from the Web Application server host, you must decide whether you prefer to perform an ENOVIA installation on both machines or to mount the installation from the ENOVIA server host to the Web Application server host.|
Instructions for Manual Deployment
If the manual deployment option is chosen instead of automatic deployment, there are two cases:
Fully Manual Deployment
In this case, after running the WASSetupUI command, you must perform the following configuration on WAS (either through the WebSphere Admin Console or using wsadmin commands):
1. Declare a DB2 or ORACLE (database brand must be consistent with the one chosen in WASSetupUI) Data Source, with the following constraints:
2. You must choose a server (in WebSphere terminology: a server means a JVM -Java Virtual Machine) and setup the following for this server.
The following environment variables are set for the chosen server:
You can now run Version 5 Webtop applications on SUN Microsystems machines with a SPARC processor and running Solaris 8 upwards.
3. The EAR file generated by WASSetupUI must be installed on the chosen server, without modification on the Role mapping.
4. WAS must be restarted after all these changes to run the web applications.
Manual Deployment based on the JACL property file generated by WASSetupUI
The last deployment option, which is to select Manual deployment and Generate JACL property file is meant for advanced users who master the JACL scripting language in WAS. Using the JACL scripts which are part of ENOVIA runtime and the generate JACL property file, advanced users can customize the deployment to their specific needs.
For example, if the machine on which the WASSetupUI command is run is not the same as the targeted machine for WAS, advanced users can copy the JACL and property files and run the deployment on the WAS machine using the wsadmin command. The best way to take advantage of this is to run the WASSetupUI command in automatic mode at least once, and see how the wsadmin commands are launched in the log text area (this can be copy-pasted to a text editor for later inspection). On the remote machine, some paths will probably need to be modified in order to successfully run wsadmin with real file locations, as well as some properties in the JACL file (call, node and server name must match the targeted WAS real names).
Another usage pattern is to copy the JACL files and edit them in order to implement some specific deployment topology not externalized in the JACL property file.
Using the More Button
Click the More button to display the following information:
In automatic mode, the software assumes that the name of the WAS profile is the default profile (the profile field is grayed out because WAS was not installed on the machine on which the screen shot was made), the WAS cell and WAS node are the same as the name of the machine hosting the WAS, and that the server name is server1. You set the profile, cell, node and server names when installing WAS. If the default names are not correct, reset the correct names using the combo box showing relevant choices (in automatic mode), before clicking the Finish button.
On UNIX, hitting the "More" button lets you choose the X11 display setting (machine:1.0 for example) which is interesting when deploying on a machine without X11 (for example, big servers) or to use the Virtual Frame Buffer:
Note that the WAS profile is the default profile: it is displayed because WAS was installed on the UNIX machine on which the screen shot was made.
Generate response file
The Generate response file option generates the response file corresponding to all options selected in an interactive WASSetupUI session until the Finish button is clicked. The response file can be used by people in charge of web application deployment as a template for silent mode (i.e., non interactive) deployment.
Executing the Command
Once you have made your choice, click the Finish button now. The Output tab is then displayed containing the execution results.
If you selected the Automatic Deployment option, the application will be deployed automatically in the WebSphere Application Server. To start the application, refer to Launching the Web Application.
|Note: if the WebSphere Application Server was still running when you launched the command, restart the server once the command has been executed.|
There are several options for the WASSetupUI command
Using the Security Tab
The Security tab is designed to secure your WebSphere Application Server by allowing you to enter the information you usually enter using the WebSphere Administrative console. This means that your WebSphere Application Server can be secured and your Enterprise Archive file can be deployed at the same time.
For full details about how to do so, refer to Securing the WebSphere Application Server.