AppInternalsInstallationv10.0.1

Installing AppInternals

This material describes installing the AppInternals analysis server and agents:
 “Installation/Configuration Quick Start“
 “Analysis Server Installation“
 “Agent Installation: Windows“
 “Unattended Agent Installation: Windows“
 “Agent Installation: UNIX“
 “Unattended Agent Installation: UNIX“

Riverbed SteelCentral AppInternals Version 10.0 1

2 Riverbed SteelCentral AppInternals Version 10.0

CHAPTER 1 Installation/Configuration Quick Start

Here are the steps to quickly install AppInternals and monitor your environment.

Download and Import the Analysis Server Virtual Appliance

The AppInternals analysis server is a virtual appliance packaged in Open Virtualization Format (OVF) and distributed

as an Open Virtual Appliance (OVA) file. Download the analysis server OVA file from the AppInternals support page:
https://support.riverbed.com/content/support/software/steelcentral-ap/appinternals.html
Import the analysis server virtual appliance into a supported virtual environment. For example, on VMware ESXi:

Start the Virtual Machine and Log In

After the analysis server appliance is deployed, start the appliance from the virtual environment hypervisor. For
example, on VMware ESXi:

A command line console appears and starts the virtual machine. When the log in prompt appears, log in with the user
name and password of admin:

Riverbed AppInternals Virtual Appliance
---------------------------------------

Login with the default credentials:
Username: admin
Password: admin

---------------------------------------

appinternals login: admin
Password:

Riverbed SteelCentral AppInternals Version 10.0/Release 10.0 3

Installation/Configuration Quick Start

Supply a Host Name for the Virtual Machine

An important one-time configuration step is to set up networking on the analysis server virtual machine. Part of that
configuration is to supply a stable host name that both AppInternals agents and users need to connect to the analysis
server.
See “Configuring Networking on the Virtual Machine“ for details.

Install Agent Software

Install the agent software on systems you want to monitor. The installation prompts for the host name for the analysis
server you specified in the previous step.
Once started, the agents “phone home” to the analysis server and automatically begin sending data on key operating
system resources (CPU, memory, and networking).
For more details on agent installation, see:
 “Agent Installation: Windows“
 “Agent Installation: UNIX“

Log In to the Analysis Server Interface

In a browser, enter an address using the host name that you specified in “Supply a Host Name for the Virtual Machine“:

http://<fully-qualified-hostname>

AppInternals presents a self-signed security certificate created by the installation when browsers connect. Browsers
generate a warning when a site presents a self-signed certificate, so expect to see a warning when first connecting to
this address. For example, in Firefox:

Accept the warning (click I Understand the Risks in Firefox) to continue. You can replace the default certificate later
in the analysis server interface.

4 Riverbed SteelCentral AppInternals Version 10.0/Release 10.0

Installation/Configuration Quick Start

In the login screen, supply the default user name and password of admin:

Instrument the Processes You Want to Monitor

In the analysis server, go to Configure > Agent List to see what agents have phoned home. Click the server that is
running an application that you want to monitor. In the Agent Details screen, click the Instrument? option for the
processes you want to monitor:

Riverbed SteelCentral AppInternals Version 10.0/Release 10.0 5

Installation/Configuration Quick Start

Enjoy Your Data!

You’re done! In a few minutes, transaction data for your instrumented applications will appear in the AppInternals
interface. Each tab gives a different view of your environment:

6 Riverbed SteelCentral AppInternals Version 10.0/Release 10.0

CHAPTER 2 Analysis Server Installation

The AppInternals analysis server is a virtual appliance packaged in Open Virtualization Format (OVF) and distributed

as an Open Virtual Appliance (OVA) file.
This section describes general installation steps. See the System Requirements for details on supported virtual
environments and up-to-date requirements. The system requirements are available from the AppInternals support
page:
https://support.riverbed.com/content/support/software/steelcentral-ap/appinternals.html

Importing the Analysis Server Virtual Appliance .ova File

Download the analysis server OVA file from the AppInternals support page:
https://support.riverbed.com/content/support/software/steelcentral-ap/appinternals.html
Import the analysis server virtual appliance into a supported virtual environment. For example, on VMware ESXi
Version 5.5:

Provisioning the Virtual Machine

After you import the virtual appliance, make sure it is adequately provisioned. The analysis server will not function
correctly unless you provision its virtual machine with sufficient resources.
See the System Requirements for details on provisioning the virtual machine. The system requirements are available
from the AppInternals support page:
https://support.riverbed.com/content/support/software/steelcentral-ap/appinternals.html

Riverbed SteelCentral AppInternals Version 10.0 1

Analysis Server Installation

Starting the Virtual Machine and Logging In

1. After the appliance is deployed, start the appliance from the virtual environment hypervisor. For example, on
VMware ESXi Version 5.5:

2. A command line console appears and starts the virtual machine. When the log in prompt appears, log in with the
user name and password of admin:

Riverbed AppInternals Virtual Appliance
---------------------------------------
Login with the default credentials:

Username: admin
Password: admin
---------------------------------------
appinternals login: admin
Password:

3. Configure networking as described in “Configuring Networking on the Virtual Machine“.

Configuring Networking on the Virtual Machine

An important one-time configuration step after starting the analysis server virtual machine for the first time is to
configure networking.
It is especially important to set the host name right away to avoid unnecessary reconfiguration later. This section
describes using the automatic network wizard to set the host name and other network options.

Running the Network Wizard

The first time you log in after starting the virtual machine (see “Starting the Virtual Machine and Logging In“), the
command line interface (CLI) network “wizard” runs automatically:

.
.
.
Successfully logged into AppInternals admin interface
Press the '?' key for list of available commands
Network Configuration
----------------------------
Press CTRL+D to cancel
Current Configuration:

Interface configured for DHCP
Do you wish to use DHCP (y/n):

Use the wizard to configure the IP address, DNS, and host name. (You can cancel the wizard with CTRL/D and run it
later using the CLI command “networkcfg“.)

2 Riverbed SteelCentral AppInternals Version 10.0

Analysis Server Installation

The first prompt from the wizard is whether to use DHCP or static IP addresses. Subsequent prompts depend on that
response:

 See “Using DHCP“ to configure the network to use DHCP (Dynamic Host Configuration Protocol) to
dynamically assign an IP address for the network interface.

 See “Using a Static IP Address“ to configure the network to use static IP addresses.

Using DHCP

This section describes the network wizard prompts if you choose to use DHCP by responding y to the first prompt:

Do you wish to use DHCP? (y/n):y

With this option, the virtual machine will request an IP address from a DHCP server in your environment. The next
prompt is whether you also want DHCP to also assign the DNS (Domain Name System) server and external network
gateway:

Obtain DNS from DHCP (y/n)):

 If you choose y, the wizard prompts for the host name. See “Supplying the Host Name“.
 If you choose n, the wizard prompts for one or more DNS servers. For example:

Obtain DNS from DHCP (y/n)):n
DNS Server(s) (comma separated): 10.46.34.13

After prompting for the DNS servers, the wizard prompts for the host name. See “Supplying the Host Name“.

Using a Static IP Address

This section describes the network wizard prompts if you choose to use static IP addresses by responding n to the first
prompt:

Do you wish to use DHCP? (y/n):n

With this option, the wizard prompts for the network IP address, subnet mask, network gateway, and DNS servers. For
example:

IP Address: 10.46.35.65

Subnet Mask: 255.255.255.0

Default Gateway: 10.46.35.11

DNS Server(s) (comma separated): 10.46.34.13

The wizard next prompts for the host name. See “Supplying the Host Name“.

Supplying the Host Name

The default host name for the analysis server virtual machine is appinternals.local.You need to supply a value
suitable to your environment.

It is important to supply a fully-qualified host name that will identify the analysis server. In addition, the host name
should be unlikely to change, because the host name is used elsewhere in the analysis server and by AppInternals
agents. If the host name changes, you will need to reconfigure multiple areas as described in the description of the
“Hostname“ setting in the “Network Configuration Screen“.

Riverbed SteelCentral AppInternals Version 10.0 3

Analysis Server Installation
Regardless of whether you chose DHCP (see “Using DHCP“) or a static IP address (see “Using a Static IP Address“),
the last prompt by the network wizard is for the virtual machine host name:

WARNING: You are about to set the hostname of this system. We strongly recommend that you use a
stable, fully-qualified hostname that is accessible to both the agent machines and the end-users'
browsers. Also consider that, in some cases, you may purchase a signed certificate that matches
this hostname. Changing this value later can be a time-consuming process.
Current value: appinternals.local

System hostname:

Logging In to Analysis Server Interface

Confirm that the analysis server is fully started by logging in to the analysis server user interface:
1. In a browser, enter the host name or IP address that you configured in “Configuring Networking on the Virtual
Machine“:

https://<fully-qualified-hostname>

OR

https://<ipaddress>

2. AppInternals presents a self-signed security certificate created by the installation when browsers connect.
Browsers generate a warning when a site presents a self-signed certificate, so you will see a warning when first
connecting to this URL. This is expected. (To avoid the warning, replace the default certificate in the “TLS
Certificate Configuration Screen“.)

4 Riverbed SteelCentral AppInternals Version 10.0

Analysis Server Installation

3. In the login screen, supply the default user name and password of admin:

Installing AppInternals Agents

The next step in setting up AppInternals is to install agent software on systems you want to monitor. See the following
links for more detail:
 “Agent Installation: Windows“
 “Agent Installation: UNIX“

Riverbed SteelCentral AppInternals Version 10.0 5

Analysis Server Installation
6 Riverbed SteelCentral AppInternals Version 10.0

Analysis Server Installation

Riverbed SteelCentral AppInternals Version 10.0 7

Analysis Server Installation
8 Riverbed SteelCentral AppInternals Version 10.0

CHAPTER 3 Agent Installation: Windows

The agent and one or more sub-agents are responsible for the actual collection and communication of metric and
transaction trace data on each system being monitored by AppInternals.
On Windows, you run an interactive installer to install the agent and specify the analysis server you want it to report
to. This section describes that process. You can also install the agent without user intervention, as described in
“Unattended Agent Installation: Windows“.

Installation Prerequisites

This section describes installation requirements.

Disk and Memory

The installation requires 500 MB of available disk space to install the agent. It issues a warning if there is less than 1
GB of available space.
After installation, disk space requirements depend on the number of applications being monitored, the level of their
activity, and disk usage configuration settings. For more detail, see the System Requirements available from the
AppInternals support page:
https://support.riverbed.com/content/support/software/opnet-performance/appinternals-xpert.html
There is no minimum memory requirement.

Software

The installer requires certain Visual C++ packages. These do not have to be installed before running the agent installer.
As described in “Installing Visual C++ Packages May Require Reboot“, the installer will install them if they are not
already available.

Riverbed SteelCentral AppInternals Version 10.0 9

Agent Installation: Windows

Installation Account

Use the Windows Administrator account to install or remove agent software. Typically, accounts in the Windows
Administrators group also have sufficient privileges. On some versions of Windows Server, you have to right-click
and choose Run as administrator.

Note: Accounts Running Java and .NET Applications Require Directory Access
The user account that starts Java or .NET processes that AppInternals will monitor must have read and write access to
specific AppInternals directories.

Installing the Agent

The agent installation takes around 5 minutes.
The software is distributed as a self-extracting executable file that you download from the AppInternals support page:
https://support.riverbed.com/content/support/software/opnet-performance/appinternals-xpert.html.
Look in the Software Description column for Agent (Windows).
The self-extracting executable file is named AppInternals_Agent_<version>_Win.exe. To start the installation, click
on the file.

Installing Visual C++ Packages May Require Reboot

After the installer starts, it examines your
system to see if prerequisite software is
installed. These prerequisites include up to
four Visual C++ packages. If the agent
software installer finds they are not on the
system, it automatically installs them for
you. After each prerequisite package
installs, if you had files open during the
installation that the Visual C++ installer
must update, you are asked to reboot the
system. You are given the option to restart later.
 If you choose Restart Now, the system reboots immediately.
 If you choose Restart Later, the installer exits and does not update required files or start the agent installation.
After either choice, when the system reboots, the prerequisite installer updates those files that were open and proceeds
with the next installer. After the last prerequisite package is installed and the reboot occurs, the agent software
installation continues automatically.

10 Riverbed SteelCentral AppInternals Version 10.0

Agent Installation: Windows

Information Required for Installation

The following table summarizes the information requested by the Windows agent installer.

Information Requested Notes
Installation directory
Analysis server location Setup creates the Panorama directory and subdirectories in the parent directory you specify.
The default is C:\. You can specify a different directory.
Start services?
Specify the system name, fully-qualified domain name (FQDN), IP address for the analysis
server. If the analysis server name changes after you install the agent, you must change this
name as described in “Changing the Agent’s Analysis Server“. the help topic on “Changing
the Agent’s Analysis Server“.

The installer gives you the option to not start the Windows services for the agent and
sub-agents. By default, the installation starts the services, which is easier.

Post-Installation Tasks

The installation creates an MSI<identifier>.log file in the %temp% directory (typically, this resolves to
C:\Users\<username>\AppData\Local\Temp). You can review the log to confirm details of the installation or
troubleshoot problems.

Enable Instrumentation

An important configuration task is to enable instrumentation for Java processes you want to monitor. The configuration
topic “Enabling Instrumentation of Java Processes“ describes different approaches in detail.

Confirm that the Agent Connected to the Analysis Server

Log in to the analysis server web interface using the host name or IP address specified during installation:

http://<AppInternalsSystem>

The default username and password are both admin. In the Configure menu, navigate to the “Agent List Screen“. You
should see the system listed with the icon for new agents ( ):

Riverbed SteelCentral AppInternals Version 10.0 11

Agent Installation: Windows

Start Windows Services

The installation creates Windows services for the agent and sub-agents. The service names all start with Riverbed
SteelCentral AppInternals.
Unless you choose not to start them, all the services should start automatically. They are configured to start
automatically when the system next reboots.
Use the Windows Services utility to start, stop, and check the status of services:

Confirm That the System Time Is Synchronized

The AppInternals installation assumes that the system time on all systems (agent and analysis server) is synchronized.
After installing the agent, make sure time is synchronized as described in the “Agent Time Synchronization“
configuration topic.

Removing Agent Software

Before removing the agent, you must manually stop Java and .NET applications that AppInternals is monitoring.
Otherwise, the installation will not be able to delete files they have locked. Check the web interface “Bulk
Configuration Screen“ to see which processes you need to stop.
You can stop ASP.NET applications by using the Windows Services utility to stop the World Wide Web Publishing
service.
Use the Windows Administrator account to remove agents. Typically, accounts in the Windows Administrators
group also have sufficient privileges. On some versions of Windows Server, you may have to right-click and choose
Run as administrator. This account must have privileges to delete files on disks with database files.
To remove agent software, use the Add or Remove Programs utility. Double-click Riverbed SteelCentral
AppInternals Agent to run the uninstall program.
If the uninstall program tries to delete files that are open, it will prompt you to restart the system after it finishes.
Restarting the system closes the files and allows them to be deleted.
Make sure that the Windows Services utility is not open when you remove AppInternals components. If the Services
utility is open, the uninstall program may not be able to completely remove services.

12 Riverbed SteelCentral AppInternals Version 10.0

Agent Installation: Windows

Upgrading Agent Software

Upgrades to Version 10.0 from earlier versions of AppInternals agent software (called “managed node’ or “collector”)
are not supported.

“Repair”: Re-running the Installer to Replace Files

You can run the installer again after installing the current release to replace AppInternals program files.
When the installer detects an existing installation with the same version and build number, it gives you the option to
“repair” the agent. A repair re-installs only files that are missing or damaged.
After you click Next in the Welcome pane, select Repair and click Next.

Riverbed SteelCentral AppInternals Version 10.0 13

Agent Installation: Windows
14 Riverbed SteelCentral AppInternals Version 10.0

CHAPTER 4 Unattended Agent Installation:
Windows

Overview

The agent installation executable (AppInternals_Agent_<version>_Win.exe) is implemented using the Microsoft
Windows installer and embeds a standard MSI installation package.

This section describes how to automate the installation of agent software by specifying arguments to the agent
installation executable. There are two approaches:

 Specify installation options directly on the command line as arguments to the agent installation executable. This
approach does not require third-party tools but the command line can become complex.

 Extract the MSI file from the executable and use a third-party tool to specify installation options in an MSI
transform file. You then specify MSI and the transform (.mst) files as arguments to the Windows installer
executable, msiexec. This approach requires additional steps but allows deployment using tools such as Microsoft
System Center Configuration Manager.

See the following links for general information about the Windows installer:

http://en.wikipedia.org/wiki/Windows_Installer
http://unattended.sourceforge.net/installers.php
http://msdn.microsoft.com/en-us/library/cc185688%28VS.85%29.aspx

Prerequisite and Agent Installers May Each Require Reboot

An unattended installation (or upgrade) invokes more than one installer: one or more of a set of installers for
prerequisite Visual C++ software packages (if they are not already installed), and an installer for the agent software.

During any of these unattended installations, if you have one or more files open that the installer needs to update, the
system must reboot for those files to be updated. These installers respond differently to finding the files open:

 If a prerequisite Visual C++ installer finds you have files open that it must update, this installer exits without
rebooting. After the system next reboots, the prerequisite installer updates those files, then the unattended agent
software installation begins automatically. (If an unattended installation appears to have failed (the agent
software did not install), it might be because the prerequisite installer has exited and is waiting for you to reboot
the system.)

 In contrast, if the agent software installer finds you have files open that it must update, unlike the prerequisite
installer, this installer automatically reboots to update those files and complete the installation.

Riverbed SteelCentral AppInternals Version 10.0 15

Unattended Agent Installation: Windows

Preventing Automatic Reboot of Agent
You can prevent an automatic reboot of the agent after the installation by including
REBOOT=ReallySuppress in the Windows installer command (for details, refer to
http://msdn.microsoft.com/en-us/library/aa371101%28v=vs.85%29.aspx).

Note—Suppressing Auto-Reboot Results in Incomplete Installation—If you add
REBOOT=ReallySuppress to your installation script, when a reboot is required to complete the install, the
installer exits without completing the installation or indicating why it has exited. You must then reboot the system
to ensure the installation is complete. To handle this behavior, you could have the script send you a notification
when a reboot is required, then schedule those reboots at an appropriate time.

Specify Installation Options on the Command Line

You can specify installation options directly on the command line as arguments to the agent installation executable
(AppInternals_Agent_<version>_Win.exe).
For example, this minimal command installs the DSA to the default directory without enabling any sub-agents or
creating a log file:

AppInternals_Agent_10.0.00168_Win.exe /s /v"/qn"

Installing the agent software from the command line in this manner completes without any user interaction or
indication of progress. Use the options described in “Installation Options Reference“ to control any aspect of the agent
installation that you can specify interactively through the installer user interface.

General Syntax

In general, use the following syntax to invoke the agent installation executable from the command line:

installation-executable /s /v" [ install-option ]… [ /Llogginglevel \"logfilespec\" ] /qn"

/s
The /s argument suppresses display of the file extraction installer panel.

/v
The /v argument specifies installation options to pass to the Windows installer, misexec. Supply all options on the
same line as the installation executable file name. In general, use upper case option names and option values.
(Option names are not case sensitive but option values are case sensitive and the installer requires most to be all
upper case.) See “Installation Options Reference“ for details. See the following link for details on msiexec
switches: http://support.microsoft.com/kb/227091

install-option
These options specify details of the agent installation. There are command-line options that correspond to every
setting that you can specify interactively through the installer user interface. See “Installation Options Reference“
for details.

[ /Llogginglevel \"logfilespec\" ]
The logging level and file specification for the log file for the installation. The path to the log file location must
already exist. The installer does not create the directory structure for the log file.

16 Riverbed SteelCentral AppInternals Version 10.0

Unattended Agent Installation: Windows

The backward slashes ( \ ) are escape characters for the double quotation marks ( " )that enclose the log file
specification.

The backward slashes and double quotation marks are always allowed, but required only if the log file
specification contains spaces. The most detailed logging level specification is /L*v. For example:

/L*v \"c:\temp\Agent Install Log.log\"

See the following link for details on the different msiexec logging levels and options:
http://technet.microsoft.com/en-us/library/cc759262%28v=ws.10%29.aspx#BKMK_SetLogging

/qn

Runs the Windows installer without user intervention and suppresses display of user interface screens (/qn is a
mnemonic for "quiet mode, no user interface"). The Windows installer supports other /q options. For example,
specify /qf ("quiet mode, full user interface"), or omit the /q argument altogether, and the installer will display
the user interface screens filled in with option values supplied on the command line. This is a good way to validate
command line options.

See the following link for additional /q options:
http://technet.microsoft.com/en-us/library/cc759262%28v=ws.10%29.aspx#BKMK_SetUI

New Installation

There are command-line options for each setting that you can specify interactively through the interactive GUI
installer. For a new installation, supply values for required options and options whose default you want to override.
See “Installation Options Reference“ for details on the options.
The following command line example:
 Uses the “INSTALLDIR“ option to specify a different installation directory (c:\Riverbed).
 Uses the “O_SI_ANALYSIS_SERVER_HOST“ option to specify the IP address for the analysis server.
 Creates a log file for the installation.

AppInternals_Agent_10.0.00168_Win.exe /s /v"INSTALLDIR=c:\Riverbed
O_SI_ANALYSIS_SERVER_HOST=10.46.35.218 /L*v c:\temp\AgentInstallLog.log /qn"

Change an Existing Installation

This section describes changing an existing installation:
 Upgrading from an earlier release (see “Upgrade“)
 Repairing to replace files created by the installation (see “Repair“)

Stop Application and Web Servers, Other Sub-agents as Necessary

Before changing an existing installation, you must manually stop Java and .NET applications that AppInternals is
monitoring. Otherwise, the upgrade will not be able to replace files they have locked. Check the web interface “Bulk
Configuration Screen“ to see which processes you need to stop.
You can stop ASP.NET applications by using the Windows Services utility to stop the World Wide Web Publishing
service.

Riverbed SteelCentral AppInternals Version 10.0 17

Unattended Agent Installation: Windows

Upgrade

Upgrades to Version 10.0 from earlier versions of AppInternals agent software (called “managed node’ or “collector”)
are not supported.

Repair

You can run the installer on an existing agent installation with the same version and build number. Use only the
REINSTALL=ALL and REINSTALLMODE=vamus options to replace files created by the previous installation
without adding or removing sub-agents. This “repair” operation can be useful to restore files that were corrupted or
accidentally deleted. It preserves files created after the installation.
The following example repairs a agent installation:

AppInternals_Agent_10.0.00168_Win.exe /s /v"REINSTALL=ALL REINSTALLMODE=vamus /L*v
c:\temp\AgentRepairLog.log /qn"

Remove an Existing Installation

Use the /x argument to remove an existing installation. The following example removes the installation and creates a
verbose log file:

AppInternals_Agent_10.0.00168_Win.exe /x /s /v"/L*v c:\temp\AgentUnInstallLog.log /qn"

18 Riverbed SteelCentral AppInternals Version 10.0

Unattended Agent Installation: Windows

Specify Installation Options in an MSI Transform

The MSI format lets you modify or customize an installer by creating a transform (with a file extension of .mst). A
transform is another way to specify values for the same installation options you can specify on the command line. (See
“Installation Options Reference“ for details on the options.)
To create a transform, you first extract the MSI installation package from the agent installation executable. Then, use
a third-party tool like ORCA (Microsoft), InstallShield (Flexera) or InstEd (Instedit) to create the transform. ORCA is
most common and is free from Microsoft. The others are licensed products.
Once you create the transform, run msiexec and specify the extracted MSI and transform files to install the agent
software.
This section describes these steps in more detail.

Prerequisites

Before you begin an unattended installation, be sure that the Microsoft Visual C++ 2010 Redistributable Package (x86)
and Microsoft Visual C++ 2010 Redistributable Package (x64) are installed on the target systems. You can verify they
are installed by opening the control panel, selecting Programs and Features, and looking for Version 10.0.40219 of
each in the program list:

If you need to install them, you can download these packages from Microsoft for free from this site:
http://search.microsoft.com/en-us/DownloadResults.aspx?FORM=DLC&ftapplicableproducts=^%22Developer%20
Tools%22&sortby=+weight

Extract the MSI file

Invoke the agent installation executable with the /a argument. For example:

AppInternals_Agent_10.0.00168_Win.exe /a

Riverbed SteelCentral AppInternals Version 10.0 19

Unattended Agent Installation: Windows
The /a argument creates a “server image” that includes the MSI file without actually installing the agent software. The
installer displays a series of panels, including one where you specify the directory for the server image:

The installer creates the .msi file in the specified directory, named MNInstall.msi.

Create the Transform from the MSI File

You use a third-party tool to modify the MSI file extracted in the previous step. This section shows Microsoft Orca.
See the following link for more details on Orca:
https://msdn.microsoft.com/en-us/library/aa370557%28v=vs.85%29.aspx
Use the third-party tool to modify properties that correspond to the installation options described in “Installation
Options Reference“.
Note: Do Not Modify Any Other Properties: Tools such as Orca allow modifying any property in an MSI installation
package. Only modify properties with the O_SI prefix, and the “INSTALLDIR“ property. The agent installer does not
support modifying other properties.
Open the MSI file in Orca and click the Property table. Click the Property column in the table in the right pane to
sort by the property name and group together the O_SI properties that you can modify. Click the Transform > New
Transform menu option. To change values, click the cell in the Value column for the property you want to modify.
Some installation options (such as “INSTALLDIR“) do not have corresponding properties. To create the property, click
the Tables > Add Row… menu option and supply the property name and value.
After you modify and create properties, click the Transform > Generate Transform menu option and supply a file
name for the .mst file.

20 Riverbed SteelCentral AppInternals Version 10.0

Unattended Agent Installation: Windows
The following example shows a transform in Orca with changed properties to connect to the analysis server:

Run msiexec with the MSI and Transform Files

To install the agent software with the changes specified in the transform file, run the Windows installer executable,
msiexec, with the MSI and transform (.mst) files as arguments. The following example specifies the transform shown
in the previous step:

msiexec /i MNInstall.msi TRANSFORMS=analysisServerDetails.mst /L*v
c:\temp\AgentInstallTransformLog.log /qf

This example passes /qf as an argument to display the installer interface screens filled in with option values supplied
in the transform file. Examining these screens is a good way to validate that the transform has the options you want.

Installation Options Reference

This section describes options that control aspects of the agent installation. The options correspond to settings exposed
in the graphical user interface (GUI) version of the installer.
In general, use upper case option names and option values. (Option names are not case sensitive but option values are
case sensitive and the installer requires most to be all upper case.)

INSTALLDIR

Description Specifies the destination directory for a new agent installation. The directory does not have to exist.
Valid Values The installation creates the Panorama directory and subdirectories in the parent directory you specify.

Default Value Any valid local Window directory specification. The specification must include a local drive letter. Do
Example not specify a mapped drive or UNC path.

If you specify this option within the /v argument to the installation executable (see “General Syntax“)
and the directory specification contains spaces, enclose it with \" (see the example below). The
backward slashes ( \ ) are escape characters for the double quotation marks ( " ) that must enclose the
directory specification. The escape characters are not required (or allowed) if you specify the option
directly as an argument to msiexec (see “Run msiexec with the MSI and Transform Files“).

C:\

INSTALLDIR=d:\
INSTALLDIR=\"c:\Riverbed Technology\"

Riverbed SteelCentral AppInternals Version 10.0 21

Unattended Agent Installation: Windows

O_SI_ANALYSIS_SERVER_HOST

Description Specifies the location of the AppInternals analysis server. The agent connects to this system to initiate
communications. Use this option for new installations only. See “Changing the Agent’s Analysis
Valid Values Server“ for instructions on changing this value after the agent has been installed.
Default Value
Example The system name, fully-qualified domain name (FQDN), or IP address for the analysis server.

none

O_SI_ANALYSIS_SERVER_HOST=myserver.example.com
O_SI_ANALYSIS_SERVER_HOST=10.46.35.218

O_SI_ANALYSIS_SERVER_PORT

Description Specifies the port on which the AppInternals analysis server is listening. The agent connects to this
port to initiate communications. See “Changing the Agent’s Analysis Server“ for instructions on
Valid Values changing this value after the agent has been installed.
Default Value
Example Valid port numbers for analysis server

80

O_SI_ANALYSIS_SERVER_PORT="8051"

O_SI_ANALYSIS_SERVER_SECURE

Description Specifies whether the connection to the AppInternals analysis server should be secure.
Valid Values true false (values are not case sensitive)
Default Value false
Example
O_SI_ANALYSIS_SERVER_SECURE="true"

O_SI_START_SERVICES

Description Whether to start Windows services for the DSA and sub-agents after the installation completes.
Valid Values START DONTSTART (values are not case sensitive)
Default Value START (any value other than START will cause the services NOT to start)
Example
O_SI_START_SERVICES=DONTSTART

REINSTALL

Description Used only to modify or repair an existing installation. For Microsoft documentation on REINSTALL,
Valid Values visit: http://msdn.microsoft.com/en-us/library/windows/desktop/aa371175%28v=vs.85%29.aspx

ALL (values are not case sensitive)

22 Riverbed SteelCentral AppInternals Version 10.0

Unattended Agent Installation: Windows

Default Value none
Example
REINSTALL=ALL

REINSTALLMODE

Description Used only to modify or repair an existing installation. For Microsoft documentation on
REINSTALLMODE visit:
Valid Values http://msdn.microsoft.com/en-us/library/windows/desktop/aa371182%28v=vs.85%29.aspx
Default Value
Example vamus

None

REINSTALLMODE=vamus

Riverbed SteelCentral AppInternals Version 10.0 23

Unattended Agent Installation: Windows
24 Riverbed SteelCentral AppInternals Version 10.0

CHAPTER 5 Agent Installation: UNIX

The agent and its sub-agents are responsible for the collection and communication of metric and transaction trace data
on each system being monitored by AppInternals.
To install the agent software on UNIX, you run an installation script locally on each agent. The script prompts you for
required information. You can run the script as root or as the user for the “Dedicated Administrative Account“. You
can also install the agent software in silent mode, as described in “Unattended Agent Installation: UNIX“.
This chapter describes using the script as well as steps before and after installation.

Installation Prerequisites

This section presents general installation requirements. See the System Requirements for specific patches, maintenance
levels, and other details of supported operating system versions for installing agent software. The system requirements
are available from the AppInternals support page:
https://support.riverbed.com/content/support/software/opnet-performance/appinternals-xpert.html

Disk and Memory

The installation script temporarily extracts files to a directory that you specify before copying them to the installation
directory that you specify.
The installation requires 500 MB of available disk space to install the agent. It issues a warning if there is less than 1
GB of available space.
After installation, disk space requirements depend on the number of applications being monitored, the level of their
activity, and disk usage configuration settings. For more detail, see the System Requirements available from the
AppInternals support page:
https://support.riverbed.com/content/support/software/opnet-performance/appinternals-xpert.html
There is no minimum memory requirement.

Required 32-bit Library on Some 64-Bit Systems

On some 64-bit systems, the agent requires a 32-bit version of the C++ runtime library. See the System Requirements
for details.

Riverbed SteelCentral AppInternals Version 10.0 25

Agent Installation: UNIX

Dedicated Administrative Account

Before installing the agent software, identify a dedicated administrative account to run the agent software. The user
name for the dedicated account can be any name, but it must exist before you install. The installation creates the
Panorama directory and its contents using that account as owner. In addition, you must use the dsactl utility (see
“Using dsactl to Control Agent Software on UNIX“) from that account.
You can install the agent software from the root account or from the administrative account:
 If you run the installation script as root, it prompts you for the name of an account to be the administrative user.
 If you run the installation script from a non-root account, that account will automatically be made the

administrative user. The account must have rights to create the Panorama directory in the parent directory you
specify or the installation fails. In the following example, the user admin did not have rights to create the
directory:

Where do you want to create the Panorama installation directory:/opt
/bin/mkdir: cannot create directory `/opt/Panorama': Permission denied
Creating /opt/Panorama/hedzup/mn failed. Check that admin has write access in /opt/Panorama
Type 'y' to try again or 'n' to exit:

Administrative User Should be In Same Group as Users that Start Applications

If possible, the AppInternals administrative user should be in the same group as users who run Java applications that
AppInternals will monitor. This avoids permission issues:
 The user account that starts Java processes that AppInternals monitors must have read and write access to specific

AppInternals directories. The installation creates those directories with group read and write permissions.
 The AppInternals administrative user must have read access to the transaction trace data generated by

applications. These files are created by the user account that starts the Java process. By default, the JIDA
sub-agent creates the files with permissions that limit access to group members and exclude others from reading
the files. You can change the permissions with which JIDA creates the files in the “UNIX File Creation
Permissions“ settings of the “Configuration Settings Screen“.

Installing Agent Software

The agent installation takes around 10 minutes. The agent installation script includes a self-extracting .tar file that
contains the agent software.
Download the agent installation file from the AppInternals support page:
https://support.riverbed.com/content/support/software/opnet-performance/appinternals-xpert.html.
The installation script is a gzip-compressed file named AppInternals_Collector_<version>_Linux.gz. You must
decompress the file before running it. Running gunzip or a similar utility creates the same file name with no extension.
For example:

[root@nhv1-rh6-1 tmp]# dir
AppInternals_Agent_10.0.00169_Linux.gz
[root@nhv1-rh6-1 tmp]# gunzip AppInternals_Agent_10.0.00169_Linux.gz
[root@nhv1-rh6-1 tmp]# dir
AppInternals_Agent_10.0.00169_Linux

If you plan to install the agent on multiple systems, if possible, copy the extracted script to a disk shared across the
network. This makes installation on multiple systems more convenient.

26 Riverbed SteelCentral AppInternals Version 10.0

Agent Installation: UNIX

You must run the installation script as root or from the account you want to use as the agent administrator (see
“Dedicated Administrative Account“). If you run the script from a non-root account, the agent software will not be
configured to start automatically when the system reboots. See “Enable Agent Software to Start on System Startup“
for details on doing this after the installation.

The installation script creates log files in the <installdir>/Panorama/hedzup/mn/temp directory. You can review the
log files to confirm details of the installation or troubleshoot problems. The file name for the log file is
AppInternals_Xpert_install.<timestamp>.

Information Required for Installation

The following table summarizes the information requested by the agent installation script.

Table 1 Information Required for UNIX Agent Installation

Information Requested Notes

Administrator user account You receive this prompt only if you run the installation script as root (otherwise, the
account that started the script will be the administrative user account). Supply the user
name for the existing account you will use to run the agent and sub-agents on this system.
See the “Dedicated Administrative Account“ for more details.

Temporary and installation The installation script prompts for the location of two directories.
directories
• A temporary directory where the installation script extracts files. The default is /tmp/.
The installation creates the temporary directory (named
AppInternals_Xpert_Collector_<version>_<os>) in the parent directory you specify.
This directory is deleted after the installation.

• The actual installation directory. The installation script creates the Panorama directory
and subdirectories in the parent directory you supply.

If you run the installation from an account other than root, the account must have
privileges to create both directories, or the installation fails.

If you provide a relative path, the script appends it to the current directory and creates the
directory there. If you provide an absolute path, the script creates the directory there.

Analysis server location Specify the system name, fully-qualified domain name (FQDN), IP address for the analysis
server. If the analysis server name changes after you install the agent, you must change this
name as described in the Help topic “Changing the Agent’s Analysis Server“.

Whether to display a An important configuration task after installing is to enable instrumentation for Java
summary of options for processes you want to monitor. There are different approaches to enabling instrumentation,
enabling instrumentation and you can choose to display a summary of the options after the installation finishes. The
configuration Help topic “Enabling Instrumentation of Java Processes“ describes the
options in detail.

Whether to enable automatic You receive this prompt only under these conditions:
system-wide instrumentation • You run the installation script as root.

• You choose to display the summary of options for enabling instrumentation.

One of the options to enable instrumentation is to run a script that requires root access.
Under these conditions, the installation prompts asks if you want to run that script.

Installing as root

Respond to the prompts with the required information (see Table 1). The prompts indicate default values in brackets [
]. The following example shows required input and responses in bold.

[root@nhv1-rh6-1 tmp]# ./AppInternals_Agent_10.0.00169_Linux

Riverbed SteelCentral AppInternals Setup Menu:

Riverbed SteelCentral AppInternals Version 10.0 27

Agent Installation: UNIX

1) Install
2) Upgrade
3) Exit

Select one of the options above and press enter:
1
The installation creates a temporary directory (AppInternals_Xpert_Collector_10.0.00163_Linux_Kit
). Where do you want to create it [/tmp]?

The installation extracts files to the temporary directory:

Riverbed SteelCentral AppInternals tar-file extracted successfully
Uncompressed instrumentation.tar.gz in /tmp/AppInternals_Xpert_Collector_10.0.00163_Linux_Kit
Unpacking instrumentation...
Extracted instrumentation.tar to /tmp/AppInternals_Xpert_Collector_10.0.00163_Linux_Kit/hedzup/
mn
Removed instrumentation.tar from /tmp/AppInternals_Xpert_Collector_10.0.00163_Linux_Kit/hedzup/
mn
Uncompressed jre.tar.Z in /tmp/AppInternals_Xpert_Collector_10.0.00163_Linux_Kit
Unpacking the Java Runtime Environment (JRE)...
Extracted jre.tar to /tmp/AppInternals_Xpert_Collector_10.0.00163_Linux_Kit/hedzup/mn
Removed jre.tar from /tmp/AppInternals_Xpert_Collector_10.0.00163_Linux_Kit/hedzup/mn

After it extracts files to the temporary directory, the installation displays the following prompts:

 Administrator account

 Installation directory

 Analysis server the agent will connect to

 Whether to display a summary of options for enabling instrumentation

******************** Starting Riverbed SteelCentral AppInternals Installation *******************
*

Enter existing user account to be the Riverbed SteelCentral AppInternals administrator:ksearle
Where do you want to create the Panorama installation directory:/opt

Riverbed SteelCentral AppInternals will be installed in /opt/Panorama. Continue? [y/n]:y
Please enter the Analysis Server Hostname by nodename, FQDN, or IP address: 10.46.35.245
Do you want to review options to enable Java monitoring at the end of the install? [y/n]:y
.
.
.

For root installations only, if you chose to display the options for enabling instrumentation, there is a final prompt about
whether to enable instrumentation system-wide. If you respond yes to the prompt, the installation performs the same
steps as described in “Enable Instrumentation Automatically“ in the “Enabling Instrumentation of Java Processes“
topic.

********* Options for Enabling Java Monitoring ("Instrumentation") *********
*** Option 1: ***
Define the JAVA_TOOL_OPTIONS environment variable in your profile file (such as ~/.profile):

export JAVA_TOOL_OPTIONS="-agentpath:/opt/Panorama/hedzup/mn/\$LIB/librpilj.so $JAVA_TOOL_OPTIO
NS"

*** Option 2: ***
Define the LD_PRELOAD environment variable in your profile file (such as ~/.profile):

export LD_PRELOAD="/opt/Panorama/hedzup/mn/\$LIB/librpil.so $LD_PRELOAD"

*** Option 3: ***
Modify JVM startup options to add -agentpath:

64-bit JVM:
-agentpath:/opt/Panorama/hedzup/mn/lib/librpilj64.so

28 Riverbed SteelCentral AppInternals Version 10.0

Agent Installation: UNIX

32-bit JVM:
-agentpath:/opt/Panorama/hedzup/mn/lib/librpilj.so

*** Option 4: ***
Enable instrumentation automatically system-wide. This is
easiest but adds an entry to the /etc/ld.so.preload system file.
Enable instrumentation automatically system-wide? [no]: yes
Process injection already disabled.
Successfully uninstalled process injection library.
Successfully installed process injection library.
Successfully enabled process injection.

Riverbed SteelCentral AppInternals install completed successfully.

******************** Riverbed SteelCentral AppInternals Post Install Steps ********************

1) Start the Riverbed SteelCentral Agent and Sub-Agents. Log in as 'ksearle' and run:
/opt/Panorama/hedzup/mn/bin/dsactl start

Installing as Non-root

Respond to the prompts with the required information (see Table 1). The prompts indicate default values in brackets
[]. The following example shows required input and responses in bold.

-bash-4.1$ ./AppInternals_Agent_10.0.00176_Linux

Riverbed SteelCentral AppInternals Setup Menu:

1) Install
2) Upgrade
3) Exit

Select one of the options above and press enter:

1
The installation creates a temporary directory (AppInternals_Xpert_Collector_10.0.00176_Linux_Kit
). Where do you want to create it [/tmp]?

At this point, the installation extracts files to the temporary directory and generates several messages:

Riverbed SteelCentral AppInternals tar-file extracted successfully
Uncompressed instrumentation.tar.gz in /tmp/AppInternals_Xpert_Collector_10.0.00176_Linux_Kit
Unpacking instrumentation...
.
.
.

After it extracts files to the temporary directory, the installation displays remaining prompts:
 Installation directory
 Analysis server the agent will connect to
 Whether to display a summary of options for enabling instrumentation

******************** Starting Riverbed SteelCentral AppInternals Installation *******************
*

Where do you want to create the Panorama installation directory:/home/ksearle

Riverbed SteelCentral AppInternals will be installed in /opt/Panorama. Continue? [y/n]:y
Please enter the Analysis Server Hostname by nodename, FQDN, or IP address: 10.46.35.218
Do you want to review options to enable Java monitoring at the end of the install? [y/n]:y

Riverbed SteelCentral AppInternals Version 10.0 29

Agent Installation: UNIX

After you respond to those prompts, the installation completes without further intervention. At the end, it summarizes
options for enabling instrumentation (if you chose to display them) and other “Post-Installation Tasks“.

*** Option 1: ***
Define the JAVA_TOOL_OPTIONS environment variable in your profile file (such as ~/.profile):

export JAVA_TOOL_OPTIONS="-agentpath:/opt/Panorama/hedzup/mn/\$LIB/librpilj.so $JAVA_TOOL_OPTIO
NS"

*** Option 2: ***
Define the LD_PRELOAD environment variable in your profile file (such as ~/.profile):

export LD_PRELOAD="/opt/Panorama/hedzup/mn/\$LIB/librpil.so $LD_PRELOAD"

*** Option 3: ***
Modify JVM startup script to add -agentpath:

64-bit JVM:
-agentpath:/opt/Panorama/hedzup/mn/lib/librpilj64.so

32-bit JVM:
-agentpath:/opt/Panorama/hedzup/mn/lib/librpilj.so

*** Option 4: ***
Enable instrumentation automatically system-wide. This is
easiest but adds an entry to the /etc/ld.so.preload system file.
Run /opt/Panorama/hedzup/mn/bin/instrumentationoptions.sh as root to enable instrumentation syste
m-wide

Riverbed SteelCentral AppInternals install completed successfully.

******************** Riverbed SteelCentral AppInternals Post Install Steps ********************

1) Enable automatic startup on system reboot: Log in as root and run /home/ksearle/Panorama/insta
ll_mn/install_startup.sh
2) Start the Riverbed SteelCentral Agent and Sub-Agents. Run:
/home/ksearle/Panorama/hedzup/mn/bin/dsactl start

-bash-4.1$

Post-Installation Tasks

Start the Agent Software

The installation script does not start the agent software. Log into the user account specified during the installation and
use the dsactl start command:

bash-4.1$ ./dsactl start

Starting all Riverbed SteelCentral AppInternals components...
starting the DSA...

[waiting 10 seconds for the DSA to fully start up]
[started] UID:ksearle PID:9494 dsa -d
[started] UID:ksearle PID:9552 os_agent
bash-4.1$

See “Using dsactl to Control Agent Software on UNIX“ configuration Help topic for details on dsactl.

30 Riverbed SteelCentral AppInternals Version 10.0

Agent Installation: UNIX

Enable Agent Software to Start on System Startup

If you ran the installation script from an account other than root, you must run a script to configure an initialization
script that starts the agent software automatically when the system reboots. (If you installed the agent software from
the root account, the installation script automatically performs this step.)
You must run this script as root. Log in as root and run <installdir>/Panorama/install_mn/install_startup.sh:

[root@vh2-rh5-1 install_mn]# ./install_startup.sh
Installing the system-level automatic startup/shutdown script and links...
Successfully disabled panorama managed node service
Successfully added panorama as a service

The script fails if you are not logged in as root:

bash-3.1$pwd
/usr/Panorama/install_mn
bash-3.1$ # Script fails from non-root accounts:
bash-3.1$ ./install_startup.sh
install_startup.sh: FATAL: You must be running as 'root' to execute this script.
install_startup.sh: FATAL: Unable to continue the install_startup.sh process due to errors.

Enable Instrumentation

An important configuration task is to enable instrumentation for Java processes you want to monitor. The configuration
topic “Enabling Instrumentation of Java Processes“ describes different approaches in detail.

Confirm that the Agent Connected to the Analysis Server

Log in to the analysis server web interface using the host name or IP address specified during installation:

http://<AppInternalsSystem>

The default username and password are both admin. In the Configure menu, navigate to the “Agent List Screen“. You
should see the system listed with the icon for new agents ( ):

Confirm That the System Time Is Synchronized

The AppInternals installation assumes that the system time on all systems (agent and analysis server) is synchronized.
After installing the agent, make sure time is synchronized as described in the “Agent Time Synchronization“
configuration topic.

Riverbed SteelCentral AppInternals Version 10.0 31

Agent Installation: UNIX

Configure the Agent to Run In Secure Red Hat Linux Environments

The Agent may fail to start in Red Hat Enterprise Linux 5 systems running Security-enhanced Linux (SELinux). When
you run the dsactl start dsa command, the DSA does not start and there is no log file created:

$ dsactl start dsa
Starting selected SteelCentral AppInternals components...
starting the DSA...
[waiting 10 seconds for the DSA to fully start up]
[stopped] dsa

The problem occurs because the Java library libjvm.so requires text relocation. SELinux has a set of default security
rules that allow the library to do this. However, those rules do not apply to the Java Runtime Environment (JRE)
installed with the DSA.
To allow the DSA to run, you need to change the security context on the copy of libjvm.so installed with the DSA to
allow text relocation. Log in as root and use the following command:

chcon -t textrel_shlib_t <installdir>/Panorama/hedzup/mn/jre/lib/i386/server/libjvm.so

To verify that the DSA can run, use the ls –alZ command to check that the security context on libjvm.so includes
textrel_shlib_t. For example:

$ ls -alZ /riverbed/Panorama/hedzup/mn/jre/lib/i386/server/libjvm.so
-rwxr-xr-x oracle oinstall system_u:object_r:textrel_shlib_t
/riverbed/Panorama/hedzup/mn/jre/lib/i386/server/libjvm.so

See the following link for details on why the Java library requires text relocation:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6538311

Removing Agent Software

Before removing the agent, you must manually stop Java applications that AppInternals is monitoring. Otherwise, the
installation will not be able to delete files they have locked. Check the web interface “Bulk Configuration Screen“ to
see which processes you need to stop.
You must be logged in as root or as the user specified as the agent administrator (see “Dedicated Administrative
Account“) to remove or upgrade agent software. However, with a non-root user, the installation script first checks for
the presence of files that require root access to delete. If any of the following files are present, the installation script
will not allow non-root users to proceed:
 The librpil.so shared object in the /lib and /lib64 system directories. These files allow automatic instrumentation

of Java applications when they start.
 The appinternals script in the /etc/init.d/ system directory. This script starts AppInternals automatically when the

system reboots.
In this case, you must either run the installation script as root, or run the script
<installdir>/Panorama/uninstall_mn/uninstall_root_required.sh as root. This script removes the files requiring root
access. After you run uninstall_root_required.sh as root, you can remove or upgrade the agent as the non-root agent
administrator.
To remove agent software, run the uninstall script in the <installdir>/Panorama/uninstall_mn directory.

[root@nhv1-rh6-1 uninstall_mn]# ./uninstall
Do you want to uninstall Riverbed SteelCentral AppInternals 10.0.0? [y/n]:y
Successfully disabled process injection.
Process injection already disabled.
Successfully uninstalled process injection library.

32 Riverbed SteelCentral AppInternals Version 10.0

Agent Installation: UNIX

Stopping all Riverbed SteelCentral AppInternals components...
stopping the DSA...
stopping the DSA...
stopping the DSA...
stopping the DSA...
[ok]

[stopped] dsa
[stopped] os_agent
Uninstalling the system-level automatic startup/shutdown script and links...
/etc/init.d/appinternals was removed successfully

Riverbed SteelCentral AppInternals uninstall completed successfully.

******************** Riverbed SteelCentral AppInternals Post Uninstall Steps ********************

Change to different directory (i.e. cd ..) and execute /bin/rm -rf /opt/Panorama/uninstall_mn to
completely remove Riverbed SteelCentral AppInternals Collector files
[root@nhv1-rh6-1 uninstall_mn]#

The uninstall script deletes the <installdir>/Panorama/hedzup/mn directory and its descendants. You need to
manually delete the Panorama directory and any remaining descendants.

Upgrading Agent Software

Upgrades to Version 10.0 from earlier versions of AppInternals agent software (called “managed node’ or “collector”)
are not supported.

The Upgrade option of the installation script replaces executable and program files for agent software while
preserving configuration settings and data.

Before upgrading the agent, you must manually stop Java applications that AppInternals is monitoring. Otherwise, the
installation will not be able to delete files they have locked. Check the web interface “Bulk Configuration Screen“ to
see which processes you need to stop.

You must be logged in as root or as the user specified as the agent administrator (see “Dedicated Administrative
Account“) to remove or upgrade agent software. However, with a non-root user, the installation script first checks for
the presence of files that require root access to delete. If any of the following files are present, the installation script
will not allow non-root users to proceed:

 The librpil.so shared object in the /lib and /lib64 system directories. These files allow automatic instrumentation
of Java applications when they start.

 The appinternals script in the /etc/init.d/ system directory. This script starts AppInternals automatically when the
system reboots.

In this case, you must either run the installation script as root, or run the script
<installdir>/Panorama/uninstall_mn/uninstall_root_required.sh as root. This script removes the files requiring root
access. After you run uninstall_root_required.sh as root, you can remove or upgrade the agent as the non-root agent
administrator.

As described in “Installing Agent Software“, decompress the installation script before upgrading. Choose the Upgrade
option, and the script prompts for the location of a temporary directory to extract files. The following example shows
required input and responses in bold.

bash-4.1$ ./AppInternals_Agent_10.0.1187_Linux

Riverbed SteelCentral AppInternals Setup Menu:

Riverbed SteelCentral AppInternals Version 10.0 33

Agent Installation: UNIX

1) Install
2) Upgrade
3) Exit
Select one of the options above and press enter:
2
The installation creates a temporary directory (AppInternals_Agent_10.0.1187_Linux_Kit). Where do
you want to create it? [/tmp]:

At this point, the upgrade extracts files to the temporary directory. It then prompts for whether you want to continue:

Stop all Java processes that were being monitored by AppInternals (they lock files you want to re
move).
Do you want to upgrade Riverbed SteelCentral AppInternals from 10.0.0 10.0.0_BL176 to 10.0.1187 1
0.0.1_BL187? [y/n]:y
Stopping all Riverbed SteelCentral AppInternals components...

stopping the DSA...
stopping the DSA...
[ok]
[stopped] dsa
[stopped] os_agent

If the upgrade detects Java processes and JIDA log files, it prompts you to make sure that no instrumented Java
processes are running. Note that this message appears even if you have stopped all instrumented Java processes. It only
means that there is a Java process running on the system that may or may not be instrumented:

The uprade process found JIDA log files and at least one running Java process. The upgrade will n
ot update JIDA if it is running. Shut down any applications instrumented with JIDA before continu
ing.
Answer 'y' to continue or 'n' to terminate Riverbed SteelCentral AppInternals upgrade [y/n]:y
/home/ksearle/Panorama/hedzup/mn/userdata already exists. No files will be moved.
Riverbed SteelCentral AppInternals file transfer to /home/ksearle/Panorama/ was successful
Riverbed SteelCentral AppInternals upgrade completed successfully.
******************** Riverbed SteelCentral AppInternals Post Install Steps ********************
1) Enable automatic startup on system reboot: Log in as root and run /home/ksearle/Panorama/inst
all_mn/install_startup.sh
2) Start the Riverbed SteelCentral Agent and Sub-Agents. Run:
/home/ksearle/Panorama/hedzup/mn/bin/dsactl start
bash-4.1$

34 Riverbed SteelCentral AppInternals Version 10.0

CHAPTER 6 Unattended Agent Installation: UNIX

This section describes how to automate the installation of agent software by specifying options in a response file and
invoking the agent installer with the -silent argument.
Unattended installations are supported for new installations only. You cannot remove or upgrade an agent with the
-silent argument.

Download and Decompress the Agent Installation

Download the agent installation from the AppInternals download page:
https://support.riverbed.com/content/support/software/opnet-performance/appinternals-xpert.html.
The agent installer is a gzip-compressed file named AppInternals_Collector_<version>_Linux.gz. Decompress the
file with gunzip or a similar utility. This creates the same file name with no extension. For example:

[root@nhv1-rh6-1 tmp]# ls -al AppInternals_Agent_10.0.1.7_Linux*
-rwxr-xr-x 1 root root 82281878 Jun 25 11:39 AppInternals_Agent_10.0.1.7_Linux.gz
[root@nhv1-rh6-1 tmp]# gunzip AppInternals_Agent_10.0.1.7_Linux.gz
[root@nhv1-rh6-1 tmp]# ls -al AppInternals_Agent_10.0.1.7_Linux*
-rwxr-xr-x 1 root root 82550447 Jun 25 11:39 AppInternals_Agent_10.0.1.7_Linux
[root@nhv1-rh6-1 tmp]#

Create a Response File

The -silent argument to the agent installer requires that you specify the name of a response file. This section describes
extracting the AppInternals kit to a temporary directory and adapting a template to create the response file.
However, once you have a response file, you can simply use it by invoking the agent installer directly without
extracting kit files.

1) Use the -extract argument with the agent installer to extract the kit contents to a temporary directory you specify.
For example, to extract to /tmp:

Riverbed SteelCentral AppInternals Version 10.0 37