IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1

Manually configuring the data collector to monitor an application server instance - WAS agent

You can configure the data collector to monitor an application server instance without using the configuration utility. To do this, you need to create a settings file, and then manually add settings using WebSphere Administrative Console. The runtime directory will be created automatically when the data collector is started for the application server instance.


Step 1. Create a settings file

The settings file contains the values needed for initial configuration of the Data Collector.

To create this file, copy the file DC_home/itcamdc/etc/dcInputs_manual.txt into DC_home/runtime/dcInputs.txt. Then, edit DC_home/runtime/dcInputs.txt, setting the configuration parameters according to the comments in the file.

Tip: you can use a different name if needed. In this case, use a different value for the -Ditcamdc.inputs property in the next step.

You must set the parameters in Section 1. Change parameters in Section 2 if the defaults are not suitable. Do not change anything below the end of Section 2.

Set the appserver.platform parameter according to the product that is to be monitored:

Product name and version Value of appserver.platform
WAS 6.0 was60
WebSphere Enterprise Service Bus (ESB) 6.0, based on WAS 6.0 was60.esb60
WebSphere Process Server 6.0, based on WAS 6.0 was60.prs60
WAS 6.1 was61
WebSphere Enterprise Service Bus (ESB) 6.1, based on WAS 6.1 was61.esb61
WebSphere Process Server 6.1, based on WAS 6.1 was61.prs61
WebSphere Enterprise Service Bus (ESB) 6.2, based on WAS 6.1 was61.esb62
WebSphere Process Server 6.2, based on WAS 6.1 was61.prs62
WAS 7.0 was70
WebSphere Portal Server 6.0, based on WAS 6.0 wps60
WebSphere Portal Server 6.1, based on WAS 6.1 wps61


Step 2. Add settings using WebSphere Administrative Console

Complete the following steps:

  1. Log into the WAS administrative console.

  2. Click Server > Application Servers and select the server_name.

  3. In the Configuration tab, navigate to Server Infrastructure > Java and Process Management > Process Definition > Additional Properties: Java Virtual Machine.

  4. In the Generic JVM arguments field, add the following entries. All of them must be on a single line; separate different arguments by spaces before the - sign, do not use spaces anywhere else.

    Replace DC_home with ITM_home/TMAITM6/wasdc/7.1.0.1 on Windows, ITM_home/architecture_code/yn/wasdc/7.1.0.1 on Linux and UNIX systems. On Windows, use / as directory separator (for example, C:/IBM/ITM/TMAITM6/wasdc/7.1.0.1.

    For the value of appserver_version, see Table 1.

    For node_name and server_name, use the node and server name of the application server instance.

    For number, use 14 for WAS 6.0 and products based on it, 15 for WAS 6.1 and products based on it, or 16 for WAS 7.0 and products based on it. 

    -Xbootclasspath/p:DC_home/toolkit/lib/bcm-bootstrap.jar;
DC_home/itcamdc/lib/ppe.probe-bootstrap.jar
-agentlib:am_ibm_number=DC_home/runtime/
appserver_version.node_name.server_name/
-Ditcamdc.inputs=dcInput.txt

    Tip: if you have used a different file name instead of dcInput.txt, use the name for the -Ditcamdc.inputs parameter.

    Also, for IBM Virtual Machines, add:

    -Xverbosegclog:${SERVER_LOG_ROOT}/itcam_gc.log,5,3000
    For Sun Java Virtual Machines (typically used on Solaris and HP/UX systems), add:
    -XX:+PrintGCTimeStamps -verbosegc -Xloggc:${SERVER_LOG_ROOT}/itcam_gc.log

  5. Click Apply.

  6. In the Messages dialog box, click Save.

  7. In the Save to Master Configuration dialog box:

    • If you are under a Network Deployment environment, be sure the check box Synchronize changes with Nodes is selected and then click Save.

    • If you are not under a Network Deployment environment, click Save.

  8. Click Server > Application Servers and select the server_name.

  9. In the Configuration tab, navigate to Server Infrastructure > Java and Process Management > Process Definition > Environment Entries.

  10. Depending on the operating system and hardware platform, set the following environment entry:


    Platform Entry name Entry value
    AIX4_R1 LIBPATH DC_home/toolkit/lib/aix533
    AIX_64 LIBPATH DC_home/toolkit/lib/aix536
    HPUX10 SHLIB_PATH DC_home/toolkit/lib/hp11
    HPUX_64 SHLIB_PATH DC_home/toolkit/lib/hp116
    HPUX_IA64 SHLIB_PATH DC_home/toolkit/lib/hpi116
    HPUX_IA64N SHLIB_PATH DC_home/toolkit/lib/hpi113
    LINUX_IX64 LD_LIBRARY_PATH DC_home/toolkit/lib/lx8266
    LINUX_IX86 LD_LIBRARY_PATH DC_home/toolkit/lib/li6263
    LINUX_PPC LD_LIBRARY_PATH DC_home/toolkit/lib/lpp263
    LINUX_PPC64 LD_LIBRARY_PATH DC_home/toolkit/lib/lpp266
    LINUX_S390 LD_LIBRARY_PATH DC_home/toolkit/lib/ls3263
    LINUX_S390_64 LD_LIBRARY_PATH DC_home/toolkit/lib/ls3266
    SOLARIS2 LD_LIBRARY_PATH DC_home/toolkit/lib/sol293
    SOLARIS2_IX86 LD_LIBRARY_PATH DC_home/toolkit/lib/sol603
    SOLARIS2_IX86_64 LD_LIBRARY_PATH DC_home/toolkit/lib/sol606
    SOLARIS_64 LD_LIBRARY_PATH DC_home/toolkit/lib/sol296
    W32_IX86 (Windows 32-bit) PATH DC_home/toolkit/lib/win32
    W64_X64 (Windows 32-bit) PATH DC_home/toolkit/lib/win64

  11. Click Apply.

  12. In the Messages dialog box, click Save.

  13. In the Save to Master Configuration dialog box:

    • If you are under a Network Deployment environment, be sure the check box Synchronize changes with Nodes is selected and then click Save.

    • If you are not under a Network Deployment environment, click Save.

  14. Restart the application server instance. The data collector will read the settings file and create the runtime directory.


Parent topic:

Manual changes to application server configuration for the data collector

+

Search Tips   |   Advanced Search