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 application archive (WAR), Session Initiation Protocol (SIP) archive (SAR), resource adapter (connector or RAR), and application client modules. They can be installed on a server. 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 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 Java Management Extensions (JMX) 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 J2EE 1.2 or Java EE 5.0 and later specification levels. Use this option for drag and drop deployment of J2EE 1.3 or 1.4 modules. Unlike the monitored directory option, the rapid deployment tools do not support drag and drop deployment of Java EE 5.0 and later modules.

 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.

For a list of ways in which the rapid deployment tools differ from monitored directory deployment, see the monitored directory description in this table.

 Use any of the options in this table 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.
Deprecated feature: Application installation using JSR-88 was deprecated in WebSphere Application Server Version 8.0. Use another way listed in this table to deploy applications or modules.
 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.