From the administrative console, you can install managed WebSphere® Application Server
Community Edition Version 2.0 applications to servers and dynamic
clusters.
Before you begin
已淘汰的特性: Assisted and Complete Lifecycle servers have been deprecated in
WebSphere Application Server Version 9.0. Migrate WebSphere Liberty servers to a
Liberty Collective configuration. There is no recommended migration action for other server
types.
depfeat
- Create a WebSphere Application
Server Community Edition deployment target by creating a complete
life cycle WebSphere Application
Server Community Edition server or dynamic cluster. Verify that you
can start the deployment targets. For more information read about creating complete lifecycle WebSphere Application Server Community Edition servers and
dynamic clusters.
- Prepare your WebSphere Application
Server Community Edition application
to be deployed. The application consists of an archive file and an
external deployment plan, which are both deployed to the WebSphere Application Server Community
Edition server.
Important: With managed WebSphere Application
Server Community Edition applications, you must
complete all deployment actions from within the administrative console
only. Use the WebSphere Application
Server Community Edition console
only for functions that are not available from the administrative
console.
About this task
Deploy a
WebSphere Application
Server Community Edition application
to experience the same qualities of service that
智慧型管理 provides for Java™ Platform, Enterprise Edition
5 (Java EE 5) applications and
PHP applications.
Procedure
- Open the WebSphere Application
Server Community Edition application
wizard. In the administrative console, click . Select WebSphere
Application Server Community Edition as the application
type, and click Next.
- Specify either the local or remote location of the application
archive file and external deployment plan, and click Next.
- Specify the name, edition, and edition description of the
application. The application name must be unique among
all of the applications that are deployed in the cell, including applications
that are other types, such as Java EE
5 or unmanaged web applications.
- Select the servers and clusters on which the application
runs by selecting the deployment targets. You can filter
the list of deployment targets by only clusters, only servers, or
by entering a name. Click Add or Remove to
specify which servers and clusters run the application.
- Specify the location of the virtual host for the web modules.
- Review the confirmation details of the WebSphere Application
Server Community Edition application, and save
the changes.
- Start the application. The application displays
as started in the administrative console when the middleware server
on which the application is deployed starts. To start middleware servers
from the administrative console, read about configuring middleware
server operations.
Attention: If the server or node agent
stops, the application might still show as started or partially deployed
in the administrative console.
Results
Your
WebSphere Application
Server Community Edition application
runs on the defined deployment targets.
What to do next
Define service policies and routing policies for the application.
All application edition manager functions are available.