Deploy WebSphere Application Server Community Edition applications
From the administrative console, we can install managed WebSphere Application Server Community Edition Version 2.0 applications to servers and dynamic clusters.
- Create a WAS Community Edition deployment target by creating a complete life cycle WebSphere Application Server Community Edition server or dynamic cluster. Verify that we can start the deployment targets. For more information read about creating complete lifecycle WebSphere Application Server Community Edition servers and dynamic clusters.
- Prepare the WAS Community Edition application to be deployed. The application consists of an archive file and an external deployment plan, which are both deployed to the WAS 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 WAS Community Edition console only for functions that are not available from the administrative console.
Deploy a WAS Community Edition application to experience the same qualities of service that Intelligent Management provides for Java EE 5 applications and PHP applications.
- Open the WAS Community Edition application wizard. In the administrative console, click Applications > Install new middleware application. 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. We 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 WAS 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.
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.
Related tasks
Deploy applications with defined service levels Define a service policy Deploy and managing application editions with Intelligent Management Create complete life-cycle WebSphere Application Server Community Edition servers and dynamic clusters
Intelligent Management: middleware application administrative tasks Intelligent Management: middleware server creation administrative tasks