CHAPTER
1
Preparing to Deploy
This
chapter discusses:
•
Understanding Oracle VM and the People-soft Deployment
•
Obtaining Oracle VM for People-soft Templates from Oracle Software Delivery
Cloud
•
Planning the People-soft Template Deployment
•
Reviewing the Oracle VM Setup
Understanding Oracle VM and the People-soft Deployment
This
documentation explains how to deploy the Oracle VM templates for People-soft
Human Capital Management (HCM) 9.1 Feature Pack 2. People-soft HCM 9.1 Feature
Pack 2 deployment requires two Oracle VM templates. The Oracle VM templates for
HCM include the following features:
•
Database template
• People-soft HCM 9.1 Feature Pack 2 application software, including the demo
database, built on Oracle 11gR2 RDBMS database software
•
Oracle Linux 5.7 operating system
• HCM
Application VCD Install directory
This
Application VCD Install directory (this will be found in
/opt/oracle/psft/ptdb/apptools after
deployment)
will be mounted transparently onto the PIA-App-batch virtual machine (this will
be found under /opt/oracle/psft/pt/apptools after deployment) if options for
Demo environment setup and Decoupled Application Home setup are chosen during PIA-App-batch virtual machine configuration.
See
"Deploying the People-soft Templates," Starting the Oracle VM for People-soft Virtual Machines.
• PIA-App-batch template
• People-soft People Tools Install directory (this will be found in
/opt/oracle/psft/pt/tools after deployment)
• Peoples-soft Pure Internet Architecture (PIA) built with Oracle Web-logic 10.3.5
web server
•
Application Server configured using a People-soft small domain configuration.
•
Process Scheduler with a default UNIX configuration
•
Oracle Tuxedo 10gR3 and Verity included
•
Micro Focus Server Express COBOL install binaries
• People-soft Client installer
See
Obtaining Oracle VM for People-soft Templates from Oracle Software Delivery
Cloud.
Before
deploying the People-soft templates, you must install Oracle VM Server and
Oracle VM Manager. The hardware and software requirements for this deployment
are the same as those for Oracle VM Server and Oracle VM Manager.
See
Reviewing the Oracle VM Setup.
The deployment requires users with the
following roles:
• Oracle VM
Administrator
The
Oracle VM Administrator is responsible for management of the Oracle VM server
pool and user accounts, including the user accounts for the People-soft domain
and installation administrators. The Oracle VM Administrator is authorized to
create virtual machines and assign hardware resources to a virtual machine. The
Oracle VM administrator should have root access on the Oracle VM Server
machine.
• People-soft Domain and Installation Administrators
The
users
managing the People-soft People Tools environment should be familiar
with People-soft software administration. The user can be local to the
virtual
machine or a domain user. This user only has access to the resources
assigned
by the Oracle VM Administrator. While these are listed as separate
roles, both
sets of skills are needed to complete the deployment process in
very
close coordination.
Obtaining Oracle VM for People-soft
Templates
from Oracle Software Delivery Cloud
You
should have already downloaded the necessary files from Oracle Software
Delivery Cloud before beginning this procedure. This section includes
additional information on finding and using Oracle VM templates for People-soft
if necessary.
To obtain the
Oracle VM templates for HCM:
1.
Sign in to the Oracle Software Delivery Cloud portal for Oracle Linux and
Oracle VM.
See
http://edelivery.oracle.com/linux
2. On
the Media Pack Search page, select Oracle VM templates from the Select a Product
Pack drop-down list.
Select
the operating system you are running on from the Platform drop-down list, and
click Go.
3.
Select the radio button for People-soft VM templates for HCM 9.1 Release Media
Pack for x86 (64 bit), and click Continue.
4.
Download the following templates, and save the zip files to a temporary directory:
• People-soft HCM 9.1 Feature Pack 2 database with Oracle Linux 5.7.
This
template is referred to as the “Database template” in this documentation.
• People-soft PIA, Application and Batch server with People-soft Pure Internet
Architecture, Web-logic 10.3.5, Tuxedo 10gR3, and Verity.
This
template is referred to as the “PIA-App-batch template” in this documentation.
5.
Click Read-me for information on how to extract the zip files and prepare for
use.
6.
Create a directory for the templates on the Oracle VM Server, and FTP the
templates into the directory: /OVS/seed_pool/TEMPLATE_NAME.
Follow
the
instructions given in the Read-me file concerning the directory name.
The Read-me file is posted with the templates, and as such is more
current than this
documentation. It is convenient to use the template name for the
directory;
this documentation uses TEMPLATE_NAME.
Note.
If /OVS is a mounted filesystem, after unzipping
and before extracting the files you may see messages similar to the following.
You can ignore these messages and continue.
-bash-3.1# tar -xvf
OVM_EL5U7_X86_64_HCMDB9_1_2_PVM.tgz
Oracle11gR2.img
tar: Oracle11gR2.img: Cannot change
ownership to uid 0, gid 0:
Operation not permitted HCMDB.img
tar: HCMDB.img: Cannot change
ownership to uid 0, gid 0:
Operation not permitted README
tar: README: Cannot change
ownership to uid 0, gid 0:
Operation not permitted System.img
tar: System.img: Cannot change
ownership to uid 0, gid 0:
Operation not permitted vm.cfg
tar: vm.cfg: Cannot change
ownership to uid 0, gid 0:
Operation not permitted
tar: Error exit delayed from
previous errors
Planning the People-soft Template
Deployment
The
following diagram shows a sample Oracle VM architecture with the Oracle VM
templates for People-soft deployed. In this case, both People-soft templates are
deployed in a single server pool on a single Oracle VM server, but other server
pool configurations are possible. A server pool is an autonomous region that
contains one or more Oracle VM Servers.
See Oracle
VM Manager User’s Guide, "Overview of Oracle VM Manager"
The
following diagram shows the Oracle VM architecture with the two deployed
PeopleSoft templates. The components represented in the following diagram are
defined below the diagram:
Sample
Oracle VM architecture with deployed People-soft templates
• Oracle VM Manager
The
Oracle VM Manager is a web application that provides the user interface to
manage Oracle VM Server, virtual machines, and resources.
• Oracle VM Server
The
Oracle VM Server is a self-contained virtualization environment designed to
provide a lightweight,secure, server-based platform to run virtual machines.
Oracle VM Server is based upon an updated version of the underlying Xen hyper-visor technology, and includes Oracle VM Agent.
• Oracle VM Agent
Oracle
VM Agent is installed with Oracle VM Server. It communicates with Oracle VM
Manager
to
manage virtual machines.
• dom0
This
is an abbreviation for domain zero, which is the management domain with
privileged access.
• domU
Each
domU (dom1, dom2, dom3) is an unprivileged Oracle VM domain with no
direct access to the hardware or device drivers. Each domU is started by Oracle
VM Server in dom0. In this example, each domain holds a single People-soft
virtual machine.
In
planning the deployment, consider the following:
• In
addition to the Oracle VM components discussed above, you need a utility to
access and control the virtual machines in a console. You can consult the
Oracle VM documentation for information on downloading a plug-in, or use a VNC
client of your own choosing.
See Oracle
VM Manager User’s Guide, "Connecting to a Virtual Machine’s
Console."
•
After setting up the virtual machines you will need to use a secure shell (SSH)
client to log in to the virtual machines.
• The
delivered Oracle VM for HCM templates include a People-soft HCM 9.1 demo
database. Depending upon the products that you want to have available, you may
need to acquire licenses for COBOL, SAP® Business Objects Crystal Reports®, or
SAP® Business Objects™ Enterprise
software. See "Licensing Notes for People-soft Enterprise People Tools
8.52," My Oracle Support (search for the article name).
If
you plan to use any products that require COBOL, such as Oracle’s People-soft
Enterprise Benefits Administration, Payroll for North
America, or Global Payroll, be aware that you must have a properly
licensed and installed Micro Focus COBOL compiler.
See
"Deploying the People-soft Templates," Starting the PIA-App-batch
Virtual Machine.
See
"People-soft Enterprise Frequently Asked Questions About People-soft and the
Micro Focus COBOL Compiler," My Oracle Support, (search for the article
name).
See PeopleSoft
Enterprise HRMS 9.1 Applications Installation Guide, My Oracle Support
(search for the application and release).
•
Decide how to distribute the templates. The example in the previous section
shows both templates in a single server pool, but your environment may favor
the database template in one server pool, and the PIA-AppBatch template in
another.
• It
is possible to combine a deployed PeopleSoft template with a conventional
installation.
For
example, if you deploy the PIA-AppBatch template, you can connect to a
traditional, non-virtual database instance.
• The
environment installed by the deployment of the Oracle VM for HCM templates can
be used as a starting point that can subsequently be enhanced and tuned to fit
the requirements of the target system.
See
"Deploying the People-soft Templates," Managing the Virtual
Environment Life-cycle.
• To
avoid potential conflicts, the Oracle VM Administrator should keep careful
record of the host names and IP addresses associated with the virtual machines.
Reviewing the Oracle VM Setup
Before
you begin the Oracle VM for HCM template deployment, the Oracle VM
Administrator should have completed the following tasks:
•
Downloaded the Oracle VM Server and Oracle VM Manager Installation software
from Oracle Software Delivery Cloud.
•
Installed Oracle VM Server and Oracle VM Manager Software.
See Oracle
VM Server Installation Guide.
See Oracle
VM Manager Installation Guide.
• Set
up a server pool.
See Oracle
VM Manager User’s Guide.
• Set
up a server.
See Oracle
VM Manager User’s Guide.
•
Recorded, and if necessary, communicated information such as hostnames, IP
addresses, and other access information, to the user who will deploy the
templates.
You
should give due consideration to the best server pool configuration for your
system. For example, you can create different virtual machines for the
PIA-App-Batch and Database templates, on different physical servers, and put
them into the same server pool. The Oracle VM documentation includes guidance
on designing your system.
CHAPTER 2
Deploying the PeopleSoft Templates
This
chapter discusses:
• Importing Oracle VM for People-soft Templates
•
Creating the Virtual Machines
•
Starting the Oracle VM for People-soft Virtual Machines
•
Using the People-soft Installation
•
Configuring Oracle SES
•
Configuring HCM
•
Troubleshooting
•
Managing the Virtual Environment Life-cycle
Importing Oracle VM for PeopleSoft
Templates
There
are several methods of importing virtual machines templates. This section
assumes that you downloaded the Oracle VM for People-Soft templates from Oracle
Software Delivery Cloud, extracted the two templates, and saved them in
/OVS/seed_pool/TEMPLATE_NAME on the computer where you set up your
Oracle VM server pool. Carry out the procedure described here for each of the
templates you downloaded.
Use
the examples shown here for information, but keep in mind that there may be
slight differences in appearance due to different browsers and so on.
See
"Preparing to Deploy," Obtaining the Oracle VM for People-Soft
Templates from Oracle Software Delivery Cloud.
For
other methods of importing templates, see the Oracle VM Manager User’s Guide.
To
import the virtual machine template that you downloaded previously, and
register it in Oracle VM Manager:
1.
Launch the Oracle VM Manager in a browser and log in.
Log
in with a user account that has the permissions to import templates and create
virtual machines.
Oracle VM
Manager Login
User id: - admin
Password: -
*****
Click Login tab
Open Oracle VM Manager Home Page:-
2.
Select the Resources tab.
3.
Click Virtual Machines Templates, and then click the Import button.
Oracle VM Manager Resources page
4. on the Source
page, select the option Select from Server Pool (Discover and register), and
then click Next.
5. on the
General Information page, enter or select the following general information:
General
information page
• Server Pool
Name
Select
the server pool on which the imported virtual machine template will be located.
• Virtual
Machine Template Name
Select
the virtual machine template to be imported.
• Enable High
Availability (Optional)
You
can enable high availability for the imported virtual machine template.
See Oracle
VM Manager User’s Guide, "Managing Server Pools."
• Operating
System
Enter
Oracle Enterprise
Linux 5 64-bit as the guest operating system of the virtual machine
template.
• Virtual
Machine System Username
Enter
the user name used to log in to the virtual machine after it is booted. In the
example shown root is supplied as the user name.
• Virtual
Machine System Password
Enter
the Oracle VM template root account password, ovsroot.
Note.
This is not the same as the console password that you choose in the next
step to create the virtual machine. The Console Password is used to log in to
the console using a VNC client while the password chosen here is used to log in
to the system using SSH client sessions.
6. Click Next,
and confirm that the information you entered, such as Server Pool Name, Virtual
Template Name, Operating System, and so on, are correct.
Confirm Information page
7. Click
Confirm.
After
importing, the status of the virtual machine template is Pending. You need to
approve it to make it available for creating virtual machines.
8. Select the
template you want to approve, and click Approve.
A
page appears with information about the template. Click Approve again. The
status changes to Active.
Virtual Machine Templates page
Creating the Virtual Machines
This
section assumes that you have imported the templates as described in the
previous section, and are logged in to Oracle VM Manager. Carry out the
procedure described here for each of the Oracle VM for PeopleSoft templates.
To
create a virtual machine based on an Oracle VM for HCM template:
1.
Select the Virtual Machines tab.
The
Virtual Machines page lists existing virtual machines.
2.
Click the Create Virtual Machine button.
3.
Select the option Create virtual machine based on virtual machine template, and
click Next.
Creation Method page
4.
Select the server pool where the virtual machine is to be located.
Accept
the default Preferred Server option, Auto, and click Next.
Server pool
page with selected server pool
A
preferred server is a Virtual Machine Server that provides resources such as
memory, CPUs, virtual network interfaces (VIFs), and disk for the virtual
machine. If you select only one Virtual Machine Server as the preferred server,
the virtual machine then always starts from and runs on this server. If you
select multiple preferred servers, each time the virtual machine starts, it
will choose to run on the one with the maximum resources available (including
memory and CPU).
When
creating a virtual machine, there are two ways to select a Virtual Machine
Server for the virtual machine:
•
Auto: In the Auto mode, when the virtual machine starts, Oracle VM
automatically assigns a Virtual Machine Server with the maximum resources
available to run the virtual machine. The virtual machine then runs on this
Virtual Machine Server temporarily, until it is shut down.
•
Manual: In the Manual mode, you select one or more Virtual Machine Servers as
the preferred servers.
The
virtual machine then starts from and runs on the preferred server with the
maximum resources available.
Note.
If none of the preferred servers can provide sufficient resources, the
virtual machine may fail to start.
5.
Select the template that you imported to use for this virtual machine, and then
click Next.
Source page
with selected template
6.
Enter the following information, and then click next:
Virtual
Machine Information page
• Virtual
Machine Name
This
name will be used as the name of the directory under /OVS/running_pool, where
the files associated with this virtual machine are stored.
Note.
The virtual machine name does not have to be the same as the name of the
virtual machine host.
• Console
Password
Enter
the password to log in to the console, and enter it again to confirm the
password. You use the connection through the console to access and start the
virtual machine. This may be the console plug-in documented in the Oracle VM
Manager User’s guide, or another VNC client.
See Oracle
VM Manager User’s Guide "Connecting to a Virtual Machine’s
Console."
• Enable High
Availability
This
is optional. See the section on enabling high availability in the Oracle VM
documentation.
See Oracle
VM User’s Guide, "Managing Server Pools."
• Add Row
This
is optional. Select this option to add more virtual network interfaces. By
default, virtual
network
interfaces are named VIF0, VIF1, VIF2, and so on. You can rename them after
creating
the
virtual machine. See the information on changing virtual machine configuration
in the Oracle
VM
documentation.
See Oracle
VM Manager User’s Guide, "Managing Virtual Machines."
7. Confirm
that the information for user, virtual machine, virtual machine template, and
server pool are correct, and then click Confirm.
Confirm Information for the virtual machine
8.
Click Refresh periodically until the status of the virtual machine changes from
Creating, as shown in the first example, to Powered Off, as shown in the second
example.
The
process of creating a virtual machine takes time. You can choose to refresh
manually, or to refresh every 30 seconds.
Creating
Virtual Machine page with virtual machine in creating status
Creating
Virtual Machine page with virtual machine in Powered Off status
9. If
the status goes to Error, refer to the virtual machine error section in the
Oracle VM Manager User’s Guide.
See Oracle
VM Manager User’s Guide, "Managing Virtual Machines"
Starting the Oracle VM for PeopleSoft
Virtual Machines
This
section discusses:
•
Understanding the Virtual Machine Initialization
•
Starting the Database Virtual Machine
•
Starting the PIA-AppBatch Virtual Machine
•
Installing Micro Focus Server Express 5.1 after Starting the Virtual Machines
18 Copyright © 2012, Oracle and/or its affiliates.
All rights reserved.
Chapter 2 Deploying the PeopleSoft Templates
Understanding the Virtual Machine
Initialization
Start
the virtual machines for each of the Oracle VM for HCM templates. It is
important that you start the Virtual machines in the following order:
1.
Database
2.
PIA-AppBatch
After
starting the virtual machines in Oracle VM Manager, log in to each virtual machine
in a console to verify that the virtual machine creation was successful, and
that it is accessible. You will be prompted with a few configuration questions
for the PeopleSoft installation. You must supply both network information, such
as IP addresses, and information specific to the PeopleSoft installation, such
as the database SID.
Be
aware that if you supply incorrect network information in response to these
prompts (such as IP address, hostname, DNS server IP, gateway and so on) the
new virtual machine will not function, and you should create a fresh virtual
machine.
Starting the Database Virtual Machine
Starting
a virtual machine is analogous to starting a computer by pressing the Power On
button. Ensure that the virtual machine is powered off before you start it.
To
start and initialize the Database virtual machine:
1. Select the
Virtual Machines tab.
2. On the
Virtual Machines page, select the virtual machine that you created for the
Database template.
3. Click the
Power On button.
4. Wait until
the virtual machine status changes from Initializing to Running.
The
status of the virtual machine will automatically be updated every 30 seconds.
You can also choose to manually refresh the status by clicking the Refresh
button.
5. Open your console
application (for example, VNC client) and log into the virtual machine.
Log
in using the console password you specified when importing the template.
6. At the
following prompt, enter the password for root.
New UNIX Password:<val>
Reenter
the same password at the following prompt:
Retype new UNIX Password:
7. Enter the
required network-related information.
There
are several prompts asking for network-related information. You see the same
network-related prompts when starting each of the virtual machines. The text in
bold font indicate places that require user input:
Configuring network interface.
Enter static IP address: 12.345.67.900
Enter netmask[255.0.0.0]: 555.555.555.5
Enter gateway: 12.345.678.9
Enter DNS server: 123.45.678.90
Confirm the host name that is resolved by the
DNS server: host_name
Stopping network...
Shutting down interface eth0: [OK]
Shutting down loopback interface: [OK]
Configuring static IP.
IP address: 12.345.678.900
Net mask: 555.555.555.5
Gate way: 12.345.678.9
Host name: host_name
Starting network...
Bringing up loopback interface: [OK]
Bringing up interface eth0: [OK]
Note.
If the host name does not get resolved by the DNS server, the network
related answers are probably wrong and the virtual machine will not boot
correctly. If this happens, you will have to reset the virtual machine and
restart the whole boot sequence from the beginning. Refer to the section
Resetting PeopleSoft Virtual Machines later in the document.
8. Respond to
the following prompts requesting database information.
Enter
values for your environment or accept the defaults.
Note.
If necessary, check with your Oracle database administrator for information
about these values.
Do you want to relink the binaries? (y/n) [n]
Specify a port that will be used for the
database listener [1521]:
Do you want Oracle Database to be started on
boot (y/n) [y] :
9.
Specify a database name at the following prompt.
The
database name must include only uppercase letters, for example HCM91:
Enter the name of the database SID [TESTDB]: HCM91
10.
Log in to the virtual machine using Secure Shell (SSH), with root and the
password entered at the beginning of the boot sequence.
Note.
You can also log in using oracle as the user and oracle as the password.
Oracle Linux Server release 5.7 Kernel
2.6.32-200.13.1.el5uek on an x86_64
Host_name login:
After
you answer the configuration questions, the database server starts, and the
demo database is available for the PIA-AppBatch server.
Starting the PIA-AppBatch Virtual
Machine
This
section discusses:
•
Understanding the PIA-AppBatch Virtual Machine
•
Using the Micro Focus Server Express COBOL Compiler
•
Starting and Initializing the PIA-AppBatch Virtual Machine
Understanding the PIA-AppBatch Virtual
Machine
The
PIA-AppBatch virtual machine is used to run PeopleSoft Pure Internet
Architecture (PIA), the PeopleSoft Application Server, and the PeopleSoft
Process Scheduler within the same virtual machine. You can choose to run
PeopleSoft Pure Internet Architecture on one virtual machine, and the
PeopleSoft Application Server and Process Scheduler on a separate virtual
machine by your response to the prompts in the section Starting and
Initializing the PIA-AppBatch Virtual Machine. Furthermore you can decide to
deploy neither the PIA nor AppBatch on a virtual machine. In this case the
virtual machine that you created from the PIA-AppBatch template would be
analogous to a traditional system with PeopleSoft People Tools installed in PS_HOME
and PeopleSoft application files installed in PS_APP_HOME, but with
no Application Server domain, Process Scheduler domain, or PeopleSoft Pure Internet
Architecture site set up.
PIA-AppBatch
virtual machine can be configured either for a HCM Demo environment or a
non-Demo environment.
• Demo
Environment
To
set up a HCM Demo environment, you must answer y (yes) to both of the
prompts “Do you wish to configure the VM for Demo Purposes” and “Do you
wish to configure a Decoupled Application Home”. The term “Decoupled
Application Home” refers to a deployment in which the HCM Application software resides
in an installation directory, PS_APP_HOME that is separate from PS_HOME,
the installation directory for PeopleSoft People Tools. The PS_APP_HOME directory
that is installed onto the HCM Database virtual machine under
/opt/oracle/psft/ptdb/apptools will be mounted transparently onto the PIA-AppBatch
virtual machine under /opt/oracle/psft/pt/apptools during configuration.
See People
Tools 8.52: System and Server Administration People Book, "Working
with Server Domain Configurations."
• Non-Demo
Environment
Choose
this option if you want to connect the PIA-AppBatch virtual machine to a
pre-existing (traditional) database or an environment with an Integration
Gateway.
In
this mode, the configuration is done manually and the user typically chooses
not to use any default initialization steps. If you answer n (no) to the
question “Do you wish to configure the VM for Demo Purposes”, you will be given
an option of providing an external script to configure the virtual machine. If you
decide to provide an external script, you will be prompted to provide the FTP
information (location and credentials) where the external script resides. This
script is downloaded and then executed. You decide what this external script
does and you control the contents of the external script.
The external script should follow certain
rules:
• The
script must be named oraclevm-template-ext.sh.
• The
script must include the functions ovm_configure_pre, ovm_configure_post,
ovm_cleanup_pre,ovm_cleanup_post.
• The
function ovm_configure_pre must declare the variable OVM_PEOPLETOOLS=0.
Using the Micro Focus Server Express
COBOL Compiler
The
procedure to start the PIA-AppBatch virtual machine includes prompts for the
Micro Focus Server Express COBOL compiler and license management facility
(LMF). You can choose to install at this time or do it after you finish
starting the virtual machines. If you answer yes to the prompts:
•
Micro Focus Cobol Compiler and Runtime along with LMF are installed.
• A
30-day evaluation license is installed.
For
information on installing a full license, see the Enterprise People Tools 8.52
installation guide and the COBOL information on My Oracle Support.
See People
Tools 8.52 Installation for Oracle.
See
"PeopleSoft Enterprise Frequently Asked Questions about PeopleSoft and the
Micro Focus COBOL Compiler," My Oracle Support, (search for article name).
• HCM
COBOL sources are automatically compiled and linked.
See
Installing Micro Focus Server Express 5.1 After Starting the Virtual Machines.
Starting and Initializing the
PIA-AppBatch Virtual Machine
Ensure
that the database server is running before beginning this procedure.
To
start and initialize the PIA-AppBatch virtual machine:
1.
Select the Virtual Machines tab.
2. On
the Virtual Machines page, select the virtual machine that you created for the
PIA-AppBatch template.
3.
Click the Power On button.
4.
Wait until the virtual machine status changes from Initializing to Running.
The
status of the virtual machine will automatically be updated every 30 seconds.
You can also choose to manually refresh the status by clicking the Refresh
button.
5.
Open your console application and log into the virtual machine using the
console password you specified when importing the template. The same root user
password prompts and network-related prompts appear as in the previous section
6.
Respond y (yes) to this prompts if you want to configure the virtual
machine for a Demo environment:
Do you wish to configure the VM for Demo
Purposes [y/n]:
Note.
You must answer y to both this question and to the subsequent
question “Do you wish to configure a Decoupled Application Home” in order to
set up an Application Demo environment. By answering y to both these
questions, the Application VCD installed on the database virtual machine under /opt/oracle/psft/ptdb/apptools
will be mounted transparently onto the PIA-AppBatch virtual machine under /opt/oracle/psft/pt/apptools
and PS_APP_HOME environment variable is set to point to this location.
7. If
you answer n (no) to the question “Do you wish to configure the VM for
Demo Purposes,” you see the following prompt:
Do you wish to configure the VM using an
external script [y/n]:
a.
Respond y to the external script question if you want to configure the
VM manually.
See
Understanding the PIA-AppBatch Virtual Machine.
See
Using the PeopleSoft Configuration Script.
Note.
If you answer n (no), you see the prompt in step 8.
b.
Respond to the following prompt for FTP information:
Enter the hostname for FTP access:
.
Enter the username for FTP access:
Enter the password for FTP access:
Enter the directory where the external script
resides:
Using
the information provided, the external script is downloaded and then executed.
8.
Respond y to the following prompt if you want to set up a PS_APP_HOME
that is separate from PS_HOME, referred to as a Decoupled
Application Home:
Do you wish to configure a Decoupled
Application Home [y/n]:
Note.
In order to set up an Application Demo environment, you must answer y
(yes) to this question. By answering y to this question, the
Application install directory that resides on the Database template (under /opt/oracle/psft/ptdb/apptools)
is mounted transparently onto the PIA-AppBatch virtual machine. If you answer n
(no) to the “Do you wish to configure a Decoupled Application Home”
question, then the PIA-AppBatch virtual machine will be configured without any PS_APP_HOME
setup. You will have to set this up manually after the system has completed
its initialization. Setting up PS_APP_HOME manually will require
reconfiguration of the PeopleSoft Application Server and Process Scheduler
domains.
9.
Respond y to this prompts if you want to set up the PeopleSoft
Application Server and Process Scheduler:
Do you wish to setup PeopleSoft Application
Server on this VM [y|n]:
10.
Provide the name of the database and the host on which the database is running.
The
database host will be either a virtual machine that you set up in the previous
task or a pre-existing (traditional) database. The default port used by the
database virtual machine is 1521. Enter y when you have finished.
Enter the name of the database [HCM91]:
Enter the hostname for the database server
[localhost]:
Enter the port number for the database host
[1521]:
Are you happy with your answers [y|n] :
11.
Enter y if you want to have the installer complete additional setup
steps, as described in the prompt:
If this VM is connecting to a PeopleSoft
database created from an Oracle VM
template some additional setup may be
required. We can automate these steps
for you. If you are connecting to a Database
that has been used before
you may wish to skip this step.
Do you want this additional setup to be
performed? [y|n]:
You
see a progress indicator as the PeopleSoft Application Server and Process
Scheduler domains are started.
Note.
If you experience problems in starting the PeopleSoft Application Server
and Process Scheduler domains, see “Resetting PeopleSoft Virtual Machines.”
12.
Read the information concerning the installation of Micro Focus Server Express
5.1 WP4 and license management facility (LMF):
Installing Micro Focus Server Express 5.1 WP4
and LMF ...
------------------------------------------------------------------------------
Before installing and using this software
product you must
agree to be bound by the terms and conditions
of the end user
license agreement ("License
Agreement") which accompanies this product.
Please take this time to read the License
Agreement. If you are not in
agreement with the terms and conditions of
the License Agreement, please
return the product to your Account
Representative and your money will
be refunded. If you require a replacement
copy of the License
Agreement, please contact your Account
Representative before proceeding
with the install process.
Do you agree to the terms of the License
Agreement? (y/n):
13.
If you want to accept the installation of Micro Focus Server Express with a
30-day license, enter y.
You
see the following message:
------------------------------------------------------------------------------
This product is protected using the Micro
Focus License Management
Facility (LMF).
Please refer to the Development System
Licensing Guide for information relating
to the installation of the licensing system
and licenses.
Empty database created ok
LMF installation complete
------------------------------------------------------------------------------
Installation completed successfully.
The COBOL system is ready to use.
A 30 day evaluation license has been
installed for the Micro Focus Server
Express 5.1 COBOL Compiler and Runtime.
Please contact Micro Focus or
Oracle Sales for a full license if you intend
to use this product beyond
the 30 day evaluation period.
MF-LMF: Thu Sep 2 13:59:50 2010: LMF Starting
Compiling & Linking COBOL sources ...
14.
If you do not want to install Micro Focus Server Express at this time, enter n.
Note.
Follow the procedure in the task Installing Micro Focus Server Express 5.1
after Starting the Virtual Machines to install Cobol Compiler and Runtime after
the PIA-AppBatch virtual machine has completed the initialization.
15.
After the PeopleSoft Application Server and Process Scheduler domain
initialization has completed, respond y to the prompt to set up PIA:
Note.
If you wish to use a separate virtual machine for PIA, answer n to
this prompt.
Do you wish to setup PeopleSoft Pure Internet
Architecture on this VM [y|n]:
The
setup process will run for a few minutes.
16.
If you want to specify an authentication domain (for example, mycompany.com),
enter it at this prompt:
Enter the Authentication Domain for PIA []:
If
you do not want to specify an authentication domain, leave it blank.
See People
Tools 8.52 Installation for Oracle, "Setting Up the PeopleSoft Pure
Internet Architecture in Console Mode."
17.
At the prompt asking for the PeopleSoft Application Server host and Jolt port,
accept the default or provide a DNS-recognized name or IP address for the host.
The default port number is 9000.If you want to connect to an Application Server
domain that was set up and is running independently of the current virtual
machine, provide the appropriate information for that domain.
Enter the connect string for the App Server
domain. This is the host: port
on which the Application Server domain will
listen for incoming connections.
You may provide failover and load balancing
rules using the format described
in the People Books. Hit Enter to use the
default [localhost:9000]:
18.
Answer y to the following prompt if you want the installer to complete
additional setup steps:
You are running both AppBatch and PeopleSoft
Internet Architecture in the
same VM. This means that some additional
automated setup can be done.
Report Nodes, integrations etc. can be
created due to the presence of
multiple tiers in the same host.
Note: you may not wish to do this if
connecting to an existing database.
This is a step typically taken in demo
environment with a clean database.
Do you wish for this additional setup to be
performed [y|n]:
19.
Log in to the virtual machine using Secure Shell (SSH), with root and ovsroot
as the user and password:
Note.
You can also log in to the console using one of the default accounts
described in the task Using the PeopleSoft Installation.
Oracle Linux Server release 5.7 Kernel
2.6.32-200.13.1.el5uek on an x86_64
host_name login:
The
Application Server and Process Scheduler domains will successfully start
provided the database server is running. The Application Server domain is based
on the small domain configuration. The PeopleSoft Pure Internet Architecture
domain is configured to connect to the Application Server domain. After a few
minutes, you can log in to the PeopleSoft application in a browser using the
following URL, with VP1/VP1 as the user name and password:
http://VM_HOST_NAME:8000/ps/signon.html
Installing Micro Focus Server Express
5.1
After Starting the Virtual Machines
If
you chose not to install the Micro Focus COBOL compiler during the procedure to
start the virtual machines, use these instructions to install the compiler.
After you start the PIA-AppBatch virtual machine, you can find the installation
binaries for Micro Focus Server Express 5.1 on the virtual machine.
1. On
the PIA-AppBatch virtual machine, go to the directory
/opt/oracle/psft/pt/cobol/svrexp-51_wp4-64bit.
cd /opt/oracle/psft/pt/cobol/svrexp-51_wp4-64bit
2.
Run the install script to install Micro Focus Compiler and License Management
Facility (LMF).
For example:-
sh install
The
welcome prompt appears:
This script will install Micro Focus Server
Express 5.1 on this computer.
The readme.txt file included in this delivery
contains details of
new features, enhancements and any
restrictions of which you should
be aware. This file is located in :
/opt/oracle/psft/pt/cobol/svrexp-51_wp4-64bit/docs
We strongly recommend you read this file once
the installation is complete.
Do you wish to continue (y/n):
3.
Type y to continue after the welcome prompt.
4.
Read and type y to accept the license agreement:
Before installing and using this software
product you must agree to be
bound by the terms and conditions of the end
user license agreement
("License Agreement") which
accompanies this product.
Please take this time to read the License
Agreement. If you are not
in agreement with the terms and conditions of
the License Agreement,
please return the product to your Account
Representative and your
money will be refunded. If you require a
replacement copy of the
License Agreement, please contact your
Account Representative before
proceeding with the install process.
Do you agree to the terms of the License
Agreement? (y/n): y
5.
After reading the information below type y to continue:
Note.
Only a portion of the prompt is given here.
This product is certified on the following
reference environment
....
....
Please confirm that you want to continue
with this installation (y/n): y
6.
After reading the information below press RETURN to continue:
When you press return you will be shown
details of the reference
environment (and any compatibility
environments).
Please press return when you are ready:
7.
After reading the information below type y to continue:
Note.
Only a portion of the prompt is given here.
This product is certified on the following
reference environment:
The command(s) used to gather the information
is given following each entry.
...
...
...
Please confirm your understanding of the
above reference environment
details (y/n): y
8.
Answer n to the following prompt:
Note.
PeopleSoft COBOL implementations do not require COBOL and Java to work
together.
Do you want to make use of COBOL and Java working
together? (y/n): n
Skipping Java setup Should you want to use
Java with COBOL later on as super user, run the command
/opt/oracle/psft/pt/cobol//svrexp-51_wp4-64bit/bin/java_setup
to select the version of Java you want to
use.
9.
Answer y to the following prompt concerning the License Management
Facility:
This product is protected using the Micro
Focus License Management
Facility (LMF). Please refer to the
Development System Licensing Guide
for information relating to the installation
of the licensing system
and licenses. If you do not have LMF
installed or want to upgrade to the latest version, we recommend that you
install it now.
Would you like to install LMF now? (y/n): y
10.
Enter /opt/oracle/psft/pt/cobol/microfocus as the directory to install the LMF:
Enter the directory name where you wish to
install License Manager.
(Press Enter for default directory
/opt/microfocus/mflmf)
/opt/oracle/psft/pt/cobol/microfocus
/opt/oracle/psft/pt/cobol/microfocus does not
exist
do you wish to create it ? (y/n) y
11.
Enter y to restrict access to the License Admin System to the superuser
account:
Empty database created ok. Do you want only
superuser to be able to access the
License Admin System? (y/n) y
12.
Enter y to start license manager automatically at boot time:
It is recommended that you let license
manager autostart at boot time.
Do you want license manager to be
automatically started at boot time? (y/n) y
LMF installation complete.
13.
If you want to consult the documentation on how to install licenses, follow the
instructions in this prompt:
Please consult the Development Licensing
Guide for detailed information
on how to install licenses. This may be done
by running the mflicense tool. License tool can be run by changing directory to
where the LMF was installed
(/opt/oracle/psft/pt/cobol/microfocus) and typing.
/mflmcmd
--------------------------------------------------------------------------------
To run your applications you need a
deployment license installed using Apptrack.See your Deployment Licensing Guide
for details.
Installing Apptrack...
Access permissions on directory /var/mfaslmf
have changed on this release
Write access permission has been removed
except for superuser use
Apptrack installation complete
14.
Enter 64 for the system default mode:
This product can be used in either 32-bit or
64-bit modes.
Please enter either 32 or 64 to set the
system default mode: 64
System default COBMODE has been set to 64.
15.
Enter n at the following prompt:
Installing documentation. Please wait...
Enterprise Server provides a scalable,
managed, and high-performance
transactional environment for the deployment
of COBOL applications and
services, COBOL/J2EE applications and direct
COBOL Web Services.
Your Enterprise Server requires
configuration. You can either do it
now or later. To do it now, you need to know
the alphanumeric user ID of the
Enterprise Server System Administrator.
To do it later, enter the following commands
whilst logged in as root:
/opt/oracle/psft/pt/cobol/microfocus/svrexp-51_wp4-64bit/bin/eslminstall
/opt/oracle/psft/pt/cobol/microfocus/svrexp-51_wp4-64bit/bin/casperm
Do you wish to configure Enterprise Server
now? (y/n): n
16.
Enter n at the following prompt:
XDB is a fully-functional ANSI-compliant
relational database management system,
providing support for SQL data access for
development purposes.
Do you want to install XDB? (y/n): n
Skipping XDB install. Should you want to
install XDB later on,
run the following command as the root user:
sh /opt/oracle/psft/pt/cobol/microfocus/svrexp-51_wp4-64bit/xdb/xdb_install
17.
Review the information concerning setting the COBDIR, LD_LIBRARY_PATH, and PATH
environment variables in the concluding prompt:
(Remember to set COBDIR to
/opt/oracle/psft/pt/cobol/svrexp-51_wp4-64bit,
include /opt/oracle/psft/pt/cobol/svrexp-51_wp4-64bit/lib
in LD_LIBRARY_PATH
and include
/opt/oracle/psft/pt/cobol/svrexp-51_wp4-64bit/bin on your PATH)
WARNING: Any executables (whether a Run-Time
System or an application)
must be relinked using this new release.
Otherwise, the results
of running the older executables with this
new release are undefined.
Installation
completed successfully.
The
COBOL system is ready to use.
18.
Use the instructions in step 13 to install the Micro Focus license and start
the LMF:
cd /opt/oracle/psft/pt/cobol/microfocus
./mflmman
Note.
You can find the 30-day evaluation license in the license.txt file in the
directory
/opt/oracle/psft/pt/cobol/svrexp-51_wp4-64bit
19.
Log in to the PIA-AppBatch virtual machine using the user ID psadm1.
See
Using the PeopleSoft Installation.
20.
Compile and link the COBOL sources.
For
example, use these commands:
cd $PS_HOME/setup
./pscbl.mak
./psrun.mak
Using the PeopleSoft Installation
This
section discusses:
•
Reviewing the File System
•
Using Application Designer
Reviewing the File System
The
PeopleSoft installation deployed by the Oracle VM for HCM templates sets up an
environment comprised of the following directories on the PIA-AppBatch virtual
machine:
• PS_HOME
The
binary installation files are placed into a secure PS_HOME directory at
/opt/oracle/psft/pt/tools. This directory can only be written to by the
PeopleSoft administrator, psadm1.
• PS_APP_HOME
If
you answered y when prompted to set up a Demo environment, and also
answered y when
prompted
to install a Decoupled Application Home during the procedure to start and
initialize the
PIA-AppBatch
virtual machine, the application installation files are placed into a mounted
directory at /opt/oracle/psft/pt/apptools. This directory can only be written
to by the PeopleSoft administrator, psadm3.
• PS_CFG_HOME
The
application server and Process Scheduler server configuration files are placed
into
PS_CFG_HOME.
This directory is owned by psadm2. The PS_CFG_HOME path is
/home/psadm2/psft/pt/<peopletools_version>.
• Other directories
The
rest of the environment, outside PS_HOME and PS_CFG_HOME, is
owned by root. The file system ownership and permissions are similar to typical
OEL installations.
Note:-
The psadm1, psadm2, and psadm3 users with the passwords below, are also
available for the PIA-App Batch virtual machine.
The
deployed configuration includes three default users:
• The
PeopleSoft installation administrator who owns PS_HOME is psadm1. The
password for this user is 0radmin (the first character is the number zero).
This user cannot write into PS_CFG_HOME.
• The
domain user who creates and configures the application server domain, Process
Scheduler (batch server) domain, and the PIA, is psadm2. The password for this
user is 0radmin (the first character is the number zero). This user cannot
write to PS_HOME, but has read-execute access.
• The
PeopleSoft installation administrator who owns PS_APP_HOME is psadm3,
with password 0radmin (the first character is the number zero).
• The
users psadm1, psadm2, and psadm3 can only access the PIA-AppBatch virtual
machine.
The
deployed configuration on the Database virtual machine includes the ORACLE_HOME
directory,/uo1/app/oracle/product/11.1.0/db_1. You can find the sqlplus
utility in the ORACLE_HOME/bin directory.
Using Application Designer
This
section discusses:
•
Understanding Application Designer and the Oracle VM Templates
•
Installing and Starting Application Designer
Understanding Application Designer and
the Oracle VM Templates
The
Microsoft Windows-based program Application Designer is an important tool that
is used to perform a variety of administrative tasks in a PeopleSoft
environment.
The
PeopleSoft installation deployed by the Oracle VM for HCM templates includes
the PeopleSoft Client installer that packages Application Designer and other
client tools (for example, Change Assistant, Configuration Manager, and the
PeopleSoft Test Framework). The installer is provided in two zip archives (toolsclient.zip
and toolspatchvcd.zip) on the PIA-AppBatch virtual machine in the following
directory:
/opt/oracle/psft/pt/tools.
See People
Tools 8.52 Installation for Oracle, ”Preparing for Installation,” Planning
Your Initial Configuration. Application Designer runs only on Microsoft Windows
and therefore cannot be run in the OVMs that are provided with this
distribution. You must install and run Application Designer on a separate
computer with a supported Microsoft Windows operating system.
In
order to work with the Application Designer client it is necessary to enable
the Workstation Listener (WSL) process in the Application Server domain. The
WSL process listens by default on port 7000 for incoming connections from
Application Designer.
Enable
the WSL process by reconfiguring the App Server domain through PSADMIN and
turning on the WSL option in the domain configuration dialog. Once domain
reconfiguration is completed and the domain is restarted, you can use the
following procedure to run and sign in on Application Designer.
See People
Tools 8.52 People Book: System and Server Administration for information on
using PSADMIN and WSL.See People Tools 8.52 Installation for Oracle,
“Configuring the Application Server on UNIX,” Creating, Configuring, and
Starting an Initial Application Server Domain.
Installing and Starting Application
Designer
To
install the PeopleSoft Client tools and start Application Designer on a
Microsoft Windows machine:
1.
FTP the Client Installer archive (toolsclient.zip) and Patch VCD installer
archive (toolspatchvcd.zip) from /opt/oracle/psft/pt/tools on the PIA-AppBatch
virtual machine to a convenient directory, referred to here as TEMP_DIR,
on the Microsoft Windows machine.
Note.
To FTP from the virtual machine, use the SFTP server.
2.
Carry out the following steps first with the Client Installer archive, followed
by the Patch VCD Installer archive:
a.
Extract the zip file into TEMP_DIR.
b.
Run TEMP_DIR\Disk1\setup.bat to launch the installer.
c.
Specify the installation location for the PeopleSoft Client tools, referred to
here as INSTALL_DIR, and select defaults for the rest of the options.
Note.
When the Patch VCD is installed, chose the option “Client Only” before
proceeding with the installation.
See People
Tools 8.52 Installation for Oracle, "Using the PeopleSoft
Installer."
3.
Run INSTALL_DIR\bin\client\winx86\pside.exe to start Application
Designer.
The
PeopleSoft Sign on dialog box opens.
PeopleSoft Sign
on dialog box with Application Server Connection Type
4.
Select Application Server from the Connection Type drop-down list as shown in
the example above.
5.
For Application Server Name, enter the hostname and WSL port for the PeopleSoft
Application Server that you want to connect to.
The
example shows the default WSL port 7000.
6.
Enter VP1/VP1 for User ID and Password.
Configuring Oracle SES
Oracle
Secure Enterprise Search (SES) is the search engine on which the PeopleSoft
Search Framework relies. To configure your system to use Oracle SES, see the
information in the People Tools 8.52 Installation Guide for Oracle.
Configuring HCM
The
deployment of the PeopleSoft templates provides a PeopleSoft HCM demo database.
For additional information on post-installation steps, see the PeopleSoft People
Tools and PeopleSoft HCM documentation referenced in the preface.
See
"About this Documentation," Related Information. As with any
installation, it is a good idea to verify that the installation completed
successfully, using your normal testing procedure. For information on
installation verification, contact Oracle Global Customer Support.
After
you complete the installation, enable internal integrations. The integrations
across PeopleSoft HCM products are not active by default after a PeopleSoft HCM
demo database installation.
Troubleshooting
Here
are some resources to use if you encounter a problem during the deployment of
the Oracle VM for HCM templates:
• For
problems with Oracle VM Manager and Oracle VM Server, read the troubleshooting
sections in the user’s guides.
• For
logging information, read the /var/log/oraclevm-template.log file.
The
oraclevm-template.log is a centralized log file that includes information about
the Oracle VM
initialization
and the PeopleSoft deployment.
• See
the PeopleSoft People Tools installation guide and People Books for information
on the application server, Process Scheduler, and PeopleSoft Pure Internet
Architecture.
Here
are a few suggestions for typical troubleshooting avenues:
•
Verify that you have enough resources—disc space, memory—on the machine that is
running the Oracle VM Server.
• If
an error status was reported in Oracle VM Manager immediately after starting
the virtual machine this may be due to insufficient resources on the host
computer.
You
can verify this by consulting the log file linked from the Virtual Machine tab
in Oracle VM Manager. This error is commonly reported as “not enough space
under /OVS” with a report of how much disk space is required and how much is
available.
• If
you deployed the templates using more than one computer, make sure the network
communication between the computers is functioning.
• Use
the Oracle VM Manager for information on template status, as shown previously.
See
Importing Oracle VM for PeopleSoft Templates.
• If
you are sure the templates are up and running, but the PeopleSoft log in window
does not appear, try the same steps that you use for traditional PeopleSoft
installations, such as rebooting the application server and restarting
PeopleSoft Pure Internet Architecture.
To
access the PeopleSoft People Tools utilities such as psadmin, go to
/opt/oracle/psft/pt/tools.
See People
Tools 8.52 Installation for Oracle.
Managing the Virtual Environment
Lifecycle
This
section discusses:
•
Understanding Virtual Machine Management
•
Saving Virtual Machines as Templates
•
Using the PeopleSoft Configuration Script
•
Resetting PeopleSoft Virtual Machines
Understanding Virtual Machine Management
After
you create and initialize your PeopleSoft virtual machine environment, you may
want to customize it and save the customized environment as a template to share
within your company. In general, the steps to follow in creating a template
from a customized environment are:
1.
Set up the virtual machines using the original templates.
2.
Customize the environment.
See
Saving Virtual Machines as Templates.
3. Edit
the configuration plug-in script.
See
Using the PeopleSoft Configuration Script.
4.
Issue commands to clean up and restart the virtual machines using the modified
configuration script. See Resetting PeopleSoft Virtual Machines.
5.
Save the virtual machine as a new template.
Saving Virtual Machines as Templates
The
virtual machines that you create from the PeopleSoft templates can actually be
saved as customized templates. For example, you may create a virtual machine
from the PeopleSoft PIA-AppBatch template, change some of the domain
configuration settings, and then save the virtual machine as a new template.
This new template can then be replicated throughout the organization. This
means that you don’t need to repeat the same customization steps each time you
create a virtual machine. Instead it is possible to install software into a virtual
machine or add specific configuration preferences and then save the virtual
machine as a new template.
This
new template can be used to create any number of virtual machines.
There
are a few things to keep in mind when saving a virtual machine as a template.
When saving a virtual machine as a template you may want to install software
into the virtual machine from which you will create the template. If you do so,
you must make sure that the software that you have installed is virtualization safe.
This means that the installation is not bound to the IP address or hostname
through any configuration files, database entries, and so on. When you save a
virtual machine as a template the installed components must be host neutral, so
that they will be able to run without any problems in new virtual machines that
have different hostnames or IP addresses.
If
the software that you have installed requires licensing on a per host or per
processor basis, you should ensure that you have the adequate number of
licenses for your site. The terms surrounding licensing will vary from
application to application.When saving a PeopleSoft virtual machine as a
template you may wish to add customized first boot configuration steps. This
means that you should edit the first boot configuration script, as described in
the following section.
See
Using the PeopleSoft Configuration Script.
Using the PeopleSoft Configuration
Script
To
add configuration steps to the PeopleSoft templates, use the delivered
configuration script,
/opt/oracle/psft/vm/oraclevm-template-ext.sh.
You can find this script in any PeopleSoft template. If you wish to extend the
template, you can overwrite or add to this script.
The oraclevm-template-ext.sh script
includes the four functions described in this table:
Function Name Description
Ovm_configure_pre
This function is run before the PeopleSoft People Tools
Configuration
scripts. This function can perform any custom setup steps prior to the running
of the PeopleSoft People Tools setup.ovm_configure_post This function is run
after the PeopleSoft People Tools
Configuration
scripts. This function can perform any custom steps required after the
PeopleSoft People Tools setup has completed.
ovm_cleanup_pre
This function is run when a virtual machine is being cleaned up. This function
is called before the PeopleSoft People Tools cleanup. ovm_cleanup_post This
function is run when a virtual machine is being cleaned up. This function is
called after the PeopleSoft People Tools cleanup.
When
the template is being initialized, the first boot configuration calls the four
functions in the order presented in the table. The first boot configuration
calls the function ovm_configure_pre() before any of the PeopleSoft People
Tools setup functions begin, and ovm_configure_post() after the PeopleSoft People
Tools setup functions have completed.
This
script does not just play a role when initializing. When the virtual machine is
being cleaned,
the
PeopleSoft People Tools cleanup script calls the ovm_cleanup_pre() function
before any of the
PeopleSoft
PeopleTools setup functions begin, and ovm_cleanup_post() function after the
PeopleSoft PeopleTools setup functions have completed. As described in the
above table these functions are located in
/opt/oracle/psft/vm/oraclevm-template-ext.sh.
Any
of these functions may be empty. These functions may call any of the functions
in the PeopleSoft People Tools scripts. This allows them to manipulate and
override the functions delivered in the PeopleSoft People Tools scripts.
After
you have modified the /opt/oracle/psft/vm/oraclevm-template-ext.sh
configuration script to include your preferred code, it is necessary to
reset the template to get it ready to be saved, as described in the following
section.
See
Resetting PeopleSoft Virtual Machines
For
more detailed information about the functions discussed in this section, review
the README file included in the /opt/oracle/psft/vm directory.
Resetting PeopleSoft Virtual Machines
It is
possible to reset your virtual machine such that the next time it is started it
will appear as a clean, newly started template. This is achieved by using the
following commands, in the order given:
/usr/sbin/oraclevm-template --cleanup
/usr/sbin/oraclevm-template --enable
Use
these commands when you have customized a virtual machine and want to save it
as a template. Once you have decided that you want to save a particular virtual
machine as a template, connect to the virtual machine using the VNC client,
issue the two commands above, shut it down using Oracle VM Manager, and then
finish by saving it as a template.
Note: - Because the /usr/sbin/oraclevm-template --cleanup option resets the
network stack on the virtual machine it may appear to hang. If this happens,
exit your login session and reconnect to the virtual machine, using the VNC
client to invoke the /usr/sbin/oraclevm-template
--enable option.
No comments:
Post a Comment