Soa installation

1. Installation of SOA Suite component of Oracle Fusion MiddleWare (FMW) 11g R1
(11.1.1.1).
Oracle Fusion Middleware 11g components (SOA, Webcenter, Identity
Management….) uses Oracle WebLogic Server 11g R1 (10.3.1) as underlying Application
Server. If you are new to WebLogic Server then my recommendation is to read more about
Domain, Administration and Managed Server in WebLogic here
.
Overview of Fusion Middleware 11g R1 SOA Installation
Installation of Oracle SOA 11g R1 is five step process where step1 & 2 are same for most
of Fusion 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 and Managed Server
in WebLogic
5. Start Administration & Managed Server (soa_server1, bam_server1) for SOA 11g R1
.
.
.

2. .
.
1. Install & Configure repository for SOA Suite
1.1 Install Oracle Database
1.1.1 Install 10.2.0.1 or 11.1.0.6 Database
Follow 11g Database Installation Guide from here
Download 11g R1 (11.1.0.6) or 10gR2 (10.2.0.2) Database from here
1.1.2 Upgrade Database to minimum 10.2.0.4 or 11.1.07 version
Apply 11.1.0.7 patchset (available via patch 6890831) on top of 11.1.0.6
or
Apply 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 information on RCU click here
.
.
For Oracle’s Documentation on RCU click here
Download RCU from here
.
.
2. Install Oracle WebLogic Server 11gR1 (10.3.1)

3. 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/mid
FMW_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

4. .
more information on installing SOA Suite here
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 create
1. One domain under directory $FMW_HOME/ user_projects/ domain and
2. Configure one Administration Server 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

5. .
Specify Domain Name and Location
.
After this step you will see directory structure like below

6. .
more information on how to configure SOA Suite here
.
.
5. Start WebLogic Server SOA suite Domain (Managed & Administration Server) :
Finally start domain (Administration Server and two Managed Server)
5.1 Start Administration Server
$FMW_HOME/user_projects/domains/<soa_domain>/bin/startWebLogic.sh
5.2 Start Managed Servers : soa_server1, bam_server1
cd $FMW_HOME/ user_projects/ domains/ <soa_domain>/ bin/
5.2.1 startManagedWebLogic.sh bam_server1
5.2.2 startManagedWebLogic.sh soa_server1
when prompted for password enter weblogic/<password>
.
.
.

7. Finally access Oracle Fusion Middleware 11g SOA Suite (default web port is 7001)
.
a) Fusion Middleware 11g
http://servername.domainname:7001
.
b) Fusion Middleware 11g Enterprise Manager
http://servername.domainname:7001/em

8. .
c) Fusion Middleware 11g SOA Suite Administration Console
http://servername.domainname:7001/console
ConnectjDeveloper
to SOA Servers
| Print|
E-
mail
WrittenbyAnil Passi
Monday,08 January2007
In thisarticle,Iwill showyouhowto connectyourjDevelopertothe SOA Servers.This
includes connectingtoApplicationServer,Oracle Lite Database andBPELPM. I hope youhave read the
article onSOA Install Validation atlink
I have two installationsof jDeveloper10.1.3.1.0??
First:- jDeveloper10g that got InstalledstandalonefromTechnetWebsite

9. Second:- jDeveloper10gthat got installedbyOracle SOA Suite CompanionCD.
I decidedtouse standalone install.
WhySo? Because inmost installationsBPELserverwill be onaremote machine,anddeveloperswould
endup installingjustthe jDeveloperontheirPC.
[withtheirBPELserverrunningonthe networkmachine].
EstablishConnectionto Oracle Lite Database from jDeveloper10g
UsingjDeveloper,we needtoensure thatyoucan establishconnectiontoOracleLitedatabase.
Followthe instructionsinbelowlink,andensure thatyouare able to connectto Oracle Lite Database
usedbyBPEL.
http://download-
uk.oracle.com/docs/cd/B31017_01/integrate.1013/b28212/buildendtoend.htm#BEIDHFJG
Followthe above instructionsuntil yougetSUCCESSconnectingtothe database.Effectivelywe have
successfullymanagedtovalidate aconnectionwithOracleLite database thatcomespre-installedwith
SOA Suite.
EstablishConnectionto ApplicationServer from jDeveloper
Step 1. Rightclickon ApplicationServerandselectNew Connection
Note that I am usingAnilAppServerConnwithType StandaloneOC4J10.1.3
Step 2. Clicknextandtype Username/Passwordoc4jadmin/xx23xx23
I checkedthe DeployPasswordcheckbox.
Step 3. Host Name localhost,withRMIPort 12401
Note:Inthe previoustrainingarticle,we hadnoteddownthisportnumber.
Please referto http://oracle.anilpassi.com/validate-your-soa-suite-install-on-pc.html incase youwishto
knowyourRMI Port Number.

10. Step 4. Clickon Next,andTestConnection
EstablishConnectionto BPEL PM Server from jDeveloper
Step 1. Rightclickon IntegrationServerandselectNew Connection
Step 2. I gave the name as AnilBPELServerConnandclickedonNext.
Step 3. You will notice thatthe ApplicationServerConnectiondetailshave beendefaultedfromthe
previousstep.
Step4. Clicknextagainandtestyour connection,ittakesfew secondsandshowsprogress%.
The end resultwill be aresponse of OKas below.
Introduction to One-Way Messages

11. 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
. . .
<wsdl:portType name="BPELProcess1">
<wsdl:operation name="process">
<wsdl:input message="client:BPELProcess1RequestMessage" />
</wsdl:operation>
</wsdl:portType>
. . .
Figure 6-1 provides an overview.
Figure 6-1 One-Way Message
Descriptionof "Figure 6-1One-WayMessage"
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.

12. 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
. . .
<wsdl:portType name="BPELProcess1">
<wsdl:operation name="process">
<wsdl:input message="client:BPELProcess1RequestMessage" />
<wsdl:output message="client:BPELProcess1ResponseMessage"/>
</wsdl:operation>
</wsdl:portType>
Figure 6-2 provides an overview.
Figure 6-2 Synchronous Interaction
Descriptionof "Figure 6-2SynchronousInteraction"
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.

13. 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
. . .
<wsdl:portType name="BPELProcess1">
<wsdl:operation name="process">
<wsdl:input message="client:BPELProcess1RequestMessage"/>
</wsdl:operation>
</wsdl:portType>
. . .
<wsdl:portType name="BPELProcess1Callback">
<wsdl:operation name="processResponse">
<wsdl:input message="client:BPELProcess1ResponseMessage"/>
</wsdl:operation>
</wsdl:portType>
Figure 6-3 provides an overview.
Figure 6-3 Asynchronous Interaction

14. Descriptionof "Figure 6-3AsynchronousInteraction"
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
Basicallyall the SOA componentslikeBPEL,ESB (CalledMediatorin11g),& OWSMare broughtintoone
place in11g usingSCA composite concept.

15. The major difference between10g& 11g wouldbe the appservercontainer.10g by defaultrunson
OC4J while 11g runson WeblogicServer.
It isprettysimple tolearn11g SOA if you know 10g already.Youwill alsoneedabasicunderstandingof
Weblogicservers/domains.
SOA 10g : BPEL ---Webservice -ESB
Composite
SOA 11g : BPEL …SCA(SDO) Mediator

21. 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:

22. 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.

23. 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

24. Oracle JDeveloper
Oracle Enterprise Manager