WebSphere Application Server Network Deployment, Version 6.0.x   Operating Systems: AIX, HP-UX, Linux, Solaris, Windows
             [TIP: Focusing the table of contents and search results]

Configuring Performance Manager Infrastructure using scripting

You can use scripting to configure a Performance Manager Infrastructure service.

Before you begin

Before starting this task, the wsadmin tool must be running. See the Starting the wsadmin scripting client article for more information.

About this task

Use the following steps to configure the Performance Manager Infrastructure (PMI) service for an application server:

Procedure

  1. Identify the application server and assign it to the s1 variable, for example:
    • Using Jacl:
      set s1 [$AdminConfig getid /Cell:mycell/Node:mynode/Server:server1/]
    • Using Jython:
      s1 = AdminConfig.getid('Cell:mycell/Node:mynode/Server:server1/') 
    where:
    set is a Jacl command
    s1 is a variable name
    $ is a Jacl operator for substituting a variable name with its value
    AdminConfig is an object representing the WebSphere Application Server configuration
    getid is an AdminConfig command
    Cell is an attribute
    mycell is the value of the Cell attribute
    Node is an attribute
    mynode is the value of the Node attribute
    Server is an attribute
    server1 is the value of the Server attribute
    Example output:
    server1(cells/mycell/nodes/mynode/servers/server1|server.xml#Server_1)
  2. Identify the PMI service that belongs to the server and assign it to the pmi variable, for example:
    • Using Jacl:
      set pmi [$AdminConfig list PMIService $s1]
    • Using Jython:
      pmi = AdminConfig.list('PMIService', s1)
      print pmi 
    where:
    set is a Jacl command
    pmi is a variable name
    $ is a Jacl operator for substituting a variable name with its value
    AdminConfig is an object representing the WebSphere Application Server configuration
    list is an AdminConfig command
    PMIService is an AdminConfig object
    s1 evaluates to the ID of the application server specified in step number 1
    Example output:
    (cells/mycell/nodes/mynode/servers/server1|server.xml#PMIService_1)
  3. Modify the attributes, for example:
    • Using Jacl:
      $AdminConfig modify $pmi {{enable true} {statisticSet ALL}}
    • Using Jython:
      AdminConfig.modify(pmi, [['enable', 'true'], ['statisticSet','ALL']]
    This example enables PMI service and sets the specification levels for all of components in the server. The following are the valid specification levels for the components:
    NONE No statistics are enabled.
    BASIC Statistics specified in J2EE 1.4, as well as top statistics like CPU usage and live HTTP sessions are enabled. This set is enabled out-of-the-box and provides basic performance data about runtime and application components.
    EXTENDED Basic set plus key statistics from various WebSphere Application Server components like WLM and Dynamic caching are enabled. This set provides detailed performance data about various runtime and application components.
    ALL All statistics are enabled.
    CUSTOM Enable or disable statistics selectively.
  4. Save the configuration changes. See the Saving configuration changes with the wsadmin tool article for more information.
  5. In a network deployment environment only, synchronize the node. See the Synchronizing nodes with the wsadmin tool article for more information.



Related tasks
Using the AdminConfig object for scripted administration
Enabling PMI using the wsadmin tool
Related reference
Commands for the AdminConfig object
Task topic    

Terms of Use | Feedback

Last updated: Mar 8, 2007 8:14:28 PM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/txml_pmi.html

© Copyright IBM Corporation 2004, 2006. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)