Deploying applications with defined service levels

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

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

   • PHP Hypertext Preprocessor (PHP) applications: You can deploy PHP applications to PHP deployment targets, including PHP servers and PHP dynamic clusters. For more information, read about deploying PHP applications.
   • WebSphere® Application Server Community Edition applications: You can deploy Java™ Platform, Enterprise Edition (Java EE) application applications and Geronimo modules with Geronimo artifacts to WebSphere Application Server Community Edition deployment targets, including servers and dynamic clusters. For more information, read about deploying WebSphere Application Server Community Edition applications.
   • 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 you 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. For more information. read about deploying unmanaged web applications.
   • Enterprise applications: You can deploy enterprise applications to dynamic clusters that are running WebSphere Application Server application servers. For more information, read about deploying enterprise applications.
2. Define service levels with service policies.
   A service policy is a user-defined business goal, and correlates to transaction and work class components. For more information, read about defining a service policy.
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, Enterprise JavaBeans (EJB), or Java Message Service (JMS) patterns and conditional rules for associating requests to transaction classes. Transaction classes are then associated with service policies. For more information, read about routing and service policies

   Alternatively, you can use the workclassoperations.py script to define and modify the settings of work classes. For more information, read about the workclassoperations.py script.

4. Start the application.
   • Enterprise applications: In the administrative console, click Applications > Application types > WebSphere enterprise applications. Select the application, and click Start.
   • PHP Hypertext Preprocessor (PHP) applications: In the administrative console, click Applications > All applications. Select the PHP application that you want to start. Choose the Start action and click Submit action. This action starts all of the PHP servers that are associated with this application. To start the servers individually, click Servers > Server types > PHP servers.
   • WebSphere Application Server 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.
     Attention: If the server or node agent stops, the unmanaged web application might still show as started or partially deployed in the administrative console.