This procedure uses a script that calls up the WebSphere response file during automated installation.
Upload the WebSphere RPM to the local knowledge base.
The RPM will be listed under Local -> Local RPMs. See Adding Undetected Linux Software.
Create a Local File Declaration that is the path where the response file should be installed.
For example, the path is /tmp/WSresponse.txt
Upload the response file as a Local Configuration File under the File Declaration.
Create a script that runs WebSphere integrated installation procedures with the response file and then starts WebSphere.
#!/bin/sh # In this example, the installation directory should be # on a local filesystem. Should be updated for NFS if # moved to a non-standalone demo system SOURCE_DIR=”/root/demoscripts/websphere/WAS5Trial” WS_DIR=”/opt/WebSphere/AppServer/bin” # Ensure that the installation directory is available if [ ! -f $SOURCE_DIR/install ] ; then echo “WebSphere installer not available.” exit 1 fi #Install WebSphere using response file $SOURCE_DIR/install -options /tmp/wsresponse.rsp # Start the WebSphere server $WS_DIR/startServer.sh server1 exit 0 |
Upload the script under Local -> Post-actions -> postinstallWS.
See Uploading Actions.
Create a script that creates WebSphere users and groups.
#!/bin/sh # In this example, the installation directory should be # on a local filesystem. Should be updated for NFS if # moved to a non-standalone demo system SOURCE_DIR=”/root/demoscripts/websphere/WAS5Trial” # Users and groups needed if installing the Messaging Sub-system # (MQ Series) groupadd mqm groupadd mqbrkrs useradd -g mqm -G mqbrkrs mqm # Ensure that the installation directory is available if [ ! -f $SOURCE_DIR/install ] ; then echo “WebSphere installer not available.” exit 1 fi exit 0 |
Upload the script under Local -> Post-actions -> postsetupWS.
See Uploading Actions.
Create a profile that requires the following:
WebSphere RPM
Local -> Configuration files -> response file
Local -> Post-actions -> postinstallWS
See To Create a Profile.
Create a profile that requires Local -> Post-actions -> postsetupWS.
See To Create a Profile.
Create a complex job that deploys the first profile and then the second profile on selected hosts.