442 Implementing a Tivoli Solution for Central Management of Large Distributed Environments
# Messaging client below. If you set the Server and Client to “true,” please
# ensure that the Client only option below is set to “false.” The same applies
# if you set the Client only option to “true,” please ensure the server and
client
# option is set to “false.”
# *********
-P mqSeriesServerBean.active=”false”
# *********
# Embedded Messaging Server and Client install location
#
# If you choose to install Embedded Messaging Server and Client above, please
# specify an install location below for Windows platforms only.
# The directory may not be configured by the user for UNIX platforms
# as it is predetermined.
# *********
-P mqSeriesServerBean.installLocation=”/opt/IBM/WebSphereMQ”
# *********
# Install Embedded Messaging Client only
# *********
-P mqSeriesClientBean.active=”false”
# *********
# Embedded Messaging Client Only install location
#
# If you choose to install Embedded Messaging Client only above, please
# specify an install location below for Windows platforms only.
# The directory may not be configured by the user for UNIX platforms
# as it is predetermined.
# *********
-P mqSeriesClientBean.installLocation=”/opt/IBM/WebSphereMQ”
# *********
# Install Message-driven beans Samples
# *********
-P mqSeriesSamplesBean.active=”false”
# *******************************************
#
# End Features for Embedded Messaging
#
# *******************************************
Appendix A. Configuration files and scripts 443
# *******************************************
# Install IHS WebServer 1.3.28
# *******************************************
-P ihsFeatureBean.active=”false”
# *******************************************
#
# Begin Features for Web Server Plugins
#
# *******************************************
# *********
# Install Web Server Plugins
# *********
-P pluginBean.active=”true”
# *********
# The next 5 features are part of Web Server Plugins.
# In order for any of these features to be installed,
# the property to install Web Server Plugins denoted
# above must be set to “true.”
# *********
# *********
# Install IBM HTTP Server v1.3 Plugin
# *********
-P ihsPluginBean.active=”false”
# *********
# Install IBM HTTP Server v2.0 Plugin
# *********
-P ihs20PluginBean.active=”true”
# *********
# Install Apache Web Server v1.3 Plugin
# *********
-P apachePluginBean.active=”false”
# *********
# Install Apache Web Server v2.0 Plugin
# *********
444 Implementing a Tivoli Solution for Central Management of Large Distributed Environments
-P apache20PluginBean.active=”false”
# *********
# Install Microsoft Internet Information Services (IIS) Plugin
# *********
-P iisPluginBean.active=”false”
# *********
# Install iPlanet Web Server Plugin
# *********
-P iplanet60PluginBean.active=”false”
# *********
# Install Domino Web Server Plugin
# *********
-P dominoPluginBean.active=”false”
# *******************************************
#
# End Features for Web Server Plugins
#
# *******************************************
# *******************************************
# Install Samples
# *******************************************
-P samplesBean.active=”false”
# *******************************************
#
# Begin Features for Performance and Analysis Tools
#
# *******************************************
# *********
# Install Performance And Analysis Tools
# *********
-P performanceAndAnalysisToolsBean.active=”true”
# *********
# The next 3 features are part of Performance And Analysis
# Tools. In order for any of these features to be installed,
Appendix A. Configuration files and scripts 445
# the property to install Performance And Analysis Tools denoted
# above must be set to “true.”
# *********
# *********
# Install Tivoli Performance Viewer
# *********
-P tivoliPerfBean.active=”true”
# *********
# Install Dynamic Cache Monitor
# *********
-P DCMBean.active=”true”
# *********
# Install Performance Servlet
# *********
-P performanceServletBean.active=”true”
# *********
# Install Log Analyzer
# *********
-P logAnalyzerBean.active=”true”
# *******************************************
#
# End Features for Performance and Analysis Tools
#
# *******************************************
# *******************************************
# Install Javadocs
# *******************************************
-P javadocBean.active=”false”
# *******************************************
# Please enter a node name and hostname for this installation.
# The node name is used for administration, and must be unique
# within its group of nodes (cell). The hostname is the DNS name
# or IP address for this computer. You must replace the
# “DefaultNode” with the node name that you want the default node
446 Implementing a Tivoli Solution for Central Management of Large Distributed Environments
# to be and “127.0.0.1” to a resolveable hostname or IP address
# for your machine.
# Warning:
# 1. If you are migrating now or plan to do so after
# installation, enter the same node name as the previous version.
# 2. If you are performing coexistence, enter a unique node name.
# *******************************************
-W nodeNameBean.nodeName=”$(hostname)”
-W nodeNameBean.hostName=”$(hostname)”
# *******************************************
# Begin Installing Services
#
# The following are to install Services for IHS and Websphere
# Application Server on Windows. Using Services, you can start and
# stop services, and configure startup and recovery actions.
# You can ignore these or comment them out for other Operating Systems.
# *******************************************
-W serviceSettingsWizardBean.active=”true”
# *********
# The next 2 options are part of Installing Services.
# In order for any of these to be set to “true,”
# the property to install Services denoted above must be set
# to “true.”
# *********
# *********
# Install the IHS service
# *********
-W serviceSettingsWizardBean.ihsChoice=”false”
# *********
# Install the WebSphere Application Server service
# *********
-W serviceSettingsWizardBean.wasChoice=”true”
# *********
# If you chose to install a service above, then you must
# specify the User Name and Password which are required to
# install the Services. The current user must be admin or must
# have admin authority to install a Service. Also the username
# which is given here must have “Log On as a Service “ authority

Get Implementing a Tivoli Solution for Central Management of Large Distributed Environments now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.