Examples: Instrument local servers

 

+

Search Tips   |   Advanced Search

 

  1. Overview
  2. Instrument a local server using the GUI
  3. Instrument a Windows computer with WAS V6.1
  4. Instrument a Linux computer WAS V5.0 or later
  5. Instrument a Linux computer with WAS V6.0
  6. Instrument a Linux computer with WebLogic
  7. Windows computer with WAS V5.0 or later
  8. Instrument a Windows computer with a WebLogic
  9. What to do next
  10. Related concepts


Overview

Instrument appservers to collect response time breakdown data.

The data collection infrastructure must be installed on any computer from which to collect performance data.


Instrument a local server using the GUI

  1. Click...

      Start | Programs | IBM Software Delivery Platform | Rational Data Collection Infrastructure | Application Server Instrumenter

    The Application Server Instrumenter starts.

  2. Use the Application Server Instrumenter to instrument the server. See the examples that follow.

  3. For WebLogic servers, restart the application server.

    For WAS, the Application Server Instrumenter automatically restarts WebSphere appservers.


Instrument a Windows computer with WAS V6.1

The server is named WebSphere_Portal, installed in...

...with a profile name of wp_profile, and security enabled.

Click Add Local and enter parameters...

Click OK. It may take several minutes for instrumentation to complete.

When complete, instrumented server is listed...



Instrument a Linux computer WAS V5.0 or later

The server is named server1, installed with no security in...

Procedure...

  1. Click Add Local.

  2. Select IBM WAS v5.x from the Type list.

  3. Type server1 in the Server name field.

  4. Type /opt/WebSphere/AppServer in the Server home field.

  5. Click OK.


Instrument a Linux computer with WAS V6.0

Server is named server2, installed in the directory...

...with profile name set to default, and security enabled.

  1. Click Add Local.

  2. Select IBM WAS v6.x from the Type list.

  3. Type default in the Profile name field.

  4. Type server2 in the Server name field.

  5. Type /opt/WebSphere/AppServer in the Server home field.

  6. Select the Requires global security check box.

  7. Type the WebSphere user ID in the User field.

  8. Type the WebSphere password in the Password field.

  9. Click OK.


Instrument a Linux computer with WebLogic

The server is named server1, installed in the directory...

...with Java home...

... admin server host abc.ibm.com, admin server port 7001, and start script file...

  1. Start the WebLogic server. The WebLogic server must be started with the JVM that is included with RPTv8. The JRockit VM is not a supported JVM. For managed WebLogic servers, the Java Home variable must refer to the Sun JVM that came with WebLogic.

  2. Click Add Local.

  3. Select WebLogic Application Server v8.x from the Type list.

  4. Type server1 in the Server name field.

  5. Type /opt/bea/weblogic81 in the Server home field.

  6. Type /opt/bea/jdk15 in the Java home field.

  7. Type abc.ibm.com in the Admin server host field.

  8. Type 7001 in the Admin server port field.

  9. Type the WebLogic user ID in the User field.

  10. Type the WebLogic password in the Password field.

  11. Select the A script starts this server check box.

  12. Type /opt/bea/weblogic81/mydomain/startManagedWeblogic.sh in the Script file field.

  13. Click OK.

  14. Stop and restart the server.


Windows computer with WAS V5.0 or later

Server is named my_Server, installed in...

...with security enabled.

  1. Click Add Local.

  2. Select IBM WAS 5.x from the Type list.

  3. Type my_Server in the Server name field.

  4. Type C:\Program Files\was5.x in the Server home field.

  5. Select the Requires global security check box.

  6. Type the WebSphere user ID in the User field.

  7. Type the WebSphere password in the Password field.

  8. Click OK.


Instrument a Windows computer with a WebLogic

Server is named server1, installed in the directory C:\bea\weblogic81, Java home C:\bea\jdk15, admin server host localhost, admin server port 7001, and start script file C:\bea\weblogic81\mydomain\startManagedWeblogic.cmd:

  1. Start the WebLogic server. The WebLogic server must be started with the JVM that is included with RPTv8. The JRockit VM is not a supported JVM. For managed WebLogic servers, the Java Home variable must refer to the Sun JVM that came with WebLogic.

  2. Click Add Local.

  3. Select WebLogic Application Server v8.x from the Type list.

  4. Type server1 in the Server name field.

  5. Type C:\bea\weblogic81 in the Server home field.

  6. Type C:\bea\jdk15 in the Java home field.

  7. Type localhost in the Admin server host field.

  8. Type 7001 in the Admin server port field.

  9. Type the WebLogic user ID in the User field.

  10. Type the WebLogic password in the Password field.

  11. Select the A script starts this server check box.

  12. Type C:\bea\weblogic81\mydomain\startManagedWeblogic.cmd in the Script field.

  13. Click OK.

  14. Stop and restart the server.


What to do next

Repeat the instrumentation steps for each application server involved in any data collection for the applications that you will profile. Typically, there will be only one application server.


Related

  1. Data collection infrastructure overview
  2. Instrument remote servers
  3. Instrument servers using the command prompt
  4. Start the data collection infrastructure
  5. Stop the data collection infrastructure
  6. Remove instrumentation
  7. Remove instrumentation using the command prompt