Installing › Installing Integration Tools › Configure Integration with CA APM › Instrumenting DevTest Processes

Instrumenting DevTest Processes

The LISA_HOME\bin directory contains a Windows executable file for each DevTest process. This folder includes separate versions for those processes that can be run as regular Windows processes and as Windows services. The list of processes and their executable file names is:

Note: This list excludes executables in the bin directory that are not relevant for the Introscope instrumentation.

To instrument any DevTest process with an Introscope agent, create a file with the same name as the executable and the extension .vmoptions. For example, to instrument the DevTest Workstation, create a Workstation.vmoptions file in the bin directory under the DevTest Server installation directory. The .vmoptions file contains the following two lines:

-javaagent:<AGENT_HOME>/Agent.jar
-Dcom.wily.introscope.agentProfile=<AGENT_HOME>/core/config/IntroscopeAgent.profile

<AGENT_HOME> is the path to a DevTest-specific Introscope agent installation. Typically this path is an absolute path, but it can also be a path relative to the current directory in which the DevTest process runs.

To have the Introscope agent report under a name other than the default DevTest Agent, add a line defining the Java com.wily.introscope.agent.agentName system property. For example, to call the agent DevTest Workstation 6.0.5.87 Agent, add the following line:

-Dcom.wily.introscope.agent.agentName=DevTest Workstation 6.0.5.87 Agent 

To set other JVM command-line options or system properties as required, add extra lines. Each option must be specified in a separate line.

The Introscope agent installation that you use can be specific to the DevTest installation, or even to the DevTest process. You can create variations in agent configurations by varying contents of the IntroscopeAgent.profile in those separate agent installations. Or, to create multiple agent profiles in a single agent installation, modify the com.wily.introscope.agentProfile system property value that is defined in each .vmoptions file. This approach allows different levels of tracing or logging (or even different Introscope Enterprise Managers) to be used to monitor different DevTest processes.

For example, a site can include a production use of DevTest that uses a coordinator node that is run as a Windows service. This site can also include a test/experimental use that uses a coordinator that is run as a regular Windows process. This coordinator could even be the one that is built into the DevTest Workstation. The production metrics are reported to the production EM, while the test/experimental metrics are reported to the test EM. This can be achieved by using multiple profiles and nominating the correct profile in the relevant. vmoptions file. It can also be achieved by overriding the value of introscope.agent.enterprisemanager.connectionorder and introscope.agent.enterprisemanager.transport.* properties that are defined in the profile by setting Java system properties of those names in the .vmoptions file. Consult the Introscope Java Agent Guide for the full range of Introscope Agent configuration options.