Configure the Execution Environment

The configuration file has the ability to customize the execution environment that will be used as the default for all applications started through the Agent Controller. This is done by defining <Variable> sub-elements within the <AgentControllerEnvironment> element in the configuration file. Variables may be configured to either replace the default environment inherited at start time or to augment the environment.

To specify the execution environment in the configuration file:

  1. Locate the serviceconfig.xml configuration file. See the related task.

  2. Open it in an editor, and search for the <AgentControllerEnvironment> element, such as the one shown:

<AgentControllerEnvironment>
    <Variable name="JAVA_PATH" value="C:\j2sdk1.4.2_06\bin\java.exe" position="replace"/>
    <Variable name="TPTP_AC_HOME" value="C:\tptp" position="replace"/>
    <Variable name="PATH" value="%TPTP_AC_HOME%\bin" position="prepend"/>
    <Variable name="SYS_TEMP_DIR" value="C:\Temp" position="replace"/>
    <Variable name="LOCAL_AGENT_TEMP_DIR" value="%SYS_TEMP_DIR%"  position="replace"/>
</AgentControllerEnvironment>

  1. Specify the execution environment you want for the Agent Controller by either modifying or adding <Variable> sub- elements.
     

Note

Any number of <Variable> sub-elements can be added to the environment.  The elements are processed in the order they appear.  These environment settings apply to all applications.  When a launch request is made, individual applications may have their environment modified further.

The environment variables defined in serviceconfig.xml can be extended through the use of the pluginconfig.xml file.  Environment variables defined in that file will be read by the Agent Controller when it first starts up and added to those obtained from its own AgentControllerEnvironment element.

 

Related tasks
Locating the configuration files
Administering the Agent Controller
The pluginconfig.xml File


Copyright (C) 2005, 2006 Intel Corporation.


Error 404 - Not Found

Error 404 - Not Found

The document you are looking for may have been removed or re-named. Please contact the web site owner for further assistance.