Ways to install enterprise applications or modules

The product provides several ways to install Java™ Platform, Enterprise Edition (Java EE) application files.

Installable files include enterprise archive (EAR), enterprise bean (EJB), Web archive (WAR), Session Initiation Protocol (SIP) module (SAR), resource adapter (connector or RAR), and application client modules. They can be installed on a server or cluster. Application client files can be installed in a WebSphere® Application Server configuration but cannot be run on a server.

Table 1. Ways to install application files. Deploy an application or module using the administrative console, wsadmin, programming, or deployment tools.
Option Method Modules Comments Starting after install
Administrative console install wizard

See topics on installing enterprise application files with the console.

Click Applications > New application > New Enterprise Application in the console navigation tree and follow instructions in the wizard. Files for all of the following modules:
  • EAR
  • EJB
  • WAR
  • SAR
  • RAR
  • Application client
Provides one of the easier ways to install application files.

For applications that do not require changes to the default bindings, after you specify the application file, expand Choose to generate default bindings and mappings, select Generate default bindings, click the Summary step, and then click Finish.

Click Start on the Enterprise applications page accessed by clicking Applications > Application Types > WebSphere enterprise applications in the console navigation tree.
wsadmin scripts Invoke AdminApp object install commands in a script or at a command prompt. Files for all of the following modules:
  • EAR
  • EJB
  • WAR
  • SAR
  • RAR
  • Application client
For an overview of wsadmin, see Getting started with scripting.

• Invoke the AdminApp startApplication command.

• Invoke the startApplication method on an ApplicationManager MBean using AdminControl.

Job manager runs wsadmin scripts Invoke AdminTask.submitJob -jobType installApplication command in a script or at a command prompt. Files for all of the following modules:
  • EAR
  • EJB
  • WAR
  • SAR
  • RAR
  • Application client
Use the job manager to submit a job that installs the application. You can also submit jobs that start and stop the application at designated times.

• Invoke the AdminTask.submitJob -jobType startApplication command.

• Invoke the AdminApp startApplication command.

• Invoke the startApplication method on an ApplicationManager MBean using AdminControl.

Java application programming interfaces Install programs by completing the steps in Installing an application through programming. All EAR files Use MBeans to install the application. For an overview of Java MBean programming, see Managing applications through programming. Start the application by calling the startApplication method on a proxy.
Rapid deployment tools Briefly, do the following:

1. Update your J2EE application files.

2. Set up the rapid deployment environment.

3. Create a free-form project.

4. Launch a rapid deployment session.

5. Drop your updated application files into the free-form project.

J2EE modules at the J2EE 1.3 or 1.4 specification levels, including EAR files and the following stand-alone modules:
  • EJB
  • WAR
  • SAR
  • RAR
  • Application client

The rapid deployment tools do not support the Java EE 5.0 or J2EE 1.2 specification levels.

Rapid deployment tools offer the following advantages:

• You do not need to assemble your J2EE application files prior to deployment.

• You do not need to use other installation tools mentioned in this table to deploy the files.

Use any of the above options to start the application. Clicking Start on the Enterprise applications page is the easiest option.
Java programs Code programs that use Java EE DeploymentManager (JSR-88) methods. All Java EE modules, including EAR files and the following stand-alone modules:
  • EJB
  • WAR
  • SAR
  • RAR
  • Application client

• Uses Java EE Application Deployment Specification (JSR-88).

• Can customize modules using DConfigBeans.

Call the Java EE DeploymentManager (JSR-88) start method in a program to start the deployed modules when the module's running environment initializes.
For transitioning users: In the Version 6.1 Feature Pack for Web services and Feature Pack for EJB 3.0, the default is to scan pre-Java EE 5 Web application modules to identify JAX-WS services and to scan pre-Java EE 5 Web application modules and EJB modules for service clients during application installation. For Version 7.0, the default is not to scan pre-Java EE 5 modules for annotations during application installation or server startup. To preserve backward compatibility with either or both feature packs, you can define Java virtual machine custom properties on servers to request scanning during application installation and server startup. trns



Related concepts
Application bindings
EJB 3.0 module packaging overview
Related tasks
Installing enterprise application files with the console
Getting started with wsadmin scripting
Installing enterprise applications using wsadmin scripting
Starting applications using wsadmin scripting
Running administrative jobs using wsadmin scripting
Administrative job types using wsadmin scripting
Administering jobs in a flexible management environment using wsadmin scripting
Installing an application through programming
Starting an application through programming
Managing applications through programming
Installing enterprise modules with JSR-88
Customizing modules using DConfigBeans
Related reference
EJB 3.0 metadata annotations
JAX-WS annotations
launchClient tool
Related information
Rapid deployment of J2EE applications
Concept topic    

Terms of Use | Feedback

Last updated: Oct 21, 2010 10:04:34 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-mp&topic=crun_app_install
File name: crun_app_install.html