WAS v8.5 > Deploy applications > Deploy enterprise applications

Install enterprise application files

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

Before we can install your Java EE application files on an application server, you must assemble modules as needed.

Also, before you install the files, configure the target application server. As part of configuring the server, determine whether the application files can be installed to your deployment targets. We can install the following enterprise modules on a server:

• Enterprise archive (EAR)

• Enterprise bean (EJB)
• Web archive (WAR)
• SIP module (SAR)
• Resource adapter (connector or RAR)
• Application client modules

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

To install your files.

1. Determine which method to use to install the application files. WAS v8.5 provides several ways to install modules.
2. Install the application files using
   • Administrative console
   • Drag and drop to a monitored directory
   • wsadmin scripts
   • Java administrative programs that use JMX APIs
   • Java programs that define a Java EE DeploymentManager object in accordance with Java EE Application Deployment specification (JSR-88)

3. Start the deployed application files using
   • Administrative console
   • wsadmin startApplication
   • Java programs that use ApplicationManager or AppManagement MBeans
   • Java programs that define a Java EE DeploymentManager object in accordance with Java EE Application Deployment specification (JSR-88)

Save the changes to your administrative configuration.

• You must use either the dmgr console or wsadmin scripting to synchronization a node. Of these two options, using the dmgr console is the best way to perform this operation. The Nodes panel in the dmgr console includes the Synchronize operation.

  If you need to use wsadmin scripting to synchronize a node, use the NodeSync mbean's sync() command.

• Do not restart the node agent as part of the synchronize node process. Administration operations, such as node synchronization for application deployment, or updates that take place while the node agent is starting, that are initiated through the node agent, and affect the application servers, fail until the node agent has a chance to discover the application servers.

Next, test the application. For example, point a web browser at the URL for a deployed application. Typically, the URL is http://hostname:9060/web_module_name, where hostname is your valid web server and 9060 is the default port number. Examine the performance of the application. If the application does not perform as desired, edit the application configuration, then save and test it again.

If the application contains many classes with annotations and takes a long time to deploy, we can reduce annotation searches to speed up deployment. See the topic on reducing annotation searches during application deployment.

Subtopics

• Installable enterprise module versions
  The contents of a Java EE module affect whether we can install the module on a deployment target. A deployment target is a server on a WAS product.
• Ways to install enterprise applications or modules
  WAS v8.5 provides several ways to install Java EE application files.
• Install enterprise modules with JSR-88
  We can install Java EE modules on an application server provided by a WAS product using the Java EE Application Deployment API specification (JSR-88).
• Customize modules using DConfigBeans
  We can configure Java EE applications or stand-alone modules during deployment using the DConfigBean class in the Java EE Application Deployment API specification (JSR-88).
• Installable enterprise module versions
  The contents of a Java EE module affect whether we can install the module on a deployment target. A deployment target is a server on a WAS product.
• Ways to install enterprise applications or modules
  WAS v8.5 provides several ways to install Java EE application files.

Related

Assemble applications
Install enterprise application files with the console
Example: Installing an EAR file using the default bindings
Example: Installing a web services sample with the console
Install enterprise application files by adding them to a monitored directory
Install enterprise application files by adding properties files to a monitored directory
Use application properties files to install, update, and delete enterprise application files
Start or stop enterprise applications
Configure enterprise application files
Deploy enterprise applications
Install enterprise applications using wsadmin.sh
Start applications using wsadmin.sh
Use administrative programs (JMX)
Reducing annotation searches during application deployment
Troubleshooting deployment

+

Search Tips   |   Advanced Search