Manually configuring the Data Collector to monitor an application server instance

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, you need to 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:

Table 1. Values for the application server platform designation
Product name and version	Value of `appserver.platform`
WebSphere Application Server 6.0	`was60`
WebSphere Enterprise Service Bus (ESB) 6.0, based on WebSphere Application Server 6.0	`was60.esb60`
WebSphere Process Server 6.0, based on WebSphere Application Server 6.0	`was60.prs60`
WebSphere Application Server 6.1	`was61`
WebSphere Enterprise Service Bus (ESB) 6.1, based on WebSphere Application Server 6.1	`was61.esb61`
WebSphere Process Server 6.1, based on WebSphere Application Server 6.1	`was61.prs61`
WebSphere Enterprise Service Bus (ESB) 6.2, based on WebSphere Application Server 6.1	`was61.esb62`
WebSphere Process Server 6.2, based on WebSphere Application Server 6.1	`was61.prs62`
WebSphere Application Server 7.0	`was70`
WebSphere Portal Server 6.0, based on WebSphere Application Server 6.0	`wps60`
WebSphere Portal Server 6.1, based on WebSphere Application Server 6.1	`wps61`

Step 2. Add settings using WebSphere Administrative Console

Complete the following steps:

Log into the IBM® WebSphere Application Server administrative console.
Click Server > Application Servers and select the server_name.
In the Configuration tab, navigate to Server Infrastructure > Java™ and Process Management > Process Definition > Additional Properties: Java Virtual Machine.
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.2 on Windows®, ITM_home/architecture_code/yn/wasdc/7.1.0.2 on Linux® and UNIX® systems. On Windows, use / as directory separator (for example, C:/IBM/ITM/TMAITM6/wasdc/7.1.0.2.

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 WebSphere Application Server 6.0 and products based on it, 15 for WebSphere Application Server 6.1 and products based on it, or 16 for WebSphere Application Server 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
```
Attention: Do not use templates, such as %pid, in these strings.
Click Apply.
In the Messages dialog box, click Save.
In the Save to Master Configuration dialog box, complete the following steps:
- 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.
Click Server > Application Servers and select the server_name.
In the Configuration tab, navigate to Server Infrastructure > Java and Process Management > Process Definition > Environment Entries.

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

Table 2.
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`

Click Apply.
In the Messages dialog box, click Save.
In the Save to Master Configuration dialog box, complete the following steps:
- 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.
Restart the application server instance. The Data Collector will read the settings file and create the runtime directory.