Upgrading Oracle BPEL Process Manager Applications 10-9
dspSystemThreads dspSystemThreads
The total number of threads that will be allocated to process system dispatcher messages. System dispatch
messages are general housecleaning tasks that are typically processed quickly by the server for example,
releasing stateful message beans back to the pool.
Typically, only a small number of threads are required to handle the number of system dispatch messages
generated during runtime. The 10g default value is 2 threads. Any value less than 1 thread will be changed
to the default.
expirationMaxRetry expirationMaxRetry
The maximum number of times a failed expiration call waitonAlarm will be retried before failing. If the
activity or instance the expiration call is targeting cannot be found, the call will be rescheduled again. The
10g default is 5.
expirationRetryDelay expirationRetryDelay
The amount of time in seconds to wait before rescheduling a failed expiration call. The 10g default
value is 120 seconds. instanceKeyBlockSize
instanceKeyBlockSize The size of the block of instance ids to allocate from the
dehydration store during each fetch. Instance ids for instantiated instances are pre-allocated from the
dehydration store and kept in-memory.
Once all of the in-memory instance ids have been exhausted, the next request will retrieve the next block
from the dehydration store. Generally, the higher the block size, the less impact fetching instance ids will
have on the overall performance of the engine as the cost of allocating the block is amortized over a larger
number of instances.
The only downside to a large block size is the gap between instances in a clustered installation as each
node will have its own in-memory block of instance ids and wasting instance ids if the engine is shutdown
and the block is not utilized fully. The 10g default value is 10000.
largeDocumentThreshold largeDocumentThreshold
The maximum size in bytes a BPEL variable can be before it is stored in a separate location from the rest of
the instance scope data. Large XML documents will severely impact the
performance of the entire BPEL server if they are constantly read-in and written-out whenever
processing on an instance must be performed.
By writing the variable to separate storage the performance impact is limited to times when the
variable is explicitly used in a BPEL activity. The 10g default value is 50 kilobytes.
minBPELWait minBPELWait
The minimum amount of time allowed for a BPEL wait duration. Wait times shorter than this duration will not
be respected and will essentially be skipped altogether. The 10g default value is 2 seconds.
Table 10–1 Cont. Domain Descriptor Properties in Oracle BPEL Process Manager 10g and 11g
Oracle BPEL Process Manager 10g in
domain.xml file Oracle BPEL Process
Manager 11
g MBean Property
Description
10-10 Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF
10.2.7 Upgrading Applications That Use Multiple Oracle BPEL Process Manager Domains
If you have developed and deployed your Oracle Application Server 10g BPEL projects using multiple Oracle BPEL Process Manager domains, then you should be
aware that Oracle Fusion Middleware 11g does not support multiple BPEL domains. processCheckSecs
NA The number of seconds to wait since the last time the
process container checked the bpel archive before checking it again.
By checking we mean checking the last modified time stamp on the bpel archive for a particular process; if the
specified number of seconds has passed and the bpel archive file has been modified since the last time we
checked, the process will be refreshed from the new archive. If not enough time has passed since the last
time the stale check was performed, the currently loaded process classes will be used.
To disable process checking use a value of -1; in this case once a process has been loaded the container will
never check if a newer version of the same process has been deployed. The 10g default value is 1 second. This
property is not relevant in 11g anymore as the SOA infrastructure now handles deployment via HTTP only.
statsLastN statsLastN
The size of the most recently processed request list. After each request is finished, statistics for the request
are kept in a list. A value less than or equal to 0 will disable statistics
gathering. NOTE: engine throughput may be affected slightly if this option is enabled. Please choose a
reasonable value for n 1000 is the recommended value.
syncMaxWaitTime syncMaxWaitTime
The maximum time the process result receiver will wait for a result before returning. Results from
asynchronous BPEL processes are retrieved synchronously via a receiver that will wait for a result
from the container. The 10g default value is 45 seconds.
txDatasourceJndi txDatasourceJndi moved
to soa-infra-config.xml The JNDI name for the domain transactional data
source. This data source must be configured for JTA support.
uddiLocation oracle.soa.uddi.registry.inq
uiryUrl moved to soa-infra-config.xml
The inquiry URL of the Uddi v3 compliant registry uddiPassword
oracle.soa.uddi.registry.pa ssword moved to
soa-infra-config.xml Set if UDDI is secured, password
uddiUsername oracle.soa.uddi.registry.us
ername moved to soa-infra-config.xml
Set if UDDI is secured, username validateXML
validateXML If set to true the engine will apply schema validation
for incoming and outgoing XML documents. The 10g default value false.
Table 10–1 Cont. Domain Descriptor Properties in Oracle BPEL Process Manager 10g and 11g
Oracle BPEL Process Manager 10
g in domain.xml file
Oracle BPEL Process Manager 11g MBean
Property
Description
Upgrading Oracle BPEL Process Manager Applications 10-11
If you are using multiple domains in Oracle Application Server 10g, then you have two options when you upgrade to Oracle Fusion Middleware 11g:
■
You can install and configure multiple Oracle SOA Suite Oracle WebLogic Server domains. You can then map each of your Oracle BPEL Process Manager 10g
domains to a separate Oracle WebLogic Server domain.
■
You can deploy all your Oracle BPEL Process Manager projects to a single Oracle SOA Suite Oracle WebLogic Server domain.
For more information, refer to the Oracle Fusion Middleware Installation Guide for Oracle SOA Suite and Oracle Business Process Management Suite.
10.2.8 Verifying Process ID, Project Name, and BPEL File Name Conventions Before Upgrade
Before you upgrade your BPEL projects to Oracle SOA Suite 11g, verify that the process ID in the bpel.xml file, the name of the BPEL project, and the name of the
BPEL file are all the same value. Otherwise, you might encounter errors during the upgrade of your project in Oracle JDeveloper 11g or some elements of your project
may not upgrade correctly.
10.2.9 Verifying Oracle BPEL Process Manager 11g Namespace Prefixes in XPath Functions
In some cases, XPath function namespace prefixes used in Oracle SOA Suite 10g have changed in Oracle SOA Suite 11g. As a result, if you are using an XPath function in an
upgraded application, you might encounter function not found errors.
For example, if your Oracle BPEL Process Manager application used the ora:parseXML function in 10g, you might encounter the following error:
Function of name: ora:parseXML not found. please check the spelling and try gain In this example, the namespace prefix for the parseXML function has changed to
oraext:parseXML in Oracle SOA Suite 11g. For more information, see parseXML in the XPath Extension Functions appendix of
the Oracle Fusion Middleware Developers Guide for Oracle SOA Suite.
10.2.10 Upgrading Oracle BPEL Process Manager Projects with Multiple Tasks
In Oracle SOA Suite 10g, Oracle BPEL Process Manager projects could contain multiple tasks that invoke the same partner link.
Example 10–1 shows an example of a 10g composite application that defines two tasks
that invoke the same partner link. If you attempt to upgrade such an application to 11g, Oracle JDeveloper generates errors when you attempt to compile the project.
To address the problem, you must modify the project before or after you upgrade the application in Oracle JDeveloper 11g so that each task invokes a unique partner link.
For more information, see Creating a Partner Link in the Oracle Fusion Middleware Developers Guide for Oracle SOA Suite.
Example 10–1 Oracle BPEL Process Manager 10g Project with Multiple Tasks That Use
the Same Partner Link
partnerLink myRole=TaskServiceCallbackListener name=TaskService partnerRole=TaskService
10-12 Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF
. .
. invoke name=initiateTask_MainTask_1 partnerLink=TaskService
portType=taskservice:TaskService operation=initiateTask
inputVariable=initiateTaskInput outputVariable=initiateTaskResponseMessage
correlations correlation initiate=yes set=WorkflowTaskIdCor
pattern=in correlations
invoke .
. .
invoke name=initiateTask_SubTask_1 partnerLink=TaskService
portType=taskservice:TaskService operation=initiateTask
inputVariable=initiateTaskInput outputVariable=initiateTaskResponseMessage
. .
. invoke
11
Upgrading Oracle Business Activity Monitoring Applications 11-1
11
Upgrading Oracle Business Activity Monitoring Applications
This chapter provides important supplementary information upgrading Oracle SOA applications to Oracle Fusion Middleware 11g.
Use Chapter 8, Overview of Upgrading Oracle SOA Suite, WebCenter, and ADF
Applications for the tasks required to upgrade any Oracle SOA Suite, WebCenter, and
ADF application. Refer to the following sections for information on upgrade tasks associated with
Oracle Business Activity Monitoring:
■
Migrating Oracle BAM Users, Groups, and Other LDAP Information to 11g
■
Verifying Oracle BAM Action Form Templates After Upgrade
■
Upgrading Oracle BAM External Data Sources
■
Upgrading Images in Oracle BAM Reports
■
Using Oracle BAM Web Services in 11g
■
Upgrading Oracle BAM Sensor Actions
■
Upgrading Enterprise Link Plans to Oracle BAM 11g
■
Additional Considerations When Upgrading to Oracle BAM 11g
11.1 Migrating Oracle BAM Users, Groups, and Other LDAP Information to 11g
In general, after upgrade of the Oracle BAM schema, any Oracle BAM 10g users will appear in the Oracle BAM Administrator as inactive if they dont exist in the Oracle
Fusion Middleware 11g security provider. However, you can use Oracle BAM Administrator software to remap 10g users to new Oracle BAM 11g users.
For more information, see Managing Oracle BAM Object Ownership, in Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle Business Process
Management Suite.
After upgrade, you might need to address the following for users and groups:
■
Reset any Shared Folder permissions
■
Reset any Data Object and Data Object folder permissions
■
Reset any Distribution Lists
■
Reset Security Filters
