4 Sep 2014

FMW 12c on the Cloud - Part 2: Installation and Configuration

This is the part 2 of the tutorial showing how to install and configure Oracle Fusion Middleware on the Cloud. To learn how to setup your environment check the Part 1.

Installing Fusion Middleware

Now that we have the environment ready, next step is to download the binaries from the Oracle. You will need the following packages from the Oracle Fusion Middleware 12c Media Pack:
  • Oracle Fusion Middleware 12c Infrastructure 
  • Oracle Fusion Middleware 12c SOA Suite and Business Process Management 

Both are jar files that can be run with:
$ java -jar <jar file>

Just follow the installer instructions, it's pretty straight forward. From this point on I'll refer to the Infrastructure installation folder as $ORACLE_HOME.

After they are both installed, next step is installing the database, in this tutorial I've used the Oracle eXpress Edition.

Database Installation

Note: Before installing the database, if you don't have enough swap space for the Database install, follow this guide to add some.

  1. Download it from the Oracle Website here
  2. Uncompress the file 
  3. Run the install: 
    • $ sudo rpm -i oracle-xe-11.2.0-1.0.x86_64.rpm 
  4. Run the configure script as root: 
    • $ sudo /etc/init.d/oracle-xe configure 

Using the Repository Creation Utility

Next, create the Database schemas using the Repository Creation Utility (RCU), installed during the FMW Infrastructure install:
  1. Run the RCU, which is located at $ORACLE_HOME/oracle_common/bin/rcu
  2. If you accepted all defaults during the database installation, your database details should be as follows:
    • Host Name: localhost
    • Port: 1521
    • Service Name: XE
    • Username: SYS
    • Password: <The one you defined in the DB install>
  3. Select SOA Suite in the Components
  4. Define the schema passwords
  5. Accept all defaults

Creating and Configuring the Weblogic Domain

Now, let's create the Weblogic domain:
  1. Run the domain creation utility $ORACLE_HOME/wlserver/common/bin/config.sh
  2. Select the desired domain templates. I'll be using SOA and BPM
  3. Input the database details created in the RCU config
  4. Accept all defaults
Now start the domain by running:
$ORACLE_HOME/user_projects/domains/<domain name>/startWebLogic.s

And the domain node manager (yes, now the node manager is domain based) by running:
$ORACLE_HOME/user_projects/domains/<domain name>/startNodeManager.sh

To configure the Weblogic Server:
  1. Access the Weblogic Console at http://<Public IP of your instance>:7001/console
  2. Go to Environment > Machines and create a new Unix Machine
  3. Add both the AdminServer and soa_server1 to the new Machine
  4. Finally, go to Environment > Server > Tab Control and start the soa_server1 server.

If everything went well, you should see your managed server in the FMW Enterprise Manager, available at http://<Public IP of your instance>:7001/em


  1. Luigi,
    I wish I had seen this earlier. I've basically gone through everything you've done here. My question is have you figured out how to expand your domain with a second ami running another managed server. I can create new servers on the 2nd ami, and enroll new them with the admin console on the first ami, but getting all the required datasources, filestores, app deployments, etc targeted to the dynamic cluster so that the new managed servers can work as the first soa_server1 is leaving me confused. Have you done this?

    1. Hi Michael,
      If I understand correctly you're trying to add a managed server to an existing domain and form a cluster with an existing managed server, right?
      You'll need to add the new Machine in the Weblogic Console (Environment > Machines), add the new server (Environment > Machines), create a cluster (in Environment > Clusters), add both your existing and your new managed servers to the cluster. Also, make sure the Node Manager in the new Machine is reacheable (Environment > Machines > Click the Machine > Monitoring).
      Now, for the configuration to be inherited by your new managed server you need either the target of each configuration to be set to the cluster (and hence by being part of the cluster the managed server would get it), or manually add the new managed server as a target for each Data Source, Queue, etc.