In this third part of the “Prompt-free Appliance deployment” series, we will see what scripts have to be modified and how to suppress the prompt on the very first VM startup.
After mounting the disk as described in the previous step we can go further and one by one, take the prompt and the corresponding piece of script.
The main script is /opt/oracle/psft/vm/oraclevm-template.sh. Everything will start/end out there.
1. License agreement
This is the very first prompt you are facing to.
Most likely you want to respond yes, otherwise everything will stop right away.
Taken the file /opt/oracle/psft/vm/oraclevm-template.sh, we can easily see where this prompt comes from:
# display the banner if it exists and greater than 0 size
if [ -s $SCRIPT_PATH/.banner ]; then
DISPLAY_BANNER=$(<$SCRIPT_PATH/.banner)
echo ""
echo "$DISPLAY_BANNER"
echo ""
echo -n "Do you want to proceed [y|n]: "
GetYNResponse
if [ $? == 0 ]; then
# user decided not to proceed, exit the VM
echo ""
echo "You have decided not to proceed with the initialization, "
echo "the VM will be shutdown now"
echo ""
ovm_press_anykey 5
shutdown -hP now
else
echo ""
fi
fi
And looking into the directory we can see that hidden file .banner:
[root@omsa:/mnt/HCMDB-SES-85302d/opt/oracle/psft/vm]# ls -la|grep banner
-r--r--r-- 1 root root 567 Apr 1 07:50 .banner
[root@omsa:/mnt/HCMDB-SES-85302d/opt/oracle/psft/vm]#
The content of the file is actually the prompt:
[root@omsa:/mnt/HCMDB-SES-85302d/opt/oracle/psft/vm]# more .banner
***SECURITY WARNING***
This virtual appliance has been constructed for ease of installation and
reduced setup time compared to a normal PeopleSoft installation using
downloaded media. It utilizes default user id and passwords throughout the
included tech stack in order to accomplish this. If your installation
requires a more secure environment please utilize the information in the
Oracle Support Document 747524.1 (Securing Your PeopleSoft Application
Environment) which can be found at:
https://support.oracle.com/epmos/faces/DocumentDisplay?id=747524.1
The easiest way to supress the license agreement prompt will probably to rename this .banner file:
[root@omsa:/mnt/HCMDB-SES-85302d/opt/oracle/psft/vm]# mv .banner .banner.orig
2. The root password
If you read the script /opt/oracle/psft/vm/oraclevm-template.sh it is starting with calling a script /usr/lib/oraclevm-template/functions. This one actually contains a lot of functions which are called later on.
The one to set the password:
…
# Set password
# $1 - username
# $2 - password, if it's null, will prompt user to enter pasword
function ovm_set_password
{
local username=$1
local passwd=$2
local encpasswd
if [ -z "$username" ] || ! id "$username" >/dev/null 2>&1; then
ovm_error "Username can't be null or does not exist."
return 1
fi
if [ -n "$passwd" ]; then
encpasswd=$(perl -e "print(crypt('$passwd','salt'),'\n')")
usermod -p $encpasswd $username
else
while ! passwd $username; do
:
done
fi
}
…
We need to call this function with username (root) and password. Please see part 5 below for the modification need.
3. Network settings
Similarly to the above with root’s password, the script /usr/lib/oraclevm-template/functions contains the function to configure the network:
…
# function ovm_configure_network
# Usage:
# 1. interactive mode
# A. No argument specified. - prompt user to select using DHCP or not.
# B. $1 = "static" - force to configure static ip address.
# prompt user to enter ipaddress, netmask, gateway,
# dns, hostname
# 2. silent mode
# A. $1 = "dhcp", force to configure dhcp silently.
# B. force to configure dhcp and set hostname silently.
# $1 = "dhcp"
# $2 = hostname
# C. 5 arguments are required to configure static ip address silently.
# $1 - ip address
# $2 - netmask
# $3 - gateway
# $4 - dns server IP
# $5 – hostname
…
Here, this function will need to be call with all the 5 parameters as described. Please see part 5 below for the modification need.
4. The database name
From the script oracle-template.sh, we can see the call to an other script, database dedicated:
#
# This function is called to setup a database on the local VM.
#
CheckCreateDBVirtualEnv() {
RETURN_VALUE=0
VBOX_SETUP=$1
if [ -d $PS_DB_HOME ]; then
. $SCRIPT_PATH/oraclevm-template-db.sh
SourcePluginScript
CreateVirtualEnvironment $VBOX_SETUP
RETURN_VALUE=1
else
log_ovm_message "No PeopleTools Database environment to be created on this host ....skipping DB Setup"
fi
return $RETURN_VALUE
}
And, in this script, oraclevm-template-db.sh, the database name is defined as follow:
# get the current database name
DBNAME=`ls -l $PSFT_DB_HOME/oradata | grep '^d' | awk '{print $9}'`
DBSIDNAME=$DBNAME
if [ "$PROMPT_DBNAME" == "TRUE" ]; then
# Prompt the user for database name
GetUserInput
fi
The GetUserInput is actually a function:
GetUserInput() {
echo ""
echo -n "Enter the name of the database [$DBNAME]:"
read VALUE
if [ "$VALUE" != "" ]; then
DBNAME=$VALUE
DBSIDNAME=$DBNAME
fi
}
To suppress the prompt, comment it out, and put the name you want:
GetUserInput() {
echo ""
#echo -n "Enter the name of the database [$DBNAME]:"
#read VALUE
VALUE="HR92DM00"
if [ "$VALUE" != "" ]; then
DBNAME=$VALUE
DBSIDNAME=$DBNAME
fi
}
5. Root password and network settings changes
Since the database is configured on this very virtual machine we are deploying, the root password and the network settings are both defined in the script oraclevm-template-db.sh.
It has already been modified for the database name (also see part 4 above when it is called).
Here, we can see the network function call:
# change the networking from static to variable
sed -i "s/ovm_configure_network \"static\"/ovm_configure_network/g" $ORACLE_DB_SCRIPT
It removes the “static” parameter to null… It should be change to put the 5 arguments needed to the network function as we’ve seen earlier. Also, whether there’s no the call to the password change function it must be change as well.
At the result we have the following:
# change the networking from static to variable
#sed -i "s/ovm_configure_network \"static\"/ovm_configure_network/g" $ORACLE_DB_SCRIPT
sed -i "s/ovm_configure_network.*/ovm_configure_network 192.168.1.20 255.255.255.0 192.168.1.254 192.168.2.254 hcm92000.phoenix.nga/" $ORACLE_DB_SCRIPT
sed -i "s/ovm_set_password.*/ovm_set_password root passw0rd/" $ORACLE_DB_SCRIPT
6. The SES installation
Finally, the last prompt your are seeing is the choice to install or not the Secure Enterprise Search (so called SES).
For this, we have to go back to the very first script, /opt/oracle/psft/vm/oraclevm-template.sh.
Here we go:
#
# This function is called to setup SES on the local VM.
#
CheckCreateSESVirtualEnv() {
RETURN_VALUE=0
VBOX_SETUP=$1
if [ -d $PS_SES_HOME ]; then
. $SCRIPT_PATH/oraclevm-template-search.sh
USER_RESPONSE=1
echo " "
echo -n "Do you wish to setup Secure Search Enterprise (SES) on this VM [y|n]: "
GetYNResponse
USER_RESPONSE="$?"
if [ "$USER_RESPONSE" == "1" ]; then
CreateVirtualEnvironment $VBOX_SETUP
# generate SES props
PROP_FILE=$SCRIPT_PATH/ses.props
echo DOMAIN_NAME=$APPSRVDOM >> $PROP_FILE
echo DB_TYPE=$DBTYPE >> $PROP_FILE
echo DB_NAME=$DBNAME >> $PROP_FILE
echo DB_USER=$APPBATCH_PIA_USER >> $PROP_FILE
echo DB_PWD=$APPBATCH_PIA_USER_PWD >> $PROP_FILE
CheckConfigSES $PROP_FILE $IS_DEMO_SETUP $VBOX_SETUP
First you have to comment out the user input, and give the proper value to the parameter USER_RESPONSE depending you want to install it (1) or not (0). Here I don’t:
#
# This function is called to setup SES on the local VM.
#
CheckCreateSESVirtualEnv() {
RETURN_VALUE=0
VBOX_SETUP=$1
if [ -d $PS_SES_HOME ]; then
. $SCRIPT_PATH/oraclevm-template-search.sh
USER_RESPONSE=1
echo " "
#echo -n "Do you wish to setup Secure Search Enterprise (SES) on this VM [y|n]: "
#GetYNResponse
#USER_RESPONSE="$?"
USER_RESPONSE="0"
if [ "$USER_RESPONSE" == "1" ]; then
CreateVirtualEnvironment $VBOX_SETUP
# generate SES props
PROP_FILE=$SCRIPT_PATH/ses.props
echo DOMAIN_NAME=$APPSRVDOM >> $PROP_FILE
echo DB_TYPE=$DBTYPE >> $PROP_FILE
echo DB_NAME=$DBNAME >> $PROP_FILE
echo DB_USER=$APPBATCH_PIA_USER >> $PROP_FILE
echo DB_PWD=$APPBATCH_PIA_USER_PWD >> $PROP_FILE
CheckConfigSES $PROP_FILE $IS_DEMO_SETUP $VBOX_SETUP
7. VMWare tools
In the very end of the script, it could be very interesting to install automatically the VMWare tools without having to do it manually and without the need to mount a CD and so forth.
To achieve this, three steps:
7.1 Copy the iso file corresponding to your ESXi into /tmp
[root@omsa:/mnt/HCMDB-SES-85302d/opt/oracle/psft/vm]# cp /nfs/software/Virtualization/VMWare/VMWare_vSphere/5.1u1/VMware-tools-linux-9.0.5-1065307.iso /mnt/HCMDB-SES-85302d/tmp
[root@omsa:/mnt/HCMDB-SES-85302d/opt/oracle/psft/vm]#
[root@omsa:/mnt/HCMDB-SES-85302d/opt/oracle/psft/vm]# ls /mnt/HCMDB-SES-85302d/tmp
CVU_11.2.0.3.0_oracle hsperfdata_oracle hsperfdata_psadm3 logs VMware-tools-linux-9.0.5-1065307.iso
7.2 Create a script to install the VMWare tools with all the default:
[root@omsa:/mnt/HCMDB-SES-85302d/opt/oracle/psft/vm]# more vmware_tools.sh
mkdir -p /mnt/vmware-tools
mount -o loop /tmp/VMware-tools-linux-9.0.5-1065307.iso /mnt/vmware-tools
tar zxf /mnt/vmware-tools/VMwareTools-9.0.5-1065307.tar.gz -C /tmp
umount /mnt/vmware-tools
rmdir /mnt/vmware-tools
rm -f /tmp/VMware-tools-linux-9.0.5-1065307.iso
/tmp/vmware-tools-distrib/vmware-install.pl --default
rm -Rf /tmp/vmware-tools-distrib
[root@omsa:/mnt/HCMDB-SES-85302d/opt/oracle/psft/vm]# chmod a+rx vmware_tools.sh
7.3 Modify /opt/oracle/psft/vm/oraclevm-template.sh and add the call to this new script
Within the main section, we can see the call to create the virtual environment:
main() {
SetEnvVars
SourcePluginScript
if [ $# -eq 1 ] && [ "$1" == "--cleanup" ]; then
CleanupVirtualEnv
else
if [ $# -eq 0 ]; then
CreateVirtualEnv
else
UsageInstructions
fi
fi
}
Once it is all done, just run the VMWare tools script previously created:
main() {
SetEnvVars
SourcePluginScript
if [ $# -eq 1 ] && [ "$1" == "--cleanup" ]; then
CleanupVirtualEnv
else
if [ $# -eq 0 ]; then
CreateVirtualEnv
$SCRIPT_PATH/vmware_tools.sh
else
UsageInstructions
fi
fi
}
Here we saw all the modifications to make the VM starting without prompting for any user input, as it will be shown in the next and second last part of this series.
Whether the manual modification above are rather tedious, there will a script to do it for us, it will be the 5th and last part.
Nicolas.
No comments:
Post a Comment