Launch the Installer

The installer is available on Windows, UNIX, or other systems. You can launch the installer in either GUI or console mode. You can run the installer automatically with a response file.
apmdevops97
The installer is available on Windows, UNIX, or other systems. You can launch the installer in either GUI or console mode. You can run the installer automatically with a response file.
2
Launch the Installer in GUI Mode on Windows
You can start the installer in GUI Mode on Windows. Use the installer that corresponds to the file type for your platform.
Follow these steps:
  1. Locate the installer .exe file.
  2. Double-click the file or invoke the installer from the command line:
    c:> .\Install.exe
    Substitute the file name for
    Install
    .exe.
Launch the Installer in GUI Mode on UNIX with a Desktop Environment
On a UNIX system, you can run the installer in GUI mode from any shell that has a windowing environment available. You use a .BIN or .JAR file to start the CA APM installer on a system that has a desktop environment.
Before you begin, determine the .JAR installer disk space.
Follow these steps:
  1. Open a command shell.
  2. Start the installer from a command line:
    • For an installer with a .BIN file extension:
      ./install.bin -i swing
      install
      .bin is the installer archive appropriate for your system.
    • For an installer with a .JAR file extension, specify the appropriate JVM (.JAR installers do not include a bundled JVM):
      [root:/] /usr/java/bin/java -classpath <InstallerName>.jar install -i swing
Launch the Installer in GUI Mode on UNIX without a Desktop Environment
On a UNIX system without a desktop, you can run the Introscope installer in GUI mode from any shell that has a windowing environment available.
Before you begin, determine the .JAR installer disk space.
Follow these steps:
  1. Copy the
    install
    .bin (the installer archive appropriate for your system) to the system where you want to install Introscope.
  2. Locate a separate system that does have an X windowing environment. For example, a Linux server, or a Windows system with Cygwin/X installed.
  3. Log in to the desktop of this second system.
  4. Open a terminal shell.
  5. Type the following command:
    xhost + <headless computer hostname or IP address>
    An Xsession starts on your local, windowing-capable system.
  6. From the terminal shell, use SSH or telnet to connect and log in to the headless system as a user.
  7. In the SSH or telnet session, type the following commands to set up the display:
    [root@headlessbox] DISPLAY=<Xserver.computer.hostname.or.IP.address>:0.0 [root@headlessbox] export DISPLAY [root@headlessbox] echo $DISPLAY
  8. In the SSH or telnet session, launch the installer in swing mode with the command:
    ./install.bin -i swing
    The installer introduction screen opens on your local desktop.
  9. Proceed with the installation.
    The installation completes.
  10. End the SSH or telnet session.
  11. Type the following command:
    xhost - <headless computer hostname or IP address>
    Your windowing-capable system returns to its previous state.
Launch .BIN Installers in Console Mode
.BIN installers are available for the Solaris, AIX, and Red Hat Linux platforms.
Follow these steps:
  1. Open a command line.
  2. Type the following command:
    <path to installer> -i console
    Example:
    [root@server:/sw/downloads] ./introscope9.0.x.solaris.bin -i console
    Note
    : The -i console flag is not necessary on Linux.
Launch .JAR Installers in Console Mode
.JAR installers are available for UNIX platforms. You can launch a .JAR installer (without a bundled JVM) in console mode.
Follow these steps:
  1. Verify that the computer has sufficient disk space to run the .JAR installers.
  2. Open a command line.
  3. Enter the following command and specify your JVM:
    [root:/] /usr/java/bin/java -classpath <installerfilename>.jar install - i console
    Use a flag to force the console mode, because Swing mode is the default for .JAR files.
Install Introscope in Silent Mode
You can install or upgrade Introscope in silent mode. Silent mode installation makes multiple installations or upgrades of Introscope easy. In silent mode, the installer runs from a command line and takes input from a response file. The silent mode installer runs in the background with no feedback. After installation, you can view the results in the installer logs.
If you are upgrading an existing Introscope installation, before performing a new installation.
Silent mode is supported on all platforms.
Silent Mode Installation Overview
Here is an overview of the silent installation process:
  1. Edit the response file.
  2. Edit the ca-eula.txt and eula.txt files.
  3. Run the installer from the command line, pointing to the response file.
Use a Response File
Instead of asking the user for input during the installation process, the silent install takes input from a prepared response file.
You can use an automatically generated response file, or modify the sample response file provided with your installation.
If you run any of the Introscope installers in silent mode, the response file that you specify must be in ASCII format. Response files in UTF-8 format are not supported. For example, if you use a UTF-8 response file and specify folder names in Japanese, the installer creates folders with incorrect and illegible characters.
Sample Response File
You can edit a sample response file with the settings you want to use during installation. Then you can use this file for subsequent silent mode installs. The sample response file is found in:
<EM_Home>/examples/installer/SampleResponseFile.txt
The response file can have any name, and can be located in any directory. You specify the name and location in the command line when invoking silent mode for the installer.
The properties in the response file are similar to those properties in the usual properties files.
Automatically Generated Response File
The automatically generated response file is created when Introscope is installed. This file contains the settings that you specified during the install process. You can use this response file for subsequent silent mode installations or upgrades.
The file, in the
<EM_Home>
/install/ directory, is named using the date and time information of the last installation. For example, an installation done April 30, 2010 at 7:10:00 a.m. would have a response file with this name:
<EM_Home>/install/autogenerated.responsefile.2010.4.30.7.10.00
Response File Guidelines
When specifying directory paths, follow these guidelines:
  • On Windows, escape backslash characters. For example:
    C:\\Program Files\\CA\\Introscope9.1.0.0\\
  • On UNIX, append a slash to directory names. For example:
    /tmp/APM/Introscopedirectory/
  • Uncomment the properties that configure the JVM settings.
  • If you specify a relative path, make it relative to the installer launch directory.
Download and Edit External Files
Before starting the installation process, you must download third-party external component package files, then edit two End User License Agreements (EULA).
The installation cannot proceed unless you follow these steps.
Note the location on your network of the downloaded files. You supply this location in the response file.
Edit the eula.txt and ca-eula.txt Files
Signify acceptance of both End User License Agreements (EULA).
To edit the eula.txt file to agree to the EULA
  1. Open the eula.txt file.
  2. Read the agreement.
  3. If you agree to the terms and conditions of the agreement, edit the LGPL property (located at the end of the file) to:
    LGPL=accept
  4. Save and close the file.
To edit the ca-eula.txt file to agree to the EULA
  1. Open the ca-eula.txt file.
  2. Read the agreement.
  3. If you agree to the terms and conditions of the agreement, edit the CA-EULA property (located at the end of the file) to:
    CA-EULA=accept
  4. Save and close the file.
Enterprise Manager Installer Silent Mode Settings
This section contains information about the properties you must specify to install CA APM components silently without user interaction.
General Settings
This section describes the properties in the General Settings section of the installer response file.
USER_INSTALL_DIR
Specifies the directory where to install Introscope.
Property settings
The absolute path and directory name. On Windows, to enter a backslash, enter an extra backslash as an escape sequence. Paths must be absolute and end with a directory separator. If no directory is specified, the defaults are used. On UNIX, the directory is under the user home directory. On Windows, the exact drive letter and name of the Program Files directory may vary depending on the Windows configuration.
Default
UNIX: /root/Introscope<version>/
Windows: C:\\Program Files\\CA\\Introscope<
version
>\\
Example
USER_INSTALL_DIR
=C:\\IntroscopeSilentInstall\\
silentInstallChosenFeatures (Enterprise Manager Installer)
A comma-separated list of the features to install using the Enterprise Manager installer.
Property settings
Enterprise Manager, WebView, ProbeBuilder, Database
"Database" refers to the APM database. For more information about this database, see the
CA APM Configuration and Administration Guide.
Default
silentInstallChosenFeatures=Enterprise Manager,WebView,ProbeBuilder
Example
silentInstallChosenFeatures=Enterprise Manager,WebView,ProbeBuilder,Database
externalComponentPackage
Specifies the location of the external component package.
If you are installing the Enterprise Manager, WebView, or Workstation, you must also specify the external component package location.
Property settings
The absolute or relative path to the external component packages. Introscope resolves the relative path based on the installer launch directory. On Windows, to enter a backslash, enter an extra backslash as an escape sequence. You can download the external component packages from http://opensrcd.ca.com/ips/osgi.
Default
There is no default setting for this property.
Example
Windows: C:\\osgiPackages.v<
x.y.z
>.windows.zip
UNIX: /osgiPackages.v<
x.y.z
>.unix.tar
<x.y.z>
is a valid version string.
eulaFile
The location of the external component library's End User License Agreement (EULA), a file named eula.txt. The file is usually located in the same directory as the externalComponentPackage location.
If you are installing the Enterprise Manager, WebView, or Workstation, use this setting to specify the EULA file location.
In addition to specifying the location of the EULA file, edit the EULA file to agree to the license agreement.
Property settings
The absolute or relative path to the external component package’s end user license agreement (EULA) file. Introscope resolves the relative path, which is based on the installer launch directory. On Windows, to enter a backslash, enter an extra backslash as an escape sequence.
In order to install the product, acknowledge and accept the EULA. To acknowledge and accept the agreement, open the file in a text editor and read the terms and conditions. Edit the end of the file to indicate acceptance of the license and save your changes. Use this eulaFile property to specify the location of the edited file.
Default
This property has no default setting.
Example
Windows: C:\\Documents and Settings\\eula.txt
UNIX: /home/myuser/eula.txt
ca-eulaFile
Location of the CA End User License Agreement (EULA), a file named ca-eula.txt. The file is usually located in the same location as the main and workstation installers. If you are installing the Enterprise Manager, WebView, or Workstation, use this setting to specify the file location.
In addition to specifying the location of the EULA file, edit the EULA file to agree to the license agreement.
Property settings
The absolute or relative path to the CA end-user license agreement (CA-EULA) file. Introscope resolves the relative path, which is based on the installer launch directory. On Windows, to enter a backslash, enter an extra backslash as an escape sequence.
In order to install the product, acknowledge and accept the CA-EULA. To acknowledge and accept the agreement, open the file in a text editor and read the terms and conditions. Edit the end of the file to indicate acceptance of the license and save your changes. Use this ca-eulaFile property to specify the location of the edited file.
Default
This property has no default setting.
Example
Windows:
ca-eulaFile=C:\\Documents and Settings\\ca-eula.txt
UNIX:
ca-eulaFile=/home/myuser/ca-eula.txt
Upgrade Settings
This section describes settings listed in the Upgrade Settings section of the installer response file.
shouldUpgrade
Specifies whether to upgrade an existing Introscope installation.
The upgrade procedure is not reversible. CA Technologies recommends creating a full backup of your Introscope installation before initiating an upgrade.
To do an upgrade in silent mode, specify the following other properties:
  • USER_INSTALL_DIR
  • externalComponentPackage
  • eulaFile
  • ca-eulaFile
  • (Optional) upgradedInstallDir
  • (Optional) shouldConfigEmAsService, emAsServiceName, emAsServiceDisplayName
Property settings
True or false
Default
shouldUpgrade=false
Example
shouldUpgrade=true
upgradedInstallDir
Specifies a new Introscope installation directory, for the following types of installations:
  • The installation does not include the APM database
  • The installation includes the APM database, which is installed in a directory separate and outside from the Enterprise Manager installation directory.
If upgrading an existing Introscope installation, use this property to rename the installation directory for the aforementioned types of installations only. If the existing installation has the APM database installed within the Enterprise Manager installation directory, the option to rename the installation directory is not available. If you specify a value for upgradedInstallDir but the option is not available, the installer ignores this setting.
If you specify a directory and you do not have permission to write to that directory, the silent upgrade fails.
Property settings
The absolute path and directory name. On Windows, to enter a backslash, enter an extra backslash as an escape sequence. Paths must be absolute and end with a directory separator. If no directory is specified, the defaults are used. On UNIX, the directory is under the user home directory. On Windows, the exact drive letter and name of the Program Files directory may vary depending on the Windows configuration.
Default
There is no default setting for this property.
Example
Windows: C:\\IntroscopeSilentlyUpgradedInstall\\
UNIX: /IntroscopeSilentlyUpgradedInstall/
Enterprise Manager Install Settings
This section describes the settings in the Enterprise Manager Install Settings section of the installer response file.
emPort
The port used by the Enterprise Manager to listen for incoming connections.
Property settings
A valid, available port number.
Default
5001
6001 for SAP
Example
emPort=5030
emWebPort
The emWebPort property specifies the port that the Enterprise Manager uses to serve web applications.
This port is also the one that Java Web Start uses.
Property settings
A valid, available port number.
Default
8081
Example
emWebPort=8050
Enterprise Manager Silent Mode Clustering Settings
This section describes the properties listed in the Enterprise Manager Clustering Settings section of the installer response file.
shouldClusterEm
Specifies whether the Enterprise Manager is part of a cluster.
Property settings
True or false. True specifies the Enterprise Manager is in a cluster.
Default
False
Example
shouldClusterEm=true
emClusterRole
For Enterprise Managers that are part of a cluster, this property specifies whether the Enterprise Manager is a Collector, a Manager of Managers (MOM), or a Cross-cluster Data Viewer (CDV).
Property settings
Valid entries are "Collector", "Manager", or "CDV". Values are case-sensitive (no quotes).
Default
This property has no default setting.
Example
emClusterRole=Collector
emCollectorHost.n and emCollectorPort.n
If installing an Enterprise Manager as a MOM, use the emCollectorHost and emCollectorPort properties to specify up to ten managed collectors that are managed by the MOM. For each Collector, specify a pair of these properties with a unique number.
If emClusterRole is Manager, specify the host and port for up to ten managed collectors. Each pair must have a unique numeral for its pair. The limit is 10 pairs.
Property settings
Specify the fully qualified hostname for emCollectorHost and a valid, available port number for emCollectorPort. Each pair of emCollectorHost and emCollectorPort must have a unique number.
Default
There are no default settings for these properties.
Example
emCollectorHost.1=myManagedEm.mydomain.com emCollectorPort.1=5005 emCollectorHost.2=computerName.domain.com emCollectorPort.2=5006
Enterprise Manager Transaction Storage Settings
This section describes the properties listed in the Enterprise Manager Transaction Storage Settings section of the installer response file.
emTxTraceDataShelfLife
Specifies the fixed length of time (in days) to store trace data to disk.
Default
14 (days)
Example
emTxTraceDataShelfLife=30
emTxTraceDir
Specifies a customized directory name in which to store transaction trace data. On Windows, to enter a backslash, enter an extra backslash as an escape sequence. The directory path can be absolute or relative to <
EM_Home
>.
Default
emTxTraceDir=traces
Example - Windows
emTxTraceDir=traces\\myTsxnTraces
Example - UNIX
emTxTraceDir=traces/myTsxnTraces
emTxTraceDiskSpaceCap
The maximum amount of disk space reserved to store transaction trace data. This setting is optional, useful if disk space is a concern.
Default
This property does not have a default setting.
Enterprise Manager Data Storage Settings
Use a separate, dedicated disk or I/O subsystem for SmartStor data to avoid affecting Enterprise Manager performance. See the
CA APM Sizing and Performance Guide
and the spreadsheet
SmartStorSizing.xls
for SmartStor sizing information.
CA Technologies recommends that you install the SmartStor and thread dump directories on separate drives.
emDataStoreDir
Name of the SmartStor directory. On Windows, to enter a backslash, enter an extra backslash as an escape sequence.
  • Default
emDataStoreDir=data
  • Example
emDataStoreDir=SmartStor
emThreadDumpDir
Name of the thread dump directory. On Windows, to enter a backslash, enter an extra backslash as an escape sequence.
  • Default
emThreadDumpDir=threaddumps
  • Example
(Windows) emThreadDumpDir=threaddumps\\storage
(UNIX) emThreadDumpDir=threaddumps/storage
Monitoring Options Settings
The Enterprise Manager installer places files used to monitor specific environments into the <EM_Home>\examples directory. To enable files for a specified environment, set the property to true.
The Enterprise Manager installer creates a separate directory for each extension in the <
EM_Home
>\examples directory. Each extension directory includes the files that you use to install and configure the extension. The extension files in the <
EM_Home
>\examples directory are organized into subdirectories. When you enable an extension, the installer copies the files from the subdirectories in the <
EM_Home
>\examples directory to the matching directory under <
EM_Home
>. For example, <
EM_Home
>\examples\PowerPackForSiteMinder directory contains files in <
EM_Home
>\examples\PowerPackForSiteMinder\config\modules and <
EM_Home
>\examples\PowerPackForSiteMinder\ext\ddtv directories. To enable and use an extension, you perform configurations and possible installations.
The APM Integration Pack for Application Delivery Analysis and CA APM for SOA are enabled by default.
  • shouldEnableAPMIntegrationPackForADA
    Enables the APM Integration Pack for Application Delivery Analysis.
  • shouldEnableCAAPMForOracleDB
    Enables CA APM for Oracle Databases.
  • shouldEnableCAAPMForSharePointPortal
    Enables CA APM for Microsoft SharePoint Portal.
  • shouldEnableCAAPMForWebServers
    Enables CA APM for Web Servers.
  • shouldEnableCAAPMForWebLogic
    Enables CA APM for Oracle WebLogic Server.
  • shouldEnableCAAPMForWebLogicPortal
    Enables CA APM for Oracle WebLogic Portal.
  • shouldEnableCAAPMForWebSphere
    Enables CA APM for IBM WebSphere Application Server for Distributed Environments.
  • shouldEnableCAAPMForWebSpherePortal
    Enables CA APM for IBM WebSphere Portal.
  • shouldEnableCAAPMForWebSphereMQandMB
    Enables CA APM for IBM WebSphere MQ and MB.
  • shouldEnableCAAPMForWebSphereZOS
    Enables CA APM for IBM WebSphere Application Server for z/OS.
  • shouldEnableCAAPMForIBMCTG
    Enables CA APM for IBM CICS Transaction Gateway.
  • shouldEnableCAAPMForIBMzOSExtension
    Enables the CA APM for IBM z/OS.
  • shouldEnableSysview
    Enables CA Cross-Enterprise Application Performance Management.
  • shouldEnableCAAPMForSiteMinder
    Enables CA APM for CA SiteMinder Application Server Agents.
  • shouldEnableCAAPMForSiteMinderSNMP
    Enables CA APM for CA SiteMinder SNMP.
  • shouldEnableCAAPMForSOA
    Enables CA APM for SOA.
  • shouldEnableCAAPMForOSB
    Enables CA APM for Oracle Service Bus.
  • shouldEnableCAAPMForTibcoBW
    Enables CA APM for TIBCO BusinessWorks.
  • shouldEnableCAAPMForTibcoEMS
    Enables CA APM for TIBCO Enterprise Message Service.
  • shouldEnableCAAPMForWPSandWESB
    Enables CA APM for IBM WebSphere Process Server and WESB.
  • shouldEnableCAAPMForWMBroker
    Enables CA APM for webMethods Broker.
  • shouldEnableCAAPMForWebMethodsIS
    Enables CA APM for webMethods Integration Server.
  • shouldEnableAPMIntegrationPackForCM
    Enables CA APM Integration with Cloud Monitor.
  • shouldEnableCAAPMIntegrationForCALISA
    Enables CA APM Integration for CA Application Test.
Enterprise Manager as Windows Service Settings
This section describes the properties listed in the Enterprise Manager as Windows Service Settings section of the installer response file.
shouldConfigEmAsService
Specifies whether to configure the Enterprise Manager as a Windows service.
Property settings
True or false.
Default
shouldConfigEmAsService=false
Example
shouldConfigEmAsService=true
emAsServiceName
If the Enterprise Manager is configured as a service, a unique name for the Service.
Property settings
A text string of eight or fewer characters without spaces.
Default
emAsServiceName=IScopeEM
Example
emAsServiceName=EM7
emAsServiceDisplayName
If the Enterprise Manager is configured as a service, a display name for the Service. May contain spaces.
Property settings
A case-sensitive alphanumeric string.
Default
emAsServiceDisplayName=Introscope Enterprise Manager
Example
emAsServiceDisplayName=Introscope EM1
Enterprise Manager Advanced JVM Settings
This section describes the properties listed in the Enterprise Manager Advanced JVM Settings section of the installer response file. These options should only be configured by advanced users. If you are unsure of the values to enter, keep the defaults by leaving these properties commented out.
emLaxNlCurrentVm
Windows: emLaxNlCurrentVM=jre\\bin\\java.exe
UNIX: emLaxNlCurrentVM=jre/bin/javaPath to the JVM that will be used to run the Enterprise Manager.
Property settings
The path may be absolute or relative to
<EM_Home>
. On Windows, to enter a backslash, enter an extra backslash as an escape sequence.
Default
By default, Introscope points to the JRE folder which is created during the installation. Edit this property if you want to point to an alternate JVM.
Example
Windows: emLaxNlCurrentVM=jre\\bin\\java.exe
UNIX: emLaxNlCurrentVM=jre/bin/java
emLaxNlJavaOptionAdditional
Specifies the optional command-line Java arguments for the Enterprise Manager. With this property, you can specify arguments, such as heap size.
Valid for
: 32-bit, 64-bit Sun JVMs only
Property settings
The following switches are recommended for 32-bit platforms:
-showversion -XX:CMSInitiatingOccupancyFraction=50 -Xss256k
The following switches are recommended for 64-bit platforms:
-Xss512k
If you are using both failover and the CEM console, use the following switch when starting the secondary Enterprise Manager (or second primary):
-Dosgi.clean=false 
Set the lax java option additional values as follows:
-Xms1024m -Xmx1024m -Djava.awt.headless=false -XX:MaxPermSize=256m -Dmail.mime.charset=UTF-8 -Dorg.owasp.esapi.resources=./config/esapi -XX:+UseConcMarkSweepGC -XX:+UseParNewGC lax.nl.java.option.additional=-Xms1024m -Xmx1024m -Djava.awt.headless=false -XX:MaxPermSize=256m -Dmail.mime.charset=UTF-8 -Dorg.owasp.esapi.resources=./config/esapi -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -showversion -XX:CMSInitiatingOccupancyFraction=50 -Xss256k
APM Database Settings
This section describes the settings used to configure the connection from an Enterprise Manager to an APM database. The specific properties you are required to set depend on the database type and whether you are installing a new PostgreSQL database instance, upgrading a database schema, or connecting to an existing database. Also, if you are installing a Cross-cluster Data Viewer (CDV), you do not need to install the APM database.
chosenDatabaseIsPostgres
Specifies whether you want the APM database to be a PostgreSQL database. You must set this property to true if you want to install or upgrade a PostgreSQL database instance on the computer where you run the silent installation. If you want to use an Oracle database, set this property to false.
Property settings
True or False
Default
true
Example
chosenDatabaseIsPostgres=true
chosenDatabaseIsOracle
Specifies whether you want the APM database to be an Oracle database. If you want to create or upgrade the APM database schema using an Oracle database instance, set this property to true. Before you run the Enterprise Manager installer: install and run the Oracle database instance, and create a database user with the proper permissions for creating the APM database schema.
Property settings
True or False
Default
False
Example
chosenDatabaseIsOracle=false
dbHost
Specifies the host name of the computer where the APM database is installed or where the APM database will be installed if you are using PostgreSQL as the database. This property is not applicable if you are using an Oracle database for the APM database schema.
Property settings
A valid IP address.
Default
The default value is the IP address for localhost, 127.0.0.1.
Example
dbHost=192.168.17.201
dbPort
Specifies the port number the Enterprise Manager uses to connect to the APM database if you are using PostgreSQL as the database. This property is not applicable if you are using an Oracle database for the APM database schema.
Property settings
A valid, available port number.
Default
5432
Example
dbPort=5432
dbName
Specifies the name of the APM database schema if you are using PostgreSQL as the database. This property is not applicable if you are using an Oracle database for the APM database schema.
Property settings
A text string that does not contain special or upper-case characters.
Default
cemdb
Example
dbName=cemdb
dbUser
Specifies the name of the database user account if you are using PostgreSQL as the database. This property is not applicable if you are using an Oracle database for the APM database schema.
Property settings
A text string that does not contain special or upper-case characters.
Default
admin
Example
dbUser=admin
dbPassword
Specifies the password for the database user account if you are using PostgreSQL as the database. This property is not applicable if you are using an Oracle database for the APM database schema.
Property settings
A text string that does not contain special or upper-case characters.
Default
wily
Example
dbPassword=qtest
validateDatabase
Option to validate database information. If enabled, the installer displays an error message if any of the following situations occur:
  • The installer cannot connect.
    Error message is output to <
    InstallationDir
    >\install\schematools.log. 
  • The database does not have the correct tablespace, schema, or version.
    Error message is output to <
    InstallationDir
    >\silent.install.failed.txt.
  • The user does not have create schema permissions.
    Error message is output to <
    InstallationDir
    >\silent.install.failed.txt.
The installer produces a warning message and writes it to silent.install.failed.txt, but does not prevent you from continuing.
Property settings
True or false.
Default
validateDatabase=true (commented out)
upgradeSchema
Specifies whether you want to upgrade an existing APM database schema to the current version if you are using PostgreSQL 9.2 for the database. This property is not applicable if you are using an Oracle database for the APM database schema.
Property settings
True or false
Default
This property set to true but commented out by default.
Example
upgradeSchema=true
databaseDir
If you are using PostgreSQL as the database, this property specifies the directory name for the APM database. This property is required when you are installing a new PostgreSQL database instance. This property is not applicable if you are using an Oracle database for the APM database schema.
If you are installing a new PostgreSQL database instance, use a separate, dedicated disk or I/O subsystem. This setup avoids affecting Enterprise Manager performance.
For sizing information, see the
CA APM Sizing and Performance Guide
.
Property settings
If the directory name or path contains spaces, use a backslash to escape the spaces or use quotes around the path.
Default
For Linux and Solaris, the default path is /opt/database. For Windows the default path is a database folder in the installation directory. For example:
C:\Program Files\CA APM\Introscope<version>\database
Example
databaseDir=database
dbAdminUser
Specifies the PostgreSQL administrator user name if you are using PostgreSQL as the database. This property is required when you are installing or upgrading a PostgreSQL database instance.
If you are installing a new PostgreSQL database instance, use a separate, dedicated disk or I/O subsystem. This setup avoids affecting Enterprise Manager performance.
For sizing information, see the
CA APM Sizing and Performance Guide
.
Default
postgres
Example
dbAdminUser=postgres
dbAdminPassword
Specifies the PostgreSQL administrator account password if you are using PostgreSQL as the database. This property is required when you are installing or upgrading a PostgreSQL database instance.
If you are installing a new PostgreSQL database instance, use a separate, dedicated disk or I/O subsystem. This setup avoids affecting Enterprise Manager performance.
For sizing information, see the
CA APM Sizing and Performance Guide
.
Property settings
A text string that adheres to your organization’s password security policies.
If the default PostgreSQL Administrator password does not comply with your organization’s password security policies, the database installation fails. Review the installation log files for more information. The installer cannot pre-check the password.
Default
C@wilyapm90
The default password only applies if you install the APM database on PostgreSQL with the default configuration.
Example
dbAdminPassword=C@wilyapm90
dbInstallScriptTimeoutInMillis
Specifies the amount of time in milliseconds for the installer to wait after running the database installation script before timeout. The default is 240000 ms, which is equivalent to 4 minutes. For example, if the computer is older or a slow VM, you can increase the wait time before timeout.
Default
240000
Example
dbInstallScriptTimeoutInMillis=240000
useExistingSchemaForOracle
Specifies whether you want to use an existing APM database schema on an Oracle database. Set this property to true if you want the Enterprise Manager to connect to an existing APM database. Set this property to false if you want to create new schema on a Oracle database. This property is not applicable if you are using PostgreSQL for the APM database schema.
Property settings
True or false
Default
This property set to false by default.
Example
useExistingSchemaForOracle=false
oracleDbHost
Specifies the host name or IP address of the computer where the Oracle database instance is installed.
Property settings
A valid host name or IP address.
Default
This property has no default value.
Example
oracleDbHost=sfcedar05
oracleDbPort
Specifies the port number the Enterprise Manager uses to connect to the APM database if you are using Oracle as the database. This property is not applicable if you are using PostgreSQL for the APM database schema.
Property settings
A valid, available port number.
Default
This property has no default value. However, the default port for the LISTENER process is 1521.
Example
oracleDbPort=1521
oracleDbSidName
Specifies the service name of the Oracle database instance. This property is not applicable if you are using PostgreSQL for the APM database schema.
Property settings
A text string.
Default
This property has no default value.
Example
oracleDbSidName=cemdb
oracleDbUsername
Specifies the name of the database user account you want to associate with the APM database schema in an Oracle database. The user account you specify is the database owner of the APM schema and requires specific rights and roles.
Property settings
A valid Oracle database user account.
Default
This property has no default value.
Example
oracleDbUsername=apmadmin
oracleDbPassword
Specifies the password of the database user account you want to associate with the APM database schema in an Oracle database.
Property settings
A valid password for the Oracle database user account.
Default
This property has no default value.
Example
oracleDbPassword=Apm4$
WebView Installation Settings
This section describes the properties listed in the WebView Install Settings section of the installer response file.
wvPort
Port on which WebView will listen for connections.
Property settings
A valid, available port.
Default
wvPort=8080
wvEmHost
Enterprise Manager host to which WebView connects.
Property settings
A valid, fully qualified domain name, or localhost.
Default
wvEmHost=localhost
wvEmPort
Enterprise Manager port on which WebView connects.
Default
wvEmPort=5001 (6001 for SAP)
WebView as Windows Service Installation Settings
This section describes the properties listed in the WebView as Windows Service Settings section of the installer response file.
shouldConfigWvAsService
Specifies to configure WebView as a Windows service. During an upgrade, if this property is set to true, Introscope revises the original values to those specified in this section.
Property settings
True or false
Default
shouldConfigWvAsService=false
wvAsServiceName
If shouldConfigWvAsService =true, specify a unique name for the service. The Windows registry uses the service name.
Property settings
The service name must be eight or fewer characters without spaces.
Default
wvAsServiceName=IScopeWV
wvAsServiceDisplayName
If shouldConfigWvAsService=true, specify a unique display name for the service. Windows control panels and the NET START command display this name.
Property settings
The display name may contain spaces.
Default
wvAsServiceDisplayName=Introscope WebView
WebView Advanced JVM Settings
This section describes the properties listed in the WebView Advanced JVM Settings section of the installer response file.
These options should only be configured by advanced users. If you are unsure of the values to enter, keep the defaults by leaving these properties commented out.
wvLaxNlCurrentVm
Path to the JVM that will be used to run WebView.
Property settings
The path may be absolute or relative to
<EM_Home>
. On Windows, to enter a backslash, enter an extra backslash as an escape sequence.
Default
By default, Introscope points to the JRE folder which is created during the installation. Edit this property if you want to point to an alternate JVM.
Example
Windows: wvLaxNlCurrentVM=jre\\bin\\java.exe
UNIX: wvLaxNlCurrentVM=jre/bin/java
wvLaxNlJavaOptionAdditional
Command line arguments to be used by the WebView JVM.
Property settings
The recommended setting for the headless switch is:
  • false for Windows, AIX, Linux, and Solaris platforms
  • true for other UNIX and mainframe platforms
Default
wvLaxNlJavaOptionAdditional=-Xms128m -Xmx512m -Djava.awt.headless=false
ProbeBuilder Installation Settings
There is nothing to set in this section.
ProbeBuilder Advanced JVM Settings
This section describes the properties listed in the ProbeBuilder Advanced JVM Settings section of the installer response file.
These options should only be configured by advanced users. If you are unsure of which values to enter, keep the defaults by leaving these properties commented out.
pbLaxNlCurrentVm
Path to the JVM that will be used to run the ProbeBuilder.
Property settings
The path may be absolute or relative to
<EM_Home>
. On Windows, to enter a backslash, enter an extra backslash as an escape sequence.
Default
By default, Introscope points to the JRE folder which is created during the installation. Edit this property if you want to point to an alternate JVM.
Example
Windows: pbLaxNlCurrentVM=jre\\bin\\java.exe
UNIX: pbLaxNlCurrentVM=jre/bin/java
pbLaxNlJavaOptionAdditional
Command line arguments to be used by the ProbeBuilder JVM.
Default
pbLaxNlJavaOptionAdditional=-Xms32m -Xmx64m (commented out)
Install Anywhere Settings
Do not edit this section.
Workstation Installer Silent Mode Settings
This section describes the properties in the response file of the Workstation installer.
Also specify the General Settings in the response file.
Workstation Install Settings
These options are applicable to the response file used with the Workstation installer.
silentInstallChosenFeatures
Identifies Workstation as the component you chose to install.
Default
silentInstallChosenFeatures=Workstation
wsUser
The workstation user account. The Introscope administrator must create this account and grant it access privileges.
For more information about granting access privileges, see the
CA APM Security Guide
.
Default
wsUser=Admin
wsHost
Enterprise Manager host to which the workstation connects.
Property settings
A fully qualified domain name or
localhost
.
Default
wsHost=localhost
wsPort
Enterprise Manager port on which the workstation connects.
Property settings
A valid, available port number.
Default
wsPort=5001 (6001 for SAP)
Workstation Advanced JVM Settings
These options should only be configured by advanced users. If you are unsure of which values to enter, keep the defaults by leaving these properties commented out.
wsLaxNlCurrentVM
Path to the JVM that will be used to run the Workstation.
Property settings
The path may be absolute or relative to
<EM_Home>
. On Windows, to enter a backslash, enter an extra backslash as an escape sequence.
Default
By default, Introscope points to the JRE folder which is created during the installation. Edit this property if you want to point to an alternate JVM.
Example
Windows: wsLaxNlCurrentVM=jre\\bin\\java.exe
UNIX: wsLaxNlCurrentVM=jre/bin/java
wsLaxNlJavaOptionAdditional
Command line arguments to be used by the Workstation JVM.
Default
wsLaxNlJavaOptionAdditional=-client -Xms64m -Xmx256m (commented out by default)
Standalone Agent Installer Silent Mode Settings
These options are applicable to the response file used with the Standalone agent installer.
USER_INSTALL_DIR (Standalone Agent)
The absolute path and directory name where you install the standalone agent files.
Property settings
On Windows, to enter a backslash, enter an extra backslash as an escape sequence. Paths must be absolute and end with a directory separator. If no directory is specified, the defaults are used. On UNIX, the directory is under the user’s
home
directory. On Windows, the exact drive letter and name of the Program Files directory may vary depending on the Windows configuration.
Default
UNIX: /root/Introscope<version>/
Windows: C:\\Program Files\\CA APM\\Introscope<
version
>\\
silentInstallChosenFeatures (Standalone Agent Installer)
Do not edit this property.
shouldInstallEPAgent
Specifies whether to install the Introscope Environment Performance Agent.
Property settings
Set this property to true to install the EPAgent. To not install the EPAgent, either leave the property blank or set it to false.
Default
shouldInstallEPAgent=false
shouldInstallPPForOracleDB
Specifies whether or not to install CA APM for Oracle Databases.
Property settings
Set this property to true to install this extension. To not install this extension, either leave the property blank or set it to false.
Default
shouldInstallPPForOracleDB=false
shouldInstallSiteMinderSNMP
Specifies whether to install CA APM SNMP Collector for SiteMinder.
Property settings
Set this property to true to install this extension. To not install this extension, either leave the property blank or set it to false.
Default
shouldInstallSiteMinderSNMP=false
shouldInstallTibcoEMS
Specifies whether to install Tibco Enterprise Message Service.
Property settings
Set this property to true to install this SOA extension. To not install this extension, either leave the property blank or set it to false.
Default
shouldInstallTibcoEMS=false
shouldInstallWMBroker
Specifies whether to install webMethods Broker.
Property settings
Set this property to true to install this SOA extension. To not install this extension, either leave the property blank or set it to false.
Default
shouldInstallWMBroker=false
shouldInstallPPForWebSphereMQandMB
Specifies whether to install CA APM for IBM WebSphere MQ and IBM WebSphere Message Broker.
Property settings
Set this property to true to install this extension. To not install this extension, either leave the property blank or set it to false.
Default
shouldInstallPPForWebSphereMQandMB=false
shouldInstallPPForWebServers
Specifies whether to install CA APM for Web Servers.
Property settings
Set this property to true to install this extension. To not install this extension, either leave the property blank or set it to false.
(This extension is not supported on AIX.)
Default
shouldInstallPPForWebServers=false
shouldInstallPPForWebServersIIS
Specifies whether to install the IIS Monitoring Components for CA APM for Web Servers.
Property settings
If shouldInstallPPForWebServers=true, you can also specify to install CA APM for Web Server IIS. To do so, uncomment this property and set to true. (Windows platforms only).
Default
shouldInstallPPForWebServersIIS=false
shouldInstallSPMonitor
Specifies whether to install the SP Monitor for SharePoint Portal.
Property settings
Set this property to true to install this extension. To not install this extension, either leave the property blank or set it to false.
(Windows Server 2003 and Windows Server 2008 only.)
Default
shouldInstallSPMonitor=false
emHost
Enterprise Manager host to which an extension connects.
Default value
localhost
Property settings
A valid, fully qualified domain name, or localhost.
Default
emHost=localhost
emPort
The port used by the Enterprise Manager to listen for incoming connections.
Property settings
A valid, available port number.
Default
5001
6001 for SAP
Example
emPort=5030
Enterprise Manager Passwords
The following properties are in the Enterprise Manager User Password Settings section of the installer response file.
  • emAdminPassword
    Specifies the password that an Admin user uses to log into the Enterprise Manager.
  • emGuestPassword
    Specifies the password that a Guest user must use to log into the Enterprise Manager. When you set the values for emAdminPassword and emGuestPassword, the users.xml file has new passwords set for Admin and Guest users and plainTextPasswords set to False. The passwords are encrypted in users.xml.
When you do not specify any values in the emAdminPassword and emGuestPassword fields and leave them blank, the users.xml file has default passwords set for Admin and Guest users and plainTextPasswords is set to False.
SAP Installer Silent Mode Settings
The SAP Enterprise Manager installer and SAP workstation installer response files use the same settings that are in the regular installer, except for the WebView settings. For SAP installations, WebView is integrated with the Enterprise Manager and WebView starts automatically when the Enterprise Manager starts. Refer to the appropriate sections for details.
Launch the Installer in Silent Mode on z/OS
After extracting the installer TAR file, you see two files:
  • runinstaller.sh: The runinstaller.sh script launches the installer, confirms that the specified response file exists, and confirms that there is at least 60 MB of space in the /tmp directory.
  • <
    installerfilename
    >.jar: You can use a Java command to launch the silent mode installer on z/OS, for example:
java -cp <
installerfilename
>.jar -f <
absolute path to response file
>
These instructions apply to installing the agent on z/OS.
Follow these steps:
  1. Before running the script, check that a JAVA_HOME environment variable exists by running:
    echo $JAVA_HOME
  2. If it exists, continue to Step 3. If no such variable exists:
    1. Open the runinstaller.sh script in a text editor.
    2. Find the line that sets the Java home.
    3. Uncomment this line and modify the path to specify your own Java home.
    4. Save your changes, and then launch the script.
  3. Launch the script using:
runinstaller.sh <
installerfilename
>.jar -silent <
absolute path to response file
>
Launch the Silent Mode Installer on Other Platforms
When installing on OS/400 or IBMi systems, to run the installer successfully, the JVM must be version 1.7 or later; other installers require at least version 1.6.x. Running Enterprise Manager and WebView requires a 1.7 JVM. For OS/400, perform silent mode installation from Qshell.
To run the installer in silent mode
:
  • For .exe or .bin files, specify the path to the installer and the absolute path to the response file:
installer.exe -f <
absolute path to response file
>
installer.bin -f <
absolute path to response file
>
For example:
[root@qaserver:/] ./introscope9.0.x.ysolaris.bin -f /tmp/myResponseFile.txt
  • For .JAR files (no bundled JVM), specify the path to the installer, the absolute path to the response file and specify the appropriate JVM:
java -classpath installer.jar install -f <
absolute path to response file
>
For example:
[root@qaserver:/] /usr/java/bin/java –classpath introscope9.0.x.yos400.jar install –f /tmp/myResponseFile.txt
Silent Mode Errors
If the response file specified does not exist or the path is invalid, the installer tries to run in GUI mode. However, if GUI mode is not supported on the platform, the installer fails.
If the silent install or upgrade fails, you can review the Introscope_<
VersionNumber
>_InstallLog.log file. This file is in the
<EM_Home>
/install directory. When the install or upgrade fails before the process creates the log file, no feedback is available.