##############################################################################
#
# Introscope Agent Silent Installation Response File
#
# Sample Response File
# CA Wily Introscope(R) Version 9.5 Release 9.5.0.0
# Copyright (c) 2013 CA. All Rights Reserved.
# Introscope(R) is a registered trademark of CA.
#
##############################################################################

##############################################################################
# How to install silently and use this file: 
#
# Introscope components can be installed in silent mode (i.e. requiring 
# no interaction with a GUI or console). Silent installations use the settings
# specified in a response file. 
#
# Silent installations are performed as follows:
#
# Edit this file to reflect your preferred settings.
# Place this file in any directory. 
# Select the appropriate command format from the list below,
# and enter it at the command line to invoke the installer:
#
#   installer.exe -f <absolute path to response file>
#   installer.bin -f <absolute path to response file>
#   java -classpath installer.jar install -f <absolute path to response file>
#
# IMPORTANT NOTES: 
# 1) This installer will:
#      - place Introscope Agent files on the filesystem
#      - edit the Introscope Agent profile
#      - generate a connector jar, if necessary
#      - optionally copy certain jars into app server directories
#      - generate a "Next Steps" readme
#    It will not stop or start the application server or modify its classpath.
#    These steps will need to be performed manually. 
# 2) This installer does not perform upgrades. By default, if the silent 
#    installer detects a preexisting Agent in the specified install dir, 
#    no installation will be performed. CA APM recommends that you do not
#    use this installer to overwrite an existing Agent installation. Advanced
#    users who wish to ignore this recommendation may do so at their own risk
#    by editing this responsefile to include the following property:
#        overwritePreexistingAgent=true
# 
##############################################################################



#######################
# General Settings
#
# ================

# The directory where Introscope Agent files (i.e. the "wily" folder)
# will be installed. CA APM recommends selecting the application server's 
# root directory. 
# The directory path must be absolute, not relative.
# On all platforms, the path must end with a file separator.
# On Windows, backslashes must be escaped.
# Example Agent install directory on Windows: C:\\myAppServerHome\\
# Example Agent install directory on Unix: /myAppServerHome/
# Left blank, this property will default to one of the following values: 
# On Windows...
#    C:\\Program Files\\CA APM\\Introscope9.5.0.0\\ 
#        (Exact name and drive letter of program files directory may vary 
#        depending on OS configuration) 
# On Unix...
#    /root/Introscope9.5.0.0/
#        (Under the logged-in-end-user's home directory. Exact directory may vary 
#        depending on user account.)
USER_INSTALL_DIR=

# Introscope Agent features to install. Must be a comma-delimited list.
# Valid values are "Agent" and "Docs" (case sensitive, no quotes).
# If the Documentation feature is included, basic documentation will be 
# installed into the Agent's wily folder.
# Example: Agent,Docs
silentInstallChosenFeatures=Agent



#######################
# Application Server Settings
#
# ================

# Specify the application server type. The installer 
# will use this property to choose a set of ProbeBuilder 
# directives for the Introscope Agent.
# Valid values are: (case sensitive)
#   Default
#   JBoss
#   Tomcat
#   WebLogic
#   WebSphere
#   Sun ONE
#   Oracle
#   Interstage
appServer=Default

# Optionally specify the home directory of the application server 
# to monitor. The installer will use this information to copy 
# certain jars into application server directories if necessary.
# On all platforms, the path must end with a file separator.
# On Windows, backslashes must be escaped.
# Example settings for Windows:
#    C:\\apache\\tomcat\\5.0.30\\
#    D:\\bea\\weblogic10.3\\
# Example setting for Unix:
#    /opt/IBM/WebSphere61/AppServer/
#appServerHome=

# Optionally specify the Java executable that is used to launch
# the monitored application server. The installer will use this  
# information to check the JVM vendor and version, and generate 
# a connector jar if necessary.
# On Windows, backslashes in the path must be escaped.
# Example settings for Windows and Unix:
#    C:\\Program Files\\Java\\jre1.5.0_06\\bin\\java.exe
#    /usr/bin/java
#appServerJavaExecutable=



##########################################
# Agent Install Settings
#
# ===================================

# Specify the level of instrumentation to use.
# Valid values are "Full" or "Typical" (case sensitive, 
# no quotes). The "Full" setting achieves more detailed 
# reporting and is recommended for test environments.
# The "Typical" setting provides less detail with reduced 
# overhead, and is recommended for production environments. 
# This instrumentation level setting is for base agent only.
instrumentationLevel=Typical

# Specify the ProbeBuilding method that will be used to instrument
# the application. Valid values are: (case sensitive)
#   JVM AutoProbe
#   Manual ProbeBuilding
# ...for JVM AutoProbe, or Manual ProbeBuilding, respectively.
# See the Introscope Java Agent Guide for more information on 
# ProbeBuilding methods. 
instrumentationType=JVM AutoProbe

# Specify the Agent and process name. 
agentName=Default Agent
processName=Default Process

# Specify the hostname and port of the Introscope Enterprise Manager 
# to which this Agent will connect. 
emHost=localhost
emPort=5001



##########################################
# Advanced Install Settings
#
# ===================================

# Optionally specify the absolute path to a custom Agent profile.
# If the specified file exists:
#   - It will be shipped instead of the default Agent profile.
#   - All of the properties in the "Agent Settings" section 
#     of this responsefile will be ignored, except for the
#     instrumentationType property.
# On Windows, backslashes must be escaped.
# Example settings for Windows and Unix:
#    C:\\customAgentProfiles\\CustomIntroscopeAgent.profile
#    /home/iscadmin/customAgentProfiles/CustomIntroscopeAgent.profile
#alternateAgentProfile=

# Optionally specify the absolute path to a "pickup folder".
# The pickup folder provides a convenient way of installing 
# extensions or add-ons alongside the base Agent.
# Any zip or tar files present in the pickup folder will be 
# extracted into the Agent directory at install time.
# (With one exception: files named IntroscopeAgent.profile
# will be ignored at this time.)
# On all platforms, the path must end with a file separator.
# On Windows, backslashes must be escaped.
# Example settings for Windows and Unix:
#    C:\\pickupFolderContainingAddOns\\
#    /home/iscadmin/customAgentProfiles/pickupFolderContainingAddOns/
#pickupFolder=

# Optionally specify whether to enable ChangeDetector Agent 
# extension during this install. You may specify true or false.
# (If you specify false, ChangeDetector files will still be 
# installed but it won't be enabled. You may enable it later 
# by editing the Agent profile.)
# Specify ChangeDetector Agent ID only if it is enabled.
changeDetectorEnable=false
#changeDetectorAgentID=

# Optionally specify the SOA Agent extensions which you want to enable
# during this install. (If you don't enable, SOA Agent extension files
# will still be installed but it won't be enabled. You may manually
# enable it later.)
#
# SPM is required if you want to enable any SOA extensions.

#CA APM for SOA
shouldEnableSPM=false

#CA APM for Oracle Service Bus
shouldEnableSOAExtForOSB=false

#CA APM for IBM WebSphere Process Server/Business Process Management
shouldEnableSOAExtForWPSandWESB=false

#CA APM for TIBCO BusinessWorks
shouldEnableSOAExtForTibcoBW=false

#CA APM for webMethods Integration Server
shouldEnableSOAExtForWebMethodsIS=false

#Specify the Power Packs you want to enable.

#CA APM for Oracle WebLogic Server
shouldEnablePowerPackForWebLogic=false

#CA APM for IBM WebSphere Application Server for Distributed Environments
shouldEnablePowerPackForWebSphere=false

#CA APM for CA SiteMinder Web Access Manager
shouldEnablePowerPackForSiteMinder=false

#CA APM for Oracle WebLogic Portal
shouldEnablePowerPackForWebLogicPortal=false

#CA APM for IBM WebSphere MQ
shouldEnablePowerPackForWebSphereMQ=false

###############################
# InstallAnywhere Settings
# 
# ========================

# Installer UI mode. Do not edit.
INSTALLER_UI=silent