Oracle SOA ESB: Quick start

The overall process and tasks required for designing the enterprise service bus are outlined in the following list. Links to step-by-step instructions are specified for each task:

1. Start the ESB Server and open Oracle JDeveloper
   The key Oracle Enterprise Service Bus design components are the ESB Server, Oracle JDeveloper, and the database that serves as the ESB Metadata Server. For information about starting ESB components, see "Starting, Stopping, and Accessing Oracle Enterprise Service Bus Components".
   
2. Create the necessary server and database connections.
   See "Creating and Testing Connections".
   
3. Create the Oracle JDeveloper applications and projects
   See "Creating Applications and ESB Projects".
   
4. Create ESB systems and, optionally, service groups.
   See "Creating ESB Systems and Service Groups"
   
5. Add or import into an ESB project.
   See "Adding Project Content" and "Importing Files into a Project".
   
6. Create the inbound and outbound services, or invoke external services.
   See Chapter 4, "Creating Inbound and Outbound Services".
   
7. Create routing services and configure the routing rules to:
   
   • Apply conditional expressions to the message instance payload
     
   • Transform the structure of the message payload
     
   • Specify where a response in a request/response scenario be sent
     
   • Specify where faulted messages be sent
   See Chapter 5, "Creating Routing Services and Routing Rules".
   
8. Register services with the ESB repository.
   See "Registering ESB Projects and Services with the ESB Server".
   
9. Sync services with the ESB Server.
   See "Syncing Services From ESB Server".

If you no longer need a service, you can remove it. See "Deleting ESB Projects".

The text above is an extract from
Oracle® Enterprise Service Bus Developer's Guide
10g (10.1.3.3.0)Part Number E10295-01
http://docs.oracle.com/cd/E11036_01/doc.1013/e10295/esb_jdev.htm

I find its a pretty short but handy overview. Hope it helps.

ANT Deployment in SOA 11g

Path setup for ANT:

I have set the PATH and JAVA_HOME variable as follows. By executing the following Set PATH command, I have just added the ant executable folder path to the existing PATH variable. echo %PATH% command shows the PATH variable after adding the ANT folder.

org.apache.ant_1.7.1 folder is found in the Jdeveloper installation directory. JDev11gR1PS3 is my JDeveloper home directory.
JAVA_HOME directory is my SOA Suite installation jdk directory. SOASuite11gPS3 is my SOA Suite installation home directory.

Package the Deployment (Generate SAR/Jar file for SOA composite)

C:\Middleware\JDev11gR1PS3\jdeveloper\bin folder has the required ant scripts

Create SOA 11g Partition using ANT

The ant command is as follows:

ant -f ant-sca-mgmt.xml createPartition -Dhost=localhost -Dport=7001 -Duser=weblogic -Dpassword=welcome1 -Dpartition=my_ant_partition

ANT_HOME and PATH system variable was not defined in my case. So for the sake of simplicity, I executed the ant commant from the ant home location itself and mentioned the absolute path of ant-sca-mgmt.xml script (C:\Middleware\SOASuite11gPS3\Oracle_SOA1\bin\ant-sca-mgmt.xml).

The standard location of the ant scripts are
<ORACL_MIDDLEWARE_HOME>/bin

Middleware home in my case is C:\Middleware\SOASuite11gPS3\Oracle_SOA1\

Fault Recovery Actions in SOA 11g Enterprise Manager

Action	Description	Action is Available for...
Retry	Retries the instance directly. An example of a scenario in which to use this recovery action is when the fault occurred because the service provider was not reachable due to a network error. The network error is now resolved.	BPEL process and Oracle Mediator
Abort	Terminates the entire instance.	BPEL process and Oracle Mediator
Replay	Replays the entire scope again in which the fault occurred.	BPEL process
Rethrow	Rethrows the current fault. BPEL fault handlers (catch branches) are used to handle the fault. By default, all exceptions are caught by the fault management framework unless an explicit rethrow fault policy is provided.	BPEL process
Continue	Ignores the fault and continues processing (marks the faulted activity as a success).	BPEL process

Source: http://docs.oracle.com/cd/E25054_01/admin.1111/e10226/soacompapp_mang.htm#BABGHCDI

MDS in SOA 11g

I found this article very useful to place fautl policy files in MDS. Worked just fine for me...

http://www.orafmwschool.com/soa-11g-mds/

Adding Jars/Classes to Classpath in SOA Server 11g

Deep Thoughts...: Adding Jars/Classes to Classpath in SOA Server 11g...: Custom java code requires classes/jars to be added to the classpath of the server. Here are few things to be considered: SOA Specific Clas...