WebSphere automated deployment on Hudson

Hudson CI server provides plug-in for automated deployment to Tomcat or JBoss servers. But on my current job we use IBM WebSphere as application server in cluster environment. To implement nightly builds with automated testing we had to figure out way to automate deployment.

General idea and code is based on Luciano Resende's posting.



Usual deployment procedure for IBM WebSphere cluster is:



1.Stop cluster

2.Undeploy application

3.Deploy application and change application parameters like classloaders' order

4.Start cluster

5.As a part of automated testing procedure, we had to wait till start completes and then start test

All these steps could take 10-15 minutes depending on environment, was security enabled or not, etc.

To implement automated deployment for WebSphere we can use wsadmin thin client and Apache ant in conjunction with bash scripts.



In order to use wsadmin remotely, several files need to be copied from IBM Websphere node manager.

Wsadmin script, provided on IBM's site, didn't work for me, so I had to change it slightly.

My version of wsadmin



view sourceprint?

01 #!/bin/bash



02 #set -x



03 # example wsadmin launcher



04 binDir=`dirname "$0"`



05 # WAS_HOME should point to the directory for the thin client



06 WAS_HOME="$binDir"



07 USER_INSTALL_ROOT="$WAS_HOME"



08 # JAVA_HOME should point to where java is installed for the thin client



09 WAS_LOGGING="-Djava.util.logging.manager=com.ibm.ws.bootstrap.WsLogManager -Djava.util.logging.configureByServer=true"



10 if [ -f ${JAVA_HOME}/bin/java ]; then



11 JAVA_EXE="${JAVA_HOME}/bin/java"



12 else



13 JAVA_EXE="${JAVA_HOME}/jre/bin/java"



14 fi



15 CLIENTSOAP=-Dcom.ibm.SOAP.ConfigURL=file:"$USER_INSTALL_ROOT"/properties/soap.client.props



16 CLIENTSAS=-Dcom.ibm.CORBA.ConfigURL=file:"$USER_INSTALL_ROOT"/properties/sas.client.props



17 CLIENTSSL=-Dcom.ibm.SSL.ConfigURL=file:"$USER_INSTALL_ROOT"/properties/ssl.client.props



18 wsadminTraceString=-Dcom.ibm.ws.scripting.traceString=com.ibm.*=all=enabled



19 wsadminTraceFile=-Dcom.ibm.ws.scripting.traceFile="$USER_INSTALL_ROOT"/logs/wsadmin.traceout



20 wsadminValOut=-Dcom.ibm.ws.scripting.validationOutput="$USER_INSTALL_ROOT"/logs/wsadmin.valout



21 # For debugging the utility itself



22 WAS_DEBUG="-Djava.compiler=NONE -Xdebug -Xnoagent"



23 #-Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=7777"



24 SHELL=com.ibm.ws.scripting.WasxShell



25 # Parse the input arguments



26 isJavaOption=false



27 nonJavaOptionCount=1



28 for option in "$@" ; do



29 if [ "$option" = "-javaoption" ] ; then



30 isJavaOption=true



31 else



32 if [ "$isJavaOption" = "true" ] ; then



33 javaOption="$javaOption $option"



34 isJavaOption=false



35 else



36 nonJavaOption[$nonJavaOptionCount]="$option"



37 nonJavaOptionCount=$((nonJavaOptionCount+1))



38 fi



39 fi



40 done



41 DELIM=" "



42 C_PATH="$WAS_HOME/com.ibm.ws.admin.client_6.1.0.jar:$WAS_HOME/com.ibm.ws.security.crypto_6.1.0.jar"



43 #Platform specific args...



44 PLATFORM='/bin/uname'



45 case $PLATFORM in



46 AIX
Linux
SunOS
HP-UX)



47 CONSOLE_ENCODING=-Dws.output.encoding=console ;;



48 OS/390)



49 EXTRA_D_ARGS="-Dfile.encoding=ISO8859-1 $DELIM-Djava.ext.dirs="$JAVA_EXT_DIRS""



50 EXTRA_X_ARGS="-Xnoargsconversion" ;;



51 esac



52 # Set java options for performance



53 PLATFORM=`/bin/uname`



54 case $PLATFORM in



55 AIX)



56 PERF_JVM_OPTIONS="-Xms256m -Xmx256m -Xquickstart" ;;



57 Linux)



58 PERF_JVM_OPTIONS="-Xms256m -Xmx256m -Xj9 -Xquickstart" ;;



59 SunOS)



60 PERF_JVM_OPTIONS="-Xms256m -Xmx256m -XX:PermSize=40m" ;;



61 HP-UX)



62 PERF_JVM_OPTIONS="-Xms256m -Xmx256m -XX:PermSize=40m" ;;



63 OS/390)



64 PERF_JVM_OPTIONS="-Xms256m -Xmx256m" ;;



65 esac



66 "$JAVA_EXE" \



67 $EXTRA_X_ARGS \



68 $CONSOLE_ENCODING \



69 $javaOption \



70 $WAS_DEBUG \



71 "$CLIENTSAS" \



72 "$CLIENTSSL" \



73 "$CLIENTSOAP" \



74 ${JAASSOAP:+"$JAASSOAP"} \



75 -Dconfig_consistency_check="$CONFIG_CONSISTENCY_CHECK" \



76 -Dwas.install.root="$WAS_HOME" \



77 -Duser.install.root="$USER_INSTALL_ROOT" \



78 $EXTRA_D_ARGS \



79 $PERF_JVM_OPTIONS \



80 $WAS_LOGGING \



81 $wsadminTraceFile \



82 $wsadminTraceString \



83 $wsadminValOut \



84 $wsadminHost \



85 $wsadminConnType \



86 $wsadminPort \



87 $wsadminLang \



88 -classpath "$C_PATH" \



89 $SHELL "${nonJavaOption[@]}"



90 exit $?





Since we want use in on Hudson, probably on other server and locally, we need Ant script.

It's kinda big and a lot of parameters repeats but it gives idea that's happening.



view sourceprint?

001 <?xml version="1.0"?>



002 <project name="was-integration" basedir=".">



003 <property environment="env"/>



004 <property name="was.python.script" value="./wsIntegration.py"/>



005 <property name="application.name" value="APPLICATION"/>



006 <property name="application.cell" value="CELL"/>



007 <property name="application.cluster" value="CLUSTER"/>



008 <property name="host" value="HOST"/>



009 <property name="port" value="PORT"/>



010 <property name="application.ear" value="PATH_TO_EAR"/>



011 <property name="wsadmin" value="${basedir}/wsadmin.sh"/>



012



013 <target name="clusterState" >



014 <exec dir="." executable="${wsadmin}" outputproperty="currentState">



015 <arg value="-conntype"/>



016 <arg value="SOAP"/>



017 <arg value="-lang"/>



018 <arg value="jython"/>



019 <arg value="-host"/>



020 <arg value="${host}"/>



021 <arg value="-port" />



022 <arg value="${port}"/>



023 <arg value="-f"/>



024 <arg value="${was.python.script}"/>



025 <arg value="clusterState"/>



026 <arg value="${application.cell}"/>



027 <arg value="${application.cluster}"/>



028 </exec>



029 </target>



030



031 <target name="clusterStart" >



032 <exec dir="." executable="${wsadmin}">



033 <arg value="-conntype"/>



034 <arg value="SOAP"/>



035 <arg value="-lang"/>



036 <arg value="jython"/>



037 <arg value="-host"/>



038 <arg value="${host}"/>



039 <arg value="-port" />



040 <arg value="${port}"/>



041 <arg value="-f"/>



042 <arg value="${was.python.script}"/>



043 <arg value="clusterStart"/>



044 <arg value="${application.cell}"/>



045 <arg value="${application.cluster}"/>



046 </exec>



047 </target>



048



049 <target name="clusterStopt" >



050 <exec dir="." executable="${wsadmin}">



051 <arg value="-conntype"/>



052 <arg value="SOAP"/>



053 <arg value="-lang"/>



054 <arg value="jython"/>



055 <arg value="-host"/>



056 <arg value="${host}"/>



057 <arg value="-port" />



058 <arg value="${port}"/>



059 <arg value="-f"/>



060 <arg value="${was.python.script}"/>



061 <arg value="clusterStop"/>



062 <arg value="${application.cell}"/>



063 <arg value="${application.cluster}"/>



064 </exec>



065 </target>



066 <target name="undeployApplication" >



067 <exec dir="." executable="${wsadmin}">



068 <arg value="-conntype"/>



069 <arg value="SOAP"/>



070 <arg value="-lang"/>



071 <arg value="jython"/>



072 <arg value="-host"/>



073 <arg value="${host}"/>



074 <arg value="-port" />



075 <arg value="${port}"/>



076 <arg value="-f"/>



077 <arg value="${was.python.script}"/>



078 <arg value="undeployApplication"/>



079 <arg value="${application.name}"/>



080 </exec>



081 </target>



082



083 <target name="redeployApplication" >



084 <exec dir="." executable="${wsadmin}">



085 <arg value="-conntype"/>



086 <arg value="SOAP"/>



087 <arg value="-lang"/>



088 <arg value="jython"/>



089 <arg value="-host"/>



090 <arg value="${host}"/>



091 <arg value="-port" />



092 <arg value="${port}"/>



093 <arg value="-javaoption" />



094 <arg value="-Dwdm.http.host=${host}" />



095 <arg value="-f"/>



096 <arg value="${was.python.script}"/>



097 <arg value="redeployApplication"/>



098 <arg value="${application.ear}"/>



099 <arg value="${application.cell}"/>



100 <arg value="${application.cluster}"/>



101 <arg value="${application.name}"/>



102 </exec>



103 </target>



104 <target name="fullRedeploy">



105 <antcall target="clusterStopt"/>



106 <exec dir="." executable="./waitForState.sh">



107 <arg value="Cluster State: websphere.cluster.stopped"/>



108 <arg value="${host}"/>



109 <arg value="${port}"/>



110 <arg value="${application.cell}"/>



111 <arg value="${application.cluster}"/>



112 </exec>



113 <antcall target="undeployApplication"/>



114 <antcall target="redeployApplication"/>



115 <antcall target="clusterStart"/>



116 <exec dir="." executable="./waitForState.sh">



117 <arg value="Cluster State: websphere.cluster.running"/>



118 <arg value="${host}"/>



119 <arg value="${port}"/>



120 <arg value="${application.cell}"/>



121 <arg value="${application.cluster}"/>



122 </exec>



123 </target>



124 </project>





Most interesting last part then we stop cluster, wait till it shut downs completely, undeploy application, redeploy application, start cluster and wait will it starts successfully.



We use jython as wsadmin programming language.

Source code for wsIntegration.py



view sourceprint?

01 import sys



02 def clusterStop(cell, cluster):



03 cluster = AdminControl.completeObjectName('cell='+cell+',type=Cluster,name='+cluster+',*')



04 print "Stop Cluster : %s" % ( repr(cluster) )



05 AdminControl.invoke(cluster, 'stop')



06 def clusterStart(cell, cluster):



07 cluster = AdminControl.completeObjectName('cell='+cell+',type=Cluster,name='+cluster+',*')



08 print "Start Cluster : %s" % ( repr(cluster) )



09 AdminControl.invoke(cluster, 'start')



10 def clusterState(cell, cluster):



11 cluster = AdminControl.completeObjectName('cell='+cell+',type=Cluster,name='+cluster+',*')



12 state = AdminControl.getAttribute(cluster, 'state')



13 print "Cluster State: %s" %(state)



14 def appState(app):



15 state = AdminControl.completeObjectName('type=Application,name='+app+',*')



16 print "App State: %s" %(state)



17 def undeployApplication(appName):



18 AdminApp.uninstall( appName )



19 AdminConfig.save()



20 def redeployApplication(pathToFile, cell, cluster, appName):



21 print "installApplicationOnServer: fileName=%s appName=%s Cell=%s Cluster=%s" % ( pathToFile, appName, cell, cluster )



22 AdminApp.install(pathToFile,'[-nopreCompileJSPs -distributeApp -nouseMetaDataFromBinary -nodeployejb -appname "'+appName+'" -createMBeansForResources -noreloadEnabled -nodeployws -MapModulesToServers [["WEB_APP_NAME" WEB_APP_NAME.war,WEB-INF/web.xml WebSphere:cell='+cell+',cluster='+cluster+' ]] -MapWebModToVH [["WEB_APP_NAME" WEB_APP_NAME.war,WEB-INF/web.xml shared_host ]] -verbose]')



23 AdminConfig.save()



24 """modify classloader model for application"""



25 deploymentID = AdminConfig.getid('/Deployment:'+appName+'/')



26 deploymentObject = AdminConfig.showAttribute(deploymentID, 'deployedObject')



27 classldr = AdminConfig.showAttribute(deploymentObject, 'classloader')



28 AdminConfig.modify(classldr, [['mode', 'PARENT_LAST']])



29 """Modify WAR class loader model"""



30 AdminConfig.show(deploymentObject, 'warClassLoaderPolicy')



31 AdminConfig.modify(deploymentObject, [['warClassLoaderPolicy', 'SINGLE']])



32 AdminConfig.save()



33 """-----------------------------------------------------------



34 Phyton script to interface with WAS Admin/Management Tools



35 -----------------------------------------------------------"""



36 if len(sys.argv) < 1:



37 print "wasAdminIntegration.py : need parameters : functionName <ARGS>"



38 sys.exit(0)



39 if(sys.argv[0] == 'clusterStop'):



40 clusterStop(sys.argv[1], sys.argv[2])



41 if(sys.argv[0] == 'clusterStart'):



42 clusterStart(sys.argv[1], sys.argv[2])



43 if(sys.argv[0] == 'clusterState'):



44 clusterState(sys.argv[1], sys.argv[2])



45 if(sys.argv[0] == 'undeployApplication'):



46 undeployApplication(sys.argv[1])



47 if(sys.argv[0] == 'appState'):



48 appState(sys.argv[1])



49 if(sys.argv[0] == 'redeployApplication'):



50 redeployApplication(sys.argv[1], sys.argv[2], sys.argv[3], sys.argv[4])





In this code, replace "WEB_APP_NAME" with real application name or change the script so it can be passed with the rest of parameters.



For waiting part of the scripts, we will user same jython script in conjuction with bash.

Source for waitForState.sh:



view sourceprint?

01 #!/bin/bash



02 binDir=`dirname "$0"`



03 REQURED_STATE=$1



04 WAS_HOST=$2



05 WAS_PORT=$3



06 WAS_CELL=$4



07 WAS_CLUSTER=$5



08 if [ ! -n "$REQURED_STATE" ]

[ ! -n "$WAS_HOST" ]

[ ! -n "$WAS_PORT" ]

[ ! -n "$WAS_CELL" ]

[ ! -n "$WAS_CLUSTER" ];



09 then



10 echo "Usage: waitForState.sh <STATE> <HOST> <PORT> <CELL> <CLUSTER>"



11 exit 1



12 fi



13 CURR_STATE=""



14 echo "CURR_STATE: $CURR_STATE"



15 while [[ "$CURR_STATE" != "$REQURED_STATE" ]]



16 do



17 sleep 20



18 CURR_STATE="$($binDir/wsadmin.sh -conntype SOAP -lang jython -host $WAS_HOST -port $WAS_PORT -f ./wsAdminIntegration.py clusterState $WAS_CELL $WAS_CLUSTER
grep State:)"



19 echo "Current State: $CURR_STATE"



20 done


So, now we can use all these code in conjunction just by calling

view sourceprint?

1 ant fullRedeploy

Output log should be monitored for Websphere errors. If it return "Result: 99" for every operation, then everything is fine, otherwise, something went wrong.

Log files for error during product binary files installation

Log files for error during product binary files installation

After installing WAS 6.1 check the app_server_root/logs/install/log.txt file

to verify that there were no file or other ununsal error while installaing. If there were errors correct them and reinstall product. If the WAS installation was successful the last line in log.txt should be something like this


(Sep 5, 2009 10:48:42 PM), Process, com.ibm.ws.install.ni.ismp.actions.SetExitCodeAction, msg1, CWUPI0000I: EXITCODE=0
(Sep 5, 2009 10:48:42 PM), Process, com.ibm.ws.install.ni.ismp.actions.ISMPLogSuccessMessageAction, msg1, INSTCONFSUCCESS

If the status was either INSTCONFPARTIALSUCCESS or INSTCONFFAILED, then that means the installation was not successful.

If the installation was not successful then take a look at log files.

• app_server_root/logs/install/log.txt: Logs all installation events.


• app_server_root/logs/install/installconfig.log.gz: Logs the activities of ANT configuration scripts that run at the end of installation procedure. If there was error in ant script configuration you should see Configuration action failed message.


• app_server_root/logs/install/trace.log.gz: Contains trace information generated during the install. If the product was installed successfully, the last few lines should look like this
  
2009.09.05 22:48:42.012 EDT I Current install/uninstall process is successful. Process type is: install
2009.09.05 22:48:42.121 EDT I CWUPI0000I: EXITCODE=0
2009.09.05 22:48:42.122 EDT I INSTCONFSUCCESS


• app_server_root/logs/install/trace.xml.gz: Contains trace information generated during the installation in xml format

If the installation of the core product files fails, fix the error and reinstall the product

Important Note: If the error happens early in the installation, look for the log.txt file in the system temporary area. The installation program copies the log from the temporary area to the logs directory at the end of the installation.

During installation, a single entry in the app_server_root/logs/install/log.txt file points to the temporary log file, either %TEMP%\log.txt on Windows platforms, or /tmp/log.txt on platforms such as AIX or Linux. The installation program copies the file from the temporary directory to the app_server_root/logs/install/log.txt location at the end of the installation.

If the installation fails and the log.txt file has only this one pointer to the temporary directory, open the log.txt file in the temporary directory. The log might have clues to the installation failure.

Installing WAS silently

Installing WAS silently

Installing WebSphere Application Server Network Deployment using silent installation refers to using a file to supply installation options without user interaction. To configure the installation, change the options in the response file before you issue the installation command.

You can find the template response file in WAS directory of the CD which has WAS installable. This is response.nd.txt from my machine.

Copy the response file customize it and then you can kick off the installation by executing install -options response_file_fullyqualifiedpath.txt -silent command. Check the app_server_root /logs/install/log.txt file to check status of install


################################################################################
#
# V6.1 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.
# 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:\installImage\WAS\responsefile.nd.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\was.primary.pak\repository\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="false"


################################################################################
#
# NonRoot Install Settings
#
# The option indicates whether you accept the limitations associated with installing
# as a non-root user, as follows:
#
# - Creation of a Windows or Linux service for WebSphere Application Server
# - Native registration with the operating system
#
# Port conflicts may occur with other installations of WebSphere Application Server that are not registered with the operating system.
#
# See the information center, (http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/rins_nonroot.html)
# for more information on performing these installation actions after installation and avoiding port conflicts.
#
# 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 are 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"

################################################################################
#
# Non-blocking Prerequisite Checking
#
# If you want to disable non-blocking 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 disableNonBlockingPrereqChecking="true"

################################################################################
#
# Install Type Settings
#
# The installType option designates the type of installation that will be
# performed.
#
# The default installType option is to install a new copy of WebSphere
# Application Server.
#
# Valid Values:
# installNew - default value, installs a new copy.
# addFeature - add features to an existing installation.

################################################################################
#
# Install a New Copy
#
# To install a new copy, be sure that the installLocation option is set to a
# new install location.
#

-OPT installType="installNew"

################################################################################
#
# Incremental Install
#
# If you are installing additional features on top of an existing installation,
# (e.g. incremental install), uncomment the following line. This will notify
# the installer that you are doing an incremental install.
#
#-OPT installType="addFeature"
#
# Define the new features you want to install on top of an existing WebSphere
# Application Server. The only additional feature available in WebSphere
# Application Server is Application Server Samples.
#
# Ensure the feature option below is set to "samplesSelected" (-OPT feature="samplesSelected")
# and the installLocation option is set to an "existing" WebSphere Application
# Server install location.
#

################################################################################
#
# Create Profile for an Existing V6.1 Installation
#
# Valid values:
# true - creates a profile for an existing installation
# false - does not create a profile
#
# To create a profile for an existing installation, uncomment the following
# entry. Comment out the "installType" option above since "installType"
# and "createProfile" options cannot be specified at the same time.
#
# Be sure the installLocation option is set to your existing install location.
#
#-OPT createProfile="true"

################################################################################
#
# "Application Server samples" feature
#
# The selection state of the "Application Server samples" feature.
#
# Valid options:
#
# samplesSelected - Indicates that the feature is selected for installation.
# noFeature - Indicates that the feature is not selected for installation,
# this is the default option.
#
# For example, to select "Application Server samples" for installation, use
#
# -OPT feature="samplesSelected"
#
# Note if feature="samplesSelected" and PROF_enableAdminSecurity="true",
# you must provide a password by uncommenting and specifying a value for
# PROF_samplesPassword in Administrative Security section below
#
-OPT feature="noFeature"

################################################################################
#
# 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 and then comment out the
# Windows operating system entry below.
#
# AIX Default Install Location:
#
#-OPT installLocation="/usr/IBM/WebSphere/AppServer"
#
# HP-UX, Solaris or Linux Default Install Location:
#
#-OPT installLocation="/opt/IBM/WebSphere/AppServer"
#
# i5OS Default Install Location:
#
#-OPT installLocation="/QIBM/IBM/WebSphere/AppServer/V61/<productOffering>"
#
# Windows Default Install Location:
#

-OPT installLocation="C:\Program Files\IBM\WebSphere\AppServer"
#
# 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/AppServer"
#
# HP-UX, Solaris or Linux Default Install Location:
#
#-OPT installLocation="<user's home>/IBM/WebSphere/AppServer"
#
# Windows Default Install Location:
#
#-OPT installLocation="C:\IBM\WebSphere\AppServer"

################################################################################
#
# Profile Creation Selection
#
# Use this option to indicate the type of profile you would like to create.
#
# Valid Values:
#
# cell - two profiles will be created, one with a deployment manager and
# another with a managed node that is pre-federated into the cell.
# deploymentManager - a profile will be created with a deployment manager.
# standAlone - a profile will be created with a stand alone Application
# server.
# custom - a profile will be created with an empty node
# none - a profile will not be created during installation.
#
# This option is required for the installation on ND. Do not comment it out!
#
# For example, to select "cell" profile creation for installation, use
#

-OPT profileType="cell"

################################################################################
#
# Administrative Security
#
# Choose whether to enable Administrative security during the installation
# process.
#
# If profileType="custom", Administrative security should be disabled, use
#-OPT PROF_enableAdminSecurity="false"
#
# Valid Values:
# true - Administrative security is enabled, user name and
# password required.
# false - Administrative security is not enabled.
#
-OPT PROF_enableAdminSecurity="true"

################################################################################
#
# Security Options
#
# The following two options should only be uncommented when
# PROF_enableAdminSecurity="true".
#
# If PROF_enableAdminSecurity="false", the following entries will be
# disregarded.
#
# If PROF_enableAdminSecurity="true", the following entries are required and must
# be filled out before proceeding with silent installation.
#
# Specify the user name for administrative security
#
# Valid Values:
# a character string - do not use the following characters:
# /, \, *, , , :, ;, =, +, ?, |, <, >, &, %, ', ", ]]>, #, $, ^, {, }
# Note: a period (.) is not valid if it is the first character.
#
-OPT PROF_adminUserName=
#
# Specify the password for the user specified in PROF_adminUserName
#
# Valid Values:
# a character string
#
-OPT PROF_adminPassword=
#
# The following option should only be uncommented when feature="samplesSelected" and
# PROF_enableAdminSecurity="true"
# Specify the password for samples user
#
# Valid Values:
# a character string
#
#-OPT PROF_samplesPassword=


################################################################################
################################################################################
#
# The following options are related to creating profiles and can only be used
# when installType="installNew" or createProfile="true". The options are dependent
# on the profileType option specified in the previous section.
#

################################################################################
################################################################################
#
# Cell Profile
#
# If profileType="cell", use the following profile creation options:
#
################################################################################
#
# Deployment Manager Profile name
#
# Specify the name of the profile for the deployment manager. The profile
# name must be unique for this WebSphere Application Server installation.
#
# Valid Values:
# a character string - do not use the following characters:
# /, \, *, , , :, ;, =, +, ?, |, <, >, &, %, ', ", ]]>, #, $, ^, {, }
# Note: a period (.) is not valid if it is the first character.
#
#-OPT PROF_dmgrProfileName=

################################################################################
#
# Application Server Profile name
#
# Specify the name of the profile for the application server. The profile
# name must be unique for this WebSphere Application Server installation.
#
# Valid Values:
# a character string - do not use the following characters:
# /, \, *, , , :, ;, =, +, ?, |, <, >, &, %, ', ", ]]>, #, $, ^, {, }
# Note: a period (.) is not valid if it is the first character.
#
#-OPT PROF_appServerProfileName=

################################################################################
#
# Profile path
#
# Specify a valid directory to contain the files that define the run-time environment,
# such as commands,configuration files, and log files.
#
# Valid Values: An empty directory, the user must have proper permissions to the directory,
# there must be adequate disk space, total path cannot be greater than 80 (windows)
#
#-OPT PROF_profilePath=

################################################################################
#
# Default Profile
#
# Uncomment the following line to make this profile the default target of commands
# that do not use their profile parameter.
# Note that the first profile created for an installation is always marked as
# the default profile.
#
# Valid Value:
# true - make this the default profile.
#
#-OPT PROF_isDefault="true"

################################################################################
#
# Host name
#
# Specify the host name for the Deployment Manager. The host name is the domain
# name system (DNS) name (short or long) or the IP address of this computer.
# Valid Values: a valid hostname or IP address
#
#-OPT PROF_hostName=

################################################################################
#
# Deployment Manager Node name
#
# Specify the node name for the deployment manager. Node names within a cell
# must be unique.
#
# Valid Values:
# a character string - do not use the following characters:
# /, \, *, , , :, ;, =, +, ?, |, <, >, &, %, ', ", ]]>, #, $, ^, {, }
# Note: a period (.) is not valid if it is the first character.
#
#-OPT PROF_nodeName=

################################################################################
#
# Application Server Node name
#
# Specify the node name for the Application Server. Node name under one cell
# has to be unique.
#
# Valid Values:
# a character string - do not use the following characters:
# /, \, *, , , :, ;, =, +, ?, |, <, >, &, %, ', ", ]]>, #, $, ^, {, }
# Note: a period (.) is not valid if it is the first character.
#
#-OPT PROF_appServerNodeName=

################################################################################
#
# Cell name
#
# Specify the cell name for the profile to be created.
#
# Valid Values:
# a character string - do not use the following characters:
# /, \, *, , , :, ;, =, +, ?, |, <, >, &, %, ', ", ]]>, #, $, ^, {, }
# Note: a period (.) is not valid if it is the first character.
#
#-OPT PROF_cellName=

################################################################################
#
# Starting Port
#
# Specify the starting port number for generating all ports for the profile.
# Do not use this parameter with the PROF_portsFile or PROF_defaultPorts parameters.
#
# Valid values: a positive integer port value, within the valid port range
#
#-OPT PROF_startingPort=

################################################################################
#
# Node Starting Port
#
# Specify the starting port number for the node portion of the cell.
# Do not use this parameter with the PROF_nodePortsFile parameter.
#
# Valid values: a positive integer port value, within the valid port range
#
#-OPT PROF_nodeStartingPort=

################################################################################
#
# Port File
#
# Specify the path to a property file containing the desired port values for
# the new profile. Do not use this parameter with the PROF_startingPort or
# PROF_defaultPorts parameters.
#
# Valid values: A fully qualified path to a valid ports property file
#
#-OPT PROF_portsFile=

################################################################################
#
# Node Port File
#
# Specify the path to a property file containing the desired port values for
# the new profile. Do not use this parameter with the PROF_startingPort or
# PROF_defaultPorts parameters.
#
# Valid values: A fully qualified path to a valid ports property file that defines
# port settings for the node portion of the cell.
# Do not use this parameter with the PROF_nodeStartingPort parameter.
#
#-OPT PROF_nodePortsFile=

################################################################################
#
# Default Ports
#
# Uncomment the following line to assign the default port values.
# Otherwise unique port values will be assigned.
# Do not use this parameter with the PROF_portsFile or PROF_startingPort parameters.
#
# Valid value:
# true - use WAS default ports.
#
#-OPT PROF_defaultPorts="true"

################################################################################
#
# Validate Ports
#
# Uncomment the following line to validate the port values to ensure they are
# not reserved or in use. Otherwise, no port validation checking will occur.
#
# Valid value:
# true - enables port validation.
#
#-OPT PROF_validatePorts="true"

################################################################################
#
# WinService Check
#
# Specify whether you want to run this server as a windows service
#
# Valid values:
# true - run as Windows service.
# false - do not run as Windows service.
#
#-OPT PROF_winserviceCheck="true"

################################################################################
#
# WinService Account Type
#
# Specify the type of the owner account of the Windows service to create.
# Uncomment the following ONLY if PROF_winserviceCheck="true"
#
# Valid values: specifieduser or localsystem
#
#-OPT PROF_winserviceAccountType=

################################################################################
#
# WinService User Name
#
# Specify the user name for the windows service. Uncomment the
# following ONLY if PROF_winserviceCheck="true"
#
# Valid values: a valid user name for the current system
#
#-OPT PROF_winserviceUserName=

################################################################################
#
# WinService Password
#
# Specify the password for the user specified by the winserviceUserName parameter
# Uncomment the following ONLY if PROF_winserviceCheck="true"
#
# Valid Values:
# a character string - do not use the following characters:
# /, \, *, , , :, ;, =, +, ?, |, <, >, &, %, ', ", ]]>, #, $, ^, {, }
# Note: a period (.) is not valid if it is the first character.
#
#-OPT PROF_winservicePassword=

################################################################################
#
# WinService Startup Type
#
# Specify the start up method for the windows service
# Uncomment the following ONLY if PROF_winserviceCheck="true"
#
# Valid values:
# manual - windows service must be started manually.
# automatic - windows service will start automatically after reboot.
# disabled - service is disabled.
#
#-OPT PROF_winserviceStartupType="automatic"

################################################################################
#
# LinuxService Check
#
# Specify whether you want to run this server as a Linux service.
#
# Note that the root permission is required to enable Linux service.
#
# Valid values:
# true - run as a Linux service.
# false - do not run as a Linux service.
#
#-OPT PROF_enableService="true"

################################################################################
#
# LinuxService User Name
#
# Specify the name of the user you wish this service to be run as. Uncomment the
# following ONLY if PROF_enableService="true". Linux services can only be created
# from profile creation if the current user is the root user.
#
# Valid values: a valid Linux user name
#
#-OPT PROF_serviceUserName=
################################################################################
#
# WebServer Check
#
# Specify whether you wish to set the web server definition.
#
# Valid values:
# true - enable the creation of a webserver definition.
# false - do not enable the creation of a webserver definition.
#
#-OPT PROF_webServerCheck="true"


################################################################################
#
# WebServer Type
#
# Specify the type of web server you are creating.
# Uncomment the following if and ONLY if PROF_webServerCheck="true".
#
# Valid values (case sensitive): IHS | IIS | SUNJAVASYSTEM | DOMINO | APACHE | HTTPSERVER_ZOS
#
#-OPT PROF_webServerType=

################################################################################
#
# WebServer OS
#
# Specify the operating system of the system where the web server is
# installed. Uncomment the following if and ONLY if PROF_webServerCheck="true".
#
# Valid values: linux | windows | aix | hpux | solaris | os390 | os400
#
#-OPT PROF_webServerOS=

################################################################################
#
# WebServer Name
#
# Specify the name of the web server. Uncomment the following if and ONLY if
# PROF_webServerCheck="true".
#
# Valid Values:
# a character string - do not use the following characters:
# /, \, *, , , :, ;, =, +, ?, |, <, >, &, %, ', ", ]]>, #, $, ^, {, }
# Note: a period (.) is not valid if it is the first character.
#
#-OPT PROF_webServerName=

################################################################################
#
# WebServer Hostname
#
# Specify the hostname of the system with the web server. Uncomment the following
# if and ONLY if PROF_webServerCheck="true".
#
# Valid values: a valid hostname or IP address
#
#-OPT PROF_webServerHostname=

################################################################################
#
# WebServer Port
#
# Specify the port from which the web server can be accessed. Uncomment the
# following if and ONLY if PROF_webServerCheck="true".
#
# Valid values: a valid port number
#
#-OPT PROF_webServerPort=

################################################################################
#
# WebServer Install Path
#
# Specify the installation path of the web server (local or remote).
# Uncomment the following if and ONLY if PROF_webServerCheck="true".
#
# Valid values: a valid directory path
#
#-OPT PROF_webServerInstallPath=

################################################################################
#
# WebServer Plugin Path
#
# Specify the path to the plugins that will be used by this web server.
# Uncomment the following if and ONLY if PROF_webServerCheck="true".
#
# Valid values: a valid directory path
#
#-OPT PROF_webServerPluginPath=

################################################################################
# Omit Action
#
# Use this option to omit the config action specified in the Application Server
# profile.
#
# Valid values: one of the following optional config actions
# deployAdminConsole
# defaultAppDeployAndConfig
# samplesInstallAndConfig
#
#-OPT PROF_omitAction=

################################################################################
#
# Deployment Manager Profile
#
# if profileType="deploymentManager", use the following profile creation
# options:
#
################################################################################
#
# Profile name
#
# Specify the name of the profile for the Deployment Manager. The profile
# name must be unique for this WebSphere Application Server installation.
#
# Valid Values:
# a character string - do not use the following characters:
# /, \, *, , , :, ;, =, +, ?, |, <, >, &, %, ', ", ]]>, #, $, ^, {, }
# Note: a period (.) is not valid if it is the first character.
#
#-OPT PROF_profileName=

################################################################################
#
# Profile path
#
# Specify a valid directory to contain the files that define the run-time environment,
# such as commands,configuration files, and log files.
#
# Valid Values: An empty directory, the user must have proper permissions to the directory,
# there must be adequate disk space, total path cannot be greater than 80 (windows)
#
#-OPT PROF_profilePath=

################################################################################
#
# Default Profile
#
# Uncomment the following line to make this profile the default target of commands
# that do not use their profile parameter.
# Note that the first profile created for an installation is always marked as
# the default profile.
#
# Valid Value:
# true - make this the default profile.
#
#-OPT PROF_isDefault="true"

################################################################################
#
# Host name
#
# Specify the host name for the Deployment Manager. The host name is the domain
# name system (DNS) name (short or long) or the IP address of this computer.
# Valid Values: a valid hostname or IP address
#
#-OPT PROF_hostName=

################################################################################
#
# Deployment Manager Node name
#
# Specify the node name for the deployment manager. Node names within a cell
# must be unique.
#
# Valid Values:
# a character string - do not use the following characters:
# /, \, *, , , :, ;, =, +, ?, |, <, >, &, %, ', ", ]]>, #, $, ^, {, }
# Note: a period (.) is not valid if it is the first character.
#
#-OPT PROF_nodeName=

################################################################################
#
# Cell name
#
# Specify the cell name for the profile to be created.
#
# Valid Values:
# a character string - do not use the following characters:
# /, \, *, , , :, ;, =, +, ?, |, <, >, &, %, ', ", ]]>, #, $, ^, {, }
# Note: a period (.) is not valid if it is the first character.
#
# -OPT PROF_cellName=

################################################################################
#
# Starting Port
#
# Specify the starting port number for generating all ports for the profile.
# Do not use this parameter with the PROF_portsFile or PROF_defaultPorts parameters.
#
# Valid values: a positive integer port value, within the valid port range
#
#-OPT PROF_startingPort=

################################################################################
#
# Port File
#
# Specify the path to a property file containing the desired port values for
# the new profile. Do not use this parameter with the PROF_startingPort or
# PROF_defaultPorts parameters.
# Valid values: A fully qualified path to a valid ports property file
#
#-OPT PROF_portsFile=

################################################################################
#
# Default Ports
#
# Uncomment the following line to assign the default port values.
# Otherwise unique port values will be assigned.
# Do not use this parameter with the PROF_portsFile or PROF_startingPort parameters.
#
# Valid value:
# true - use WAS default ports.
#
#-OPT PROF_defaultPorts="true"

################################################################################
#
# Validate Ports
#
# Uncomment the following line to validate the port values to ensure they are
# not reserved or in use. Otherwise, no port validation checking will occur.
#
# Valid value:
# true - enables port validation.
#
#-OPT PROF_validatePorts="true"

################################################################################
#
# WinService Check
#
# Specify whether you want to run this server as a windows service
#
# Valid values:
# true - run as Windows service.
# false - do not run as Windows service.
#
#-OPT PROF_winserviceCheck="true"

################################################################################
#
# WinService Account Type
#
# Specify the type of the owner account of the Windows service to create.
# Uncomment the following ONLY if PROF_winserviceCheck="true"
#
# Valid values: specifieduser or localsystem
#
#-OPT PROF_winserviceAccountType=

################################################################################
#
# WinService User Name
#
# Specify the user name for the windows service. Uncomment the
# following ONLY if PROF_winserviceCheck="true"
#
# Valid values: a valid user name for the current system
#
#-OPT PROF_winserviceUserName=

################################################################################
#
# WinService Password
#
# Specify the password for the user specified by the winserviceUserName parameter
# Uncomment the following ONLY if PROF_winserviceCheck="true"
#
# Valid Values:
# a character string - do not use the following characters:
# /, \, *, , , :, ;, =, +, ?, |, <, >, &, %, ', ", ]]>, #, $, ^, {, }
# Note: a period (.) is not valid if it is the first character.
#
#-OPT PROF_winservicePassword=

################################################################################
#
# WinService Startup Type
#
# Specify the start up method for the windows service
# Uncomment the following ONLY if PROF_winserviceCheck="true"
#
# Valid values:
# manual - windows service must be started manually.
# automatic - windows service will start automatically after reboot.
# disabled - service is disabled.
#
# -OPT PROF_winserviceStartupType="automatic"

################################################################################
#
# LinuxService Check
#
# Specify whether you want to run this server as a Linux service.
#
# Note that the root permission is required to enable Linux service.
#
# Valid values:
# true - run as a Linux service.
# false - do not run as a Linux service.
#
#-OPT PROF_enableService="true"

################################################################################
#
# LinuxService User Name
#
# Specify the name of the user you wish this service to be run as. Uncomment the
# following ONLY if PROF_enableService="true". Linux services can only be created
# from profile creation if the current user is the root user.
#
# Valid values: a valid Linux user name
#
#-OPT PROF_serviceUserName=

################################################################################
# Omit Action
#
# Use this option to omit the config action specified
#
# Valid values: A valid name for an optional config action: deployAdminConsole
#
#-OPT PROF_omitAction="deployAdminConsole"

################################################################################
#
# Stand-Alone Profile
#
# if profileType="standAlone", you may use the following profile creation
# options:
#
################################################################################
#
# Profile name
#
# Specify the name of the profile for the Application Server. The profile
# name must be unique for this WebSphere Application Server installation.
#
# Valid Values:
# a character string - do not use the following characters:
# /, \, *, , , :, ;, =, +, ?, |, <, >, &, %, ', ", ]]>, #, $, ^, {, }
# Note: a period (.) is not valid if it is the first character.
#
#-OPT PROF_profileName=

################################################################################
#
# Profile path
#
# Specify a valid directory to contain the files that define the run-time environment,
# such as commands,configuration files, and log files.
#
# Valid Values: An empty directory, the user must have proper permissions to the directory,
# there must be adequate disk space, total path cannot be greater than 80 (windows)
#
#-OPT PROF_profilePath=

################################################################################
#
# Default Profile
#
# Uncomment the following line to make this profile the default target of commands
# that do not use their profile parameter.
# Note that the first profile created for an installation is always marked as
# the default profile.
#
# Valid Value:
# true - make this the default profile.
#
#-OPT PROF_isDefault="true"

################################################################################
#
# Host name
#
# Specify the host name for the Application Server. The host name is the domain
# name system (DNS) name (short or long) or the IP address of this computer.
# Valid Values: a valid hostname or IP address
#
#-OPT PROF_hostName=

################################################################################
#
# Application Server Node name
#
# Specify the node name for the Application Server. Node name under one cell
# has to be unique.
#
# Valid Values:
# a character string - do not use the following characters:
# /, \, *, , , :, ;, =, +, ?, |, <, >, &, %, ', ", ]]>, #, $, ^, {, }
# Note: a period (.) is not valid if it is the first character.
#
#-OPT PROF_nodeName=

################################################################################
#
# Cell name
#
# Specify the cell name for the profile to be created.
#
# Valid Values:
# a character string - do not use the following characters:
# /, \, *, , , :, ;, =, +, ?, |, <, >, &, %, ', ", ]]>, #, $, ^, {, }
# Note: a period (.) is not valid if it is the first character.
#
# -OPT PROF_cellName=

################################################################################
#
# Starting Port
#
# Specify the starting port number for generating all ports for the profile.
# Do not use this parameter with the PROF_portsFile or PROF_defaultPorts parameters.
#
# Valid values: a positive integer port value, within the valid port range
#
#-OPT PROF_startingPort=

################################################################################
#
# Port File
#
# Specify the path to a property file containing the desired port values for
# the new profile. Do not use this parameter with the PROF_startingPort or
# PROF_defaultPorts parameters.
# Valid values: A fully qualified path to a valid ports property file
#
#-OPT PROF_portsFile=

################################################################################
#
# Default Ports
#
# Uncomment the following line to assign the default port values.
# Otherwise unique port values will be assigned.
# Do not use this parameter with the PROF_portsFile or PROF_startingPort parameters.
#
# Valid value:
# true - use WAS default ports.
#
#-OPT PROF_defaultPorts="true"

################################################################################
#
# Validate Ports
#
# Uncomment the following line to validate the port values to ensure they are
# not reserved or in use. Otherwise, no port validation checking will occur.
#
# Valid value:
# true - enables port validation.
#
#-OPT PROF_validatePorts="true"

################################################################################
#
# WinService Check
#
# Specify whether you want to run this server as a windows service
#
# Valid values:
# true - run as Windows service.
# false - do not run as Windows service.
#
#-OPT PROF_winserviceCheck="true"

################################################################################
#
# WinService Account Type
#
# Specify the type of the owner account of the Windows service to create.
# Uncomment the following ONLY if PROF_winserviceCheck="true"
#
# Valid values: specifieduser or localsystem
#
#-OPT PROF_winserviceAccountType=

################################################################################
#
# WinService User Name
#
# Specify the user name for the windows service. Uncomment the
# following ONLY if PROF_winserviceCheck="true"
#
# Valid values: a valid user name for the current system
#
#-OPT PROF_winserviceUserName=

################################################################################
#
# WinService Password
#
# Specify the password for the user specified by the winserviceUserName parameter
# Uncomment the following ONLY if PROF_winserviceCheck="true"
#
# Valid Values:
# a character string - do not use the following characters:
# /, \, *, , , :, ;, =, +, ?, |, <, >, &, %, ', ", ]]>, #, $, ^, {, }
# Note: a period (.) is not valid if it is the first character.
#
#-OPT PROF_winservicePassword=

################################################################################
#
# WinService Startup Type
#
# Specify the start up method for the windows service
# Uncomment the following ONLY if PROF_winserviceCheck="true"
#
# Valid values:
# manual - windows service must be started manually.
# automatic - windows service will start automatically after reboot.
# disabled - service is disabled.
#
# -OPT PROF_winserviceStartupType="automatic"

################################################################################
#
# LinuxService Check
#
# Specify whether you want to run this server as a Linux service.
#
# Note that the root permission is required to enable Linux service.
#
# Valid values:
# true - run as a Linux service.
# false - do not run as a Linux service.
#
#-OPT PROF_enableService="true"

################################################################################
#
# LinuxService User Name
#
# Specify the name of the user you wish this service to be run as. Uncomment the
# following ONLY if PROF_enableService="true". Linux services can only be created
# from profile creation if the current user is the root user.
#
# Valid values: a valid Linux user name
#
#-OPT PROF_serviceUserName=

################################################################################
#
# WebServer Check
#
# Specify whether you wish to set the web server definition.
#
# Valid values:
# true - enable the creation of a webserver definition.
# false - do not enable the creation of a webserver definition.
#
#-OPT PROF_webServerCheck="true"


################################################################################
#
# WebServer Type
#
# Specify the type of web server you are creating.
# Uncomment the following if and ONLY if PROF_webServerCheck="true".
#
# Valid values (case sensitive): IHS | IIS | SUNJAVASYSTEM | DOMINO | APACHE | HTTPSERVER_ZOS
#
#-OPT PROF_webServerType=

################################################################################
#
# WebServer OS
#
# Specify the operating system of the system where the web server is
# installed. Uncomment the following if and ONLY if PROF_webServerCheck="true".
#
# Valid values: linux | windows | aix | hpux | solaris | os390 | os400
#
#-OPT PROF_webServerOS=

################################################################################
#
# WebServer Name
#
# Specify the name of the web server. Uncomment the following if and ONLY if
# PROF_webServerCheck="true".
#
# Valid Values:
# a character string - do not use the following characters:
# /, \, *, , , :, ;, =, +, ?, |, <, >, &, %, ', ", ]]>, #, $, ^, {, }
# Note: a period (.) is not valid if it is the first character.
#
#-OPT PROF_webServerName=

################################################################################
#
# WebServer Hostname
#
# Specify the hostname of the system with the web server. Uncomment the following
# if and ONLY if PROF_webServerCheck="true".
#
# Valid values: a valid hostname or IP address
#
#-OPT PROF_webServerHostname=

################################################################################
#
# WebServer Port
#
# Specify the port from which the web server can be accessed. Uncomment the
# following if and ONLY if PROF_webServerCheck="true".
#
# Valid values: a valid port number
#
#-OPT PROF_webServerPort=

################################################################################
#
# WebServer Install Path
#
# Specify the installation path of the web server (local or remote).
# Uncomment the following if and ONLY if PROF_webServerCheck="true".
#
# Valid values: a valid directory path
#
#-OPT PROF_webServerInstallPath=

################################################################################
#
# WebServer Plugin Path
#
# Specify the path to the plugins that will be used by this web server.
# Uncomment the following if and ONLY if PROF_webServerCheck="true".
#
# Valid values: a valid directory path
#
#-OPT PROF_webServerPluginPath=

################################################################################
#
# Omit Action
#
# Use this option to omit the config action specified
#
# Valid values: one of the following optional config actions
# deployAdminConsole
# defaultAppDeployAndConfig
# samplesInstallAndConfig
#
#-OPT PROF_omitAction=

################################################################################
#
# Developer Server
#
# Uncomment the following line to configure the default application server with
# development environment settings.
# The developer server has a smaller footprint and quicker startup time.
# Otherwise the default configuration values for an application server will be assigned.
#
# Valid value:
# true - mark this default server for development purposes only.
#
#-OPT PROF_isDeveloperServer="true"

################################################################################
#
# Custom Profile
#
# if profileType="custom", you may use the following profile creation options:
#
################################################################################
#
# Profile name
#
# Specify the name of the profile for the Application Server. The profile
# name must be unique for this WebSphere Application Server installation.
#
# Valid Values:
# a character string - do not use the following characters:
# /, \, *, , , :, ;, =, +, ?, |, <, >, &, %, ', ", ]]>, #, $, ^, {, }
# Note: a period (.) is not valid if it is the first character.
#
#-OPT PROF_profileName=

################################################################################
#
# Profile path
#
# Specify a valid directory to contain the files that define the run-time environment,
# such as commands,configuration files, and log files.
#
# Valid Values: An empty directory, the user must have proper permissions to the directory,
# there must be adequate disk space, total path cannot be greater than 80 (windows)
#
#-OPT PROF_profilePath=

################################################################################
#
# Default Profile
#
# Uncomment the following line to make this profile the default target of commands
# that do not use their profile parameter.
# Note that the first profile created for an installation is always marked as
# the default profile.
#
# Valid Value:
# true - make this the default profile.
#
#-OPT PROF_isDefault="true"

################################################################################
#
# Deployment Manager Hostname
#
# Specify the hostname or address of the machine where the deployment manager
# is running.
#
# Valid values: a valid deployment manager hostname
#
#-OPT PROF_dmgrHost="localhost"

################################################################################
#
# Deployment Manager Port
#
# Specify the SOAP port of the deployment manager.
#
# Valid values: a valid port number
#
#-OPT PROF_dmgrPort="8879"

################################################################################
#
# Deployment Manager Admin User Name
#
# Specify an administrative username that can be authenticated, if
# administrative security on the deployment manager is enabled.
#
# Valid values: a valid deployment manager admin username
#
#-OPT PROF_dmgrAdminUserName=

################################################################################
#
# Deployment Manager Admin Password
#
# Specify a password that can be authenticated, if administrative security
# on the deployment manager is enabled.
#
# Valid values: a valid deployment manager password
#
#-OPT PROF_dmgrAdminPassword=

################################################################################
#
# Host name
#
# Specify the host name for the Application Server. The host name is the domain
# name system (DNS) name (short or long) or the IP address of this computer.
# Valid Values: a valid hostname or IP address
#
#-OPT PROF_hostName=

################################################################################
#
# Application Server Node name
#
# Specify the node name for the Application Server. Node name under one cell
# has to be unique.
#
# Valid Values:
# a character string - do not use the following characters:
# /, \, *, , , :, ;, =, +, ?, |, <, >, &, %, ', ", ]]>, #, $, ^, {, }
# Note: a period (.) is not valid if it is the first character.
#
#-OPT PROF_nodeName=

################################################################################
#
# Cell name
#
# Specify the cell name for the profile to be created.
#
# Valid Values:
# a character string - do not use the following characters:
# /, \, *, , , :, ;, =, +, ?, |, <, >, &, %, ', ", ]]>, #, $, ^, {, }
# Note: a period (.) is not valid if it is the first character.
#
#-OPT PROF_cellName=


################################################################################
#
# Port File
#
# Specify the path to a property file containing the desired port values for
# the new profile. Do not use this parameter with the PROF_startingPort or
# PROF_defaultPorts parameters.
# Valid values: A fully qualified path to a valid ports property file
#
#-OPT PROF_portsFile=

################################################################################
#
# Federate Later
#
# Specify whether federation of the node will be done at a later time.
#
# Valid Values:
# true - federate this node later.
# false - federate this node now.
#-OPT PROF_federateLater="false"

################################################################################
#
# Tracing Control
#
# The trace output format can be controlled via the option
# -OPT traceFormat=ALL
#
# The choices for the format are 'text' and 'XML'. By default, both formats will be produced, in two different trace files.
#
# If only one format is required, use the traceFormat option to specify which one, as follows:
#
# Valid Values:
# text - Lines in the trace file will be in a plain text format for easy readability.
# XML - Lines in the trace file will be in the standard Java logging XML format which can be viewed using any text or XML editor or using the Chainsaw tool from Apache (http://logging.apache.org/log4j/docs/chainsaw.html).
#
#
#
# The amount of trace info captured can be controlled using the option:
# -OPT traceLevel=INFO
#
# Valid Values:
#
# Level Numerical Level Description
# OFF 0 No trace file is produced
# SEVERE 1 Only severe errors are output to trace file
# WARNING 2 Messages regarding non-fatal exceptions and warnings are added to trace file
# INFO 3 Informational messages are added to the trace file (this is the default trace level)
# CONFIG 4 Configuration related messages are added to the trace file
# FINE 5 Tracing method calls for public methods
# FINER 6 Tracing method calls for non public methods except getters and setters
# FINEST 7 Trace all method calls, trace entry/exit will include parameters and return value

Checksum (installver) command

Checksum (installver) command

After installing the product or after installing maintenance packages, you can use the installation verification utility (IVU) to compute checksums of the installed file set to verify the checksum against the checksum in the product bill of materials.

The IVU tool is installed during the installation of the following product components:

• WebSphere Application Server Network Deployment


• Application Client


• IBM HTTP Server


• Web server plug-ins


• Update Installer for WebSphere Application Server

After installation, verify actual checksums of installed files against a bill of materials that ships with the product. If the checksums match, the installed product is installed correctly. If the checksums differ, review the differences to determine whether a problem exists.

Verify Instllation - Snoop servlet

WebSphere Application Server provides a default configuration that administrators can use to easily verify that the Application installed is installed properly and running. When the product is installed, it includes an application server called server1 and enterprise aplication called Default Application. The Default application has snoop servlet, that retrieves information about a servlet request. The servlet returns following information

• Servlet initialization parameters


• Servlet context initialization parameters


• URL invocation request parameters


• Preferred client locale


• Context path


• User principal


• Request headers and their values


• Request parameter names and their values


• HTTPS protocol information


• Servlet request attributes and their values


• HTTP session information


• Session attributes and their values

The Snoop servlet includes security configuration so that when WebSphere Security is enabled, clients must supply a user ID and password to initiate the servlet.

You can access the snoop servlet at http://localhost:9080/snoop. This screen shot is from the response that i get on my machine