Deploy applications with defined service levels

By deploying applications to the middleware servers and dynamic clusters and defining service policies on those applications, we can meet the performance goals for the environment.

• Create the servers and dynamic clusters for the environment, specifically the servers to which we want to deploy applications. For more information...
  • Create dynamic clusters
  • Add middleware servers to configurations

• Plan the classification and handling of traffic for the application.

Service policies provide the ability to differentiate applications according to levels of importance and target values that can be prioritized to meet specific goals.

Tasks

1. Deploy the application. Different processes are involved for the different application types:
   • PHP applications:

     We can deploy PHP applications to PHP deployment targets, including PHP servers and PHP dynamic clusters.

   • Deploy WAS Community Edition applications (deprecated)WebSphere Application Server Community Edition applications:

     We can deploy Java EE application applications and Geronimo modules with Geronimo artifacts to WAS Community Edition deployment targets, including servers and dynamic clusters.

   • Unmanaged web applications:

     Unmanaged web applications are installed and configured outside of the product environment, typically on assisted life cycle middleware servers. Configure unmanaged web applications so that we can route HTTP requests to assisted life cycle servers. By providing some basic information about the application, including context roots, virtual hosts, and servers, the ODR can route HTTP requests to these applications.

     Deprecated feature: Assisted and Complete Lifecycle servers have been deprecated in WAS v9.0. Migrate WebSphere Liberty servers to a Liberty Collective configuration. This includes PFP Hypertext Preprocessor (PHP), unmanaged web, and WebSpere Application server community edition applications. There is no recommended migration action for other server types.depfeat

   • Enterprise applications

     We can deploy enterprise applications to dynamic clusters running WAS application servers.

2. Define service levels with service policies.

   A service policy is a user-defined business goal, and correlates to transaction and work class components.

3. Classify application requests with service policy work classes. In the administrative console, click...
   Applications > All applications > application_name

   Click the Service policies tab. Work classes contain Universal Resource Identifiers (URI), Web services, EJB, or Java Message Service (JMS) patterns and conditional rules for associating requests to transaction classes. Transaction classes are then associated with service policies. See Intelligent Management: routing and service policies.

   Alternatively, we can use the workclassoperations.py script to define and modify the settings of work classes.

4. Start the application.
   • Enterprise applications: In the administrative console, click...
     Applications > Application types > WebSphere enterprise applications > application > Start

   • PHP applications: In the administrative console, click...
     Applications > All applications

     Select the PHP application to start. Choose the Start action and click Submit action. This action starts all of the PHP servers associated with this application.

     To start the servers individually, click...

     Servers > Server types > PHP servers

   • WAS Community Edition applications: The application displays as started in the administrative console when the middleware server on which the application is deployed starts.

   • Unmanaged web applications: The application displays as started when the server on which the application is deployed starts.

     If the server or node agent stops, the unmanaged web application might still show as started or partially deployed in the administrative console.

What to do next

• Use reporting to view statistics and performance of the applications, dynamic clusters, servers, and service policies.

• To achieve a healthy product environment, configure health policies which are similar to service policies, except that health policies are based on a health goal for the environment.

• To ensure positive application performance, such as applying interruption-free application updates, we can use the application edition manager to install new editions of the application.

Subtopics

• Deploy enterprise applications
  By deploying applications to dynamic clusters, requests to the application can be managed autonomically. The dynamic cluster can expand and contract with application server virtualization. By deploying applications to dynamic clusters, we enable application virtualization.

• Deploy unmanaged Web applications
  Create representations of unmanaged Web applications so that the on demand router can route requests to applications installed outside of the product environment to assisted life cycle middleware servers.

• Deploy PHP applications
  Use the various qualities of service of Intelligent Management product to manage PHP-based applications in addition to Java Platform, Enterprise Edition 5 (Java EE 5) applications.

• Deploy WAS Community Edition applications (deprecated)
  From the administrative console, we can install managed WAS Community Edition v2.0 applications to servers and dynamic clusters.

Related:

Operational policies

Set up Intelligent Management for dynamic operations

Define a service policy

Create and manage reports

Configure health management

Deploy and manage application editions with Intelligent Management

Monitor Intelligent Management operations

Create dynamic clusters

Add middleware servers to configurations

Intelligent Management: middleware application administrative tasks

Intelligent Management: routing and service policies

workclassoperations.py script