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.

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

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

  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, 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, we 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 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.

    • 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.

      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


Subtopics


Related concepts

  • Operational policies


    Related tasks

  • Set up Intelligent Management for dynamic operations
  • Deploy enterprise applications
  • Deploy PHP applications
  • Deploy unmanaged Web applications
  • Deploy WebSphere Application Server Community Edition applications
  • Define a service policy
  • Create and manage reports
  • Configure health management
  • Deploy and managing 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