SOA Appendix A OnLineComplement August2010 PDF

Oracle 11g SOA Suite Handbook: Complement to Appendix A August 1, 2010
On Line Complement to Appendix A - Migration from SOA Suite 10g to

11g
Online complement (this complements the first steps and the more general approach
described in Appendix A as included in the book).
(1) The migration continues...

So now we have a global understanding of migrating 10g ESB and BPEL projects. In the
following sections we will see some more nitty gritty details per 10g artifact you possibly might
run into.
(2) Migrating Domain Value Maps (DVM)

Domain Value Maps were introduced in ESB 10g. In later versions of Oracle SOA Suite
10g they could also be used from BPEL. In 11g, DVM’s are fully supported in SCA composite
applications. SOA Suite 11g also provides the SOA Composer to edit DVM’s at runtime from a
web environment.
In SOA Suite 10g you can use the orcl:lookup-dmv function to lookup a DVM value in
your BPEL or ESB project. In the figure below it used in a Switch Process Activity of a 10g
BPEL project.
DVM used in a BPEL 10g Switch Activity
The figure below shows a DVM used from an ESB 10g project in an XLST Transformation.
15-1
DVM lookup in a XSLT
In SOA Suite 10g the DVM has to be created in the ESB Console. With 11g you can
create a DVM in JDeveloper and reuse it in your projects. Note that in 11g the DVM function
name changed from orcl:lookup-dmv to dvm:lookupValue.
To use a “10g” DVM in 11g you need to make an full export of the ESB repository, this
will include all the DVM and XREF files. To create an export you can use a script on the SOA
Suite 10g server. Go to the integration/esb/bin folder in the SOA Suite Home and start the
export.bat script and add an output path.
Export.bat c:\dvm.zip
Copy the dvm.zip file to your JDeveloper 11g environment. You can use the same Ant
script for the DVM and XREF conversion. Open a command window and use the following
script:
set ORACLE_HOME=C:\oracle\MiddlewareJdev11gR1PS1\jdeveloper
cd %ORACLE_HOME%
bin\soaversion.cmd
8-2
ant -f %ORACLE_HOME%\bin\ant-sca-upgrade.xml upgrade-xrefdvm
-Dsource C:\projects\10.1.3\dvm.zip
-Dtarget C:\projects\11gR1\
This will generate a file called sca_XrefDvmFiles10g_rev1.0.jar. In SOA Suite 11g you
have now two options to use this DVM in your project.
 Copy the DVM file to the composite and replace the oramds reference in the DVM
lookups.
 Add the DVM to your local and remote MDS.
In the first option you need to copy the DVM file from the
sca_XrefDvmFiles10g_rev1.0.jar to the composite project folder. In this migrated composite
application you need to check if the BPEL components and XSLT files uses a DVM lookup and
replace oramds;l for Example:
dvm:lookupValue("oramds:/apps/XrefDvmFiles10g/Country.dvm "
Or:
dvm:lookupValue('oramds:/apps/XrefDvmFiles10g/Country.dvm '
and change it to:
dvm:lookupValue('Country.dvm'
The second option is more complex, here you need to add these DVM files to the local
MDS and the SOA Suite 11g runtime MDS. For the local MDS you need to create a folder
(partition) named XrefDvmFiles10g in the local MDS apps folder of your JDeveloper
(jdeveloper\integration\seed\apps).
15-3
XrefDvmFiles10g partition in the local MDS
Add the DVM’s to this local MDS folder. To see the result make a MDS connection to
your local MDS in JDeveloper.
The next step is to deploy these DVM’s to the database MDS of the SOA Suite 11g
server. Navigate to the apps folder of the local MDS and add the XrefDvmFiles10g folder to a
zip file. Rename the zip extension to jar. After this you need to add this jar to a new zip file.
This zip file with the jar can be deployed to SOA Suite 11g by using the Ant deploy script:
set ORACLE_HOME=C:\oracle\MiddlewareJdev11gR1PS1\jdeveloper
cd %ORACLE_HOME%
bin\soaversion.cmd
ant -f %ORACLE_HOME%\bin\ant-sca-deploy.xml
-DserverURL=http://localhost:8001
-DsarLocation=C:\projects\11gR1\XrefDvmFiles10g.zip
-Doverwrite=true
-Duser=weblogic
-Dpassword=weblogic1
8-4
-DforceDefault=true
You can check this import by making a new Database MDS connection or you can use
the Composer application (http://yoursoaserver:8001/soa/composer/faces/login.jspx). In this Web
application you can change the DVM’s.
(2) Oracle Enterprise Service Bus (ESB)

The checks you need to perform after the ESB migration are relative easy compared to
those of BPEL. First you need to check the Adapters. Important is to verify that the header
properties in the XSLT are migrated correctly.
During automated migration you can get an EHDR (ESBHeaderFunctions) warning:
WARNING: UPGMED-02060: Encountered XSL conditional element like xsl:if or xsl:for-

each. All ehdr functions may not be migrated properly from the XSL. Manually check
the XSL
Or:
WARNING: UPGMED-02022: Encountered customized 10.1.3 ESB ehdr:setOutboundHeader

function "/aq:HeaderType/aq:Priority", Please verify .mplan file of corresponding
component manually. Modify <assign> for the equivalent case.
In 10g the way to change an adapter property was to add an ESBHeaderFunction in an

ESB Routing rule transformation, like this
<xsl:variable name="setPriority"
select="ehdr:setOutboundHeader('/aq:HeaderType/aq:Priority'
,'5'
,'aq=http://xmlns.oracle.com/pcbpel/adapter/aq/outbound/;')"/>
The migration will remove this ESBHeaderFunction from the XSLT and add them as
assignment in the Mediator component. Probably this assignment input is not correct and you
need to correct this in the Mediator Component.
15-5
Migrated Header property
In this example the “to” value of the assign must be changed to the right AQ priority
property.
(2) Adapters
Adapters can be used from both ESB 10g and BPEL 10g. After their migration to 11g it
is advised to open all the adapter wizards and follow all steps to check for errors.
(3) Web Service Adapter

In SOA Suite 10g you can use ESB Routers from BPEL even when these Routers do not
have an exposed Web Service. This can cause a migration warning:
[upgrade] INFO: UPGBPEL-02041: Retrieving wsdl for partnerLink

"PartnerLink_XXXXXX" from "http://soa10g/esb/wsil/example/employee/Employee?wsdl".
[upgrade] WARNING: UPGBPEL-02009: No Binding setup for : "PartnerLink_XXXXXX".
This can be resolved by migrating and deploying the reference Composite to the SOA
Suite 11g server. When this is successful you can open the Web Service Adapter and use the
WSDL URL of the reference Composite.
8-6
WS adapter error, it cannot find the Web Service endpoint
Open the Web Service Adapter and lookup the WSDL on the SOA Suite 11g Server. Go
to the Resource Palette and select the Reference Composite application.
Overview of all the Soa Services in the Resource Palette
15-7
(3) JMS Adapter

The JMS adapter supports three implementation types:
 Use WebLogic Server JMS
 AQ ( JMS) with the JMS Foreign Server in WebLogic
 Third Party JMS
This section will only dive into the JMS and AQ option. For standard JMS you need to
open the JMS adapter and select Oracle Weblogic JMS as JMS provider.
JMS provider options
Select the WebLogic application server connetion on which JMS is implemented.
8-8
Overview of the JMS queue and topics on the Weblogic Server
Select the right or queue or topic.
When you use AQ with JMS you need to select Oracle Advanced Queueing as JMS
provider.
15-9
You will get a selection of the all the JMS Foreign Server queues and topics.
8-10
When you select the Queue, JDeveloper will probably change your JNDI name. Correct this to
the original value.
(3) AQ Adapter
For AQ you only need to open the Adapter and follow the wizard till the end.
(3) Database Adapter

In 10g the DB adapter wizard creates some Toplink entity classes which will are used in
the adapter. This can lead to this error when you rebuild the composite application.
This error can be solved by removing the unused Toplink imports in the java classes or add the
Toplink library to the project.
15-11
The java class needed for the DB adapter with the Toplink imports which can be removed.
These changes are enough to successful deploy the Composite application to the SOA
Suite Server.
When you want to open the DB adapter to see if everything is ok or if you want change
something in the DB adapter wizard, it will give you a lot of errors. In 11g the DB adapter
wizard is build on the new Toplink implementation. If you still want to change this, take a look
at the “Remove the 10g code from the Composites applications”
After the migration you can optional do some cleaning up to get rid of now obsolete 10g code by
upgrading the Database adapter and remove the 10g toplink xml’s and classes.
In 11g the DB adapter wizard uses the 11g Toplink implementation, this explains the
errors when you open the DB adapter wizard. If you want to change this and remove the
8-12
unnecessary 10g files then follow these steps. Be aware this can lead to changes to the
Mediator XSLT transformations or the BPEL invoke activity parameters.
First remove the offline tables, Toplink mapping and classes
Adapter_10.tif Migrated 10g project with the necessary Toplink files for the DB adapter
After removing of these code it will look like this.
15-13
after removal of the TopLink code.
Start the wizard for this Database adapter. You need to import the Database tables or procedures
again, define the relations between the tables and optional add some parameters to the queries
The final result.
In 11g the DB adapter does not need any java classes or offline databases. These files are
replaced by the or-mapping and properties files.
Possible errors with this DB adapter upgrade:
 WSDL import errors: you can get this error because the XSD used by the DB adapter is
moved to the xsd folder. Search for this XSD and add xsd/ to the import path.
 Runtime error, XXX_toplink_mappings.xml not found. Open the jca file and change the
MappingsMetaDataURL property to the right XXX_ or-mapping file instead of
XXX_toplink_mappings file.
(2) BPEL
To successfully migrate a BPEL project to a composite applications you may need to do
some extra configuration work when you use one of the following in your BPEL project.
 Properties
8-14
 Sensors
 Test Suites
 Fault Policies
These after migration steps are described in the next part of this section.
(3) BPEL Properties

In 10g you can add BPEL properties to the BPEL.xml and change these values in the
BPEL console.
<?xml version = '1.0' encoding = 'UTF-8'?>
<BPELSuitcase>
<BPELProcess id="EmployeeSalaryApproval" src="EmployeeSalaryApproval.bpel">
<preferences>
<property name="ok" encryption="plaintext">approved</property>
<property name="nok" encryption="plaintext">declined</property>
</preferences>
</BPELProcess>
</BPELSuitcase>
In 11g these properties are migrated to the BPEL component in the composite.xml.
<?xml version="1.0" encoding="UTF-8"?>
<composite name="EmployeeSalaryApproval2" revision="1.0" mode="active" state="on"

xmlns="http://xmlns.oracle.com/sca/1.0"
xmlns:ui="http://xmlns.oracle.com/soa/designer/"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
<component name="EmployeeSalaryApproval">
<implementation.bpel src="EmployeeSalaryApproval.bpel"/>
<property name="preference.ok">approved</property>
<property name="preference.nok">declined</property>
15-15
</component>
</composite>
These BPEL properties need to start with preference and can only be changed at runtime
in properties attribute of the BPEL component MBean. For this you need to open the System
MBean browser in the Enterprise Manager and find your composite application MBean.
The attributes of a BPEL component through the Component MBean.
Click on the properties attribute where you can change the BPEL property.
8-16
The BPEL property inside the properties attribute.
(3) BPEL Sensors

In 10g you can add Activity Sensor on a BPEL activity and you can connect this Activity
Sensor to a Database Sensor Action.
15-17
Activity Sensor on a receive activity.
In 11g you also have BPEL Sensors only you have to switch to the Monitor view of your BPEL
process editor to see them.
In the right corner of the BPEL process you can switch to the BPEL monitor view.
To see the Sensor values of the instances of this BPEL component in 11g you need to open the
BPEL component in the instance view. The instances are accessible in the Enterprise Manager.
8-18
Sensor value in a 11g BPEL component instance.
(3) BPEL Test Suites

The 11g migration will convert the BPEL Test Suites (see Chapter 17 for an introduction
of the Test Suites) to Composite Test suites.
15-19
A 10g BPEL project with two Test Suites
The 11g migrated Composite Test Suites.
Because the 10g BPEL Test Suite are designed for BPEL and the 11g Test Suites only
work on the composite level , the migration removed the specific BPEL tests like an Assert in an
Assign activity.
8-20
BPEL 10g Test Suite with an initiate Message and an Assert check
If the 10g BPEL Test Suite has an initiate message then this is converted to an initiate
message on the Client Service of the Composite Application.
15-21
The migrated initiate message
You need to add some extra tests on the wire actions in the 11g Test Suite to compensate
for the removal of the Assign Assertion Checks, else you only invoke the composite service and
not test the response for the expected result.
In 11g the Test Suites are included in the Composite deployment . This means you don’t
need to deploy these tests separately and you can run your Test Suites right the way.
Unit Test part of the deployed composite in the Enterprise Manager.
In the Enterprise Manager you can make a new Test Case and select the Test Suites you
want to use in this Test. In the Test Runs or Instances tab you can follow the started instances of
these tests. Also see Chapter 17.
(3) BPEL Fault Policies

The migration cannot convert the BPEL Fault Policies to Composite Fault Policies
because in 10g these policies are defined in the BPEL domain folder and not in the BPEL
project. The second reason is that in 11g the Fault policies are defined on the Composite Level
8-22
and has impact on every component in the composite application (see Chapter 16 for more
details on the 11g Fault Policy Framework).
For these reasons, you have to analyze the 10g fault policies and add the new fault
policies to the composite project. To do this add the fault-policies.xml and fault-bindings.xml
files to your composite project folder . It is a best practice to analyze both ESB 10g and BPEL
10g fault handling and integrate those into measures into 11g fault policies as you integrated (or
merged) ESB 10g and BPEL 10g projects into SCA composites.
The fault-binding.xml file associates fault policies to a composite or its components, just
like the fault –binding.xml located in the BPEL domains config folder.
The following snippet shows an 11g fault-binding.xml example:
<faultpolicybindings version="2.0.1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://schemas.oracle.com/bpel/faultpolicy fault-bindings.xsd"
xmlns="http://schemas.oracle.com/bpel/faultpolicy">
<composite faultPolicy="MyFaultHandler"/>
</faultpolicybindings>
Next step is to define the MyFaultHandler policy in the fault-policies.xml. The fault-
policies file contains the fault conditions and its actions. In this example when there is a remote
fault on a partnerlink it will wait for a human intervention before the BPEL instance continues.
15-23
Fault policy file in SOA Suite 11g
Here is an example of the 10g fault-policy, this policy is almost the same as the 11g
version. You only need to add the faultPolicies Element.
SOA Suite 10g Fault policy definition
8-24
(3) BPEL Domains

BPEL 10g has the notion of domains to structure BPEL projects and to tune and deploy
BPEL processes. In SOA Suite 11g R1 PS1 you don’t have this option. In the Enterprise
Manager you will see all the composites on the same level. If you want to group some composite
applications you need to make an extra Weblogic SOA domain.
Patch Set 2 or 11g R2 of the SOA Suite Oracle supports Composite Folders (partitions).
This makes it possible to group composite applications.
(3) BPEL Domain properties

In BPEL 10g you can tune the BPEL Engine by changing the properties in the
domain.xml. For example the threads count for Invoke or for the BPEL Engine, Instance
Persistence parameters and controlling the audit Level. In 11g you can change the same
parameters but not every parameter can be changed in the Enterprise Manager Website.
The parameters which can be changed in the Enterprise Manager
To see or change all BPEL parameters you can invoke or change the attributes of the
BPEL Mbean .
15-25
The BPEL MBean where you can change the BPEL parameters
This BPEL MBean will change the properties in the bpel-config.xml and soa-infra-
config.xml files. You can see these files in the JDeveloper Resource Pallette when you
make a Soa Suite MDS Database connection.
8-26
SOA Suite configuration files inside the SOA Suite MDS
(2) Custom XPath and XSLT extensions

SOA Suite 10g and 11g both support custom functions which can be used in a XLST
editor or in a BPEL activity. These custom XSLT extensions are implemented in Java and can be
used to realize transformations that are impossible or difficult to achieve using “plain” XSLT and
XPath. To use these custom functions you need to migrate the configuration xml and maybe need
to change the java classes so it uses the fabric classes.
In 11g you need the use the oracle.fabric.common.xml.xpath classes in an XPATH

function instead of com.oracle.bpel.xml.xpath.
Here a example of an 11g XPATH function.
package soa.demos.extensions.xpath;
import java.util.List;
import org.w3c.dom.Node;
import oracle.fabric.common.xml.xpath.IXPathContext;
15-27
import oracle.fabric.common.xml.xpath.IXPathFunction;
import oracle.fabric.common.xml.xpath.XPathFunctionException;
public class GetNodeValueFunction implements IXPathFunction {
public GetNodeValueFunction() {
public Object call(IXPathContext context,
List args) throws XPathFunctionException {
try {
if (args.size() == 1)
return evaluate(args.get(0));
} catch (Exception e) {
throw new XPathFunctionException(e);
throw new XPathFunctionException("getNodeValue() requires one arugment

which is a dom node.");
public Object evaluate(Object node) throws Exception {
if (node != null) {
if (node instanceof Node)
return ((Node)node).getFirstChild().getNodeValue().trim();
else
return String.valueOf(node);
} else {
8-28
return null;
In 10g you need to add this XPATH function definition to the Xpath-functions.xml file
(located on the 10g SOA Suite Server).
<function id="getNodeValue" arity="1">
<classname>soa.demos.extensions.xpath.GetNodeValueFunction</classname>
<comment>
<![CDATA[This function returns the value of a dom node as String. The

signature of this function is <i>ora:getNodeValue(node)</i>.]]>
</comment>
<property id="namespace-uri">
<value>http://soa.demo/xpath/function</value>
<comment>Namespace URI for this function</comment>
</property>
<property id="namespace-prefix">
<value>demo</value>
<comment>Namespace prefix for this function</comment>
</property>
</function>
In 11g you can control where you can use this XPATH function. For example use this
XPATH only in BPEL, Mediator or in all SOA 11g Components. To control this you need to
define this XPATH function and the definition in one of the following files.
 Oracle BPEL Process Manager ext-bpel-xpath-functions-config.xml
 Oracle Mediator ext-mediator-xpath-functions-config.xml
15-29
 Human workflow ext-wf-xpath-functions-config.xml
 All components ext-soa-xpath-functions-config.xml
Custom XPATH function definition in 11g.
Add this xml to the META-INF folder of your extension jar.
(3) Custom XSLT function in 10g & 11g

Here is an example of a custom XLST function, this will work in 10g and 11g.
package soa.demos.extensions.xslt;
import java.text.ParseException;
import java.text.SimpleDateFormat;
import java.util.Calendar;
import java.util.Date;
public class Functions {
private static final SimpleDateFormat format =
new SimpleDateFormat("yyyy-MM-dd");
public static String getWeekFromDate(String date) throws ParseException {
8-30
Calendar calendar = Calendar.getInstance();
try {
calendar.setTime(format.parse(date));
} catch (Exception e) {
calendar.setTime(new Date());
int weekOfYear = calendar.get(Calendar.WEEK_OF_YEAR);
if (weekOfYear < 10) {
return "0" + weekOfYear;
return "" + weekOfYear;
Example of the 10g extension file
<extension-functions>
<functions
xmlns:customFunctions="http://www.oracle.com/XSL/Transform/java/soa.demos.extensio
ns.xslt.Functions">
<function name="customFunctions:getWeekFromDate" as="string">
<param name="date" as="string"/>
</function>
</functions>
</extension-functions>
15-31
The 11g extension ext-mapper-xpath-functions-config.xml file looks like this. In 11g the
XSLT namespace still needs to start with http://www.oracle.com/XSL/Transform/java/
The 11g definition of this XLST function.
To use your own XPATH and XSLT function you need to add these jars in JDeveloper
(Tools  Preferences  SOA).
JDeveloper 11g SOA preference where you can add your extension jars.
You also have to put these jar in the SOA Suite domain. Add these jars to the (WebLogic
Server) domain lib folder.
8-32
The WLS Domain lib folder with the extension jars.
(2) Oracle Web Services Manager

In Fusion Middleware 11g Oracle redesigned the Oracle Web Services Manager
(OWSM) and is now fully integrated in the Oracle WebLogic Server runtime; read more on this
in chapter 15. The following changes are applied to OWSM 11g compared to 10g:
 Attach policies to Web Service endpoints instead of enforcement points
 Policies consist of assertions, in 10g you have policy steps
 Web Service clients can’t use the JAX-RPC framework
 OWSM 11g does not support a gateway; only agents. You need to use OWSM 10g for
now if you want gateway functionality.
There is no 10g to 11g migration tool available for OWSM. You have to do this step for
step and this chapter will guide you through the migration steps. The WSM migration steps
include:
 Analyzing the policies of the WSM 10g enforcements points
 Determine which 11g WSM policies to use
 Configure WSM in the 11g Enterprise Manager
15-33
 Identify the 10g Web Services which have WSM Server policies
 Add the WSM 11g server policies to the Composite Services
 Analyze the 10g WSM Clients
o SOA Suite 10g Service references
o J2EE EJBs & Web Applications
o J2SE Standalone Java Applications
 Add WSM 11g client policies to the Composite References
 Change the java applications for WSM 11g client policies
(3) OWSM Gateway

FMW 11g does not have an WSM gateway. This means you still need to use the 10g
WSM gateway if you use this gateway for the following situations:
 Exposing Web Services in a DMZ
 Protocol switching, For example from JMS to HTTP
 Security switching, For example from basic authentication to SAML
For these situations you probably have this WSM Gateway not installed on the Soa Suite
Server, so you can still upgrade the 10g Soa Suite server to FMW and upgrade this WSM
Gateway at a later time when Amberpoint is fully integrated in FMW. The FMW license still
allows you to use WSM 10g.
(3) Policy Manager

In 10g, WSM is also part of the Soa Suite but in 10g WSM is not fully integrated as in
FMW. You have in 10g a Policy Manager web application called Web Service Manager Control
to configure the policies for WSM. This Policy manager is not aware of the deployed EJBs, Web
Applications or Web Services. In the Policy Manager you can add an enforcement point with a
policy and in the Enterprise Manager or in the Java application add the enforcement point
reference id to a web service or a web service client. In 11g you can configure policies in the
Enterprise Manager and add them right away to the deployed Web Services or Web Service
8-34
clients. These policies are immediate active, you don’t need to restart the Weblogic Server. In
10g after configuring or changing a policy you always need to redeploy this WSM Server agent
to the Oracle Application Server or when it is a client policy you have to deploy this to a folder.
WSM 11g is not only fully integrated in the Oracle Weblogic Server but also in the
Fusion Middleware Development environment. In JDeveloper 11g you can also add the WSM
policies to a Composite Service, Composite Reference, an ADF Web Service DataControl or a
Web Service Proxy Client. In 11g adding policies to a Web service or Web Service Client is not
so difficult and is not only an administrator task.
The best way to add a WSM policy to a Composite Service or Reference is to do this in
JDeveloper. Then every version of the Composite Application deployed on the Weblogic Server
have these WSM policies. In the Enterprise Manager you can only define a WSM policy to one
version of the Composite Application. This means that the administrator needs to add the
policies for every version of Composite Application and after each deployed of a new version .
(3) Policies
OWSM in FMW 11g have the same policies as WSM 10g but in 11g this is different
organized. In 10g you can add one of more steps to a request or response pipeline. So you can
have Decrypt and Verify Signature combined with a SAML Verify WSS token..
15-35
Example of a 10G WSM Server policy
In 10g you have to define the pipeline steps for the request and the response and for the
client and server policy. In 11g you have assertions like signing or logging and these assertions
can be combined to a client and server policy .
8-36
Example of a pre-defined 11g WSM policy
The first step in the WSM migration is to know which Pipeline steps are used in WSM
10g, when you know this then you can determine which WSM 11g policy matches with the 10g
policy steps. In the Manage Policies page of the 10g Web Services Manager Control Application
you can see all the enforcement points and from here you can open the policy page.
15-37
Overview of the WSM 10g Enforcement Point
(3) Logging
In WSM 10g you can see the messages log in the Operational Management of the Web
Service Manager Control application. In FMW you can’t see these messages in the Enterprise
Manager. To take a log at these messages you need to go to your SOA Suite Weblogic domain
and go the owsm logging folder
(user_projects\domains\soa_domain\servers\soa_server1\logs\owsm\msglogging). Here you can
open the diagnostic.log file.
8-38
The location in the Weblogic SOA Suite domain of the WSM logging
For more information about choosing the right WSM 11g policy which matches your 10g
policy steps see the Interoperability Guide for Oracle Web Services Manager manual, part of
the Fusion Middleware 11g documentation.
15-39

SOA Appendix A OnLineComplement August2010 PDF

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

SOA Appendix A OnLineComplement August2010 PDF

Загружено:

Авторское право:

Доступные форматы

Oracle 11g SOA Suite Handbook: Complement to Appendix A August 1, 2010

On Line Complement to Appendix A - Migration from SOA Suite 10g to

(1) The migration continues...

(2) Migrating Domain Value Maps (DVM)

DVM used in a BPEL 10g Switch Activity

DVM lookup in a XSLT

ant -f %ORACLE_HOME%\bin\ant-sca-upgrade.xml upgrade-xrefdvm

 Add the DVM to your local and remote MDS.

and change it to:

XrefDvmFiles10g partition in the local MDS

(2) Oracle Enterprise Service Bus (ESB)

During automated migration you can get an EHDR (ESBHeaderFunctions) warning:

WARNING: UPGMED-02060: Encountered XSL conditional element like xsl:if or xsl:for-

WARNING: UPGMED-02022: Encountered customized 10.1.3 ESB ehdr:setOutboundHeader

In 10g the way to change an adapter property was to add an ESBHeaderFunction in an

Migrated Header property

(3) Web Service Adapter

[upgrade] INFO: UPGBPEL-02041: Retrieving wsdl for partnerLink

[upgrade] WARNING: UPGBPEL-02009: No Binding setup for : "PartnerLink_XXXXXX".

WS adapter error, it cannot find the Web Service endpoint

Overview of all the Soa Services in the Resource Palette

(3) JMS Adapter

 Use WebLogic Server JMS

 AQ ( JMS) with the JMS Foreign Server in WebLogic

 Third Party JMS

JMS provider options

Select the WebLogic application server connetion on which JMS is implemented.

Overview of the JMS queue and topics on the Weblogic Server

Select the right or queue or topic.

(3) Database Adapter

First remove the offline tables, Toplink mapping and classes

After removing of these code it will look like this.

after removal of the TopLink code.

The final result.

Possible errors with this DB adapter upgrade:

(3) BPEL Properties

<?xml version = '1.0' encoding = 'UTF-8'?>

<BPELProcess id="EmployeeSalaryApproval" src="EmployeeSalaryApproval.bpel">

<property name="ok" encryption="plaintext">approved</property>

<property name="nok" encryption="plaintext">declined</property>

<?xml version="1.0" encoding="UTF-8"?>

<composite name="EmployeeSalaryApproval2" revision="1.0" mode="active" state="on"

The attributes of a BPEL component through the Component MBean.

The BPEL property inside the properties attribute.

(3) BPEL Sensors

Activity Sensor on a receive activity.

Sensor value in a 11g BPEL component instance.

(3) BPEL Test Suites

A 10g BPEL project with two Test Suites

The 11g migrated Composite Test Suites.

The migrated initiate message

Unit Test part of the deployed composite in the Enterprise Manager.

(3) BPEL Fault Policies

The following snippet shows an 11g fault-binding.xml example:

<?xml version="1.0" encoding="UTF-8"?>

Fault policy file in SOA Suite 11g

SOA Suite 10g Fault policy definition

(3) BPEL Domains

(3) BPEL Domain properties

The parameters which can be changed in the Enterprise Manager

make a Soa Suite MDS Database connection.

SOA Suite configuration files inside the SOA Suite MDS

(2) Custom XPath and XSLT extensions