Oracle SOA Suite 10g
http://www.oracle.com/technology/products/soa/soasuite/collateral/documentation.html#10.1.3.1.0
Oracle Fusion Middleware 11g Release 1 (11.1.1) Documentation
http://www.oracle.com/technology/documentation/middleware.html
Download the Oracle JDeveloper 11g (11.1.1.2.0) (Build 5536) and run the executable file.
Complete the installation wizard as follows
![clip_image002[5]](http://www.installationwiki.org/images/8/82/9782_04_26.png "clip_image002[5]")
![clip_image002[7]](http://www.installationwiki.org/images/d/dc/9782_04_27.png "clip_image002[7]")
![clip_image002[9]](http://www.installationwiki.org/images/f/f7/9782_04_28.png "clip_image002[9]")
SOA design time in JDeveloper requires a JDeveloper extension called Oracle SOA Composite Editor (11.1.1.2.0). While this is normally updated over the network when using release-level software, you can also perform the update manually if you have the extension file.
We will update it manually using the locally downloaded Oracle SOA Composite Editor (11.1.1.2.0)
JDeveloper periodically prompts you to accept an automatic network update. Since this is released software, you have the option to click on OK to update to a newer version. The SOA extension is about 230 MB and may take some time.
Please follow these steps
Now you can update the SOA Composite Editor extension. These instructions show you how to update the extension over the network.
![clip_image002[11]](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgYPfxfzpUlWiJCM9VLQdtzeu3GOQy4m6efqM59Su3RcSBVWr1f3czWa12F4tMOmC8tqKKQwpkI9JYG7yPX4K7GdfWOF8XtpyTVho90i9exRPxrArWBpCTXcn_-p7AJLvqnooV0Wnvcgtvr/s1600-h/clip_image002%5B11%5D%5B5%5D.jpg "clip_image002[11]")
![clip_image002[13]](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj2XDbGBnMnB4FNdC5d7M_6lRrRpRjCpADWZsQZJv_cdKAP7z7tn11ELKmAlejIfvGxxle0h2sIMoTqhDEhr9bP4tjwuVOP0RrEAmCgXnIQIRbKw_kFW5RsmpT1sIW0aoPF5FG3uYfCFG07/s1600-h/clip_image002%5B13%5D%5B4%5D.jpg "clip_image002[13]")
![clip_image002[15]](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiXoaUFX6ny71id_QhKb0ZoUu1Gr5wR1edaALvZKotoAQIIxhDWAUK4Kd9cUzdexZ3uhAbt6Tx030hBBeaFg6CcfcvCTZXEzbhk_xxZlQxN-pvG8tn0ELPPMl74PYadPUkJb6CtPbNHgM2X/s1600-h/clip_image002%5B15%5D%5B4%5D.jpg "clip_image002[15]")
The above sequence assumes that the installation of the extension is done via a PC Connected to Internet.
The SOA JDeveloper Extension can also be installed locally at Step (3)
The WebLogic Fusion Order Demo application of the Fusion Order Demo was created to demonstrate using Oracle SOA Suite for processing orders from a Web shopping store front. This tutorial focuses on rebuilding the WebLogic Fusion Order Demo application, the SOA sample application of Fusion Order Demo.
Run by a fictitious company called Global Company, the Fusion Order Demo provides two main parts, the Store Front module and the WebLogic Fusion Order Demo application.
The StoreFront modules sells electronic devices through a storefront-type Web application. The StoreFrontUI project uses JavaServer Faces (JSF) as the view technology, and relies on the Oracle ADF Model layer to interact with Oracle Application Development Framework (Oracle ADF) Business Components in the StoreFrontService project.
Once a customer places an order, the WebLogic Fusion Order Demo application processes the order.
This tutorial covers the creation of the WebLogic Fusion Order Demo application. Prior to reading this tutorial, use the Oracle Fusion Middleware Tutorial for Running a Sample Application with Oracle SOA Suite to understand the runtime environment. It explains how you place an order through the StoreFront module, and describes how to monitor the order as it is processed by the WebLogic Fusion Order Demo application through Oracle Enterprise Manager Fusion Middleware Control.
Link to PDF file of this tutorial
This chapter introduces the Fusion Order Demo and the WebLogic Fusion Order Demo application. It provides the tasks for preparing to build the Fusion Order Demo, including installation and configuration.
This set of exercises describes how to create the WebLogic Fusion Order Demo application in Oracle JDeveloper and how to create the PartnerSupplierComposite composite during the creation of the application.
This set of exercises describes how to create the OrderBookingComposite composite of the WebLogic Fusion Order Demo application.
This set of exercises describes how to create the first half of the OrderProcessor BPEL process for the OrderBookingComposite composite.
This set of exercises describes how to create the second half of the OrderProcessor BPEL process for the OrderBookingComposite composite.
This set of exercises describes how to subscribe to a business event using Oracle Mediator. It describes how to create a business event for when an order is created by the StoreFrontService service. It also describes how to create a mediator service component to subscribe to this business event and invoke the OrderProcessor BPEL process through a routing rule to process a new order.
This set of exercises how to use Oracle Mediator to publish and subscribe to a business event for updated orders.
This set of exercises describes how to create a task form for the ApprovalHumanTask human task in the OrderProcessor BPEL process for orders requiring approval. The task form displays the contents of the task to approver jstein.
With the new SOA 11g release a lot of new features are introduced. In the previous releases, we had our sample directory for each product. With this new release, the samples are not in the distribution. Here is a list of links were you can find the example for 11g as well for 10g:
First the release calendar, Patch Set1 and Soa Suite 10.1.3.5 for OC4J and WLS are already out, So we can expect the coming 4, 5 months BPM 11g , OSB 11g and off course at last Patch Set 2 
The new features of PS1, like Soa composer, Spring preview support, invocation api
PS2 will probably bring us composite folders ( domains ) , BPEL 2.0, Spring support in production, Direct binding between OSB and Soa Suite
And maybe Soa Suite 11G release 2 will have a light soa console, Rest / JSON & Debugger support
For more info see the original document on OTN.
You need XE Universal database version 10.2.0.1 or 10g database version 10.2.0.4+ or 11g database version 11.1.0.7+. You cannot use any other database version.
If you are using XE, you must update database parameters if you have never done this for your database installation. You only have to do this once after installing. Make sure processes parameter is >=200.
Sometimes the shutdown/startup command at the end here fails. In that case, simply restart the XE service in the Control Panel/Administrative Tools dialog after setting your parameters.
sqlplus sys/welcome1@XE as sysdba
SQL> show parameter session
SQL> show parameter processes
SQL> alter system reset sessions scope=spfile sid='*';
SQL> alter system set processes=200 scope=spfile;
SQL> shutdown immediate
SQL> startup
SQL> show parameter session
SQL> show parameter processes
cd D:\oracle\wls_090602\Oracle_SOA1\common\binconfig.cmd
Wait for the Admin Server to finish starting up. It takes a few minutes – watch for status Server started in RUNNING mode and SOA Platform is running and accepting requests in log console windowD:\oracle\wls_090602\user_projects\domains\soadev\bin
startWebLogic.cmd
Introduction:
In this post we will see detailed steps to install SOA 11g. The approach used in all 11g FMW components (Including SOA) is very different then 10g. The basic limitation of any 10g component involving infrastructure was that the product itself used to create database and configure the entire infrastructure. This used to put limitation on database port which always used to be 1521.
Here in 11g version, a user has a flexibility to use any port. 11g expects installed database as a pre-reqs and uses that database to create corresponding repository. This way we can have database and listener at any port and provide that information while creating repository.
Also another important feature with all 11g components is that web server used is weblogic and it is kept as another separate component in the form of pre-reqs. So any 11g components requiring web server expects weblogic as pre-reqs. With this brief introduction about 11g FMW components characteristics we will see the installation procedure for SOA 11g.
Installing SOA 11g:
Following are the brief steps for installing SOA 11g
Download Locations:
Download all the software to get started.
1. In the following steps, save all downloaded files to c:\stageSOA. This document assumes that path. If you save them somewhere else then make sure there are no spaces in your path and adjust accordingly when c:\stageSOA is referenced in this document.
2. Unzip the Oracle SOA Suite (11.1.1.2.0) ZIP file to c:\stageSOA.
3. Unzip the Repository Creation Utility (11.1.1.2.0) ZIP file to c:\stageSOA.
Step 1) Install database 11g including configuring TNS and listener or XE Universal Edition
Having your database up and running is the most important pre-requisite for installing SOA Suite.
<Prompt> sqlplus sys/welcome1@XE as sysdba
<SQL> show parameter session
<SQL> show parameter processes
<SQL> alter system reset sessions scope=spfile sid='*';
<SQL> alter system set processes=200 scope=spfile;
<SQL> shutdown immediate
<SQL> startup
<SQL> show parameter session
<SQL> show parameter processes
Step 2) Create repository using Oracle RCU (Repository Creation Utility)
Using RCU, you can create repository for SOA. You dont have to install RCU for using it. RCU comes as a zip file which you need to unzip. Once you unzip you run <RCU_UNZIP>/bin/rcu binary
This will invoke a GUI. On the first page you can select “Create Repository” and click on next.
On the next page RCU will ask for database details in which you want to create the repository. The page will look as shown below
Once you connect to database, on the next page you need to select the repository that you want to create. Here you can select SOA as shown below. Metadata services will get selected automatically. Also you can use any prefix for these schema. All these schema created will have the prefix string prefixed to it. In this case it will prepend DEV before each schema name. Example DEV_MDS, DEV_SOAINFRA etc.
Once you click on next, it will show the summary and will create tablespace if they dont exists. After tablespace creation, click on create and it will create the required repository schemas.
Step 3) Install WLS (weblogic Server) and create a middleware home
Next step is to install WLS server. Carry out the basic installation of WLS. You need to provide a new location for middleware home when asked for as shown below.
Next it will ask for the location of weblogic. Here you can accept the default value as it will be created inside middleware home.
Select all other values as default and install WLS.
Step 4) Install SOA 11g inside middleware home
Installation of SOA home is again very straight. Installation of SOA will just lay down the file system, it wont configure anything. Important input while installing SOA is the middleware home location and location for SOA home
Here Oracle_SOA1 directory will get created inside mwhome directory. Rest of the inputs for SOA installation can be default.
Step 5) Use config.sh or WLST to create and configure SOA domain and managed servers
Once SOA installation is done, the last and the most important step is configuring SOA domain.
You need to navigate to <middleware_home>/Oracle_SOA1/common/bin location and run config.sh script. This script will open a new GUI window. Follow the below screen shots for configuring SOA.
Select all the required template from this screen. If you don’t need BAM installation, you can uncheck the Business Activity Monitoring template. Click on Next.
On the next screen give any domain name (soa_domain) in this case. You can keep the Domain location and Application location as default. These directories will get automatically created when this domain gets created at the end of installation. Click on Next.
On this screen, provide the weblogic password and click on Next.
On this screen you need to provide the database connection details like database name, hostname and database port. You also need to provide all the schema names and password you created using RCU. RCU will create exact 5 schemas required for SOA configuration. You need to provide details of those schemas on this screen. Once you click in next, the configurator will test the connection for all 5 schemas.
Once the connection test goes successful, you can keep rest of the values as default and create the required domain.
After domain creation start the weblogic server using <middleware_home>/user_projects/domain/<domain_name>/bin/startWeblogic.sh script
Also start the managed servers using <middleware_home>/user_projects/domain/<domain_name>/bin/startManagedWeblogic.sh script
You can then login to console using http://<SOA hostname>:<AdminServer port>/console
In the next post, I will provide the WLST details instead of config.sh for performing tasks in step 5) above.
Hope this helps !!
