Last week at Oracle OpenWorld 2009 in San Francisco we announced the availability of a SOA Suite image for developers to deploy on the Amazon EC2 cloud. What does that give you? Access to a fully configured SOA Suite environment (Oracle Service Bus, BPEL PM, Business Activity Monitoring, JDeveloper, Enterprise Manager, etc.), running on a high-end server (8GB RAM, 64-bit Linux). You can now provision new development environment in minutes, without even having to download any Oracle software!

(credits go to Prasen Palvankar for putting that image together)
 

SIGN-UP FOR AMAZON EC2

You need an Amazon AWS account to test SOA Suite on EC2. If you don’t already have one, go to http://aws.amazon.com/console/ and sign up for EC2. Note that you will need a credit card to set up an EC2 account.

CONFIGURE YOUR LOCAL ENVIRONMENT TO WORK WITH EC2

In order to work effectively with servers running in the cloud you will first need to set up a few things on your local machine:

1. Using the AWS Console, create a key pair. This key pair will be used for authentication.
   
   
   
2. Using PuTTYGen, convert the key for use in PuTTY
3. Configure PuTTY to use this key. PuTTY will eventually be used for console access to your server on the cloud.
4. Download NoMachine’s NX Client for Windows. NX will eventually be used for graphical access to your server’s desktop.

PROVISION A SOA SERVER ON AMAZON EC2

When you provision an Oracle SOA Suite server on the Amazon EC2 cloud you will be using two components:

1. An Amazon Machine Instance (AMI) for SOA Suite (id = ami-acb557c5). Note that AMIs are volatile: if you terminate an instance you will lose any data that you might have stored on that instance.
2. An Elastic Block Store (EBS) volume that will be seeded using a snapshot (id = snap-dd980db4) that we provide. This volume will be used to persist your data across sessions and AMI start/stop.

Start the SOA Suite AMI

1. Log in to the AWS console at https://console.aws.amazon.com/ec2/home
2. Click on “AMIs” in the left-hand side navigation bar and choose to view “All Images”  
   
   
   
3. Search for “oracle-soa” or AMI ID ami-acb557c5
4. Select the image and click on Launch
5. Use the following settings to start the instance:
   • number of instances = 1
   • instance type = m1.large (feel free to go for a beefier type of machines but this one is enough)
   • Key pair name = (select the key pair you created earlier) 
     
     
6. Select the keypair previously created. 
7. Click on “Launch”. This will start the base image. Note that this can take up to a minute. Go to the “Instances” page and refresh the page from time to time until you see the status of your instance change to “running”. 
   
   
   
8. Take note of some important information about your instance: the zone it runs in and its public DNS address: 
   
   
   

You should now have a dedicated server running in the cloud.

SSH to your image & Accept license

1. Using the AWS console, navigate to your running instance and find out its public DNS address: 
   
   
   
2. Using PuTTY, SSH to the image as the root user: 
   
   
   
   Note that the initial connection might take close to a minute to establish.
   If you get a security alert, click Yes to accept to add the host key to PuTTY’s registry:
   
   
   
     
   
3. As you log in, a script will prompt you to accept the software license
4. After the license agreement you will be prompted to set new passwords for “root” and “oracle” (the account you will use when working with the SOA Suite). Make sure to keep track of these passwords.
   
   
5. Next you are prompted to press Enter to set up an Oracle SOA 11g volume (it’s an EBS Elastic Block Store) for use with your AMI. This volume is unique to your environment and is the workspace you use to persist data across sessions. There are 2 options here:
1. This is the first time you start a SOA AMI: provide this ID to create a new volume pre-seeded with a snapshot we have created: snap-dd980db4.
2. You already have created an EBS volume for SOA during an earlier session and simply want to reattach it to this AMI: select your volume from the list that the script presents you with.
6. As part of the process you will have to provide your Amazon Access Key ID and your Secret Access Key. Both of these can be found from the AWS > Your Account > Security Credentials page.
   
   
7. If anything goes wrong during that process, you can restart it by typing “add-soa-volume” from the prompt, as root.
   

WORKING WITH SOA SUITE IN THE CLOUD

Now that everything is up and running on Amazon EC2, it is time to start doing something with it!
You have two main options here:

• Run JDeveloper locally, SOA Suite on the cloud.
• Run everything on the cloud – this is the option we will describe below. For this we use NX as remote desktop technology.

CONNECT TO THE GRAPHICAL ENVIRONMENT USING NX AND START YOUR SERVERS

1. To connect to the desktop in the image use NX (download client from http://www.nomachine.com/download.php).
2. Start the NX connection wizard, give a name to your session and enter the public DNS address of your AMI as hostname:
   
   
   
3. Make sure to choose the GNOME desktop and not KDE (which is the default in the NX client) 
   
   
   
4. Log in as “oracle” using the password that you set up earlier through SSH:
   
   
5. Once you log in you should see the following on your desktop:
   
   
   1. Start/stop Oracle DB: double-click on this icon to start the Oracle database
   2. Start/Stop SOA/OSB servers: double-click on this icon to start the SOA Suite
   3. Oracle JDeveloper: double-click on this icon to start JDeveloper on the server
   4. Double-click on this text file to get information about your environment (Middleware home, ports, etc.)

GET TO WORK!

That’s it, you should now be ready to start developing against the Oracle SOA Suite 11g!

USING ELASTICFOX TO STREAMLINE EC2 INTERACTIONS

If you are a regular EC2 user you should definitely look into Elasticfox, a Firefox add-on that really speeds up many of the common tasks that EC2 users will have to perform: shutdown/startup, start SSH, etc.

• Install Elasticfox
• Learn how to configure and use Elasticfox

Downloading the packages

(Before we even get started – have you defragmented your drive lately? If not, why don’t you do this now, before we add more software to your machine! This tends to be a recurring issue in our trainings: people come with heavily fragmented drives and this tremendously slows down installers. Right-click on your drive in “My Computer” > Properties > Tools > Defragment Now)

First, you will need to have an OTN account to download packages – you can sign up here; it’s free. Then head here http://www.oracle.com/technology/products/soa/soasuite/index.html and click on the “Free Download” link in the top right corner.

Here are the packages you will need (under 3.5GB for all the installation packages):

1. Oracle Database 10g Express Edition: the SOA Suite requires a database for persistence. While you can go for the full Enterprise version, the Express edition is a fine choice for a development environment.
2. WebLogic Server: this will provide the JEE environment (as well as the JMS provider) required to run the SOA Suite (a JEE application).
   Choose the “Oracle WebLogic Server 11gR1 (10.3.1) - Package Installer” (or the corresponding international version). The name of the package is wls1031_win32.exe, 570MB in size.
3. Repository Creation Utility: this will lay the database schemas that the SOA Suite uses for various persistence tasks (audit trails, etc,). The name of the package is ofm_rcu_win32_11.1.1.1.0_disk1_1of1.zip and it is 282MB in size.
4. SOA Suite: this is the actual JEE application that contains the SOA engines and that will be deployed on WebLogic.
   Choose the “SOA Suite, Generic” package, its name is ofm_soa_generic_11.1.1.1.0_disk1_1of1.zip and it is 1.5GB in size.
5. JDeveloper: this is the IDE that you will use to design and deploy your SOA composites.
   Choose the “Studio Edition”. The name of the package is jdevstudio11111install.exe and is 934MB in size.

Installation steps

Install a Database

Install the XE database if you don’t already have one. We will not detail this here.

Run the Repository Creation Utility (RCU)

Run the Repository Creation Utility (RCU) to create the database schemas:

1. unzip the package you downloaded earlier to C:\ORACLE\11gR1 (for instance).
   Execute C:\ORACLE\11gR1\rcuHome\BIN\rcu.bat.
   Here is the main screen that requires input:
   
   
2. Ignore the warning message (as Heidi mentioned earlier, this simply indicates that Oracle XE is not certified for production use):
   
   
3. Check “SOA Infrastructure” and enter a prefix:
   
   
4. Accept everything after that and create the tables.

Install WebLogic

1. Execute wls1031_win32.exe
2. Choose a location for your install – I picked C:\ORACLE\11gR1\MW_HOME
   
   
3. Enter your email if you wish to receive security updates (something you should definitely do if you are an administrator)
4. Choose a typical install
5. Accept all other defaults

(no need to run QuickStart since it is really geared towards WebLogic users more than SOA)

Install SOA Suite

1. Extract the zip file that you downloaded for SOA. I extracted mine to C:\DOWNLOADS\ORACLE\11gR1\soa.
2. Execute C:\DOWNLOADS\ORACLE\11gR1\soa\Disk1\setup.exe
3. You might be prompted for a JDK, if so simply enter the path to the one that was installed with WLS: C:\ORACLE\11gR1\MW_HOME\jdk160_11 in my case.
4. Choose a name for your home directory (for me it will be DMD_SOA1) or accept the default of Oracle_SOA1:
   
   

Configure SOA Suite

1. Go to your SOA home directory, common/bin (for me it will be C:\ORACLE\11gR1\MW_HOME\DMD_SOA1\common\bin) and execute config.cmd
2. Create a new WebLogic domain
3. I would recommend you put both Oracle SOA Suite and Oracle Enterprise Manager in the same domain.
   
   
4. Choose a name for your domain (for me it will be dmd_soa_domain1)
5. Choose a JDK or accept the default (Sun SDK for development environments)
6. The next screen “Configure JDBC Component Schema” is probably the one that requires the most attention in the whole install process (definitely need to improve this step in subsequent releases!):
   1. If you have picked the default prefix of “DEV_” during the RCU install then check all schemas and then update:
      • service (XE is often the default)
      • hostname (localhost for us)
      • port (1521 is the XE default)
   2. If you have not picked the default prefix, then in addition to the above you will also need to cycle through each schema to update the prefix: Check one schema. Make your change. Uncheck the schema and check the next one. etc.
7. Ensure that all the tests on the next screen are successful
8. Don’t select anything on the “Select Optional Configuration” screen
9. Note down the URL for the admin server

Start the Servers

At this point you should be ready to start the servers!

• admin server: C:\ORACLE\11gR1\MW_HOME\user_projects\domains\dmd_soa_domain1\startWebLogic.cmd
• managed SOA server: C:\ORACLE\11gR1\MW_HOME\user_projects\domains\dmd_soa_domain1\bin\startManagedWebLogic.cmd soa_server1

Obviously you should create some shortcuts to easily start these in the future.

Test the Consoles

1. Ensure you can reach the WebLogic Administration Console: http://localhost:7001/console (if you have installed using default ports).
2. Ensure you can reach Enterprise Manager: http://localhost:7001/em (if you have installed using default ports).
3. In Enterprise Manager, ensure that you see the “SOA” folder in the left-hand side navigation tree:
   
   
4. That’s it for the runtime part! Let’s now install JDeveloper so that we can start our development and deploy a few composites to our brand new shiny servers.

Install JDeveloper

1. Execute jdevstudio11111install.exe
2. Create a new middleware home for JDeveloper (this is to ensure that JDeveloper doesn’t overwrite the container that we have already installed in the previous steps). For instance C:\ORACLE\11gR1\JDev.

Install the SOA Extension for JDeveloper

1. Start JDeveloper
2. Execute C:\ORACLE\11gR1\JDev\jdeveloper\jdev\bin\jdev.exe (if you want the console window) or C:\ORACLE\11gR1\JDev\jdeveloper\jdeveloper.exe (if you don’t care about the console).
3. “Check for Updates”:
   
   
4. Ensure the “Oracle Fusion Middleware Products” and “Official Oracle Extensions and Updates” centers are checked and click “Next”
5. Check the “Oracle SOA Composite Editor” and then hit “Next”
   
   
6. You will be prompted for your OTN credentials
7. At this point JDev will start downloading the extension and restart itself to complete the installation

That’s it. You have just installed a very complete SOA development environment, including everything from the core JEE container, a messaging provider, a BPEL engine, a human workflow and associated worklist, a rules engine, a mediation component, various adapters, a security policy manager, monitoring and management environment and an IDE. Next we will look at a few things we can do with all this!