zRemote Agent

The zRemote Agent is an aggregation and data processing component that installs in the distributed environment and extends the zLocal Agent. The zRemote Agent offloads some of the Agent data processing in the zLocal Agent, reducing the MIPS load incurred in instrumenting mainframe applications.

Note

The zRemoteAgent should only service one zLocalAgent (zDC). Refer to the instructions on installing multiple zRemoteAgent launcher service instances for configuring multiple zRemoteAgents.

Installation and configuration

The parameter for DTAGTCMD is part of the zDC SYSIN. See zDC SYSIN Parameters for more information.

The port in zremoteagent=ipaddress:port defaults to 8898. That ipaddress and port should correspond to a distributed machine where the actual zRemoteAgent executes. The port parameter is optional and defaults to 8898.

The zRemote Agent is supported on the following operating systems:

  • Windows x64 2008 R2 / 2012 R2

  • Linux x64

Optional parameters to register the Windows service / start the *NIX daemon

  • zdclistenerport is the port that the zRemoteAgent listens to for zDC connections. This corresponds to the port in the zremoteagent SYSIN DTAGTCMD parameter previously described. This setting is optional, and if not present defaults to 8898.
  • name is the standard AppMon Agent name mapped in the System Profile. This name should reflect that this is a zremoteagent. If it services a particular LPAR, it could include the SMF ID of that LPAR, for example, name=zremoteagent_<lpar>. When you click Add Tier > CICS in the default Monitoring System Profile, the mapping defaults to CICS_Monitoring. This value is also optional, but is highly recommended.
  • server is the name of AppMon Collector with which to connect. This setting is optional, and if not present defaults to localhost.

Windows service

For a default AppMon full installation on 64-bit Windows, <DT_HOME> is C:\Program Files\dynaTrace\dynaTrace 7.2, for an Agent-only installation, go to C:\Program Files (x86)\dynaTrace\dynaTrace Agent 7.2. The zRemote Agentdtzagentlauncher.exe is in <DT_HOME>\agent\lib64.

The associated dtzagentlauncher.ini must be modified similar to the following:

`-exec=dtzagent.exe  
      -Deof=eof  
      -name=CICS_Monitoring  
      -server=localhost  
      -zdclistenerport=8898`

Installing a 2nd (or 3rd) zRemoteAgent launcher service instance

Create a new .ini file containing the different parameters (usually zdclistenerport=, and name=). To install the new service instance, issue the following command. In this example, the new port =8899, so the new .ini file is named as such.

dtzagentlauncher -service install "-ini=dtzagentauncher8899.ini" -servicename=<your service name>

If you'd like to use the init.d service scripts to start more than one zRemote Agent, you have to modify the DT_OPTARGS variable in the script.

We recommend to create a script per instance, in other words per every .ini file.

For this to work, you need a patched version of the .../init.d/functions.agent.sh file:

For example, if you want to have two separate instances, you need two .../init.d/dynatracezremoteagent scripts:

  • init.d scrpit for the first instance
    DT_HOME="/opt/dynatrace-7.2"
    DT_OPTARGS="-ini ${DT_HOME}/agent/lib64/dtzagentlauncher_for_first_instance.ini"
    
  • init.d scrpit for the second instance
    DT_HOME="/opt/dynatrace-7.2"
    DT_OPTARGS="-ini ${DT_HOME}/agent/lib64/dtzagentlauncher_for_second_instance.ini"
    

*NIX daemon

Install a .jar with java -jar <pathToJar>/dynatrace-agent-7.2.0.####-unix.jar.
When you issue a cd/opt command and perform a default 64-bit AppMon full or Agent-only installation on a 64-bit *NIX, then <DT_HOME> is /opt/dynatrace-7.2.
The executable is dtzagent in <DT_HOME>/agent/lib64.

You may have to use chmod or chown to get the right permissions.

For testing, you can use the example shell script to interactively start the zRemote Agent in the background with <DT_HOME>/init.d/dynatracezremoteagent start.
To permanently add the zRemote Agent to your boot sequence and start it as a daemon, either copy [](/support/doc/appmon/images/application-monitoring/agents/zos-agent/zremote-agent/dynatracezremoteagent) to, or reference it in, /etc/init.d and activate it with chkconfig --add dynaTracezRemoteAgent.

You can also start the zRemote Agent with <DT_HOME>/agent/lib64/dtzagent zdclistenerport=<port> name=<AgentName>[server=<CollectorName>[:port]]. The server (Collector) argument defaults to [localhost:9998](http://localhost:9998). The zdclistenerport argument defaults to 8898. See previous for a description of the name parameter.

You can also use the new dtzagentlauncher by modifying the dtzagentlauncher.ini file

`-Deof=eof  
      -name=CICS_Monitoring  
      -server=localhost  
      -zdclistenerport=8898`

Installing a 2nd (or 3rd) zRemoteAgent launcher instance

Create a new .ini file that contains the different parameters (usually zdclistenerport= and the name=). To start the new instance, specify the -ini parameter. For example:

./dtzagentlauncher -ini=dtzagentauncher8899.ini