WebSphere Extended Deployment, Version 6.0.x
             Operating Systems: AIX, HP-UX, Linux, Solaris, Windows, z/OS


Enabling the on demand router to work with IBM Enterprise Workload Manager

Use this task to enable IBM® Enterprise Workload Manager™ to monitor WebSphere® Extended Deployment.

Before you begin

To perform this task, you must own IBM Enterprise Workload Manager software and have it installed. See the IBM Enterprise Workload Manager Information Center for installation instructions.

About this task

By performing this task, the on demand router (ODR) makes Application Response Measurement (ARM) calls to report response times to IBM Enterprise Workload Manager™. IBM Enterprise Workload Manager can use the response time information to monitor the environment both inside and outside of the WebSphere Extended Deployment domain. See WebSphere Extended Deployment and IBM Enterprise Workload Manager for more information.

Procedure

  1. Install WebSphere Extended Deployment. See Installing and configuring the product for more information.
  2. Configure service and transaction classes in IBM Enterprise Workload Manager. See the Enterprise Workload Manager Information Center for more information. The service and transaction classes that you configure in IBM Enterprise Workload Manager override any service classes that are configured in WebSphere Extended Deployment.
  3. Configure IBM Enterprise Workload Manager to manage WebSphere Extended Deployment. After you complete this step, any service policies that are configured in WebSphere Extended Deployment are not valid. IBM Enterprise Workload Manager has its own configured service and transaction classes.
  4. Copy the ARM libraries from IBM Enterprise Workload Manager to the WebSphere Extended Deployment configuration. Include the ARM libraries from IBM Enterprise Workload Manager in the install_root/bin directory. Remember the name of this class so that you can supply the information in the administrative console. Alternatively, you can add two custom properties to the application server or ODR Java™ virtual machine (JVM). First, define the java.library.path custom property and set its value to the IBM Enterprise Workload Manager library path, for example c:\Program Files\IBM\VE2\EWLMMS\classes\ms. Next, create the ws.ext.dirs custom property and set its value to the folder that contains the ARM libraries that are provided by IBM Enterprise Workload Manager, for example, c:\Program Files\IBM\VE2\EWLMMS\classes\ARM.
  5. Enable ARM reporting. Read the Getting performance data from request metrics topic in the WebSphere Application Server Information Center for more information. On the request metrics administrative console page, use the following settings:
    • Select the appropriate application component, such as servlets or Web services, that needs to report ARM statistics.
    • Defining the trace level is optional.
    • Enter the name of the IBM Enterprise Workload Manager ARM factory in the ARM transaction factory implementation class name. The transaction class factory name for IBM Enterprise Workload Manager is com.ibm.wlm.arm40SDK.transaction.Arm40TransactionFactory.
  6. Enable ARM reporting on your other tiers and applications, such as IBM DB2®, IBM HTTP Server, and also for the various components running on WebSphere Application Server. You can enable ARM instrumentation in specific WebSphere Application Server components by selecting the appropriate components. Read the Getting performance data from request metrics topic in the WebSphere Application Server Information Center for more information. See the product documentation for your specific tier applications regarding more information on enabling ARM reporting. Any tiers that send requests to the WebSphere Extended Deployment tier must be ARM enabled to facilitate the interaction between IBM Enterprise Workload Manager and WebSphere Extended Deployment. Any tiers that receive requests from the WebSphere Extended Deployment tier do not need to have ARM enabled, however, enabling ARM on these tiers is strongly encouraged.
  7. To enable WebSphere Application Server and WebSphere Extended Deployment with IBM Enterprise Workload Manager, you must manually update the WebSphere Application Server server.policy files. You must update the server.policy file for all application servers and on demand routers. See the server.policy file permissions topic in the WebSphere Application Server Information Center for more information about server.policy files.
  8. Restart all applications and servers that IBM Enterprise Workload Manager is now monitoring.

Results

After you complete this task, the on demand routers in the WebSphere Extended Deployment infrastructure begin to make ARM calls to report response times on requests, so IBM Enterprise Workload Manager can monitor the WebSphere Extended Deployment environment.



Related concepts
WebSphere Extended Deployment and IBM Enterprise Workload Manager
Related tasks
Configuring the health controller
Configuring the autonomic request flow manager
Getting performance data from request metrics
Related reference
Related information
IBM Enterprise Workload Manager Information Center
Task topic    

Terms of Use | Feedback

Last updated: Oct 16, 2009 11:07:34 AM EDT
http://publib.boulder.ibm.com/infocenter/wxdinfo/v6r0/index.jsp?topic=/com.ibm.websphere.xd.doc/info/odoe_task/todrenablearm.html