Getting started with Agent Controller - OS/390
This guide contains the following information:
- RAServer requires the directories of the JRE that contain executable
libraries such as libjvm.so to be added to the LIBPATH
environment variable. For example, if you are using the IBM JRE 1.4.1, the
LIBPATH variable would be set as follows:
Note: The path that contains the JVM library libjvm
should match the one specified inside Agent Controller's configuration file,
config/serviceconfig.xml, under the AgentControllerConfiguration
element's jvm attribute. For example, if the configuration file
is pointing to the server JVM, then the library path should also points to the
location of the server JVM, not the client JVM. Agent Controller will not
function properly if the library path and the configuration do not match.
- RAServer requires the following XML4C parser on OS/390: IBM XML C++ Parser
1.4 for z/OS. It can be downloaded from the following web site:
After installing the XML4C parser on the OS/390 system, add the XML4C
parser lib directory to the LIBPATH environment variable. For
example, the LIBPATH variable would be set as follows:
the TPTP 3.3.0 Runtime.
Configuring and starting Agent
<unzip directory> = The absolute directory path where Agent Controller
has been unzipped. For example, /opt/Hyades.
<RAServer PID> =
The process identifier for the server process.
- Add the <unzip directory>/lib directory to the system's
LIBPATH environment variable.
- Add the <unzip directory>/bin directory to the system's
PATH environment variable.
- Set the RASERVER_HOME environment variable to point to
<unzip directory>. The server will use this environment
variable to locate the configuration file.
- Ensure that the files in the <unzip directory>/bin and
<unzip directory>/lib directory are executable.
- Generate the configuration file that provides the rules for which
applications that can be executed with the server. This can be accomplished by
running the <unzip directory>/bin/SetConfig.sh script. Run this
script from a command shell in the <unzip directory>/bin
directory. This step will require that a Java Virtual Machine (JVM) be present
in the system's PATH. Follow the prompts and the output will be the
<unzip directory>/config/serviceconfig.xml file. This is a
sample of the configuration file that will be used by the server when it is
started. You may edit this file manually using the rules as outlined in the
Controller configuration files. To load any changes, restart the server.
- Ensure that the <unzip directory>/bin/RAServer file is
- Start the server by running <unzip
- Stop the server by running <unzip
Querying Agent Controller version information
To display the version of Agent Controller, simply type:
The Agent Controller will
display its version and terminate.
Server LoggingAll server log entries will be
placed in <unzip directory>/config/servicelog.log.
Invoking the Java Profiler
The Java Profiler is a library that attaches to a JVM to capture and record
the Java application's behavior. The output from the profiling agent is in the
form of XML fragments.
Documentation on the composition of these XML
fragments is located at:
Invocation of the Java Profiler from the Hyades Workbench
The Java Profiler can be launched from the Hyades workbench. Open the
Profiling Perspective and you can launch applications using the 'Profile' menu
contribution or the toolbar button. Applications can be run either using code
within the current Hyades workbench's workspace or binaries that are on the file
Invocation of the Java Profiler from the Command Line
The Java Profiler is invoked using the -Xrun JVM option as follows:
where agent_parm may be:
To uninstall the agent controller:
- Stop the server by running <unzip directory>/bin/RAStop.sh.
- Remove the agent controller directory.