Installation of SOA Suite component ofOracle Fusion MiddleWare (FMW)11g R1 (11.1.1.1). OracleFusion Middleware 11g components (SOA, Webcenter, Identity Management.)usesOracle WebLogic Server 11g R1(10.3.1)as underlying Application Server. If you are new to WebLogic Server then my recommendation is toread more about Domain, Administration and Managed Server in WebLogic here

.

Overview of Fusion Middleware 11g R1 SOAInstallation

Installation of Oracle SOA 11g R1 is five step process where step 1 & 2 aresameformost ofFusion Middleware 11g products (WebCenter, Identity Management..)

1. Install Oracle Database (repository for SOA Suite) and load Oracle SOA suite repository using rcu (Repository Creation Utility).2. Install Oracle WebLogic Server 11gR1 (10.3.1)3. Install Oracle SOA Suite 11g R1 (11.1.1)4. Configure SOA Suite (soa & bam)by creating domain - Administration andManaged Server in WebLogic5. Start Administration & Managed Server (soa_server1, bam_server1) for SOA 11g R1

.

.

.

.

.

1. Install & Configure repository for SOA Suite1.1 Install Oracle Database1.1.1 Install 10.2.0.1 or 11.1.0.6 DatabaseFollow 11g Database Installation Guide from hereDownload 11g R1(11.1.0.6) or 10gR2 (10.2.0.2)Database from here1.1.2 Upgrade Database to minimum 10.2.0.4 or 11.1.07 versionApply 11.1.0.7patchset (available via patch 6890831)on top of 11.1.0.6orApply 10.2.0.4 patchset (available via patch 6810189) on top of 10.2.0.1

1.2. Load Oracle SOA suite repository using rcu (Repository Creation Utility)

For more informationon RCU click here

.

.For Oracles Documentation on RCU click hereDownload RCU from here

.

.

2. Install Oracle WebLogic Server 11gR1 (10.3.1)

In this step you use WebLogic 11g R1 (10.3.1) software to install Oracle WebLogic. This step will create Fusion Middleware top level directory (aka FMW_HOME) lets assume this directory as /oracle/apps/fusion/midFMW_HOME=/oracle/apps/fusion/mid

under FMW_HOME WebLogic software will create directory wlserver_10.3(aka WLS_HOME)WLS_HOME=/oracle/apps/fusion/mid/wlserver_10.3

.

.

3. Install Oracle SOA Suite 11g R1 (11.1.1)

Next step after installation of WebLogic Server is to install Oracle 11g SOA Suite, this step will install SOA software under directory Oracle_SOA1 inside FMW_HOME(aka SOA_ORACLE_HOME)SOA_ORACLE_HOME=/oracle/apps/fusion/mid/Oracle_SOA1

.

more information on installing SOA Suitehere

You can download SOA suite 11g R1 software from here

.

.

4. Configure SOA Suite installed in step3

Next step is to configure SOA suite on WebLogic Server . This is similar to creating a domain with one Administration Server and two Managed Server (soa_server1, bam_server1)in weblogic.

This step will create1. One domain under directory $FMW_HOME/ user_projects/ domain and2. Configure one AdministrationServer and two Managed Server (by default)* It is possible to create more managed server using this step

- To configure SOA stuite, start config.sh from SOA_ORACLE_HOME/common/bin directory

/oracle/apps/fusion/mid/Oracle_SOA1/common/bin/config.sh

Select - Create a new WebLogic domain

Select - Domain Source

.

SpecifyDomain Name and Location

.

After this step you will see directory structure like below

.more information on how to configure SOA Suite here

.

.

5. Start WebLogic ServerSOA suiteDomain (Managed & Administration Server) :

Finally start domain (Administration Server and two Managed Server)

5.1 Start Administration Server $FMW_HOME/user_projects/domains//bin/startWebLogic.sh

5.2 Start Managed Servers : soa_server1, bam_server1

cd $FMW_HOME/ user_projects/ domains/ / bin/5.2.1 startManagedWebLogic.sh bam_server15.2.2 startManagedWebLogic.sh soa_server1

when prompted for password enter weblogic/

.

.

.

Finally access Oracle Fusion Middleware 11g SOA Suite (default web port is 7001)

.

a)Fusion Middleware 11g

http://servername.domainname:7001

.

b)Fusion Middleware 11gEnterprise Manager

http://servername.domainname:7001/em

.

c)Fusion Middleware 11gSOA Suite Administration Console

http://servername.domainname:7001/console

Connect jDeveloper to SOA Servers

|Print|

E-mail

Written by Anil Passi

Monday, 08 January 2007

In this article, I will show you how to connect your jDeveloper to the SOA Servers. This includes connecting to Application Server, Oracle Lite Database and BPEL PM. I hope you have read the article on SOA Install Validation at link I have two installations of jDeveloper 10.1.3.1.0??First:- jDeveloper 10g that got Installed standalone from Technet WebsiteSecond:- jDeveloper 10g that got installed by Oracle SOA Suite Companion CD.I decided to use standalone install. Why So? Because in most installations BPEL server will be on a remote machine, and developers would end up installing just the jDeveloper on their PC.[with their BPEL server running on the network machine].Establish Connection to Oracle Lite Database from jDeveloper 10gUsing jDeveloper, we need to ensure that you can establish connection to OracleLite database.Follow the instructions in below link, and ensure that you are able to connect to Oracle Lite Database used by BPEL.http://download-uk.oracle.com/docs/cd/B31017_01/integrate.1013/b28212/buildendtoend.htm#BEIDHFJGFollow the above instructions until you get SUCCESS connecting to the database. Effectively we have successfully managed to validate a connection with OracleLite database that comes pre-installed with SOA Suite.Establish Connection to Application Server from jDeveloperStep 1. Right click on Application Server and select New ConnectionNote that I am using AnilAppServerConn with Type Standalone OC4J 10.1.3Step 2. Click next and type Username/Password oc4jadmin/xx23xx23I checked the Deploy Password checkbox.Step 3. Host Name localhost, with RMI Port 12401Note: In the previous training article, we had noted down this port number.Please refer to http://oracle.anilpassi.com/validate-your-soa-suite-install-on-pc.html in case you wish to know your RMI Port Number. Step 4. Click on Next, and Test ConnectionEstablish Connection to BPEL PM Server from jDeveloperStep 1. Right click on Integration Server and select New ConnectionStep 2. I gave the name as AnilBPELServerConn and clicked on Next.Step 3. You will notice that the Application Server Connection details have been defaulted from the previous step.Step4. Click next again and test your connection, it takes few seconds and shows progress %. The end result will be a response of OK as below.

Introduction to One-Way Messages

In a one-way message, or fire and forget, the client sends a message to the service (d1 in Figure 6-1), and the service does not need to reply. The client sending the message does not wait for a response, but continues executing immediately. Example 6-1 shows the portType and operation part of the BPEL process WSDL file for this environment.

Example 6-1 One-Way WSDL File

. . . . . .

Figure 6-1 provides an overview.

Figure 6-1 One-Way Message

Description of "Figure 6-1 One-Way Message"

BPEL Process Service Component as the Client

As the client, the BPEL process service component needs a valid partner link and an invoke activity with the target service and the message. As with all partner activities, the Web Services Description Language (WSDL) file defines the interaction.

BPEL Process Service Component as the Service

To accept a message from the client, the BPEL process service component needs a receive activity.

Introduction to Synchronous Interactions

In a synchronous interaction, a client sends a request to a service (d1 in Figure 6-2), and receives an immediate reply (d2 in Figure 6-2). A BPEL process service component can be at either end of this interaction, and must be coded based on its role as either the client or the service. For example, a user requests a subscription to an online newspaper and immediately receives email confirmation that their request has been accepted. Example 6-2 shows the portType and operation part of the BPEL process WSDL file for this environment.

Example 6-2 Synchronous WSDL File

. . .

Figure 6-2 provides an overview.

Figure 6-2 Synchronous Interaction

Description of "Figure 6-2 Synchronous Interaction"

BPEL Process Service Component as the Client

When the BPEL process service component is on the client side of a synchronous transaction, it needs an invoke activity. The port on the client side both sends the request and receives the reply. As with all partner activities, the WSDL file defines the interaction.

BPEL Process Service Component as the Service

When the BPEL process service component is on the service side of a synchronous transaction, it needs a receive activity to accept the incoming request, and a reply activity to return either the requested information or an error message (a fault; f1 in Figure 6-2) defined in the WSDL.

1)From the client side Will call the webservice provider and will wait for the answer/resume

2)From the webservice provider side request and response will be travelled from same port type same operation.

3)Port type Operation contains input element and also output element.

4) We will have a time limit for sync ws request processing if it exceeds that time client will get the timeout fault.

For more information about synchronous interactions, see Chapter 8, "Invoking a Synchronous Web Service from a BPEL Process."

Introduction to Asynchronous Interactions

In an asynchronous interaction, a client sends a request to a service and waits until the service replies. Example 6-3 shows the portType and operation part of the BPEL process WSDL file for this environment.

Example 6-3 Asynchronous WSDL File

. . . . . .

Figure 6-3 provides an overview.

Figure 6-3 Asynchronous Interaction

Description of "Figure 6-3 Asynchronous Interaction"

BPEL Process Service Component as the Client

When the BPEL process service component is on the client side of an asynchronous transaction, it needs an invoke activity to send the request and a receive activity to receive the reply. As with all partner activities, the WSDL file defines the interaction.

BPEL Process Service Component as the Service

As with a synchronous transaction, when the BPEL process service component is on the service side of an asynchronous transaction, it needs a receive activity to accept the incoming request and an invoke activity to return either the requested information or a fault. Note the difference between this and responding from a synchronous BPEL process: a synchronous BPEL process uses a reply activity to respond to the client and an asynchronous service uses an invoke activity.

1) Client wont wait after the request.

2) For the request different port and response different port type operation.

3)WSDL contains 2 port types and each operation we find only input element

4)No time limit.

Differences between 10g and 11 g

Basically all the SOA components like BPEL, ESB (Called Mediator in 11g), & OWSM are brought into one place in 11g using SCA composite concept.The major difference between 10g & 11g would be the app server container. 10g by default runs on OC4J while 11g runs on Weblogic Server. It is pretty simple to learn 11g SOA if you know 10g already. You will also need a basic understanding of Weblogic servers/domains.

SOA 10g : BPEL ---Webservice -ESB

Composite

SOA 11g : BPEL SCA(SDO) Mediator

Introduction to Oracle SOA Suite

The components of Oracle SOA Suite benefit from common capabilities, including a single deployment, management, and tooling model, end-to-end security, and unified metadata management. Oracle SOA Suite is unique in that it provides the following set of integrated capabilities:

Messaging

Service discovery

Orchestration

Web services management and security

Business rules

Events framework

Business activity monitoring

These capabilities help address the fragmented IT landscape and addresses the difficulties associated with silos of IT infrastructure and applications. It enables greater flexibility through:

Interoperability: SOA, and the industry standards underpinning it, enable existing siloed applications to interoperate seamlessly and in an easier-to-maintain manner than any traditional EAI solution.

Increased reuse: Once legacy systems and applications are service enabled, these services can be reused, which results in reduced ongoing development costs and results in reduced time to market. Further, business processes built as an orchestration of services can also be exposed as services, further increasing reuse.

More agile business processes: SOA reduces the gap between the business process model and implementation. This enables changes to business processes already implemented as orchestrations of services to be easily captured and implemented.

Improved visibility: SOA can give improved business visibility by enabling business capabilities exposed as services, and the status of in-flight business processes automated with business activity monitoring, to be rapidly integrated into service-enabled enterprise portals, aiding business decision-making.

Reduced maintenance costs: SOA development encourages duplicated overlapping business capabilities (services) that span multiple applications and systems to be consolidated into a small number of shared services. SOA development enables elimination of redundant services and reduces the cost of maintaining systems by providing a single point of change for application logic. Further, SOA gives IT the means to gradually phase out legacy systems and applications, while minimizing disruption to the applications that are built on or are integrated with them using SOA principles. This process frees up funds for new projects.

Compliance and governance: By realizing better and more standardized operational procedures, SOA provides the basis for a comprehensive security solution, and enables better visibility into business operations and exception conditions.

Oracle SOA Suite Standards

Oracle SOA Suite puts a strong emphasis on standards and interoperability. Among the standards it leverages are:

The Service Component Architecture (SCA) assembly model abstracts the implementation and allows assembly of components, with little implementation details. SCA enables you to represent business logic as reusable service components that can be easily integrated into any SCA-compliant application. The resulting application is known as an SOA composite application. The specification for the SCA standard is maintained by the Organization for the Advancement of Structured Information Standards (OASIS).

Service Data Objects (SDO) provide a data programming architecture. It provides a standardized view on data, and provides efficient transportation, as well as change capture, in form of a change summary. More specifically, it collects a data graph of related business objects, called DataObjects. This graph tracks the schema that describes the DataObjects. Knowledge is not required about how to access a particular back-end data source to use SDO in an SOA composite application. Consequently, you can use static or dynamic programming styles and obtain connected and disconnected access.

Business Process Execution Language (BPEL) provides enterprises with an industry standard for business process orchestration and execution. Using BPEL, you design a business process that integrates a series of discrete services into an end-to-end process flow. This integration reduces process cost and complexity.

XSL Transformations (XSLT) processes XML documents and transforms document data from one XML schema to another.

Java Connector Architecture (JCA) provides a Java technology solution to the problem of connectivity between the many application servers in Enterprise Information Systems (EIS).

Java Messaging Service (JMS) provides a messaging standard that allows application components based on the Java Enterprise Edition (JEE) to access business logic distributed among heterogeneous systems.

Web Service Description Language (WSDL) file provides a standardized view on the capabilities of a service. Bindings provide the entry points into the composite at runtime.

SOAP over HTTP (SOAP) provides the default network protocol for message delivery.

Introduction to Oracle SOA Suite Components

Oracle SOA Suite provides a comprehensive suite of components for developing, securing, and monitoring service-oriented architecture (SOA).

Service components (BPEL process, business rule, human task, and mediator) are the building blocks that you use to construct an SOA composite application. The Service Infrastructure provides the internal message transport infrastructure capabilities for connecting service components and enabling data flow. Service engines for the components process the message information received from the Service Infrastructure. See SOA Composite Application Architecture for more information about service components.

Oracle Business Activity Monitoring consumes data transported over the Service Infrastructure, providing powerful business insight capabilities.

The following components comprise an Oracle SOA Suite installation:

Service Infrastructure

Oracle Mediator

Oracle Adapters

Business Events and Events Delivery Network

Oracle Metadata Repository

Oracle Business Rules

Oracle WSM Policy Manager

Oracle BPEL Process Manager

Human Workflow

Oracle Business Activity Monitoring

Oracle User Messaging Service

Oracle B2B

Oracle JDeveloper

Oracle Enterprise Manager