This chapter provides an overview of installing Oracle Virtual Assembly Builder. This chapter includes the following sections:
The steps you need to take to install Oracle Virtual Assembly Builder are described in Table 1-1.
|Tasks||Details and Documentation|
Prepare your system environment for installation.
Ensure that your system environment meets the general installation requirements for Oracle Virtual Assembly Builder.
See the following sections:
Ensure that reference systems are set up.
To create appliances using Oracle Virtual Assembly Builder Introspection functionality, you must have appropriate reference systems set up. Refer to product specific documentation for those system requirements and set up.
Install and configure your deployment environment.
An Oracle VM environment must be installed and configured to deploy your assemblies. See Oracle VM (
Install an Application Server.
Oracle Virtual Assembly Builder Deployer requires Oracle WebLogic Server to be installed in an Oracle Middleware Home.
Installing Oracle WebLogic Server creates the Middleware home and WebLogic home directories, which are required for an Oracle Virtual Assembly Builder Deployer installation. For more information, see "Middleware Home and WebLogic Home Directories" in Oracle Fusion Middleware Installation Planning Guide. Also see the following sections in Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server:
Install Oracle Virtual Assembly Builder.
Use this installer to install Oracle Virtual Assembly Builder Studio and Deployer and configure an Studio instance.
This creates the following directories:
See Chapter 2, "Installing Oracle Virtual Assembly Builder" for installation instructions.
Start the servers.
Start the Administration Server.
See "Starting and Stopping Servers" in Oracle® Fusion Middleware Managing Server Startup and Shutdown for Oracle WebLogic Server for instructions on how to start the Administration Server.
The Oracle Virtual Assembly Builder Deployer component runs inside Oracle WebLogic Server. The CLI and the Studio graphical user interface interact with the Oracle Virtual Assembly Builder Deployer through a Web service exposed in Oracle WebLogic Server. You must configure Oracle WebLogic Server as part of the installation and configuration process.
You can select one of the following installation options:
This is the correct installation option for an Oracle Exalogic environment. In an Oracle Exalogic environment, you use the Deployer installed in Exalogic Control VM. Thus, you only need to install and configure Oracle Virtual Assembly Builder Studio for creating assemblies.
This option installs only Oracle Virtual Assembly Builder Studio. It contains the capabilities to create appliances and assemblies, create appliance templates and assembly archives and creating deployment plans.
This option gets installed in a new Oracle Home under a new or an existing Middleware Home.
This option exposes abctl command line and Studio graphical user interfaces.
This option installs only Oracle Virtual Assembly Builder Deployer. It contains the capabilities to configure deployment targets, upload assembly archives to Deployer, create assembly instances, deploy/undeploy/start/stop assembly instances and scale appliance instances.
Oracle WebLogic Server should be pre-installed under a Middleware Home.
Oracle Virtual Assembly Builder Deployer gets installed in a new Oracle Home under the same Middleware Home where you have Oracle WebLogic Server installed.
This option exposes abctl command line and Web Services interfaces.
The default installation option installs both Oracle Virtual Assembly Builder Studio and Deployer. It contains the capabilities described for Oracle Virtual Assembly Builder Studio and Oracle Virtual Assembly Builder Deployer install options.
Oracle WebLogic Server should be pre-installed under a Middleware Home.
Both Oracle Virtual Assembly Builder Studio and Deployer get installed in a new Oracle Home under the same Middleware Home where you have Oracle WebLogic Server installed.
This option exposes abctl command line, Studio graphical user interface and Web Services interfaces.
The user who installs should be a trusted user, and a member of a trusted OS group.
The template creation process does a security check to see that the Operating System (OS) user attempting to create the template is the same OS user who owns the Oracle Virtual Assembly Builder
bin directory. Having the OS user who installs the product be the same OS user who creates templates ensures that the security check will succeed.
Oracle WebLogic Server must be installed in a secure configuration prior to deploying the Oracle Virtual Assembly Builder Deployer to it.
Oracle Virtual Assembly Builder uses the Oracle VM product set as the virtualization infrastructure.
Oracle Virtual Assembly Builder and Oracle VM Manager are network and storage- intensive products. The Oracle VM servers, the Oracle VM Manager and Oracle Virtual Assembly Builder communicate over the network during the course of introspection, registration and deployment of VMs.
The setup should have the following characteristics:
Oracle VM server pools machine with at least 16GB of total physical memory, gigabit networking facility, high capacity and high speed storage space for various tests and configuration, and acceptable processing power. The best performance will come from server-class machines with fast processors, memory and a high performance storage subsystem.
Oracle VM Manager machine which is hosted on another machine. This machine will run OEL x86_64 Linux and must be connected to the Oracle VM server pool by a Gigabit network switch.
Reference systems (products you plan to introspect) may also be installed on this machine to help speed up introspection and file set capture. Oracle Virtual Assembly Builder also supports remote introspection, so reference systems do not have to be co-located with Oracle Virtual Assembly Builder. Due to the large size of various Oracle Virtual Assembly Builder artifacts that will be created for your components you should make sure to have plenty of disk space on this machine.
If you going to use static IP addresses for your appliances of an assembly for deployment, you should have one static IP address per appliance instance.
Before using Oracle Virtual Assembly Builder, ensure that your environment meets the following prerequisites. These items are not required for installation, but are necessary environmental components for the use of Oracle Virtual Assembly Builder.
Ensure your environment meets all requirements before starting the installation.
This certification document details supported installation types, platforms, operating systems, databases, and JDKs. See Virtual Assembly Builder in Oracle Fusion Middleware 11g Release 1 (at
The following operating systems are supported:
Oracle Enterprise Linux 5 (UL3+) (32-bit. 64 bit supported in 32-bit mode)
Red Hat Enterprise Linux 5 (UL3+) (32-bit. 64 bit supported in 32-bit mode)
You can verify your operating system version using the commands listed here.
Oracle Enterprise Linux:
# cat /etc/enterprise-release
Red Hat Enterprise Linux:
# cat /etc/redhat-release
Oracle Universal Installer includes Sun JDK for Linux. You can choose to install it (the JDK) during installation and use it with Oracle Virtual Assembly Builder. You can also choose to us your own JDK installation.
Download and install Oracle Enterprise Linux JeOS from:
http://edelivery.oracle.com/oraclevm. If this is your first time using eDelivery, you will be required to register. Register, then continue.
On the Welcome screen, click Continue. The Media Pack Search screen appears.
Select a Product Pack (Oracle Linux), and Platform (x86 32 bit). Click Go. The Results are displayed.
Select Oracle Linux JeOS for Building Oracle VM templates for x86 (32 bit). Click Continue. Available downloads appear.
Download JeOS Base x86 and x86_64, by clicking Download. The file is downloaded.
Unzip the downloaded zip file.
(As root) install the "ovm-modify-jeos" package using the
rpm command with the
Download and install Oracle Open-OVF package from the OVM 3.0 channels of a yum repository. For information on setting up a yum repository see
See also the following whitepaper on the Unbreakable Linux Network, a comprehensive resource for Oracle Linux and Oracle VM support subscribers, offering access to Linux software patches, updates and fixes, along with information on yum program and support policies:
The supported Guest OS is an Oracle Enterprise Linux Base Image.
You have a choice of downloading an Oracle provided sample Oracle Enterprise Linux Base Image, or creating your own. The sample image is available on Oracle Technology Network:
Ensure that the base image architecture matches your component software. That is, use a 32-bit base image if your component software is 32-bit; 64-bit base image for 64-bit component software.
To create the appropriate Base Image(s):
Oracle Enterprise Linux Base Image, see:
http://www.oracle.com/technetwork/server-storage/vm/overview/templates-101937.htmlThe information on this, and referenced pages, will provide the information you need to create your own System Base Image.
When specifying a base image, the image must meet the following requirements:
Oracle Enterprise Linux 5 (UL3+)
At least 250MB of free space for /tmp. (depending on the type of product your are creating appliance for and deploying, you may need more free space. Refer to appropriate product install guide for the specific free space requirement).
At least 500MB of swap space
You must have installed the following packages (RPMs):
Install the following kernal modules:
ovmapi_5.5.ko (32 bit)
ovmapi_5.3_64bit.ko (64 bit)
In addition, for deploying virtual machines for FMW components, you must have installed:
openmotif22 (only required for Oracle Forms and Oracle Reports servers)
For deploying virtual machines for Oracle Database, you must have installed:
For FMW components, the following shell parameters must be set:
For Oracle database, the following shell parameters must be set
For Oracle database, the following kernel parameters must be set:
semmni=128 # max number of arrays; default is 128 semmsl=250 # max semaphores per array. default is 250 semmns=32000 # max semaphores system wide; default is 32000 semopm=100 # max ops per semop call; default is 32
Shared Memory Limits
shmmni=4096 # max number of segments; default is 4096 shmmax=0.5GB # max seg size (kbytes); default is 4194303, which is 3GB shmall=2097152 # max total shared memory (kbytes); default is 1073741824
file-max=6815744 # system wide file descriptors; default is 204573; aio-max-nr=Maximum:1048576 # default is 65536; ip_local_port_range=9000 65500 # default is 32768 61000; rmem_default=262144 # default is 109568; rmem_max=4194304 # default is 131071; wmem_default=262144 # default is 105968 wmem_max=1048576 # default is 131071
Additional database requirements:
Name Resolution: Ensure that host names are resolved through the
/tmp directory should have a minimum of 1GB of space.
Add the following line in the
session required pam_limits.so
You must turn on
oraclevm-templates while creating the image.
Oracle recommends that you turn off
iptables while creating the image.
You must turn off
requiretty in the base image for sudo operations to work. This is a requirement to deploy the assembly archive through Enterprise Manager.
The base image must have the user oracle. One way to add a user to the base image is to boot the base image, log on to it as root, and call
The primary group for oracle user must be oracle. By default, when you create the oracle user, it is automatically set. To set it manually, create the group and assign it to oracle user by executing:
/usr/sbin/groupadd oracle /usr/sbin/usermod -g oracle -a -G oracle oracle