Appendix A. Configuration files and scripts 437
error_file_append = n
reporting_stdout_on_server = y
reporting_stderr_on_server = y
max_stdout_size = 10000
max_stderr_size = 10000
bootable = n
retry = 1
exit_codes
success = 0,0
success = 1,65535
end
end
end
execute_user_program
caption = “remove work_dir”
transactional = n
during_remove
path = $(bin_dir)/do_it
arguments = “/bin/rm -r $(work_dir)”
inhibit_parsing = n
working_dir = $(root_dir)
timeout = -1
unix_user_id = 0
unix_group_id = 0
user_input_required = n
output_file = $(log_dir)/$(prod_name)_remove_workdir.out
error_file = $(log_dir)/$(prod_name)_remove_workdir.err
output_file_append = n
error_file_append = n
reporting_stdout_on_server = y
reporting_stderr_on_server = y
max_stdout_size = 10000
max_stderr_size = 10000
bootable = n
retry = 1
exit_codes
success = 0,0
success = 1,65535
end
end
end
438 Implementing a Tivoli Solution for Central Management of Large Distributed Environments
end
end
was_appserver_510.rsp
Example A-43 is the response file controlling the installation and basic
customization of WebSphere Application Server 5.1.
Example: A-43 Response file for WAS 5.1 installation
# *******************************************
#
# Response file for WebSphere Application Server 5.1 Install
#
# Please follow the comments to use the response file and
# understand the various options. You must carefully complete
# or change the various values. If the values are not completed
# properly, the install may be unsuccessful.
#
# NOTE: This file is for silent install only.
#
#
# IMPORTANT: ALL VALUES MUST BE ENCLOSED IN DOUBLE QUOTES ( ““ ).
#
# *******************************************
# *******************************************
# This value is required.
# PLEASE DO NOT REMOVE THIS VALUE.
# *******************************************
-W setupTypes.selectedSetupTypeId=”custom”
# *******************************************
# Below is the beginning of the response file that needs to be
# filled in by the user.
# *******************************************
# *******************************************
# The below value specifies silent install. This value
# indicates that the install will be silent.
# *******************************************
-silent
Appendix A. Configuration files and scripts 439
# *******************************************
# WebSphere Application Server Install Location
#
# Please specify the destination directory for the WebSphere Application
# Server installation. You will need to change this for UNIX
# platforms. As an example for AIX, the value may be
# “/usr/WebSphere/AppServer”
# *******************************************
-P wasBean.installLocation=”$(inst_dir)”
# *******************************************
# IBM HTTP Server Install Location
#
# Please specify the destination directory for the IBM HTTP Server
# installation. This value will need to be completed if you
# choose to install IBM HTTP Server. If you choose to not install IBM
# HTTP Server, then this value is not required. You will need to change
# the default value below for UNIX platforms. As an example for AIX, the
# value may be “/usr/IBMHTTPServer”
# *******************************************
-P ihsFeatureBean.installLocation=”/opt/IBMIHS”
# *******************************************
# Below are the features that you may choose to install.
# Set the following values to “true” or “false,” depending upon whether
# you want to install the following features or not.
#
# NOTE: The default settings for features in this response file
# detail the defaults for a typical installation.
# *******************************************
# *******************************************
# Install Server
# *******************************************
-P serverBean.active=”true”
# *******************************************
#
# Begin Features for Administration
#
440 Implementing a Tivoli Solution for Central Management of Large Distributed Environments
# *******************************************
# *********
# Install Administration
# *********
-P adminBean.active=”true”
# *********
# The next 2 features are part of Administration. In order for any of these
# features to be installed, the property to install Administration denoted
# above must be set to “true.”
# *********
# *********
# Install Admin Scripting
# *********
-P adminScriptingFeatureBean.active=”true”
# *********
# Install Administrative Console
# *********
-P adminConsoleFeatureBean.active=”true”
# *******************************************
#
# End Features for Administration
#
# *******************************************
# *******************************************
#
# Begin Features for Application Assembly and Deployment Tools
#
# *******************************************
# *********
# Install Application Assembly and Deployment Tools
# *********
-P applicationAndAssemblyToolsBean.active=”true”
# *********
# The next 3 features are part of Application Assembly and Deployment
# Tools. In order for any of these features to be installed,
# the property to install Application And Assembly Tools denoted
Appendix A. Configuration files and scripts 441
# above must be set to “true.”
# *********
# *********
# Install Deploy Tool
# *********
-P deployToolBean.active=”true”
# *********
# Install Ant Utilities
# *********
-P antUtilityBean.active=”true”
# *******************************************
#
# End Features for Application Assembly and Deployment Tools
#
# *******************************************
# *******************************************
#
# Begin Features for Embedded Messaging
#
# *******************************************
# *********
# Install Embedded Messaging
# *********
-P mqSeriesBean.active=”false”
# *********
# The next three features are for Embedded Messaging. In order to install
# any of the following three subfeatures, the property to install Embedded
# Messaging denoted above must be set to “true.”
#
# IMPORTANT NOTE: If you do not want to install Embedded Messaging, please
# ensure all of the following options are set to “false” as well as the above
# option.
# *********
# *********
# Install Embedded Messaging Server and Client
#
# You may only install the Embedded Messaging Server and Client or the Embedded

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.