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.
About this task
Service policies provide the ability to differentiate applications
according to levels of importance and target values that can be prioritized
to meet specific goals.
Procedure
- 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. See Deploying PHP applications for more information.
- WebSphere Application Server
Community Edition applications:
You can deploy Java 2 Platform, Enterprise Edition (J2EE) applications
and Geronimo modules with Geronimo artifacts to WebSphere Application Server
Community Edition deployment targets, including
servers and dynamic clusters. See Deploying WebSphere Application Server Community Edition applications for
more information.
- 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. See Deploying unmanaged Web applications for more information.
- Enterprise applications: You can deploy enterprise applications
to dynamic clusters that are running WebSphere Application
Server application servers. See Deploying enterprise applications for
more information.
- 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.
- 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, see Routing and service policies.
Alternatively, you
can use the workclassoperations.py script to define
and modify the settings of work classes. For more information, see workclassoperations.py script.
- Start the application.
What to do next
Use reporting to view statistics and performance
of your applications, dynamic clusters, servers, and service policies.
- To achieve a healthy product environment, configure
health policies. Health policies 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, you can use the application edition manager to
install new editions of your application.