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 or cluster. Application client files can be installed in a WebSphere® Application Server configuration but cannot be run on a server.
Option | Method | Modules | Comments | Starting after install |
---|---|---|---|---|
Administrative console install wizard See topics on installing enterprise application files with the console. |
Click | in the console navigation tree and follow instructions in the wizard.Files for all of the following modules:
|
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 in the console navigation tree. |
Monitored directory | Add an EAR file or module to a monitoredDeployableApps
subdirectory of an application server or deployment manager profile. For base (stand-alone) application servers, the monitored directory is the monitoredDeployableApps/ servers/server_name directory of the application server profile. For deployment managers, a deployment manager
profile has the following monitored directories:
|
Files for all of the following modules:
Use this option for drag and drop deployment of Java EE 5.0 and later modules. |
Provides one of the easier ways to install applications. You cannot specify bindings during deployment. For applications that require changes to the bindings, install the application using the administrative console install wizard, application properties files, or wsadmin scripts. Monitored directory deployment differs from rapid deployment tools in several ways:
|
After application or module installation or update, the product starts the
application or module automatically. For installations on a deployment manager monitored directory, the product does not start an application or module automatically if the node agent or server is not running. |
Application properties files | Create a properties file that specifies to install or update application
files. Then, run the wsadmin applyConfigProperties command in any of the
following ways:
|
Files for all of the following modules:
|
For information on deploying applications using properties files, see the
following topics:
|
After application or module installation or update, the product starts the
application or module automatically. For installations on a deployment manager monitored directory, the product does not start an application or module automatically if the node agent or server is not running. |
wsadmin scripts | Invoke AdminApp object install commands in a script or at a command prompt. | Files for all of the following modules:
|
For an overview of wsadmin, see Getting started with scripting. | 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:
|
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. |
|
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:
|
J2EE modules at the J2EE 1.3 or 1.4 specification levels, including EAR files
and the following stand-alone modules:
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:
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:
|
|
Call the Java EE DeploymentManager (JSR-88) start method in a program to start the deployed modules when the module's running environment initializes. |