Skip to content
CA Application Performance Management - 10.5
Documentation powered by DocOps

Install APM in Silent Mode

Last update August 6, 2018

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.

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 file.
  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 installation takes input from a prepared response file.

You can use an automatically generated response file, or can modify the sample response file that is provided with your installation.

Note: When 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, when you use a UTF-8 response file and you 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.
  • When you specify a relative path, make the path relative to the installer launch directory.

Download and Edit External Files

You must download CA End User License Agreements (EULA) before you start the installation process.

Note the location on your network of the downloaded file. You supply this location in the response file.

Edit the ca-eula.txt Files

Signify acceptance of CA End User License Agreements (EULA).

Follow these steps:

  1. Open the ca-eula.txt file.
  2. Read the agreement.
  3. When you agree to the terms and conditions of the agreement, edit the CA-EULA property (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

This property specifies the directory where to install Introscope. 

Note: For upgrades, this property indicates the Enterprise Manager directory to be upgraded.

Property settings

Use 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 can 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, Database

Note: "Database" refers to the APM database.

Default

silentInstallChosenFeatures=Enterprise Manager,WebView

Example

silentInstallChosenFeatures=Enterprise Manager,WebView,Database
ca-eulaFile

Location of the CA End User License Agreement (EULA), a file named ca-eula.txt. The file is typically located in the same location as the main and Workstation installers. When you are installing the Enterprise Manager, WebView, or Workstation, use this setting to specify the file location.

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.

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 that are listed in the Upgrade Settings section of the installer response file.

shouldUpgrade

This property specifies whether to upgrade an existing Introscope installation.

The upgrade can be reversed if you enable Backup at the time of the upgrade.

To do an upgrade in silent mode, specify the following other properties:

  • USER_INSTALL_DIR
    Specify the folder of the Enterprise Manager to be upgraded.
  • ca-eulaFile
  • (Optional) upgradedInstallDir
  • (Optional) shouldConfigEmAsService, emAsServiceName, emAsServiceDisplayName

Property settings

True or false

Default

shouldUpgrade=false

Example

shouldUpgrade=true
enableBackup

When set to True, this property lets you back up a CA APM instance during upgrade. If there are any failures during the upgrade, you can roll back.

Default:

True

upgradedInstallDir

This property specifies a new Introscope installation directory for these 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.

When upgrading an existing Introscope installation, use this property to rename the installation directory only for the two previously mentioned types of installations. When the APM database is installed within the Enterprise Manager installation directory, the option to rename the installation directory is not available. When you specify a value for upgradedInstallDir but the option is not available, the installer ignores this setting.

When 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

This property has no default.

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 that is 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

This property specifies the port that the Enterprise Manager uses to serve web applications.

Note: 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 that are listed in the Enterprise Manager Clustering Settings section of the installer response file.

shouldClusterEm

This property 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

Use this property when Enterprise Managers 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

When installing an Enterprise Manager as a MOM, use the emCollectorHost and emCollectorPort properties to specify up to ten Collectors that the MOM manages. 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 ten 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

This property has no default setting.

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 that are listed in the Enterprise Manager Transaction Storage Settings section of the installer response file.

emTxTraceDataShelfLife

This property specifies the fixed length of time (in days) to store trace data to disk.

Default

14 (days)

Example

emTxTraceDataShelfLife=30
emTxTraceDir

This property 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 that is 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 CA APM Sizing and Performance for SmartStor sizing information.

We recommend 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 that are 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 <EM_Home>\examples subdirectories to a same-named directory under <EM_Home>. For example, <EM_Home>\examples\PowerPackForSiteMinder directory contains files in these two directories:

  • <EM_Home>\examples\PowerPackForSiteMinder\config\modules
  • <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
    This property enables the APM Integration Pack for Application Delivery Analysis.
  • shouldEnableCAAPMForOracleDB
    This property enables CA APM for Oracle Databases.
  • shouldEnableCAAPMForSharePointPortal
    This property enables CA APM for Microsoft SharePoint Portal.
  • shouldEnableCAAPMForWebServers
    This property enables CA APM for Web Servers.
  • shouldEnableCAAPMForWebSphereMQandMB
    This property enables CA APM for IBM WebSphere MQ and MB.
  • shouldEnableCAAPMForWebSphereZOS
    This property enables CA APM for IBM WebSphere Application Server for z/OS.
  • shouldEnableCAAPMForIBMCTG
    This property enables CA APM for IBM CICS Transaction Gateway.
  • shouldEnableCAAPMForIBMzOSExtension
    This property enables the CA APM for IBM z/OS.
  • shouldEnableSysview
    This property enables CA Cross-Enterprise Application Performance Management.
  • shouldEnableCAAPMForOSB
    This property enables CA APM for Oracle Service Bus.
  • shouldEnableCAAPMForTibcoBW
    This property enables CA APM for TIBCO BusinessWorks.
  • shouldEnableCAAPMForTibcoEMS
    This property enables CA APM for TIBCO Enterprise Message Service.
  • shouldEnableCAAPMForWMBroker
    This property enables CA APM for webMethods Broker.
  • shouldEnableCAAPMForWebMethodsIS
    This property enables CA APM for webMethods Integration Server.
  • shouldEnableAPMIntegrationPackForCM
    This property enables CA APM Integration with Cloud Monitor.

Enterprise Manager as Windows Service Settings

The following properties are listed in the Enterprise Manager as Windows Service Settings section of the installer response file.

shouldConfigEmAsService

This property 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. The name can 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 that are listed in the Enterprise Manager Advanced JVM Settings section of the installer response file. These options should only be configured by advanced users. When 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 is 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 When you want to point to an alternate JVM.

Example

Windows: emLaxNlCurrentVM=jre\\bin\\java.exe
UNIX: emLaxNlCurrentVM=jre/bin/java

emLaxNlJavaOptionAdditional

This property specifies the optional command-line Java arguments for the Enterprise Manager. With this property, you can specify arguments, such as heap size.

Valid for: 64-bit Sun JVMs only

Property settings

Use the following switches for 64-bit platforms:

-Xss512k

When 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:MaxMetaspaceSize=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:MaxMetaspaceSize=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 that are used to configure the connection from an Enterprise Manager to an APM database. The properties that you are required to set depend on the database type and several other factors. The factors include whether you are installing a new PostgreSQL database instance, upgrading a database schema, or connecting to an existing database. Also, when you are installing a Cross-cluster Data Viewer (CDV), you do not need to install the APM database.

Tip: The properties for an Oracle upgrade are listed in this section. For a condensed list of these Oracle properties, see KB000010061 Using the Silent Install Process to Upgrade Oracle APM Database

chosenDatabaseIsPostgres

This property specifies whether you want the APM database to be a PostgreSQL database. You must set this property to true when installing or upgrading a PostgreSQL database instance on the computer where you run the silent installation. When you want to use an Oracle database, set this property to false.

Property settings

True or False

Default

True

Example

chosenDatabaseIsPostgres=true
chosenDatabaseIsOracle

This property specifies whether you want the APM database to be an Oracle database. When 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

This property specifies the host name of the computer where the APM database is or is to be installed when you are installing PostgreSQL as the database. This property is not applicable when 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

This property specifies the port number the Enterprise Manager uses to connect to the APM database when you are using PostgreSQL as the database. This property is not applicable when you are using an Oracle database for the APM database schema.

Property settings

A valid, available port number.

Default

5432

Example

dbPort=5432
dbName

This property specifies the name of the APM database schema when you are using PostgreSQL as the database. This property is not applicable when you are using an Oracle database for the APM database schema.

Property settings

A text string that does not contain special or uppercase characters.

Default

cemdb

Example

dbName=cemdb
dbUser

This property specifies the name of the database user account when you are using PostgreSQL as the database. This property is not applicable when you are using an Oracle database for the APM database schema.

Property settings

A text string that does not contain special or uppercase characters.

Default

admin

Example

dbUser=admin
dbPassword

This property specifies the password for the database user account when you are using PostgreSQL as the database. This property is not applicable when you are using an Oracle database for the APM database schema.

Property settings

A text string that does not contain special or uppercase characters.

Default

wily

Example

dbPassword=qtest
validateDatabase

Option to validate database information. Set this property to False when you are installing database. Set this property to True, when you are upgrading or creating a schema. 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.

Note: The installer produces a warning message and writes it to silent.install.failed.txt, but does not prevent you from continuing.

Note:  The "validateDatabase" is a PostgreSQL only property during the silent installation.

Property settings

True or false.

Default

validateDatabase=true (commented out)
upgradeSchema

This property specifies whether you want to upgrade an existing APM database schema to the current version of PostgreSQL or Oracle.

Property settings

True or false

Default

This property set to true but commented out by default.

Example

upgradeSchema=true

This table describes how the validateDatabase and upgradeschema properties control the behavior of database installation and upgrade.

validateDatabase upgradeSchema Action
False False Fresh Installation of PostgreSQL
True False Create database if does not exist.
True True Upgrades the existing database schema
False True Upgrades the existing database schema
databaseDir

When 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 when you are using an Oracle database for the APM database schema.

When you are installing a new PostgreSQL database instance, use a separate, dedicated disk or I/O subsystem. This setup avoids affecting Enterprise Manager performance.

Note: For sizing information, see CA APM Sizing and Performance.

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\PostgreSQL-<version>

Example

databaseDir=database
newPgInstallDir

When you are upgrading a PostgreSQL APM database that requires a major upgrade, use this property to specify the install location for the upgraded PostgreSQL instance. This property is not for use when installing (not upgrading) the PostgreSQL database or using an Oracle database for the APM database schema.

Define the newPgInstallDir property when upgrading from respective previous CA APM release on the respective platforms.

Releases When Defining the newPgInstallDir Property is Mandatory when Upgrading


APM 9.5.x APM 9.6.X APM 9.7.x APM 10.x
Windows Yes
Yes Yes No
Linux Yes No No No
Solaris Yes No No No

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/PostgreSQL-<version>. For Windows, the default path is a database folder in the installation directory. For example:

C:\Program Files\CA APM\PostgreSQL-<version>

Example:

newPgInstallDir= C:\\Program Files\\PostgreSQL-<version>
dbAdminUser

This property specifies the PostgreSQL administrator user name when you are using PostgreSQL as the database. This property is required when you are installing or upgrading a PostgreSQL database instance.

When you are installing a new PostgreSQL database instance, use a separate, dedicated disk or I/O subsystem. This setup avoids affecting Enterprise Manager performance.

Default

postgres

Example

dbAdminUser=postgres
dbAdminPassword

This property specifies the PostgreSQL administrator account password when you are using PostgreSQL as the database. This property is required when you are installing or upgrading a PostgreSQL database instance.

When you are installing a new PostgreSQL database instance, use a separate, dedicated disk or I/O subsystem. This setup avoids affecting Enterprise Manager performance.

Note: For sizing information, see CA APM Sizing and Performance.

Property settings

A text string that adheres to your organization password security policies.

If the default PostgreSQL Administrator password does not comply with your organization 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

Note: The default password only applies when you install the APM database on PostgreSQL with the default configuration.

Example

dbAdminPassword=C@wilyapm90
dbInstallScriptTimeoutInMillis

This property 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

This property specifies whether you want to use an existing APM database schema on an Oracle database. Set this property to true when you want the Enterprise Manager to connect to an existing APM database. Set this property to false when you want to create schema on an Oracle database. This property is not applicable when 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

This property 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

This property specifies the port number the Enterprise Manager uses to connect to the APM database when you are using Oracle as the database. This property is not applicable when 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

This property specifies the service name of the Oracle database instance. This property is not applicable when 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

This property specifies the name of the database user account you want to associate with the APM database schema in an Oracle database. The user account that 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

This property 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 that are listed in the WebView Install Settings section of the installer response file.

wvPort

Port on which WebView listens 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

The following properties are listed in the WebView as Windows Service Settings section of the installer response file.

shouldConfigWvAsService

This property specifies to configure WebView as a Windows service. During an upgrade, when this property is set to true, Introscope revises the original values to the values that are 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 that are listed in the WebView Advanced JVM Settings section of the installer response file.

Note: These options should only be configured by advanced users. When you are unsure of the values to enter, keep the defaults by leaving these properties commented out.
wvLaxNlCurrentVm

Path to the JVM that is 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 when 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

InstallAnywhere 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

This property 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 must grant it access privileges.

Note: For more information about granting access privileges, see APM Security.

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. When you are unsure of which values to enter, keep the defaults by leaving these properties commented out.
wsLaxNlCurrentVM

Path to the JVM that is 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 when 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

This property is commented out by default.

wsLaxNlJavaOptionAdditional=-client -Xms64m -Xmx256m

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 <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

This property specifies whether to install the Introscope Environment Performance Agent.

Property settings

Set this property to true to install the EPAgent. Otherwise, leave the property blank or set it to false.

Default

shouldInstallEPAgent=false

shouldInstallPPForOracleDB

This property specifies whether to install CA APM for Oracle Databases.

Property settings

Set this property to true to install this extension. Otherwise, leave the property blank or set it to false.

Default

shouldInstallPPForOracleDB=false

shouldInstallSiteMinderSNMP

This property specifies whether to install CA APM SNMP Collector for SiteMinder.

Property settings

Set this property to true to install this extension. Otherwise, leave the property blank or set it to false.

Default

shouldInstallSiteMinderSNMP=false

shouldInstallTibcoEMS

This property specifies whether to install Tibco Enterprise Message Service.

Property settings

Set this property to true to install this SOA extension. Otherwise, leave the property blank or set it to false.

Default

shouldInstallTibcoEMS=false

shouldInstallWMBroker

This property specifies whether to install webMethods Broker.

Property settings

Set this property to true to install this SOA extension. Otherwise, leave the property blank or set it to false.

Default

shouldInstallWMBroker=false

shouldInstallPPForWebSphereMQandMB

This property 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. TOtherwise, leave the property blank or set it to false.

Default

shouldInstallPPForWebSphereMQandMB=false

shouldInstallPPForWebServers

This property specifies whether to install CA APM for Web Servers.

Property settings

Set this property to true to install this extension. Otherwise, leave the property blank or set it to false.

This extension is not supported on AIX.

Default

shouldInstallPPForWebServers=false

shouldInstallPPForWebServersIIS

This property 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

This property specifies whether to install the SP Monitor for SharePoint Portal.

Property settings

Set this property to true to install this extension. Otherwise, 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 that is 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
    This property specifies the password that an Admin user uses to log in to the Enterprise Manager.
  • emGuestPassword
    This property specifies the password that a Guest user must use to log in to the Enterprise Manager. When you set the emAdminPassword and emGuestPassword values, the users.xml file has new passwords set for Admin and Guest users. The passwords are encrypted in users.xml. The plainTextPasswords property is set to False.

    When you leave the emAdminPassword and emGuestPassword values blank, the users.xml file has default passwords set for Admin and Guest users. The plainTextPasswords property is set to False.

SAP Installer Silent Mode Settings

The SAP Enterprise Manager installer and SAP Workstation installer response files use the same settings as the standard installer, except for the WebView settings. For SAP installations, WebView is integrated with the Enterprise Manager. WebView starts automatically when the Enterprise Manager starts. Refer to the appropriate sections for details.

Launch the Installer in Silent Mode on z/OS

You can see these two files after you extract the installer TAR file:

  • runinstaller.sh 
    The runinstaller.sh script launches the installer. The script also 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. Perform this step before running the script. Check that a JAVA_HOME environment variable exists by running this command:

    echo $JAVA_HOME
  2. When a JAVA_HOME environment variable exists, continue to Step 3.
    If a JAVA_HOME environment variable does not exist, follow these steps:
    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.
  3. Launch the script using this command:
runinstaller.sh <installerfilename>.jar -silent <absolute path to response file>

Launch the Silent Mode Installer on Other Platforms

When installing on other platforms, to run the installer successfully, the JVM must be version 1.6 or later. Running Enterprise Manager and WebView requires a 1.7 JVM.

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.yotherUnix.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.

Note: If the silent installation or upgrade fails, you can review the Introscope_< VersionNumber>_InstallLog.log file. This file is in the <EM_Home>/install directory. When the installation or upgrade fails before the process creates the log file, no feedback is available.
Was this helpful?

Please log in to post comments.