Introduction

HVR agents cannot use an environment variable in their /Path parameter. HVR does not support substitution of environment variables inside parameter values (e.g. action AgentPlugin /Command=”$QHOME/myagent.pl” or AgentPlugin /Path=”$QHOME” ).

Environment

Local Data Processing

Resolution

An HVR feature that can be used instead is Configuration Actions.

Imagine the following scenario: A channel requires an agent “myagent.pl” to be called on an integrate location. Therefore the channel definition should contain the agent action: AgentPlugin /Command=”myagent.pl” . But this agent script could be on a different directory on the test machine as on production machine, so adding the absolute path to it in the channel definition would break the golden rule of “ never mix channel definition with channel configuration “.

For this reason a second action should be defined: AgentPlugin /Path=”/usr/test/qhome” which specifies the absolute directory on the test machine. But this action should be defined as a configuration action (using the Configuration Action check-box below Table in each action dialog). The effect of this is that this action will not be exported when you choose “ Export Catalogs… ” of the channel definition. Instead you will have to define a new action once the channel is imported into the production hub database ( AgentPlugin /Path=”/usr/prod/qhome” ).