Installing J2EE application files

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

Before you begin

Before you can install your J2EE 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 your application files can be installed to your deployment targets.

About this task

You can install the following modules on a server:

Application client files can be installed in a WebSphere® Application Server 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. WebSphere Application Server 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.

Avoid trouble Avoid trouble: [Updated in July 2011]
  • You must use either the administrative console or wsadmin scripting to synchronization a node. Of these two options, using the administrative console is the best way to perform this operation. The Nodes panel in the administrative 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.
[Updated in July 2011]
jul2011
gotcha

Next, test the application. For example, point a Web browser at the URL for a deployed application (typically http://hostname:9060/Web_module_name, where hostname is 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.




In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 12:02:36 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-zos&topic=trun_app_install
File name: trun_app_install.html