Use Introscope Installers

You use installers and other files to install Introscope components. When getting ready for your CA APM installation or upgrade, you download the correct installers for Introscope. Due to the Introscope multi-tier architecture, separate installers exist for each component to install. The components run on various platforms, and your deployment plan affects which components you install on which computers.
apmdevops106
You use installers and other files to install Introscope components. When getting ready for your CA APM installation or upgrade, you download the correct installers for Introscope. Due to the Introscope multi-tier architecture, separate installers exist for each component to install. The components run on various platforms, and your deployment plan affects which components you install on which computers.
2
The configuration settings that you specify during the installation include persisted properties files or other configuration artifacts that you can edit manually post-installation. Most configuration files reside in the
<EM_Home>
\config directory.
To perform a fresh installation or to upgrade an existing installation, use the Introscope installers. You can back up and restore customizations and other artifacts from your existing installation during an upgrade. Introscope installers supply default values for key configuration settings, such as:
  • The ports that components use to communicate
  • Location and aging rules for data stores
  • JVM options
    If you plan to configure settings other than the default port assignments or the bundled JVM, determine the preferred values before starting the installation.
Either accept the default settings or supply your own, as appropriate.
Several Introscope installers are available:
  • Enterprise Manager installer
    Installs the Enterprise Manager, WebView, and databases (SmartStor, Transaction Event, baseline, and the APM database).
    This installer also provides files that are needed for extensions; you enable and configure these files to use the extensions. You can install all components, or select only desired components to install.
    For information about enabling and configuring an extension, see the documentation for that extension.
  • Introscope Workstation installer
    Installs only the Introscope Workstation and connects to an existing Enterprise Manager. This installer also installs some files for ChangeDetector.
  • Introscope Standalone agent installer
    Installs the Environment Performance Agent (EPAgent) or standalone extensions.
    In addition to the Enterprise Manager or agents, some extensions also have components that you install independent from the Java or .NET agents. For example, these components need files that are installed where a web server or database is installed. Use the Standalone agent installer to install these additional components.
    The Standalone Agent installer also performs some initial Enterprise Manager configuration for a specified extension. To enable an extension, consult the user guide for the extension.
  • Introscope Workstation Java Web Start
    Enables online installation and automatic updates of the Workstation, so that end users have the version of the Workstation that matches the Enterprise Manager.
  • Introscope SAP installer
    Installs certain customized files, ports, and SAP-specific components. This installer is for SAP NetWeaver users to whom SAP distributes Introscope components.
For information about the agent installation, see the and
Enterprise Manager Installers
The following table lists the installer file and installer archive files that are available for each operating system:
OS
Installer
RedHat Enterprise /LinuxSuSE Linux Enterprise
Linux 64-bit
introscope<
version
>linuxAMD64.bin
Windows 64-bit
introscope<
version
>windowsAMD64.exe
Note:
If you are installing on a 64-bit computer and you want to run the Enterprise Manager on a 64-bit JRE, use this installer archive. Despite the name, the brand of chipset does not matter.
Solaris
introscope<
version
>solarisSparc.bin
AIX
introscope10.7.0.45aix64.tar
Other UNIX
introscope<
version
>otherUnix.jar
Use this installer for UNIX platforms on which the bundled JVM Linux installer is not supported, such as:
Linux/PPC
Linux on SystemZ
Linux/390
Note:
For information, see the Product Compatibility Matrix.
Consider the following information about the Enterprise Manager installer:
  • Some distributions of the Enterprise Manager installer include the Introscope agent. These archives have filenames ending with install.zip or install.tar. However, the installer does not install the agent.
    For more information, see the and
  • If you are installing a PostgreSQL database instance for the APM database, the operating system user account that you use to install must have permission to create users. On Windows, the installer can install PostgreSQL only from a direct login or console session. You cannot install PostgreSQL by way of terminal services.
  • Before an Enterprise Manager or WebView installation, pause any antivirus services that continuously scan the file system. Resume the antivirus service after the installation is complete. If you do not pause the service, the file scanning service can lock new or temporary files as soon as the installer creates them. Installation errors can occur as a result.
The Workstation-only Installers
The following Workstation-only installer files are available for your operating system:
  • Windows
    -- IntroscopeWorkstation<
    version
    >windows.exe
  • Linux
    -- IntroscopeWorkstation<
    version
    >linux.bin
The Standalone Agent Installers
The following Standalone agent installer files and installer archive files are available:
  • Windows
    -- IntroscopeStandaloneAgentPPInstaller<
    version
    >windows.exe
  • UNIX
    -- IntroscopeStandaloneAgentPPInstaller<
    version
    >unix.bin
SAP Installers
The following table lists the SAP Enterprise Manager installer files and installer archive files for each operating system:
Operating System
Installer Filename
Windows
introscope<
version
>windowsAMD64SAP.exe
Solaris
introscope<
version
>solarisSparcSAP.bin
AIX
introscope<
version
>aix64SAP.bin
Linux
introscope<
version
>linuxAMD64SAP.bin
Other UNIX
introscope<version>otherUnixSAP.jar
Use this installer to install Introscope on other UNIX platforms that are otherwise not listed here or in the Product Compatibility Matrix.
The SAP Enterprise Manager installers install Enterprise Manager components. The following extensions are handled differently from the Enterprise Manager installer:
  • ChangeDetector, ErrorDetector, LeakHunter, and SNMP Adapter, and CA Cross-Enterprise Application Performance Management extensions are installed but not enabled.
  • CA APM for SOA is enabled by default.
  • The following SOA extensions are installed but not enabled:
    • SOA Extension for webMethods Integration Server
    • SOA Extension for TIBCO BusinessWorks
    • SOA Extension for Oracle Service Bus
  • Other extensions are not installed.
  • Console mode installation is not supported for SAP end users. If you are installing Introscope on an SAP end-user computer, use silent install mode.
  • The SAP Enterprise Manager installer comes bundled with additional JVMs.
The following table lists the SAP workstation installers for each operating system:
Operating System
Installer Filename
Windows
IntroscopeWorkstation<
version
>windowsAMD64SAP.exe
IntroscopeWorkstation<
version
>windowsSAP.exe
Linux
IntroscopeWorkstation<
version
>linuxAMD64SAP.bin
IntroscopeWorkstation<
version
>linuxSAP.bin
Introscope Bundled JVMs
The Java Virtual Machine is bundled with the Introscope installers on Sun Solaris, Windows, AIX, and Red Hat Linux. By default, an Introscope component runs on the JVM with which it is bundled. You can specify that a component use a different JVM during the installation process. The JVM bundled with Introscope depends on the operating system where you install the component.
For the list of supported versions, see the Product Compatibility Matrix.
Run an Installer with an Alternate JVM
For most platforms, JVM is bundled with and installed by the installer.
We recommend that you start the installer with a JVM that meets the minimum requirements for the components you are installing.
Follow these steps:
  1. Navigate to the installer directory.
  2. Run the following command in the installer directory:
    <installerName>.[exe|bin] LAX_VM <path to alternate JVM>
Specify an Alternate JVM for the Enterprise Manager or WebView
By default, Enterprise Manager and WebView use the JVM installed in
<EM_Home>
/JRE. You can designate Enterprise Manager WebView to use an alternate JVM to run. If you specify an alternate JVM, it must be version 1.7 or above. In particular, this applies to installations that require you to specify an existing JVM to run the installer.
JRE and JVM are used interchangeably to refer to the same Java executable.
Follow these steps:
  1. Before a silent install, configure these properties in the response file:
    • emLaxNlCurrentVm property (for Enterprise Manager)
    • wvLaxNlCurrentVm property(for WebView)
  2. Do one of the following procedures:
    • During the GUI installation, provide the installer with an alternate path to the JVM.
    • After an installation, edit the .LAX files for Enterprise Manager or WebView.
      1. Open the Introscope_Enterprise_Manager.lax or WebView.lax files for editing.
      2. Edit the LAX.NL.CURRENT.VM property to point to a different JRE.
      3. Save and close the file.
      4. Restart the Enterprise Manager or WebView.
      The change takes effect.
If you specify a 64-bit JVM, the uninstaller does not work. In this situation, restore the default JVM and then uninstall.