Installing Oracle VM Manager

This document is intended for users who want to install Oracle VM Manager. This document provides an overview of the Oracle VM Manager installation process.

 Installation Overview
Oracle VM uses an Oracle database as a repository. Oracle VM production deployments require Oracle Database Standard Edition (Oracle SE) or Enterprise Edition (Oracle EE). If you are testing Oracle VM and do not require a supported product, you can use Oracle Database Express Edition (Oracle XE). Oracle XE is not a supported product, and Oracle Support Services cannot supply patches for it. If you require full support from Oracle, you should use Oracle SE or EE as the Oracle VM database repository.
Oracle VM Manager can be installed in a demo installation using Oracle XE, or as a production installation using Oracle SE or EE. The demo installation installs Oracle XE on the local host and configures it to use as the repository. The production option collects information on the pre-installed Oracle Database and uses it as the repository. In both install types, Java, the Oracle VM Manager application, and Oracle WebLogic Server are installed on the local host.
An uninstaller is included with the installation script. The uninstaller gives you options to remove Oracle XE, Java, the Oracle VM Manager application, and the Oracle WebLogic Server.

Oracle VM Manager Components

The applications necessary to run Oracle VM Manager are packaged in the ISO image. Some or all of the following applications may be installed on the host computer when you install Oracle VM Manager:
Oracle VM Manager
The Oracle VM Manager application provided as a Oracle WebLogic Server domain and container.
Oracle WebLogic Server 11g
Oracle WebLogic Server Release 11g, including Application Development Framework (ADF) Release 11g. For more information about Oracle WebLogic, see the Oracle WebLogic 11g documentation.
Use of Oracle WebLogic Server with Oracle VM Manager is restricted to the servlet functionality without clustering for the Oracle VM Management Server.
Oracle Database
In a new installation, Oracle Database 11g Express Edition (Oracle XE) for Linux 64-bit may be installed. If Oracle XE is already installed, the installer asks whether it should use the existing database, install a new one, or use another database in the local area network (LAN). For more information about Oracle XE, see the Oracle Database Express Edition Documentation for 11g Release 2 (11.2).
You should only use the Oracle XE database as the Oracle VM Manager repository in non-production environments. Oracle XE is not a supported product and Oracle Support Services cannot provide bug fixes or patches for this product. If you are deploying Oracle VM Manager in a production environment, you should use Oracle Database Standard or Enterprise Edition, which you must install separately to Oracle VM. Oracle VM Manager includes a restricted-use license of the Oracle Database (Standard Edition or Enterprise Edition) for use as the Oracle VM Manager Management Repository only. The supported version of Oracle Database are:
  • Oracle Database Release 10.2.0.4 or greater
  • Oracle Database Release 11.1.0.7 or greater
  • Oracle Database Release 11.2.0.1 or greater
 Minimum Hardware and Software Requirements
The following minimum system requirements must be met on the computer on which you want to install Oracle VM Manager.

Hardware Requirements

Before you install Oracle VM Manager, make sure that your computer meets the minimum hardware requirements

Hardware Requirements for Oracle VM Manager


Items                                   Minimum Value             
Memory                               1.5 GB,4 GB with Oracle XE
Processor Type                   64 bit
Processor Speed                 1.83 GHz*1
Swap Space                         2.1 GB
Hard Disk Space                  5 GB in /u01,2 GB in /tmp

Software Requirements
Before you install Oracle VM Manager, make sure that your computer meets the following minimum software and configuration requirements.

Operating Systems

Oracle VM Manager is supported on the following operating systems:
  • Oracle Linux 5 Update 5 64-bit or later
  • Oracle Linux 6 64-bit or later
  • Red Hat Enterprise Linux 5 Update 5 64-bit or later
  • Red Hat Enterprise Linux 6 64-bit or later
You can download Oracle Linux from:
https://edelivery.oracle.com/linux

Network

The host computer on which you install Oracle VM Manager must have the host name correctly configured (pingable). Make sure the computer's host name matches the host name in the /etc/hosts file. Use the following command to check the host name:
# hostname
Use a text editor to check the host name in the /etc/hosts file. For example, to use VI enter
# vi /etc/hosts
For example, if the computer's host name is hostname1.example.com, and the IP address is 10.1.1.1, the corresponding item in the /etc/hosts file should be:
10.1.1.1 hostname1.example.com hostname1

Web Browsers

The Oracle VM Manager user interface is supported in the following Web browsers:
  • Microsoft Internet Explorer 7.0 and above
  • Mozilla Firefox 3.5 and above
  • Apple Safari 5.0 and above
  • Google Chrome 1.0 and above

Environment Configuration Script

The createOracle.sh is a script that automatically:
  • Creates the operating system dba group
  • Creates the oracle user and adds it to the dba group
  • Creates the /u01 directory
  • Sets the required parameters in the /etc/security/limits.conf file
  • Opens the required ports in the /etc/sysconfig/iptables file
To run the createOracle.sh script, you must first mount the Oracle VM Manager installer ISO file or CD. See Section 3.4.1, “Mounting the Oracle VM Manager Installation Media” for information on mounting the installation media. Then enter the following command as the root user:
# ./createOracle.sh

Prerequisite Packages

This section contains the prerequisite operating system packages that may be required prior to installing Oracle VM Manager.
  libaio
If you select during the Oracle VM Manager installation to use Oracle Database 11g Express Edition (Oracle XE) as the management data repository, you must install the libaio package. You must install libaio release 0.3.104 or above.
If your computer is configured with Oracle Unbreakable Linux Network (ULN) you can run either of the following commands to update or install libaio, whichever is appropriate for your system:
# yum install libaio
or
# up2date libaio
You can also find the libaio package on the Oracle Linux DVD or ISO file. To install libaio, go to the directory where the libaio.rpm is located, and enter the command:
# rpm -ivh libaio-version.rpm
To upgrade libaio, you can use the command:
# rpm -Uvh libaio-version.rpm
  unzip
If you have a minimal installation of Oracle Linux, you may not have unzip installed, which is a required package for the Oracle VM Manager installer. To install unzip, enter:
# yum install unzip
  bc
If you plan to use the Oracle XE database as the management data repository, you must install the bc package (GNU numeric processing language). To install bc, enter:
# yum install bc

Firewall Configuration

A default Oracle Linux install has the firewall enabled (iptables on). In order to use Oracle VM Manager on a system with iptables enabled you can either open all the ports used by Oracle VM Manager, or open all ports by disabling iptables.
The ports required for the web browser connection to Oracle VM Manager are: 7001, 7002 and 15901. The ports used by the Oracle VM Servers to connect to Oracle VM Manager are: 7001, 7002, and optionally 54321 and 54322 for remote API access. Oracle VM Manager, in turn, connects to the Oracle VM Servers through port 8899 for Oracle VM Agent communication, and port 6900 and up for secure VNC tunneling to virtual machines (one port per VM). Be sure to open the necessary ports on the different firewalls that may be installed between different parts of your network. Follow the guidelines of in the diagram below:
This diagram illustrates the firewall rules in Oracle VM Manager.

To disable iptables and open all ports, enter the following commands as the root user:
# service iptables stop
# chkconfig iptables off
Alternatively, open the required ports by using the iptables command as the root user:
# iptables -A INPUT -m state --state NEW -m tcp -p tcp --dport 7001 -j ACCEPT
# iptables -A INPUT -m state --state NEW -m tcp -p tcp --dport 7002 -j ACCEPT
# iptables -A INPUT -m state --state NEW -m tcp -p tcp --dport 15901 -j ACCEPT
# iptables -A INPUT -m state --state NEW -m udp -p udp --dport 123 -j ACCEPT
To remotely connect to the Oracle VM Manager core API, also enter the following command:
# iptables -A INPUT -m state --state NEW -m tcp -p tcp --dport 54321 -j ACCEPT
# iptables -A INPUT -m state --state NEW -m tcp -p tcp --dport 54322 -j ACCEPT
When all the ports have been opened, save the iptables configuration:
# service iptables save
This does not require iptables to be restarted as the commands open the ports while iptables is running and the save ensures they are opened on reboot/restart in future.
To configure the firewall to open the required ports automatically, use the environment configuration script provided with the Oracle VM Manager installer. See Section 3.3.2.4, “Environment Configuration Script” for information on using this script.

Installation Ports, Passwords, and Database Information

During the Oracle VM Manager installation, you may be required to set or enter the following ports, passwords and database connection information:
  • The Oracle Database hostname. This is the IP address or hostname of the host on which the Oracle Database to use as the Oracle VM Manager database repository is located. The default is localhost.
  • The Oracle Database System ID (SID). This is the database SID to use to connect to the Oracle VM Manager database repository.
  • The Oracle Database HTTP port. The default port number is 8080.
  • The Oracle Database listener port. The default port number is 1521.
  • The password for the Oracle Database SYS and SYSTEM accounts. You cannot use special characters for this password. Use only alpha numeric characters.
  • The password for the Oracle VM Manager OVS database schema.
  • The password for the Oracle WebLogic admin account.
The password you use for the Oracle WebLogic admin account must conform to the following rules:
  • Be between 8 and 16 characters in length.
  • Contain at least 1 lower case and 1 upper case letter.
  • Contain at least 1 numeric value or special character.

Oracle XE User

You must have an oracle user that is a member of a group named dba. If an oracle user does not exist on the Oracle VM Manager host, enter the following commands as the root user to create the user, create the group, add the user to the group, and set the user's password:
# groupadd dba
# useradd -g dba oracle
If the oracle user already exists, add it to the dba group using the following command:
# usermod -g dba oracle
The oracle user must also have a hard nofiles and soft nofiles minimum of at least 8192, as well as some other security limits set. To set these, edit the /etc/security/limits.conf file to include the following:
oracle       hard    nofile  8192
oracle       soft    nofile  8192
oracle       soft    nproc   4096
oracle       hard    nproc   4096
oracle       soft    core    unlimited
oracle       hard    core    unlimited
To configure the oracle user automatically, use the environment configuration script provided with the Oracle VM Manager installer. See Section 3.3.2.4, “Environment Configuration Script” for information on using this script.

  /u01 Directory

Oracle VM Manager and supporting products are installed into the /u01/app/oracle directory. Before you begin the Oracle VM Manager installation, make sure a /u01 directory exists, and it has at least 2.4 GB of space available.
To create the /u01 directory automatically, use the environment configuration script provided with the Oracle VM Manager installer. See Section 3.3.2.4, “Environment Configuration Script” for information on using this script.

Installing Oracle VM Manager

It takes approximately 8-15 minutes to complete the installation of Oracle VM Manager, depending on the performance of the Oracle VM Manager host, and the installation type you choose.
Before you can being the install, download the Oracle VM Manager software from:
http://edelivery.oracle.com/oraclevm
This section describes the Oracle VM Manager installation process.
Note
If you want to install Oracle VM Manager in a virtualized environment, do not install it on Oracle VM Server (dom0) directly; install it into a virtual machine running on an Oracle VM Server. For more information, see Section 3.7, “Running Oracle VM Manager as a Virtual Machine”.

Mounting the Oracle VM Manager Installation Media

Before you can run the Oracle VM Manager installer, you must mount the installation media. You can either burn the installation media to a CD and mount the CD, or mount the ISO file directly from the hard drive. Which ever way you choose to mount the installation media, you should perform this as the root user on the computer on which you want to install Oracle VM Manager.
  • To install Oracle VM Manager from a CD, burn the Oracle VM Manager ISO file to a CD. Insert and mount the Oracle VM Manager CD using the following commands:
    # mkdir mount-point
    # mount /dev/cdrom mount-point
    Where mount-point refers to the directory on which you mount the ISO file.
  • To install Oracle VM Manager from a hard drive, locate the folder that contains the ISO file. Mount the ISO file to an existing directory using the following commands:
    # mkdir mount-point
    # mount -o loop OracleVM-Manager-version.iso mount-point
    Where mount-point refers to the directory on which you mount the ISO file. For example:
    # mkdir /OVMCD
    # mount -o loop OracleVM-Manager-3.x.x.iso /OVMCD
    You can find all the mounted files under the directory /OVMCD.
    Note
    The location of the mounted Oracle VM Manager ISO file should be accessible by the oracle user.

Running the Oracle VM Manager Installer

To install Oracle VM Manager, enter the mount point you created in Section 3.4.1, “Mounting the Oracle VM Manager Installation Media”, for example, /OVMCD and start the installation with the runInstaller script as the root user:
# cd /OVMCD
# ./runInstaller.sh
A set of installer options are displayed:
Please select an installation type:
   1: Demo
   2: Production
   3: Uninstall
   4: Help
At the command prompt, enter 1 (a demo install) or 2 (a production install) to install Oracle VM Manager. If you already have Oracle VM Manager installed and want to uninstall it, select 3 (uninstall).
See Section 3.4.2.1, “Demo Install” for information on installing Oracle VM Manager and Oracle XE database, using the same password for all components. This should only be used in non-production environments. Oracle XE is not a supported product and Oracle Support Services cannot provide bug fixes or patches for this product.
See Section 3.4.2.2, “Production Install” for information on installing Oracle VM Manager as a production-level installation. This is the preferred installation type, with options for selecting Oracle SE or EE database as the location for the Oracle VM Manager repository, as well as setting individual passwords for each component.
See Section 3.14, “Uninstalling Oracle VM Manager” for information on uninstalling Oracle VM Manager, and its components such as Oracle XE (if applicable), Oracle WebLogic Server, ADF and Java.
You can also perform a silent install using the installer script optional parameters. See Section 3.4.2.3, “Performing a Silent Install”on how to perform a silent install, and Appendix A, Oracle VM Manager Installation Script (runInstaller) at the end of this chapter for the full syntax to the installation script.
The following sections walk through the following demo, production and silent install options.

3.4.2.1. Demo Install

The demo installation installs Oracle Database XE, Oracle WebLogic Server, Oracle Application Development Framework (ADF), Java, and Oracle VM Manager on the local system. Use this installation option for testing and non-production environments; do not use this installation option in production environments. Oracle XE is not a supported product and Oracle Support Services cannot provide bug fixes or patches for this product. The following example install shows a demo installation, and sample configuration options.
Example 3.1. Demo installation
# ./runInstaller.sh

Oracle VM Manager Release 3.x.x Installer
 
Oracle VM Manager Installer log file:
  /tmp/install-date-id.log
 
 
Please select an installation type:
   1: Demo
   2: Production
   3: Uninstall
   4: Help
 
   Select Number (1-4): 1 
The installation process starts, and the following is displayed:
Starting demo installation ...

The Demo installation type will use an XE database.
The usage of XE is for *demo purposes only* and is not supported for production.
Please *do not* plan to start with XE and migrate to a supported version of the database as this 
may not be possible.
For production environments or any long term usage please use the "Production" option with an SE 
or EE database.
   1: Continue
   2: Abort

   Select Number (1-2): 1 
You have the option to continue or abort the installation. Enter 1 to continue.
Enter a password to use for all users created during the demo installation. Password requirements are outlined in Section 3.3.2.7, “Installation Ports, Passwords, and Database Information”.
Verifying installation prerequisites ...

One password is used for all users created and used during the installation.
Enter a password for all logins used during the installation: 
Enter a password for all logins used during the installation (confirm): 

Verifying configuration ... 
Warnings may occur if not all recommendations are met, as you can see in the screen output above. If one of the prerequisites is not met, the installation will abort.
You have the option to continue or abort the installation. Enter 1 to continue. Progress of the installation is output on your screen step by step, as shown below:
Start installing the configured components:
   1: Continue
   2: Abort

   Select Number (1-2): 1

Step 1 of 9 : Database ...
Installing Database ...
Retrieving Oracle Database 11g XE ...
Installing Oracle Database 11g XE ...
Configuring Oracle Database 11g XE ...

Step 2 of 9 : Java ...
Installing Java ...

Step 3 of 9 : Database Schema ...
Creating database schema 'ovs' ...

Step 4 of 9 : WebLogic ...
Retrieving Oracle WebLogic Server 11g ...
Installing Oracle WebLogic Server 11g ...

Step 5 of 9 : ADF ...
Retrieving Oracle Application Development Framework (ADF) ...
Unzipping Oracle ADF ...
Installing Oracle ADF ...

Step 6 of 9 : Oracle VM  ...
Retrieving Oracle VM Manager Application ...
Extracting Oracle VM Manager Application ...
Installing Oracle VM Manager Core ...

Step 7 of 9 : Domain creation ...
Creating Oracle WebLogic Server domain ...
Starting Oracle WebLogic Server 11g ...
Configuring data source 'OVMDS' ...
Creating Oracle VM Manager user 'admin' ...

Step 8 of 9 : Deploy ...
Deploying Oracle VM Manager Core container ...
Deploying Oracle VM Manager UI Console ...
Deploying Oracle VM Manager Help ...
Enabling HTTPS ...
Granting ovm-admin role to user 'admin' ...

Step 9 of 9 : Oracle VM Manager Shell ...
Retrieving Oracle VM Manager Shell & API ...
Extracting Oracle VM Manager Shell & API ...
Installing Oracle VM Manager Shell & API ...

Retrieving Oracle VM Manager Upgrade tool ...
Extracting Oracle VM Manager Upgrade tool ...
Installing Oracle VM Manager Upgrade tool ...
Copying Oracle VM Manager shell to '/usr/bin/ovm_shell.sh' ...
Installing ovm_admin.sh in '/u01/app/oracle/ovm-manager-3/bin' ...
Installing ovm_upgrade.sh in '/u01/app/oracle/ovm-manager-3/bin' ...
Enabling Oracle VM Manager service ...
Shutting down Oracle VM Manager instance ...
Restarting Oracle VM Manager instance ...
Waiting 15 seconds for the application to initialize ...
Oracle VM Manager is running ...
Oracle VM Manager installed.
Please wait while WebLogic configures the applications... This can take up to 5 minutes.
When the installation is complete a summary similar to the following is displayed:
Installation Summary
--------------------
Database configuration:
  Database host name          : localhost
  Database instance name (SID): XE
  Database listener port      : 1521
  Application Express port    : 8080
  Oracle VM Manager schema    : ovs

Weblogic Server configuration:
  Administration username     : weblogic

Oracle VM Manager configuration:
  Username                    : admin
  Core management port        : 54321
  UUID                        : 0004fb0000010000cc1b57e39ff77ea9

Passwords:
There are no default passwords for any users. The passwords to use for Oracle VM
Manager, Oracle Database 11g XE, and Oracle WebLogic Server have been set by you
during this installation. In the case of a demo install, all passwords are the
same.

Oracle VM Manager UI:
  http://myserver.example.com:7001/ovm/console
  https://myserver.example.com:7002/ovm/console
Log in with the user 'admin', and the password you set during the installation.

Please note that you need to install tightvnc-java on this computer to access a virtual 
machine's console.

For more information about Oracle Virtualization, please visit:
  http://www.oracle.com/virtualization/

Oracle VM Manager installation complete.

Please remove configuration file /tmp/ovm_configid.

Important
Make sure you delete the temporary configuration file created during the installation:
/tmp/ovm_configid

3.4.2.2. Production Install 

The production installation lets you use an existing local or remote Oracle database as the Oracle VM Manager database repository. You set the users and passwords to use for the Oracle Database, Oracle VM Manager database repository, Oracle WebLogic Server, and Oracle VM Manager during the production installation. This is the preferred installation method. Use this installation option in production environments; do not use an Oracle XE database in a production environment. The following example describes how to connect to an existing local Oracle database.

 
Example 3.2. Production installation
# ./runInstaller.sh

Oracle VM Manager Release 3.x.x Installer
 
Oracle VM Manager Installer log file:
  /tmp/install-date-id.log
 
 
Please select an installation type:
   1: Demo
   2: Production
   3: Uninstall
   4: Help
 
   Select Number (1-4): 2 
The installation process starts, and the following is displayed:
Starting production installation ...

Verifying installation prerequisites ...

Oracle Database Repository
==========================
Use an existing Oracle database  
When prompted, enter the following information as outlined in section Section 3.3.2.7, “Installation Ports, Passwords, and Database Information”:
Enter the Oracle Database hostname [localhost]: 
Enter the Oracle Database System ID (SID) [XE]: 
Enter the Oracle Database SYSTEM password: 
Enter the Oracle Database listener port [1521]:  
Enter the Oracle VM Manager database schema [ovs]: 
Enter the Oracle VM Manager database schema password: 
Enter the Oracle VM Manager database schema password (confirm): 

Oracle Weblogic Server 11g
==========================
Enter the Oracle WebLogic Server 11g user [weblogic]: 
Enter the Oracle WebLogic Server 11g user password: 
Enter the Oracle WebLogic Server 11g user password (confirm): 

Oracle VM Manager application
=============================
Enter the username for the Oracle VM Manager administration user [admin]: 
Enter the admin user password: 
Enter the admin user password (confirm): 

Verifying configuration ...

Start installing the configured components:
   1: Continue
   2: Abort

   Select Number (1-2): 1
You have the option to continue or abort the installation. Enter 1 to continue. You may be prompted again to either abort or continue the installation in case certain components are already present on your system. Progress of the installation is output on your screen step by step, as shown below:
Start installing the configured components:
   1: Continue
   2: Abort

   Select Number (1-2): 1

Step 1 of 9 : Database ...
Installing Database ...
Database installation skipped ...

Step 2 of 9 : Java ...
Installing Java ...
If an existing Oracle VM Manager database schema is found in the database, the following is displayed:
Step 3 of 9 : Database Schema ...
An existing OVM database was found.  How should the install proceed?
   1: Use the existing OVM database
   2: Remove the existing OVM database and create a new OVM database
   3: Abort

   Select Number (1-3): 1
Enter 1 - 3, depending on your requirements. In this example, the existing schema is retained.
Alternatively, if no existing Oracle VM Manager database schema is found in the database, the schema is created.
Step 3 of 9 : Database Schema ...
Creating database schema 'ovs' ...

Step 4 of 9 : WebLogic ...
Retrieving Oracle WebLogic Server 11g ...
Installing Oracle WebLogic Server 11g ...

Step 5 of 9 : ADF ...
Retrieving Oracle Application Development Framework (ADF) ...
Unzipping Oracle ADF ...
Installing Oracle ADF ...

Step 6 of 9 : Oracle VM  ...
Retrieving Oracle VM Manager Application ...
Extracting Oracle VM Manager Application ...
Installing Oracle VM Manager Core ...

Step 7 of 9 : Domain creation ...
Creating Oracle WebLogic Server domain ...
Starting Oracle WebLogic Server 11g ...
Configuring data source 'OVMDS' ...
Creating Oracle VM Manager user 'admin' ...

Step 8 of 9 : Deploy ...
Deploying Oracle VM Manager Core container ...
Deploying Oracle VM Manager UI Console ...
Deploying Oracle VM Manager Help ...
Enabling HTTPS ...
Granting ovm-admin role to user 'admin' ...

Step 9 of 9 : Oracle VM Manager Shell ...
Retrieving Oracle VM Manager Shell & API ...
Extracting Oracle VM Manager Shell & API ...
Installing Oracle VM Manager Shell & API ...

Retrieving Oracle VM Manager Upgrade tool ...
Extracting Oracle VM Manager Upgrade tool ...
Installing Oracle VM Manager Upgrade tool ...
Copying Oracle VM Manager shell to '/usr/bin/ovm_shell.sh' ...
Installing ovm_admin.sh in '/u01/app/oracle/ovm-manager-3/bin' ...
Installing ovm_upgrade.sh in '/u01/app/oracle/ovm-manager-3/bin' ...
Enabling Oracle VM Manager service ...
Shutting down Oracle VM Manager instance ...
Restarting Oracle VM Manager instance ...
Waiting 15 seconds for the application to initialize ...
Oracle VM Manager is running ...
Oracle VM Manager installed.

Please wait while WebLogic configures the applications... This can take up to 5 minutes.
When the installation is complete a summary similar to the following is displayed:
Installation Summary
--------------------
Database configuration:
  Database host name          : localhost
  Database instance name (SID): MYDB
  Database listener port      : 1521
  Application Express port    : 8080
  Oracle VM Manager schema    : ovs

Weblogic Server configuration:
  Administration username     : weblogic

Oracle VM Manager configuration:
  Username                    : admin
  Core management port        : 54321
  UUID                        : 0004fb0000010000cc1b57e39ff77ea9

Passwords:
There are no default passwords for any users. The passwords to use for Oracle VM
Manager, Oracle Database 11g XE, and Oracle WebLogic Server have been set by you
during this installation. In the case of a demo install, all passwords are the
same.

Oracle VM Manager UI:
  http://myserver.example.com:7001/ovm/console
  https://myserver.example.com:7002/ovm/console
Log in with the user 'admin', and the password you set during the installation.

Please note that you need to install tightvnc-java on this computer to access a virtual 
machine's console.

For more information about Oracle Virtualization, please visit:
  http://www.oracle.com/virtualization/

Oracle VM Manager installation complete.

Please remove configuration file /tmp/ovm_configid.

Important
Make sure you delete the temporary configuration file created during the installation:
/tmp/ovm_configid

3.4.2.3. Performing a Silent Install

The Oracle VM Manager installer can be installed silently, without any intervention. An installation configuration script can be used to provide the installation options, and a set of command line options are available for the installation parameters. See Appendix A, Oracle VM Manager Installation Script (runInstaller) at the end of this chapter for information on the command line options.
The following example silently performs a production install.
Warning
Always provide the absolute path to the configuration file. The installer cannot process a relative path and will simply terminate the installation process.
Example 3.3. Silent install using configuration file

The command to run the silent production installation using a configuration file is:
./runInstaller.sh --config=/path/config.yml --installtype=production --assumeyes 
The configuration file used in this installation example (config.yml) installs a local Oracle XE database. Replace the password entry with your own password.
db:
      install       : Yes
      host          : localhost
      sys_password  : password
      port          : 1521
      sid           : XE 
      mgmt_port     : 8080
      user          : ovs
      password      : password
 
webLogic:
      install       : Yes
      user          : weblogic
      password      : password
 
java:
      install       : Yes
 
ADF:
      install       : Yes
 
OVMCore:
      install        : Yes
      user           : admin
      password       : password
 
OVMConsole:
      install       : Yes
 
OVMShell:
      install       : Yes
 
onFailure:
      cleanup       : No 

OVMUpgrade:
      install       : Yes

Configuring the NTP Service

When an Oracle VM Server is discovered from Oracle VM Manager, NTP (Network Time Protocol) is automatically configured and enabled to ensure time synchronization. Oracle VM automatically configures Oracle VM Manager as the NTP source for all Oracle VM Servers under its control.
However, to provide time services to the Oracle VM Servers, NTP must first be installed and configured on the Oracle VM Manager host server. Make sure that your Oracle VM Manager host is either registered with the Unbreakable Linux Network (ULN) or configured to use Oracle's public YUM service.
To configure NTP on the Oracle VM Manager host:
  1. Install the NTP package.
    # yum install ntp
    Once NTP is installed, configure it to both synchronize with upstream servers and provide time services to the local network, where the Oracle VM Servers reside.
  2. Enable upstream synchronization by defining the upstream time servers in the ntp.conf file.
    Oracle Linux uses three public NTP servers as upstream time sources by default. Check with your network administrator if time services are provided on the corporate network and, if necessary, replace the default entries with the names or IP addresses of your NTP servers.
    Use your favorite text editor to modify /etc/ntp.conf. Search for these entries:
    # vi /etc/ntp.conf
    
    server 0.rhel.pool.ntp.org
    server 1.rhel.pool.ntp.org
    server 2.rhel.pool.ntp.org
  3. Configure downstream access for the Oracle VM Servers in your local network. To do so, disable the default "noquery" option for the Oracle VM Server management network.
    Again in the /etc/ntp.conf file, search for this entry:
    #restrict 192.168.1.0 mask 255.255.255.0 nomodify notrap
    Replace 192.168.1.0 with the network address of your Oracle VM Server management network. You may also need to adjust the netmask (255.255.255.0). Remove the # character at the start of the line to uncomment this entry. Once you have finished editing, save the /etc/ntp.conf file.
  4. Start the NTP service and set it to launch automatically upon boot.
    # service ntpd start
    # chkconfig ntpd on
  5. When NTP is running, check upstream synchronization. The ntpq command should output something similar to this example:
    # ntpq -p
    
         remote           refid      st t when poll reach   delay   offset  jitter
    ==============================================================================
     lists2.luv.asn. 203.161.12.165  16 u   25   64    3    3.495   -3043.1   0.678
     ns2.novatelbg.n 130.95.179.80   16 u   27   64    3   26.633   -3016.1   0.797
     sp1.mycdn.fr    130.234.255.83  16 u   24   64    3    4.314   -3036.3   1.039
    When upstream NTP is working properly, delay and offset values should be non-zero and the jitter value should be below 100.
  6. Test downstream synchronization from another server in the management network to ensure that NTP services are working. Note that it may take several minutes before your NTP server is able to provide time services to downstream clients. Begin by checking the stratum level of your server:
    # ntpq -c rv
    
    assID=0 status=c011 sync_alarm, sync_unspec, 1 event, event_restart,
    version="ntpd 4.2.4p8@1.1612-o Tue Jul  6 21:50:26 UTC 2010 (1)",
    processor="x86_64", system="Linux/2.6.32-200.19.1.el6uek.x86_64",
    leap=11,  stratum=16 , precision=-20, rootdelay=0.000,
    rootdispersion=1.020, peer=0, refid=INIT,
    reftime=00000000.00000000  Thu, Feb  7 2036 17:28:16.000, poll=6,
    clock=d21d4a96.a26c5962  Fri, Sep 16 2011 14:09:58.634, state=0,
    offset=0.000, frequency=0.000, jitter=0.001, noise=0.001,
    stability=0.000, tai=0   
    If the server is showing stratum=16, wait a few minutes and try again. It may take up to 15 minutes for an NTP server to stabilize sufficiently to lower its stratum level.
    Downstream clients will not synchronize with a server at stratum level 16. Once the stratum level has dropped, log in to any available Linux host in your management network and issue the following command:
    # ntpdate -d manager.hostname
    [...]
    16 Sep 13:58:25 ntpdate[1603]: step time server 192.168.1.1 offset 3.009257 sec
    This command runs ntpdate in debug mode, in which case the availability of the remote time server is checked. If the debug run ends in a line similar to the one in this example, the test is successful. In case the stratum level is still too high, the error message "Server dropped: strata too high" is displayed.
Once you have confirmed with these tests that NTP is working properly for your environment, you should not need to check this again.
Caution
NTP communicates over UDP port 123. Ensure that no firewall is blocking this traffic.

Installing and Configuring a VNC Viewer

Oracle VM Manager uses a secure tunnel to protect the virtual machine console (remote connection utility) data across the network. Oracle VM Manager does not communicate directly with the VNC client, but rather connects via an SSH-encrypted tunnel on port 69xx (where xx is based on the guest to which it is connecting).
Any firewall between the client and Oracle VM Manager needs port 15901 to be open. Any firewall between the Oracle VM Manager and the Oracle VM Servers needs ports 6900 and above open; one port for each virtual machine on an Oracle VM Server. For example, if you have 100 virtual machines on an Oracle VM Server, you should open ports 6900-6999 (100 ports) on any firewall between the Oracle VM Server and Oracle VM Manager.
To connect to a virtual machine's console in Oracle VM Manager, you should have a VNC viewer installed somewhere in your environment, either:
  • On the Oracle VM Manager host computer
  • On the client computer
  • On both the Oracle VM Manager host computer and the client computer
The virtual machine console feature uses the client instance of a VNC viewer, if one exists, to connect to a virtual machine's console. If a VNC viewer is not found on the client computer, a request is sent to the Oracle VM Manager host computer to display the VNC viewer.
It is preferred that you install either TightVNC on the Oracle VM Manager host computer. You can get the latest TightVNC package from:
http://oss.oracle.com/oraclevm/manager/RPMS/
Install TightVNC with the command:
# rpm -ivh tightvnc-java-version.noarch.rpm
On the client computer you use to connect to Oracle VM Manager it is recommended that you install RealVNC. Oracle recommends RealVNC on the client computer as it renders quickly, has better keyboard support, and has less mouse control issues compared to other VNC clients. The RAS proxy applet used to view the screen or console of a virtual machine looks for RealVNC by default. If you have multiple VNC viewers on your client computer, you can configure which one is used from the virtual machine console in Oracle VM Manager. See Connecting to a Virtual Machine for more information on using and configuring the VNC client.
If you are using a Linux-based operating system on your client computer, you can also install TightVNC as above on your client computer and it is automatically discovered when you connect to a virtual machine using the console feature in Oracle VM Manager.

 Installation Logs

If any errors occur during installation, check the Oracle VM Manager installation log file:
/tmp/ovmm-installer.selfextract_id/install-date.log
When the installation is complete, the installation log is copied to:
/tmp/install-date.log

Installation Directories

The locations of the Oracle VM Manager components are listed

Oracle VM Manager component installation locations

Component                                   Location
Java                                               /u01/app/oracle/java
Oracle WebLogic Server 11g         /u01/app/oracle/Middleware/
Oracle ADF                                 /u01/app/oracle/Middleware/
Oracle VM Manager application    /u01/app/oracle/ovm-manager-3/
Oracle WebLogic Server domain  /u01/app/oracle/ovm-manager-3/machine1/base_adf_domain 

******************************END**********************************

No comments:

ORA-01552: cannot use system rollback segment for non-system tablespace 'TEMP'

 ORA-01552: cannot use system rollback segment for non-system tablespace "string" Cause: Used the system rollback segment for non...