Wednesday, July 2, 2014

Oracle Business Integration PS6 VirtualBox Appliance
With Process Accelerators 7.1
Oracle SOA Suite with Oracle Service Bus
Oracle BPM Suite with Process Accelerators
Oracle Event Processing


  1. Using the Virtual Appliance


           1.1. Install the appliance


  •  Ensure system requirements are met i.e. 64-bit machine with at least 16 GB RAM and 50 GB free disk space. Enable hardware virtualization in your PC BIOS (required).
  • Download and install the latest Oracle VM VirtualBox.
  • Download all parts of the archive i.e. files with names ending in .001, .002 etc.
  • Download the .md5 checksum file, which contains the MD5 checksums of all the parts to test the integrity of the downloaded files. Use utilities such as md5sum on Linux, or any compatible Windows utility, for example http://www.etree.org/md5com.html / Cygwin.
  • Unzip the archive using latest WinZip or 7Zip. This should create a single file, ending in .ova – this is the virtual appliance that is ready for import.
  • Start VirtualBox and set the import folder for the image. Go to File -- > Preferences

  • Set the Default Machine Folder to a location of your choice with enough free disk space. This is where VirtualBox will store the virtual image you are about to import. Click OK
  • Import the appliance (File -->Import Appliance …) and choose the .ova file created earlier. You can change the name of the virtual machine if you wish.
  • Click Import. Read the license agreement and accept by clicking Agree. The import will take a few minutes.

         1.2 Configure the virtual machine


Change memory settings

  • With the appliance selected, click on Settings and then go to System.



  •  Set the memory to the desired value depending on the intended use of the appliance. The seeded value is 13 GB. Note: You will get a “non-optimal settings” warning if you exceed the memory threshold for your host machine. You may ignore these warnings as long as you leave enough memory for the host OS e.g. minimum 1.5 GB for Windows. Also ensure no programs are running in the background e.g. email clients.

Change the number of CPUs

  • Go to the “Processor” tab and enter the desired value. Leave it at the maximum value (recommended for laptops), or reduce it to limit the number of CPUs available to the virtual machine (e.g. use only 2 cores of a quad-core or larger machine).

Handling errors related to USB 2.0

  • If you see an error related to USB 2.0, either install the Oracle VM Virtual Box extension (available in the same location as the image), or disable USB 2.0:
  • Go to USB
  • Uncheck the box in front of “Enable USB 2.0 (EHCI) Controller” and click OK.

Setup shared folders between the Virtual Machine and local disk

  • To copy files between the image and a local disk, select Shared Folders on the VM settings and click on the + icon to add a new share

  • Select Auto-mount and Make Permanent
  • The folder name is what will be visible within the Linux machine under /media/sf_<folder>. In the example shown below, the E:\scratch folder on Windows will be visible within the virtual appliance under /media/sf_scratch. For best performance, copy frequently used files to the virtual machine disks e.g. under /home/oracle.

  • Configure network settings on local machine

    When running the appliance in “Server Only” mode, you will need to run JDeveloper, Enterprise Manager and browser applications on your local host machine, connecting to the virtual machine over the network. This requires network setting changes on your local host machine.


    • Edit your local machine’s hosts file and add soabpm-vm and soabpm-vm.site as aliases for your loopback address as shown below. The hosts file can be found in /etc/hosts (Linux) and %WIN%\system32\drivers\etc\hosts (Windows)

                   127.0.0.1 soabpm-vm soabpm-vm.site localhost
      • Note: Using a loopback address will only work for NAT network mode (see below). If you change the VirtualBox network mode to Bridged, then run “ifconfig” within the VM to note the IP address assigned to the virtual machine eth0 interface, and use that instead of 127.0.0.1.
      • If you are unable to connect to soabpm-vm from your local machine to the VM, change the Network Proxy settings on your local machine to ensure that there are no conflicts with any other machine on the network. For example, there probably will be another VM instance named soabpm-vm running on the corporate network, whose IP address is being used by the browser instead of your local machine loopback address. To avoid this, either turn off any Network Proxy, or ensure that soabpm-vm, soabpm-vm.site, localhost and 127.0.0.1 are bypassed from the proxy. This will force the IP address resolution to happen from your local machine hosts file instead of the corporate DNS.

      Configure network adapter settings for the VM

      • The default network adapter configuration is set to NAT mode. If you wish to have the VM directly exposed to the external network for server-to-server communication with an external machine, you can change the network adapter to Bridged mode. This is only recommended for certain complex configurations such as running multiple virtual machines. For more details on this mode, refer to the VirtualBox documentation.

                 1.3 Start the appliance

      • With the appliance selected, click on Start
      • Login as oracle with password as oracle (see Appendix for list of seeded credentials). After logging in, you will see a menu with various options.
      • The VBox appliance is started in console/text mode by default to save memory. To start the desktop, choose “Start Graphical Desktop” and press return, which will start the Gnome desktop. This is only required to be done once to change seeded JVM settings for the WLS servers (see the next section).






        0 Comments:

        Post a Comment

        Subscribe to Post Comments [Atom]

        << Home