Test driving the VirtualBox SOA Suite and BPM 11g Appliance

Few weeks ago I mentioned the VirtualBox SOA Suite and BPM 11g R1 PS2 Appliance. In the last week we’ve been test driving it on several machines.

32-bits Windows7

We noticed that on some 32-bits Windows7 machines the WebLogic Server and SOA Suite fail to start. The reason seems to be that on some 32-bit Windows 7 machines the amount of memory that can be allocated to the VirtualMachine in VirtualBox is limited to 1500 MB.
VirtualBox explains:

The Base Memory sets the amount of RAM that is allocated and given to the VM when it is running. The specified amount of memory will be requested from the host operating system, so it must be available or made available as free memory on the host when attempting to start the VM and will not be available to the host while the VM is running. This is the same setting that was specified in the “New Virtual Machine” wizard.

This can cause a crash when starting the WebLogic Server since the SER_MEM_ARGS are set to:
SER_MEM_ARGS="-Xms512m -Xmx1536m"

These are set in the wls_env.sh which can be found in the /home/oracle/bin/. Altering the -Xmx to a lower value (lower than the amount you can allocate on your workstation) can solve this problem.

Oracle Service Bus

Since I’ve been involved in several projects in the last year that want to use both SOA Suite and the Oracle Service Bus (which at least from some perspectives is part of the SOA Suite) it was a bit disappointing for me that OSB isn’t included. I’ve been asking around for the rationale behind this choice without any satisfying answers so far. Please leave your thoughts in the comments or in this thread of the Oracle forums.

4 thoughts on “Test driving the VirtualBox SOA Suite and BPM 11g Appliance

  1. Pingback: Tweets that mention deltalounge ยป Test driving the VirtualBox SOA Suite and BPM 11g Appliance -- Topsy.com

  2. Irshad Buchh

    I have a Windows 7 (64 bit) machine with 4G RAM and I installed the Oracle SOA Suite 11g on VirtualBox. All the things work great, but the VirtualBox only recognizes 2G RAM not 4G RAM.

    Do you have any ideas as to why?

  3. PeterPaul Post author

    Try to change the settings using the menu “Machine”, then choose “System” -> “Motherboard”. You should be able to change the memory settings there.


Leave a Reply

Your email address will not be published. Required fields are marked *