WAS 7 installation config files

01-was7-install-responsefile.txt

-OPT silentInstallLicenseAcceptance="true"
-OPT disableOSPrereqChecking="true"
-OPT disableNonBlockingPrereqChecking="true"
-OPT installType="installNew"
-OPT profileType="standAlone"

-OPT feature="noFeature"

-OPT PROF_enableAdminSecurity="true"
-OPT PROF_adminUserName=wasadmin
-OPT PROF_adminPassword=wasadmin

-OPT installLocation="/opt/IBM/WebSphere/AppServer"
-OPT PROF_profilePath="/opt/IBM/WebSphere/AppServer/profiles/dev"

-OPT PROF_profileName=dev
-OPT PROF_hostName=afrodite.cit
-OPT PROF_nodeName="dev-node01"
-OPT PROF_cellName="dev-cell01"
-OPT PROF_serverName="server1"

#-OPT PROF_enableService="true"
#-OPT PROF_serviceUserName="root"

02-responsefile.updiinstaller.txt

################################################################################
#
# InstallShield Options File
#
# Wizard name: Install
# Wizard source: setup.jar
#
# This file can be used to configure Install with the options specified below
# when the wizard is run with the "-options" command line option. Read each
# setting's documentation for information on how to change its value.
# Please enclose all values within a single pair of double quotes.
# 
# A common use of an options file is to run the wizard in silent mode. This lets
# the options file author specify wizard settings without having to run the
# wizard in graphical or console mode. To use this options file for silent mode
# execution, use the following command line arguments when running the wizard:
# 
#    -options "D:\UpdateInstaller\responsefile.updiinstaller.txt" -silent
#
################################################################################

#################################################################################
#
# License Acceptance
#
# Valid Values:
#	true - Accepts the license. Will install the product.
#	false - Declines the license. Install will not occur.  
#
# If no install occurs, this will be logged to a temporary log file in the 
# user's temporary directory.
#
# By changing the silentInstallLicenseAcceptance property in this response file 
# to "true", you agree that you have reviewed and agree to the terms of the 
# IBM International Program License Agreement accompanying this program, which is 
# located at <CD_ROOT>\updi.primary.pak\repository\updi.legal\lafiles.  If you do 
# not agree to these terms, do not change the value or otherwise download, install, 
# copy, access, or use the program and promptly return the program and proof of 
# entitlement to the party from whom you acquired it to obtain a refund of the 
# amount you paid.
#
# 
-OPT silentInstallLicenseAcceptance="true"


################################################################################
#
# NonRoot Install Settings
#
# The option indicates whether you accept the limitations associated with installing 
# as a non-root user, which are detailed in the documentation. (specifics to be add)
#
# Valid Values:
#	true - Accepts the limitations. Will install the product.
#	false - Do not accept the limitations. Install will not occur.  
#
# Uncomment the following only if you're installing as a non-root user. Specify one of the
# valid options listed above before proceeding to install:
# -OPT allowNonRootSilentInstall="true"

################################################################################
# Operating System Prerequisite Checking
#
# If you want to disable operating system prerequisite checking, uncomment
# the following line. This will notify the installer to continue with
# the installation and log the warnings even though the prerequisite checking
# has failed.
#
-OPT disableOSPrereqChecking="true"

################################################################################
# Existing Installation Checking
#
# If you want to disable the checking for existing Update Installer, uncomment
# the following line.  This will notify the installer to continue with the
# installation and log the warnings even though the prerequisite checking has
# failed.
# 
# -OPT disableEarlyPrereqChecking="true"

################################################################################
#
# Install Location
#
# The install location of the product. Specify a valid directory into which the
# product should be installed. If the directory contains spaces, enclose it in
# double-quotes as shown in the Windows example below. Note that spaces in the
# install location is only supported on Windows operating systems. Maximum path 
# length is 60 characters for Windows 2000 and Windows XP.
# 
# Below is the list of default install locations for each supported operating
# system when you're installing as a root user.  By default, in this response file, 
# the Windows install location is used.  If you want to use the default install 
# location for another operating system, uncomment the appropriate default install 
# location entry (by removing '#') and then comment out (by adding '#') the 
# Windows operating system entry below.
#
# AIX Default Install Location:
#
#  -OPT installLocation="/usr/IBM/WebSphere/UpdateInstaller"
#
# HP-UX, Solaris or Linux Default Install Location:
#
  -OPT installLocation="/opt/IBM/WebSphere/UpdateInstaller"	
#
# i5OS Default Install Location:
#
#  -OPT installLocation="/QIBM/IBM/WebSphere/UpdateInstaller/V61/<productOffering>"
#
# Windows Default Install Location:
#

#-OPT installLocation="C:\Program Files\IBM\WebSphere\UpdateInstaller"

# If you are installing as non-root user on Unix or non-administrator on Windows, 
# the following default install locations are suggested. Be sure you have write 
# permission for the install location chosen.
#
# AIX Default Install Location:
#
#  -OPT installLocation="<user's home>/IBM/WebSphere/UpdateInstaller"
#
# HP-UX, Solaris or Linux Default Install Location:
#
#  -OPT installLocation="<user's home>/IBM/WebSphere/UpdateInstaller"
#
# i5OS Default Install Location: 
#
#  <not applicable>
#
# Windows Default Install Location: 
#
# -OPT installLocation="C:\IBM\WebSphere\UpdateInstaller"

#
# When the target operating system is Windows, or Linux IA32, you can
# skip the creation of start menu by set the skipStartMenu to true.  
# This option does not apply for all other platforms.
#
# -OPT skipStartMenu=true

################################################################################
# 
# Trace Control Output
# 
# Valid Values for traceFormat:
#     ALL - output files saved as separate plain text and XML files.
#     text - output file saved in plain text format only.
#     XML - output file saved in standard Java logging XML format only.
# 
# Trace output is saved as both text and XML files by default, but it can be 
# restricted to only one output format.
# 
# The amount of trace information captured can be controlled. All informational
# messages, warnings, and severe warnings are output to a trace file by default. 
# 
# Valid values for traceLevel:
#     OFF - No trace file is produced.
#     SEVERE - Only severe errors are output to a trace file.
#     WARNING - Non-fatal exceptions and warnings are added to trace file.
#     INFO - Informational messages are added to the trace file.
#     CONFIG - Configuration related messages are added to the trace file.
#     FINE - Trace all public method calls.
#     FINER - Trace all non-public method calls except getters and setters.
#     FINEST - Trace all methods, entry and exit parameters, and return values.
# 
 -OPT traceFormat=ALL
 -OPT traceLevel=INFO
# 
################################################################################

03-updater-responsefiles-install.txt

################################################################################
#
# This is the silent install response file for installing maintenance packages
# using the update installer.
# 
# A common use of an options file is to run the wizard in silent mode. This lets
# the options file author specify wizard settings without having to run the
# wizard in graphical or console mode. To use this options file for silent mode
# execution, *uncomment* and modify the parameters defined within.
#
# Use the following command line when running the wizard from the update 
# installer directory:
# 
#    update -options responsefiles/install.txt -silent
#
# Please enclose all values within a single pair of double quotes.
#
################################################################################

################################################################################
# 
# File Permission Checking
# 
# The installer does not check that it has sufficient file permissions to 
# perform the installation by default.
# 
# Uncomment the following option to notify the installer that it should
# check that it has sufficient file permissions to perform the required 
# install operation on each file to be installed.
# 
# This option is not applicable for Windows.
# 
# -OPT checkFilePermissions="true"
# 
################################################################################

################################################################################
#
# This section describes how to apply a maintenance package using the full filename specifications to be installed. 
# There are three ways you can specify installing a maintenance package.  They are the following:
# (Use the examples below and edit where appropriate.)
#
# 1. Specify a single maintenance package full filename to be installed.
# 
#    For example:
#    -W maintenance.package="C:\Program Files\IBM\WebSphere\AppServer\UpdateInstaller\maintenance\PQ20029.pak"
#
# 2. Specify a multiple maintenance package full filename to be installed. 
#    -  Use a semicolon to separate the full filename specifications.
#    -  Update Installer will install the latest applicable maintenance in the order listed. 
#
#    For example:  
#    -W maintenance.package="C:\maintenance\PQ20029.pak;C:\maintenance\PK31008.pak;D:\6.1.0-WS-WAS-WinX32-FP0000001.pak" 
#
# 3. Specify a full folder name that contains the maintenance packages.
#    Update Installer will install the latest applicable maintenance in the order listed in the folder.
#
#    For example:
#    -W maintenance.package="D:\UpdateInstaller\maintenance"
#
# Notes: If no package is specified, maintenance packages from the default folder (such as, UpdateInstaller_HOME/maintenance )
#        will be installed.
#
#-W maintenance.package=


################################################################################
# 
# Prerequisite Checking
# 
# The update installer checks the system for prerequisites by default.
# 
# Uncomment the following option to notify the installer to continue with
# the update and log the warnings even though prerequisite checking
# failed.
# 
#-OPT disableNonBlockingPrereqChecking="true"


################################################################################
#
# AIX Non-root User Limitation
#
# The AIX user account running the Update Installer program also must be able to 
# run the slibclean command; otherwise, a root user must run the slibclean command
# before the Update Installer program runs. 
#
# Uncomment the following option to notify the installer that a root user has run
# the slibclean command before the Update Installer program runs.
#
#-OPT rootUserHasRunSlibcleanCommandSuccessfully="true"


################################################################################
#
# Used to input the product install location that will be updated.
#
#    For example:
#    -W product.location="C:\Program Files\IBM\WebSphere\AppServer"
#
# Note: The product install location should always been specified, and it should
# always be the full path.
#
-W product.location="/opt/IBM/WebSphere/AppServer"



################################################################################
#
# Do not edit these values.
#
#
-W update.type="install"

04-websphere-server1

#!/bin/sh -e
### BEGIN INIT INFO
# Provides:          ibm-websphere
# Required-Start:    $local_fs $remote_fs $network $syslog
# Required-Stop:     $local_fs $remote_fs $network $syslog
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: Start/stop IBM WebSphere Application Server
### END INIT INFO
#
# IBM WAS	This init.d script starts the IBM WebSphere 
#           Application Server.

# modify the following line as needed to reflect any custom Java
# installation directory
#ENV="env -i LANG=C PATH=/opt/IBM/ibm-java-x86_64_60/bin:/usr/bin:/bin"

set -e
if [ ! -d /opt/IBM/WebSphere/AppServer/bin ] ; then
	echo "No IBM WebSphere Application Server installed"
	exit 0
fi

. /lib/lsb/init-functions

test -f /etc/default/rcS && . /etc/default/rcS
was_user="wasadmin"
was_password="wasadmin"
server_name="server1"

startscript="/opt/IBM/WebSphere/AppServer/bin/startServer.sh $server_name -username $was_user -password $was_password"
stopscript="/opt/IBM/WebSphere/AppServer/bin/stopServer.sh  $server_name -username $was_user -password $was_password"

case $1 in
	start)
		log_daemon_msg "Starting application server" "IBM WAS"
		if $startscript ; then
			log_end_msg 0
		else
			log_end_msg 1
		fi
	;;
	stop)
		log_daemon_msg "Stopping application server" "IBM WAS"
		if $stopscript ; then
			log_end_msg 0
		else
			log_end_msg 1
		fi
	;;
	restart)
		log_daemon_msg "Restarting web server" "IBM HTTP"
		if ($stopscript && $startscript) ; then
			log_end_msg 0
		else
			log_end_msg 1
		fi
	;;
	*)
		log_success_msg "Usage: /etc/init.d/websphere {start|stop|restart}"
		exit 1
	;;
esac

README

Sample files to use on a websphere 7 installation files on linux

Why are these options commented? Incompatibility?

-OPT PROF_enableService="true"

-OPT PROF_serviceUserName="root"