In June an AMI (Amazon Machine Image to use on the EC2 platform) for SOA Suite and BPM 11g R1 PS2 became available. In the last days it was announced that a VirtualBox Appliance is available. The timing, just before Oracle OpenWorld 2010 cannot be a coincidence…
This appliance contains a fully configured, ready-to-use SOA/BPM 11g R1 installation. It contains the following software:
If you’re not using elastic IP you have to configure WebLogic / SOA Suite running on EC2 to listen to external calls. A good example of such an external call would be: you trying to deploy a composite from the JDeveloper installation on your local PC. If you don’t configure this you’ll run into:
Error sending deployment request to server
java.net.ConnectException: Connection timed out: connect
To configure the External Listen Address log into the WebLogic Console.
Select Environment – Server
Click the server (AdminServer)
Click Advanced to show the advanced settings
Enter the External Listen Address
It can be helpful to also edit your host file to save you from retyping the quite long EC2 host name over and over again.
Besides the reference in the documentation library to the Install Guide and the Quick Install Guide, there are several blogs describing the installation of 126.96.36.199. Which is actually a patch on 188.8.131.52:
The one on Oracle blogs by James Taylor includes OSB 184.108.40.206
SOA Suite on Amazon EC2
This week it was announced that BPM 11g R1 is available as an Amazon Machine Image (AMI). This AMI includes SOA Suite 11gR1 Patchset 2 and JDeveloper with the SOA and BPM extension. In AWS filter on 64-bit and put soa-bpm in the search box. This should enable you to find oracle-soa-bpm-11gr1-ps2-4.1-pub. Some of the tips I posted on x SOA Suite in the cloud could be useful here as well.
One of the things on my To Do list was to move my local SOA Suite 11g R1 to The Cloud. It seemed a good idea to save my laptop some resources (to spare some for JDeveloper) with only a limited investment. Besides that it can be a good way to demo applications, and work together with my colleagues on these demos.
During the last months I noticed that there are several good blogpost on the subject. In this post I’ll show you the ones I used and provide some additions to them.
AMIs are per region: The Amazon Machine Instance (AMI) for SOA Suite (id = ami-acb557c5) is only available in the US East (Northern Virginia) Region.
Don’t bother to setup the Elastic Block Store (EBS) Volume. It is scripted in the latest version of the AMI, as described in step 5 of “SSH to your image and accept license”. The EBS Volume is seeded using a snapshot (id = snap-dd980db4) that is provided. This volume will be used to persist your data across sessions and AMI start/stop.
When launching the image (during the Configure Firewall step) set the SecurityGroup to accept HTTP traffic on port 7001 in case you want to use the SOA Suite from outside the Image.