Oracle fusion soa magnific online training

<Insert Picture Here>

Oracle fusion soa-magnific online training

CONTACT US:
USA:+1-6786933994,+1-6786933475
INDIA:+91-9052666559,040-69990056
Mail:info@magnifictraining.com

ISV Migration Center Team
• Who we Are ISV Migration Center Team is a team of senior technical consultants based in
Eastern and Central Europe and represents Oracle's technical investment for partners.
• Mission Statement Enable partners to rapidly and successfully adopt and implement Oracle
latest technology

• What do we Offer Whether you are selling Oracle technology, building business solutions,
including hosted Internet solutions or providing system integration and implementation services
for Oracle technology, IMC Team can help you succeed.
• How can we assist We offer a wide range of free services for partners such as one2one
assistance, webinars, seminars and hands-on workshops.

Contacts:

USA:+1-6786933994,+1-6786933475
INDIA:+91-9052666559,040-69990056
Mail:info@magnifictraining.com

2

Agenda
•
•
•
•
•
•
•
•

SOA Suite 10g and 11g Architecture comparison
Setting up SOA Suite 11g environment
Oracle BPEL / Oracle ESB projects migration
Oracle BAM migration
Security components migration
Upgrading Other Oracle SOA Suite Technologies
Best practices
Getting more information

<Insert Picture Here>

SCA – key enabler of the SOA Suite 11g
properties

Service Component Architecture:

Java interface

• language-neutral
• component model
• assembly model
• Specifications backed by a growing number of
leading industry vendors

WSDL portType

S
service

S

C1

R
wire

Binding:
SOAP
JMS

S

JCS
…

C2
component

R

R
reference

Being standardized at OASIS, the international open
standards consortium

composite

SCA terminology:
• Composite: deployment unit
• Service: entry-point into composite
• Component: provides logic
• Reference: refers to external services
• Wire: connects services, components and references
– no special semantic.

SOA Suite 11g SCA Service Infrastructure
One unified infrastructure to manage
Mediation

BPEL

Human Tasks
Business Rules

Application
composers

Human
Task

Mediation
BPEL orchestration

Rules

SCA Composite

IDE

Web
services
and
adapters

Mediator

SOA Composite Editor

Business
Rules

BPEL

Human
Workflow

11g Service Infrastructure
Repository

Common JCA-based connectivity infrastructure
Optimized
binding

BAM

Policy Manager

Oracle Service Bus

SOA
Operations

B2B
Web-based
console

6

SOA 10g to 11g mapping
Role

SOA Suite 10g

SOA Suite 11g

Java EE container

OC4J

Weblogic

Management consoles

Orchestration

BPEL Console, OESB Console, OWSM Console, Enterprise Manager Fusion Middleware
Enterprise Manager (OC4J), BAM Management
Control, Weblogic Console
Oracle BPEL Process Manager
BPEL Process Service Component

Human interaction

Human Workflow Engine

Human Workflow Service Component

Externalize logic

Oracle Business Rules

Business Rules Service Component

Transformation, Routing, Oracle ESB
Fan-out, etc
Apps and systems
connectivity
Business dashboards

JCAAdapters

Inside an application/composite: Oracle
Mediator Service Component, Enterprisewide: Oracle Service Bus
JCAAdapters

Oracle BAM (.NET-based)

Oracle BAM (JEE-based)

Security

OWSM (proxy and gateway modes)

OWSM (proxy), OEG (gateway)

Upgrade - High level steps
• Plan out Upgrade
• Create 11g SOA install/domain and load balancer from scratch
• Migrate/Deploy applications to 11g
• SOA JDeveloper projects
• BAM Reports/Data Objects/Alerts
• Configure 11g system from scratch
• Migrate clients if necessary
• Secure 11g system from scratch (example Identity Management,
OWSM policies)
• Cutover to 11g production system

Comparing Oracle SOA Suite on OC4J and Oracle
WebLogic Server

SOA Suite 11g installation
Server-side installation:
• Install Oracle Database for SOA components
• Install database schemas using RCU
• Install Oracle Weblogic binaries
• Install Oracle SOA Suite binaries
• Create Weblogic domain with SOA Suite components

Client-side (developer machines) installation:
• Install Jdeveloper
• Install SOA Extensions for JDeveloper

SOA Suite 11.1.1.5 installation: server-side
• You can use existing Oracle DB instance or create a new
one (recommended)
• Oracle SOA suite 11.1.1.5 certified with Oracle DB
10.2.0.4+, 11.1.0.7+ or 11.2.0.1+
• RCU (Repository Creation Utility) used
to create the schemas needed for the
corresponding Fusion Middleware
components

• Install Weblogic 10.3.5, new Middleware home
(MW_HOME) will be created as a result
• Install SOA Suite 11.1.1.5 binaries into MW_HOME. Specific
SOA ORACLE_HOME will be created

• Start Fusion Middleware Configuration Wizard to create new
domain: <SOA_ORACLE_HOME>/common/bin/config.sh
• Specify products to be configured
inside the domain
• Specify domain name, location,
ports for managed servers, etc…
• Start Admin Server and managed
server (s)

Important notes:
• To install SOA Suite environment for production deployment,
follow the Enterprise Deployment Guide for Oracle SOA Suite
and Oracle Fusion Middleware High Availability Guide
• Developers can install SOA Suite locally as well if they have
enough resources on the laptops

SOA Suite 11.1.1.5 installation: client-side
• Install JDeveloper 11.1.1.5
• Install JDev SOA Extension
• Always use the same version
for SOA server-side and
JDeveloper
• JDeveloper 11.1.2.1 does not
have SOA Extension !

SOA Suite 10.1.3  11g Project Upgrade Path
Mostly transparent project upgrade: Open your 10g
Project or Application in JDeveloper 11g, apply any
manual steps and re-deploy!
JDeveloper
or command-line

1. open

3. deploy

2. save
11g SOA Suite
Server

10.1.3 ESB or BPEL project

11g composite project

Upgrade in JDeveloper
• In-place upgrade of application/project.
• Can upgrade any project, not just SOA projects.
• All HTTP WSDL references in project must be accessible, so
SOA 10g should be up and running.
• Logs are in …/jdeveloper/upgrade/logs.

ESB project -> SOA Composite

• Analyze the warnings
in the log files
generated during the
upgrade process

Command Line Upgrade
•
•
•
•
•

•
•
•

Ant script available to upgrade SOA projects.
Cannot upgrade whole Applications.
Upgraded directory different than source directory.
Does not Upgrade .jpr files. Opening project in Jdeveloper
creates .jpr file.
Can merge multiple BPEL source directories to a single
upgraded target directory.
All HTTP WSDL references in project must be accessible.
Logs in …/jdeveloper/upgrade/logs
Same codebase used for JDeveloper upgrade.

Upgrading SOA Suite 10g Projects Using Ant
Before you begin, set environment variables
set ORACLE_HOME=<MIDDLEWARE_HOME>jdeveloper
cd %ORACLE_HOME%
binsoaversion.cmd
Upgrade an 10g ESB service to an 11g Composite application with Mediator
component:
ant -f %ORACLE_HOME%binant-sca-upgrade.xml mediator -Dsource
C:projects10.1.3EmployeeEmployeeService -Dtarget C:projects11gR1 -DappName
Employee
Merge several 10g BPEL processes to an 11g Composite application:
ant -f %ORACLE_HOME%binant-sca-upgrade.xml bpel -Dsource
"C:projects10.1.3EmployeeEmployeeSalaryApproval;c:projects10.1.3...
...EmployeeEmployeeInfo" -Dtarget C:projects11gR1 -DappName Employee

Manual steps
• Strong attempt made to automate project upgrade as much
as possible given large differences between 10g and 11g.
• Not always possible.
• A few things deferred due to time constraints.

• Artifacts upgraded are BPEL processes, ESB services,
Rules dictionaries, Human Workflow tasks, Adapters. Some
limitations apply.
• SOA configuration plans, fault policies, build files are not
upgraded

BPEL instance Migration
• Right now there is no support on for BPEL instance
migration, or audit trail migration. Oracle investigating
feasibility of instance migration.
• Two choices for cutting over long running processes to 11g:
• Side by Side Upgrade
• Grace period cutover

Side by Side Upgrade
• 10g and 11g systems run side by side.
• 10g system has all long running processes in retired state so
no new process instances can be created.
• Clients are switched over to 11g.
• 10g system continues running until all callbacks arrive to
complete long running processes.
• 10g system is decommissioned.

Grace period cutover
• 10g system has all long running processes in retired state so
no new process instances can be created.
• After a grace period, all 10g long running processes are
killed.
• 10g system is decommissioned.
• 11g system is brought up in production.

Configuration/Deployment Upgrade
• 10g configuration files not automatically upgraded to 11g
configuration files. 11g has to be configured using EM,
JMX/Mbean APIs or WLST scripts instead.
• SOA Composite properties can be customized in the
deployment plan.
• Cannot automatically upgrade from 10g SOA deployment
plan to 11g deployment plan.
• 10g SOA deployment units cannot be upgraded to 11g
deployment units. Need to upgrade source instead and
generate deployment unit.

BAM upgrade steps overview
• RCU creates the schema for 11g BAM
• Use Upgrade assistant (UA) tool to copy data
objects/reports/alerts from 10g BAM system database to 11g
BAM system database directly
• 10g Enterprise Link is no longer supported
• Native support for JMS connectivity in 11g
• Native support for ODI integration in 11g
• Configure 10g SOA clients to talk to BAM 11g or migrate 10g
SOA clients to 11g.
• Note: 10g SOA interoperates with 11g BAM, 11g SOA interop with 10g BAM is not
certified.

Securing SOA composites
OWSM Migration
• 11g SOA install auto-deploys 11g OWSM policy manager
• 10g OWSM policies do not migrate to 11g OWSM as they
are syntactically different. Refer to OWSM guide for 10g
policy to 11g policy mapping.
• 10g OWSM Monitor functionality is provided by EM SOA Mgt
Pack for 11g AppServer.

Securing SOA composites
OWSM Migration
• If 10g BPEL/ESB is secured using OWSM agent, then
• There’s no need for agent migration as agent is built-in the 11g SOA
runtime
• Using JDev/EM, attach 11g OWSM policy to the migrated SOA
composite.

• If 10g BPEL/ESB is secured using OWSM Gateway, then
• Continue to use 10g OWSM Gateway
• Or, start using 11g built-in agents by attaching 11g OWSM policies to
SOA composite.

Upgrading DVMs and XREFs
• XPath functions to access domain value maps (DVMs) and
cross reference tables (XREFs) are upgraded automatically
when you open projects in JDeveloper 11g;
• You must manually extract the DVMs and XREFs from
Oracle ESB 10g repository and load them to the MDS
Repository. Scripts/utilities are provided;

Migrate DVMs
•

Export DVM metadata to archive:
<ESB10g_Oracle_Home>/export.sh metadata10g.zip

•

Convert the ZIP file to an Oracle SOA Suite archive file
cd <SOA11g_Oracle_Home>/bin
ant -f ant-sca-upgrade.xml upgrade-xrefdvm
-Dsource=location_of_the_zip_file
-Dtarget=location_of_the_soa_archive

Output file will be automatically called sca_XrefDvmFiles10g_rev1.0.jar

•
•
•

Create new application in Jdeveloper 11g
Import->SOA Archive into SOA project
Create jar file with DVM metadata and deploy it to MDS

Migrate XREFs
XREF_DATA table has changed in 11g, so special procedure
is required for migration
• Create public DB link dblink10g in SOA 11g DB to access
SOA 10g DB
• Extract XREF10gto11gDataUpgradeUtility located in the
RCU_HOME/rcu/integration/soainfra/sql/xref
• Modify Upgrade10gXrefTo11gXref.sql pointing to the shared
MDS data location
• Execute the Upgrade10gXrefTo11gXref.sql
• Drop dblink10g DB link

Technology adapters migration
• Run 11g Adapter Configuration Wizard for each adapter
after SOA project upgrade;
• Adapter header variables in 10g defined in the adapter
WSDL file, in 11g they are the properties defined in Invoke
activity in BPEL process or Assign values dialog in Mediator;
• Non-managed connections are not supported in 11g, check
adapter WSDL files before upgrade;
• Description lost after upgrade of technology adapter
• See the Upgrade guide for more details

Human Workflows migration
• Human Workflows in 10g are defined in .tform files, UI is
created with jsp pages in the same JDev project, deployed
together;
• Human Workflows in 11g are defined in .task files, separate
ADF projects are created for UI, deployed separately;
• During upgrade JDeveloper 11g automatically creates a new
project for the task UI and upgrades the task detail pages;
• Manual modifications of the WorkflowTask XSD may be
required, refer to the Upgrade Guide for details

Client and Invoked Service Migration
• Some 11g APIs are compatible with equivalent 10g APIs,
some are different.
•
•
•
•

Worklist APIs are compatible.
B2B APIs are compatible.
Custom Sensor APIs are compatible.
BPEL APIs are functionally roughly equivalent with signature
changes.
• Rules SDK APIs are a functional superset.

• 11g uses ws-addressing 1.0. Need patch for 10g BPEL
client.
• URLs in 11g has different syntax. (includes callback URL
used by invoked services).

Best Practices
Before migration
• Ensure that SOA Suite 10g Projects are Up and Running on Latest
SOA 10g Release
• Install the Jdeveloper 11g with SOA Extension (currently 11.1.1.5)
• Install the latest SOA Suite 11g version (currently 11.1.1.5) . Quick
start guide for SOA Suite 11g
• Configure all the necessary resources (JDBC connection pools, JCA
adapters, JMS queues, etc)
• Order matters!
• Start with a pilot project, do not use the Big Bang approach

Best Practices
During and after migration
• Recompile the migrated projects (11g BPEL compiler is stricter
than 10g);
• Think about rearranging the artifacts into the corresponding
folders (xsd, wsdl and other file types). Change the referencing
artifacts accordingly;
• Run 11g Adapter Configuration Wizard for each adapter to verify
the adapters configuration;
• If you are using adapter header variables in SOA 10g BPEL
projects, you have manually set them in the Invoke activity

Best Practices
• Refer to project for abstract WSDL and HTTP URL for concrete WSDL.
• Create configuration plans for deployment of the SOA 11g composites
• Use MDS to share WSDLs, XSD, DVM, EDL event files and other
artifacts across projects (oramds://<path_to_the_resource>). If you are
accessing any file from bpel xmllib you need to change the URL to MDS
URL:

Best Practices
• Do not blindly 1:1 migrate every BPEL /ESB project to the
corresponding composite. You can not leverage SCA benefits by having
many fine grained composites.
• Use SOA Suite 11g partitions, it has some similarities with BPEL
domains and ESB System/Service Groups in 10g
• Explore the performance tuning options available in the SOA Suite
11g, look at Oracle® Fusion Middleware Performance and Tuning
• Guide
Production deployment architecture is different in SOA cluster wide
Example: usage of Coherence instead of JGroups for Suite 11g.
deployment. Look at Oracle® Fusion Middleware Enterprise
Deployment Guide for Oracle SOA Suite

Getting more information
•

Oracle® Fusion Middleware Upgrade Guide for Oracle SOA Suite,
WebCenter, and ADF 11g Release 1 (11.1.1)

•

Oracle® Fusion Middleware Developer's Guide for Oracle SOA
Suite 11g Release 1 (11.1.1)

•

Quick Start Guide for Oracle SOA Suite - detailed download, install
and configuration instructions

•

Oracle SOA Suite 11g Handbook by Lukas Jellema.

Questions
Should you require any further
information please do not hesitate to
contact us
http://www.oraclecourseonline.com
-oracle apps technical training
contact us:
info@magnifictraining.com or +919052666559
By Real Time Experts from Hyderabad,
Bangalore
,India,USA,Canada,UK, Australia,South
Africa.

©2011 Oracle Corporation

Oracle fusion soa magnific online training

Recommended

Recommended

More Related Content

More from magnifics

More from magnifics (10)

Recently uploaded

Recently uploaded (20)

Oracle fusion soa magnific online training