Install J2EE application files

 

+

Search Tips   |   Advanced Search

 

Overview

As part of deploying an application, you install application files on a server configured to hold installable modules.

Before you can install your J2EE application files on an appserver, assemble modules as needed.

Also, before you install the files, configure the target appserver. As part of configuring the server, determine whether your application files can be installed to your deployment targets.

You can install the following modules on a server:

Application client files can be installed in a WAS configuration but cannot be run on a server.

Complete the following steps to install your files.

 

Procedure

  1. Determine which method to use to install your application files. WAS provides several ways to install modules.

  2. Install the application files using

  3. Start the deployed application files using

    • Administrative console

    • wsadmin startApplication

    • Java programs that use ApplicationManager or AppManagement MBeans

    • Java programs that define a J2EE DeploymentManager object in accordance with J2EE Deployment API Specification (JSR-88)

 

What to do next

Save the changes to your administrative configuration.

When saving the configuration, synchronize the configuration with the nodes where the application is expected to run.

Next, test the application. For example, point a Web browser at the URL for a deployed application (typically your valid Web server and 9060 is the default port number) and examine the performance of the application. If the application does not perform as desired, edit the application configuration, then save and test it again.



Installable J2EE module versions
Ways to install applications or modules
Install application files with the console
Example: Install an EAR file using the default bindings
Install J2EE modules with JSR-88
Customize modules using DConfigBeans

 

Related tasks

Deploy J2EE applications
Install applications with the wsadmin tool
Start applications with scripting
Use administrative programs (JMX)
Troubleshoot deployment