Skip Headers
Oracle® Fusion Middleware Administrator's Guide for Oracle SOA Suite and Oracle Business Process Management Suite
11g Release 1 (11.1.1.6.3)

Part Number E10226-16
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
PDF · Mobi · ePub

Index

A  B  C  D  E  F  G  H  I  J  L  M  N  O  P  Q  R  S  T  U  V  W  X 

A

abort
recovery action, 8.4, 8.5, 13.1, 14.1, 14.3, 17.1, 17.3
actionable email account, 20.2
configuring, 20.1
activating
a composite revision, 7.4.1, 7.4.2
activation specification
definition, 34.1.2
active data cache
monitoring, 24.2.1
activities
configuring for automatic recovery, 12.2
for BPEL 2.0 in process flows and audit trails, 13.1.2
activity message types
Message State list is not applicable, 14.4
adapters
See Oracle Adapters
addresses
configuring multiple send addresses, 20.7
administration tasks
for application developers, 1.5
administrator
role, C.1
ant
creating partitions, 7.8.1
deployment, 7.1.2
application developer
administration tasks, 1.5
application policies
creating, 2.2.1
application roles
creating, 2.2.1
demo user community, A.4
managing in Oracle Enterprise Manager, 20.10.4
Oracle Business Activity Monitoring (BAM), 25.3.4
seeding with WLST scripts, 20.10.3
assertions
definition, 1.4.3.4, 7.5
AsynchAuditBatchSize property
storing multiple audit trail messages in a single transaction, 12.1
audit level
BPEL process service engine, 12.1
BPMN process service engine, 37.1
configuring to display adapter header properties, 34.1
generating orphaned service component instances, 8.2
impact of disabling audit tracking across multiple composite flows, 7.4.2
order of precedence of execution, 1.4.1.1, 7.4.2
overriding the audit level defined at the SOA Infrastructure level, 7.4.2
relation to partitioning the COMPOSITE_INSTANCE table, 9.4.3.1
setting at the BPEL process service component level, 12.5
setting at the SOA composite application level, 7.4.2
SOA composite application, 7.4.2
SOA Infrastructure, 3.1
audit tracking
order of precedence of execution, 1.4.1.1
audit trail
configuring the storage in one transaction, 14.5.4
for BPEL 2.0 projects, 13.1.2
monitoring a BPEL process service component, 13.1
not generated when composite audit level is off, 1.4.1.1
not supported for spring service component, 1.2.4
rolled back transaction error message, 13.1
sensors, 13.1, 38.1
threshold setting, 12.1
viewing for a BPMN process service component, 38.1
audit trail threshold, 37.1
AuditConfig property, 3.1
bpelRecoveryStatus, 4.1, 13.1
excludeBpelMaxCreationTime key, 4.1, 8.2, 8.3
authentication providers
adding, 20.9.1
automatic recovery
configuration, 12.2
in clustered environments, 12.2
is not recovering a specific BPEL instance, B.3.2
automatic release timers
globally disabling for Oracle BPM Worklist, 20.5
automating
the testing of SOA composite applications, 7.5

B

B2B See Oracle B2B
backup, 1.4.3
BAM
See Oracle Business Activity Monitoring
binding components
can only publish web services to the UDDI registry, 36.2
configuring, 34, 34.1
configuring adapters, 34.1.2
configuring the publishing of web services to UDDI, 36.2.1
configuring web services, 34.1.1
definition, 1.2.5
direct binding, 35.1
endpoint properties, 34.1.2.8
faults, 35.1
impact when a composite is shut down, 7.4.1, 7.4.2
instances, 35.1
limitation on policy attachment errors for service binding components, 36.1
limitation on policy attachments, 36
limitation on publishing references to the UDDI registry, 36.2
managing, 36
monitoring, 4.3, 35
monitoring instances and faults, 35.1
monitoring rejected messages, 35.2
Oracle AQ Adapter properties, 34.1.2.1
Oracle AQ Socket properties, 34.1.2.7
Oracle Database Adapter properties, 34.1.2.2
Oracle File Adapter properties, 34.1.2.3
Oracle FTP Adapter properties, 34.1.2.4
Oracle JMS Adapter properties, 34.1.2.5
Oracle MQ Series Adapter properties, 34.1.2.6
policies, 36.1
properties, 34.1
publishing to the UDDI registry, 36.2
references, 1.2.5
rejected messages, 35.2
restrictions on specifying multiple bindings, 36
services, 1.2.5
BPEL 2.0
audit trail, 13.1.2
behavior of activity sensors in compensate and compensateScope activities, 13.4.1
process flow, 13.1.2
BPEL process service components
audit trail and process flow, 13.1
configuring, 12
defining a fault policy, 1.4.3.1
definition, 1.2.4
fault recovery, 14.1
faults, 13.2, 14.1
instance states remain as completed even if the composite instance state becomes stale, 7.2
instances, 13.2, 13.3
limitations on selecting the option to continue instances upon redeployment, 7.2
managing, 14
monitoring, 13, 13.3
policies, 14.2
recovery message information displayed in the Flow Trace page, 13.1
sensor data, 13.4
BPEL process service engines
audit level, 12.1
configuring, 12
deployed processes, 13.8, 16.3.4
fault recovery, 14.3
faults, 13.5, 14.3
instances, 13.5, 13.7
managing, 14
message failure and recovery, 14.4
monitoring, 13
monitoring faults, 13.5
monitoring instances, 13.5
payload validation, 12.1, 37.1
request and thread statistics, 13.6
BPEL processes
automatic recovery configuration, 12.2
automatic recovery in cluster environments, 12.2
setting the instance name during design time, 7.4.4
starting and stopping a managed server on which the SOA Infrastructure is deployed in the middle of BPEL processing, 7.4.3
BPEL sensors
disabling at the service engine level, 12.1
disabling at the SOA composite application level, 7.4.2
order of precedence for setting, 7.4.2
BPMN process service components
audit trail and process flow, 38.1
behavior of instances after redeployment, 7.2
fault recovery, 39.1
faults, 38.2, 39.1
instances, 38.2, 38.3
monitoring, 38
policies, 39.2
selecting the option to continue instances upon redeployment, 7.2
BPMN process service engines
audit level, 37.1
deployed processes, 38.7
fault recovery, 39.3
faults, 38.4, 39.3
instances, 38.4, 38.6
message failure and recovery, 39.4
monitoring, 38
request and thread statistics, 38.5
browsers
Copy details to clipboard link does not appear with Mozilla Firefox, 13.1
limitation on using the Safari Browser to view WSDL file content, B.8.1
supported, 2.1
bulk recovery
cannot perform bulk fault recovery on the Faults tab of a flow trace, 13.1
of faults, 8.4, 8.5
business event messages
cannot be recovered, 8.4, 8.5
business events
BPEL component in a retired composite cannot receive a business event, 33.3
consistency levels, 33.2
database agent subscriptions, 33.2
definition, 33
events consumed by multiple revisions of the same composite, B.5.3
fault recovery, 33.4
faults, 33.4
managing, 33
messages are lost between EDN and composites or composites across clusters, B.5.5
pausing the delivery of events, B.5.1
picked up twice or more by the SOA server, B.5.4
policies on event subscriptions are not supported, 33.2
receiving events in a composite with multiple revisions, 33.3
rolled back OAOO event messages appear in the log files, B.5.2
service component subscriptions, 33.2
setting the number of retries, B.5.1
subscribers, 33.3
subscribing to, 33.2
troubleshooting, B.5
tuning event delivery, B.5.1
business faults, 1.4.3.1
business monitors
BPEL monitors, 7.9
BPEL sensors, 7.9
BPMN measurements, 7.9
enabling and disabling, 7.9
setting the status level for all sensors, 7.9
business rule execution tracing, 19.7
audit levels, 19.7
development level, 19.7.1
production level, 19.7.2
business rule messages
cannot be recovered, 8.4, 8.5
business rules
engine cache and operation statistics, 19.2
monitoring, 19
business rules service engines
deployed components, 19.5
faults, 19.4
instances, 19.3

C

callback messages
configuring automatic recovery attempts, 12.4
configuring unresolved messages for automatic recovery, 12.2
performing manual message recovery, 14.4
recovering in resolved and undelivered states, 14.4
stranded, 14.4
callback server URL
property, 3.1
property change requires a restart, 3.1
capture composite instance state
displaying created instances immediately even if a constraint is defined, 7.4.2
if disabled, the Recent Instances section does not show instances requiring fault recovery as running, 6.1
impact of creating a new instance when this property is disabled, 3.1
meaning of ? icon, 8.2
property, 3.1
case agnostic group names
enabling in human tasks, 20.11
chunking
enabling data checking for SOAP over HTTP deliveries, 3.1
specifying a chunk size, 3.1
clusterDbTimeRefresh property
definition, 12.3
clusters
automatic recovery of BPEL processes, 12.2
configuring master node recovery, 12.3
component tables
partitioning, 9.4
composite sensors
audit trail, 13.1, 38.1
searching for, 8.2
composite URLs
editing, 8.1
configuration plan
selecting in the Deploy SOA Composite wizard, 7.1
consistency levels
of business events, 33.2
continue
recovery action, 8.4, 8.5, 13.1, 14.1, 14.3, 17.1, 17.3
conversation ID
creating on the Test Web Service page, 1.2.3
definition, 1.2.3
generating, 1.2.3
not creating on the Test Web Service page, 1.2.3
Copy details to clipboard link
does not appear with Mozilla Firefox, 13.1
cross references
Oracle Mediator, 18
custom drivers
changing the driver name, 3.5

D

data sources
creating and managing for adapters in Oracle WebLogic Server Administration Console, 2.2.5
definition, 3.1
managing SOA Infrastructure data sources from Oracle WebLogic Server Administration Console, 2.2.5
properties, 3.1
database connections
resolving slow connections, B.2.2
database growth
delete before purging large amounts of data, then add the indexes back in, 9.3.2
developing a purging and partitioning methodology, 9.2
executing the purge scripts, 9.3.6
instance purging states, 9.3.3
looped purge in parallel script, 9.3.2
looped purge script, 9.3.1
management, 9
managing with the purge script, 9.3
moving long running instances to a different partition, 9.4.6
partial partitioning of components, 9.4.7
purge scripts are only supported on Oracle databases, 9.3
purge scripts supported on different Oracle SOA Suite releases, 9.3
purge scripts to run when upgrading, 9.3
purging the instances of a specific SOA composite application, 9.3.5
referential integrity and equipartitioning, 9.1.2.1
resequenced message purge states for Oracle Mediator, 9.3.4
resolving issues caused by high transaction volume, B.6.5
selecting the schema partition keys, 9.1.2.2
database schemas
components with, 9.1.2
purge scripts are only supported on Oracle databases, 9.3
reducing the size of, 9.2
database tables
partitioning, 9.1.2
decision service components
definition, 1.2.4
deployed components, 19.5
faults, 19.4
instances, 19.6
log files, 19.8
monitoring, 19
statistics, 19.2
decision tracing
See business rule execution tracing
default composite revision
distinguishing the default revision from other revisions, 1.4.3.3, 7.4.1, 7.4.1
impact of retiring, 7.4.1, 7.4.1
impact of undeploying, 7.4.1, 7.4.1
impact of undeploying when no other active, available revisions exist, 7.3, 7.4.1
retiring, 7.4.1
setting, 7.4.1
undeploying, 7.3
undeploying causes the next active, available revision to become the default, 7.3
Delete Rejected Messages option
when to use, 8.6, 8.7
demo user community, A
definition, A.1
groups, A.3
installing in the database, A.1
must run the installation script locally in a domain, A.1
organizational hierarchy, A.2
permissions defined in the WorkflowPermission class, A.7
roles granted to and owned by users, A.6
soa-infra application roles, A.4
SOATestDemoApp application roles, A.5
users, A.2
deployment
ant, 7.1.2
composites with task flows, 7.1.1
exporting a deployed SOA composite application, 7.7
from SSO-enabled Oracle Enterprise Manager Fusion Middleware Control, 7
guidelines, 7.1
issues with deploying the same composite with a human workflow into multiple partitions, 7.1
lifecycle states, 7.4
managing the state of deployed composites, 7.4.1, 7.4.2
of SOA composite applications, 7.4.1
restrictions on cross references between composites, 7.1
revisions of different composites, 7.1
selecting partitions, 7.1
SOA composite applications, 7.1
using the Redeploy SOA Composite wizard to redeploy an existing instance, 7.1
WLST, 7.1.2
Diagnostic Framework
definition, 11.1.2
diagnostics
frameworks, 11.1
getting dump descriptions, 11.1.4
incident processing rules, 11.1.3
listing the supported dumps, 11.1.4
manually executing dumps, 11.3
notification creation, 11.2
notifications, 11.1.1.1
querying problems and incidents, 11.5
supported database diagnostic dumps, 11.1.4.3
supported deployed composite metadata diagnostic dumps, 11.1.4.4
supported deployed composite WSDL/schema cache diagnostic dumps, 11.1.4.7
supported diagnostic scenarios and MBeans, 11.1.1.2
supported event diagnostic dumps, 11.1.4.6
supported instance audit trail diagnostic dumps, 11.1.4.5
supported runtime environment diagnostic dumps, 11.1.4.1
supported runtime platform configuration diagnostic dumps, 11.1.4.2
supported SOA dumps, 11.1.4
using Diagnostic Framework, 11.1.2
using WLDF, 11.1.1
viewing incident packages, 11.4
watch creation, 11.2
watches, 11.1.1.1
direct binding
cannot configure properties for, 34
definition, 35.1
monitoring, 35.1
no policies and properties tabs are available, 35.1
Direct Binding Invocation API
inbound invocations of composites and outbound invocations of Oracle Service Bus (OSB), 10.1
direct Java invocations
using, 3.7
Disable Alert link
definition, 4.1, 6.1
dispatcher engine threads, 12.1, 37.1
dispatcher invoke threads, 12.1, 37.1
dispatcher system threads, 12.1, 37.1
distributed cache
storing instance and callback message data, 14.5
distribution lists
Oracle Business Activity Monitoring (BAM), 23.6
downloading
the deployable JAR file, 7.7
drivers
configuring, 26.4
deploying Oracle User Messaging Service, 28.1
deploying with Oracle Enterprise Manager Fusion Middleware Control, 28.1.2
deploying with Oracle Fusion Middleware Configuration Wizard, 28.1.3
deploying with WLST, 28.1.1
deploying with wsadmin, 28.1.4
email driver, 26.4.1.4
messaging extension driver, 26.4.1.3
properties, 26.4.1.1
proxy driver, 26.4.1.9
securing driver properties with passwords, 26.4.1.2
SMPP driver, 26.4.1.5
undeploying, 28.2
unregistering, 28.2
VoiceXML driver, 26.4.1.7.1
worklist driver, 26.4.1.8
XMPP driver, 26.4.1.6
dumps
getting descriptions of, 11.1.4
listing the supported dumps, 11.1.4
manually executing, 11.3
supported database diagnostic dumps, 11.1.4.3
supported deployed composite metadata diagnostic dumps, 11.1.4.4
supported deployed composite WSDL/schema cache diagnostic dumps, 11.1.4.7
supported event diagnostic dumps, 11.1.4.6
supported instance audit trail diagnostic dumps, 11.1.4.5
supported runtime environment diagnostic dumps, 11.1.4.1
supported runtime platform configuration diagnostic dumps, 11.1.4.2
supported with Oracle SOA Suite, 11.1.4
durable BPEL processes
definition, 7.2
limitations on selecting the option to continue instances upon redeployment, 7.2
durable processes
definition, B.5.5
dynamic assignments, 20.2
functions, 20.2

E

ECIDs
adding an index on the DLV_MESSAGE.ECID column to improve SQL performance when searching messages for a specific ECID, 14.4
copying from the Warning dialog on the Flow Trace page, 13.1
definition, 13.1, 14.4, 38.1
restrictions, 13.1, 38.1
searching for, 8.2, 8.3
specifying when creating a message recovery search criteria, 14.4
EJB transaction timeouts
updating, B.2.3
email addresses
configuring the outgoing email address, 20.1
configuring the Reply To address, 20.1
correcting, 22.5
email driver
client API, 26.4.1.4.4
common properties, 26.4.1.4.2
configuring, 26.4.1.4
custom properties, 26.4.1.4.3
interoperability, 26.4.1.4.1
email notification messages
configuring the number of, 20.6
email server
adding the hostname and IP address to the /etc/hosts file, 20.1
IMAP, 20.1
SMTP, 20.1
emulations, 1.4.3.4
endpoint addresses
displaying the addresses of all external services, 7.4.2
endpoint properties
definition, 34.1.2
inbound adapters, 29.1
outbound adapters, 29.2
endpoint reference
changing for Oracle Service Registry, 34.1.3
endpoint URLs
editing, 8.1
specifying during instance creation, 8.1
engine cache and operation statistics
for business rules, 19.2
enterprise message sources, 24.2.4
equipartitioning
definition, 9.1.2.1
event definition language
definition, 33.2
Event Delivery Network
definition, 33.1
EDN-DB, 33.1
EDN-JMS, 33.1
event engine
monitoring, 24.2.2
exhausted messages
resetting to the undelivered state, 14.4
exhausted state
definition, 14.4
message recovery, 14.4
exporting
a deployed SOA composite application, 7.7

F

Facade API
examples, 10.3
finding composite and component instances, 10.3.2
oracle.soa.management.facade.Locator interface, 10.1
overview of interfaces, 10.2
programmatically managing SOA composite applications, 10.1
retrieving the state of a composite, 10.3
top level entry point, 10.1
Farm home page
navigating to Oracle SOA Suite pages, 2.2.6
fault policy, 8.4
creating, 1.4.3.1, 8.4.1, 8.4.2, 8.4.3, 8.5
defining, 8.4
definition, 1.4.3.1
required for BPEL process fault recovery, 1.4.3.1
Fault Time From field, 3.1
faults
automatic recovery configuration, 12.2
automatic recovery configuration for invoke and callback messages, 12.4
automatic recovery in clustered environments, 12.2
binding components, 35.1
BPEL process service component fault recovery, 14.1
BPEL process service engine fault recovery, 14.3
BPMN process service component fault recovery, 39.1
BPMN process service engine fault recovery, 39.3
bulk recovery, 8.4, 8.4, 8.5
bulk recovery at SOA Infrastructure level does not permit a check of composite states, 8.4
business events, 33.4
business events fault recovery, 33.4
business fault definition, 1.4.3.1
business rules service engines, 19.4
example of bulk-fault recovery for BPEL processes, 8.4.1.2
example of bulk-fault recovery for BPMN processes, 8.4.2.2
example of bulk-fault recovery for Oracle Mediator, 8.4.3.2
example of single-fault recovery for BPEL processes, 8.4.1.1
example of single-fault recovery for BPMN processes, 8.4.2.1
example of single-fault recovery for Oracle Mediator, 8.4.3.1
examples of BPEL process fault recovery, 8.4.1
examples of BPMN process fault recovery, 8.4.2
examples of nonrecoverable faults, 1.4.3.1
examples of Oracle Mediator fault recovery, 8.4.3
examples of recoverable faults, 1.4.3.1
human workflow fault recovery, 22.2, 22.4
human workflow service components, 21.1, 22.4, 22.4
human workflow service engines, 21.4, 22.2
in audit trail, 13.1, 38.1
inbound adapters, 30.1
options for single-fault recovery, 8.4
Oracle Mediator, 17.1, 17.3
Oracle Web Service Manager fault definition, 1.4.3.1
outbound adapters, 30.5, 30.6, 30.7
recovery, 1.4.3.1, 8.4
recovery actions, 8.4, 8.5
recovery of SOA composite application faults, 4.1, 6.1
SOA composite application fault recovery, 8.5
SOA Infrastructure, 8.4
SOA Infrastructure fault recovery, 8.4
system fault definition, 1.4.3.1
types, 1.4.3.1
File Adapter logs, 30.9
flow traces
canceled onMessage branches are not displayed, 13.1
for composite-to-composite invocations on multiple servers, 13.1.1
impact when instance tracking is disabled, 7.4.2
issues viewing on lower end hosts, B.7.4
viewing faults, 13.1
viewing sensors, 13.1
functions
restrictions on adding multiple properties to a function, 20.2

G

Go to BPEL Recovery Console link
definition, 4.1, 6.1
governance
definition, 1.4.3.3
Gridlink
definition, 1.4.3
group names
enabling case agnostic group names in human tasks, 20.11
groups
demo user community, A.3
partitioning, 9.4.3.2
seeding with LDAP tools, 20.10
GUID attribute
mapping requirements, 20.9.3

H

heartBeatInterval property
definition, 12.3
HTTP binding
cannot change httpBinding property, 34
human workflow
configuring Oracle HTTP Server for task form attachments, 20.3
deploying composites with task flows, 7.1.1
faults not persisted in the dehydration store, 8.4, 8.5
moving data from a test to a production environment, 22.6
notification properties, 20.1
notifications, 22.5
prerequisites for configuring notification properties, 20.1
task service properties, 20.2
task status, 21.2
troubleshooting, B.4
troubleshooting AMX extension issues, B.4.14
troubleshooting design time at runtime issues, B.4.10
troubleshooting human workflow API usage issues, B.4.11
troubleshooting identity service issues, B.4.17
troubleshooting notification issues, B.4.3
troubleshooting Oracle BPM Worklist/task region issues, B.4.15
troubleshooting Oracle JDeveloper data control/form generation issues, B.4.12
troubleshooting service/System MBean Browser issues, B.4.13
troubleshooting task action issues, B.4.2
troubleshooting task assignment, routing, and escalation issues, B.4.1
troubleshooting task comments/attachment issues, B.4.9
troubleshooting task form/action issues, B.4.8
troubleshooting task history issues, B.4.7
troubleshooting task mapping attribute issues, B.4.5
troubleshooting task report issues, B.4.6
troubleshooting task view issues, B.4.4
troubleshooting test-to-production issues, B.4.16
WSDL files security, 5.7
human workflow service components
configuring, 20
definition, 1.2.4
fault recovery, 22.4
faults, 21.1, 22.4
instances, 21.1, 21.3
managing, 22
monitoring, 21
performing fault recovery from Oracle BPM Worklist, 1.4.3.1, 8.4
policies, 22.1
recommendation not to use oracle/wss10_saml_token_service_policy in a production environment, 22.1
URI of task details application, 22.3
human workflow service engines
configuring, 20
deployed workflows, 21.7
fault recovery, 22.2
faults, 21.4, 22.2, 22.4
instances, 21.4, 21.6
managing, 22
monitoring, 21
requests and operation statistics, 21.4, 21.5

I

identity service
customizing the provider, 20.9.4
GUID attribute mapping requirements, 20.9.3
third-party providers, 20.9
IMAP email server
configuring, 20.1
IMAP server
restarting the SOA server after configuring, 20.1
incident packages
creating, 11.1.2
viewing, 11.4
indexes
recommendation to delete before purging large amounts of data, then add the indexes back in, 9.3.2
indexing
LDAP attributes, 20.9.2.2
instance and callback message data
storing in Oracle Coherence distributed cache, 14.5
instance and fault metrics pages
disabling in the System MBean Browser, 3.1.1
disabling the retrieval of instance and fault count metrics, 3.1, 3.1, 3.1, B.6.1
optimizing the loading of, 3.1, 3.1, 3.1, B.6.1
setting a default search criteria to fetch recent instances and faults only within a recent duration, 3.1
instance ID
creating, 1.2.3, 8.2
displayed in the SOA composite application Instances page, 1.2.4
for BPEL process service components, 13.3
for service components, 1.2.4
for SOA composite applications, 1.2.3
instance names
setting during design time, 7.4.4
instance states, 3.1
definition, 3.1
filtering by execution state, 8.2, 8.3
filtering by fault state, 8.2, 8.3
filtering by recovery state, 8.2, 8.3
for composites in which one BPEL process is completed and another is faulted, 8.2.2
meaning of the ? icon, 8.2
of BPEL process service component remain as completed even if the composite instance state becomes stale, 7.2
of service components and SOA composite applications, 8.2.2
scenarios under which the state is not evaluated, 8.2
instance tracking
impact of disabling audit tracking across multiple composite flows, 7.4.2
impact on flow traces when tracking is disabled, 7.4.2
instances
behavior of service component instances after redeployment, 7.2
binding components, 35.1
business rules service engines, 19.3
capturing the composite instance state, 3.1
clicking the refresh icon to view the actual number of total instances, 7.4.2
decision service components, 19.6
deleting at the SOA Infrastructure level, 8.3, 8.3
deleting from a composite application home page, 8.2, 8.2
deleting large numbers of, 9.3
deleting running, rolled back instances, 8.2, 8.3
deleting with the looped purge in parallel script, 9.3.2
deleting with the looped purge script, 9.3.1
displaying created instances immediately even if a constraint is defined, 7.4.2
distinguishing unit test instances from other instances, 1.2.3, 7.5
executing the purge scripts, 9.3.6
finding composite and component instances programmatically, 10.3.2
human workflow service components, 21.1, 21.3
human workflow service engines, 21.4, 21.6
inbound adapters, 30.1
initiating a test instance, 7.4.2, 8.1
invoking multiple instances, 8.1
keeping current BPM composite instances running after redeployment, 7.2
limitations on selecting the option to continue instances upon redeployment, 7.2
mismatch between composite instances and service component instances, 8.2.1
monitoring BPEL process service component instances, 13.3
moving long running instances to a different partition, 9.4.6
orphaned service component instances, 8.2
outbound adapters, 30.5
passing security properties with messages during testing, 8.1
possible reasons for redeployment failure, 7.2, 7.2
purging the instances of a specific SOA composite application, 9.3.5
scenarios in which the Test button is disabled, 8.1
service components, 1.2.4
setting the instance name during design time, 7.4.4
SOA composite applications, 1.2.3
specific BPEL instance is not being recovered, B.3.2
specifying the XML payload data during testing, 8.1
states, 3.1
states for purging, 9.3.3
statistics
Oracle Mediator, 16.2.2
terminating, 8.2
Test button is disabled when a composite is stopped or retired, 7.4.2
throughput details, 13.2
WSDL URL that does not contain the revision number is processed by the default composite, 8.1
instant messaging
messages are not actionable, 20.1
interaction specification
definition, 34.1.2
invocations
direct binding, 3.7
invoke messages
configuring automatic recovery attempts, 12.4
configuring unresolved messages for automatic recovery, 12.2
performing manual message recovery, 14.4
situations in which the Last Modified Date column remains empty, 14.4
invoked decision function, 19.7.1
invoked decision service, 19.7.1
IPv4 support, B.7.5
IPv6 support, B.7.5

J

JAR files
downloading the deployable JAR file, 7.7
Java EE applications
navigating through, 2.2.4
JCA Adapters
See Oracle Adapters
JMS sensors
values are not displayed, 13.4

L

large document threshold, 37.1
setting a, 12.1
LDAP attributes
indexing recommendations, 20.9.2.2
LDAP tools
seeding users, groups, and application roles, 20.10
LDAP user profile
configuring for Oracle User Messaging Service (UMS), 26.5
lifecycle
of SOA composite applications, 1.4.3.3, 7.4
performing bulk lifecycle management tasks in partitions, 7.8.2
local optimization
calls when a composite is unreachable, 3.7.4
condition checks for using, 3.7
configuring, 3.7, 7.6.2
forcing the use of, 3.7.2
overriding, 3.7.2
viewing the local optimization setting for policies, 7.6.2
Locator
entry point for Facade API clients, 10.1, 10.2
log files
accessing, 2.2.1
configuring, 3.4
decision service components, 19.8
encoding property, 3.4.1
from all managed servers, B.1.1
Oracle Business Activity Monitoring (BAM), 24.6
Oracle User Messaging Service (UMS), 27.2, 27.2
log levels
setting for troubleshooting, B.1
log tracing, B.1
loggers
deployment, B.1
Event Delivery Network (EDN), B.1
human workflow/approval management extensions (AMX)/rules, B.1
Oracle Adapters, B.1
Oracle B2B, B.1
Oracle BPEL Process Manager, B.1
Oracle BPM Suite, B.1
Oracle Business Activity Monitoring (BAM), 23.4
Oracle Mediator, B.1
Oracle User Messaging Service (UMS), 27.2.1
Oracle Web Services Manager (OWSM), B.1
SOA Infrastructure, B.1
logging in
to Oracle Enterprise Manager Fusion Middleware Control, 2.1
logging out
of Oracle Enterprise Manager Fusion Middleware Control, 2.3
looped purge in parallel script
deleting instances with, 9.3.2
looped purge script
deleting instances with, 9.3.1

M

managed servers
starting and stopping, B.7.1
managing database growth, 9
mark cancelled
message recovery action, 14.4
masteAliveThreshold property
definition, 12.3
master nodes
recovering, 12.3
maxMessageRaiseSize property
definition, 12.2, 12.2
MDS connections
managing, 2.2.1
Mediator
See Oracle Mediator
message recovery
adding an index on the DLV_MESSAGE.ECID column to improve SQL performance when searching messages for a specific ECID message, 14.4
exhausted state, 14.4
filtering the display of instances by whether or not they are recoverable, 8.2, 8.3
in BPEL process service engines, 14.4
in BPMN process service engines, 39.4
managing failed automatic recovery attempts, 14.4
mark cancelled action, 14.4
Message States list not applicable to activity message types, 14.4
obtaining the ECID value for message recovery, 13.1, 14.4
recover action, 14.4
recovering callback messages in resolved and undelivered states, 14.4
recovery message information displayed in the Flow Trace page, 13.1
recovery message information displayed in the SOA Infrastructure home page, 4.1
recovery message information displayed on the SOA composite application home page, 1.2.1, 6.1
recovery options, 14.4
reset action, 14.4
resynchronizing lost, in-memory, Quartz-scheduled jobs, 14.4
situations in which the Last Modified Date column remains empty, 14.4
stranded callback messages, 14.4
message sources, 24.2.4
messaging extension driver
client API, 26.4.1.3.5
common properties, 26.4.1.3.2
configuring, 26.4.1.3
custom properties, 26.4.1.3.3
driver application archive (EAR), 26.4.1.3.1
extension driver security, 26.4.1.3.4
using, 26.4.1.3.6
migration
of human workflow data from a test to a production environment, 22.6
monitor
role, C.1
Mozilla Firefox
Copy details to clipboard link does not appear, 13.1
MTOM attachments
attaching to outbound web services, 34
multiple instances
invoking, 8.1
multiple send addresses
configuring, 20.7

N

nodeReapInterval property
definition, 12.3
nodeReapThreshold property
definition, 12.3
nodes
recovering, 12.3
nonfatal connection
specifying a retry count, 3.1
notification service
pluggable, 20.4
notifications
actionable addresses, 20.1
configuration modes, 20.1
configuring the number of email notification messages, 20.6
configuring the outgoing email address, 20.1
configuring the Reply To address, 20.1
creating, 11.2
human workflow
incoming email, 22.5
outgoing, 22.5
properties, 20.1
prerequisites for configuring, 20.1
restarting the server after IMAP and SMTP email server configuration, 20.1
sender and default sender addresses must match values on the Workflow Notification Properties page, 20.1

O

operator
role, C.1
optSoapShortcut
SOAP optimization is automatically configured in 11g, 3.1
Oracle Adapters
configuring, 29
configuring binding components, 34.1.2
deployed resource adapters, 2.2.4
endpoint properties, 34.1.2.8
inbound adapters, 29.1
outbound adapters, 29.2
faults
inbound adapters, 30.1
outbound adapters, 30.5, 30.6, 30.7
File Adapter logs, 30.9
in multiple revisions of SOA composite applications that include an inbound adapter are displayed as running, 8.2
instances
inbound adapters, 30.1
outbound adapters, 30.5
monitoring, 30
Oracle AQ Adapter properties, 34.1.2.1
Oracle Database Adapter properties, 34.1.2.2
Oracle File Adapter properties, 34.1.2.3
Oracle FTP Adapter properties, 34.1.2.4
Oracle JMS Adapter properties, 34.1.2.5
Oracle MQ Series Adapter properties, 34.1.2.6
Oracle Socket Adapter properties, 34.1.2.7
properties
inbound adapters, 30.4
outbound adapters, 30.8
rejected messages
inbound adapters, 30.2, 30.3
Oracle AQ Adapter
properties, 34.1.2.1
Oracle B2B
accessing from Oracle Enterprise Manager Fusion Middleware Control, 32.2
bindings, 32
configuring, 31
database tables are not deleted by the Oracle SOA Suite purge scripts, 9.3
foreign key constraints must be disabled before dropping the partition, 9.4.5
infrastructure monitoring, 32.1
metrics, 31.1
monitoring, 32, 32
server properties, 31
Oracle BAM adapter
configuring, 23.7
configuring HTTPS, 23.7.2.1
configuring to retry sending messages, 23.7.1.1
Oracle BPM Worklist
configuring with Oracle HTTP Server, 5.2
globally disabling automatic release timers, 20.5
performing fault recovery from, 1.4.3.1
performing human workflow service component fault recovery, 8.4
Oracle Business Activity Monitoring (BAM)
adding members to application roles, 25.3.3
adding users in Oracle BAM Administrator, 25.3.6
application roles, 25.3.4
availability management, 25.2
calling web services, 23.9.6
configuration property files, 23.10
configuration property reference, 23.11
configuring, 23
configuring advanced properties, 23.10
configuring credential mapping, 23.7.4, 23.9.1
configuring distribution lists, 23.6
configuring Oracle BAM adapter, 23.7
configuring Oracle BAM batching properties, 23.8
configuring Oracle BAM connection factories, 23.7.2
configuring Oracle Data Integrator integration properties, 23.3.6
configuring Oracle User Messaging Service (UMS), 23.5
configuring server basic properties, 23.3
configuring SSL, 23.9.3
configuring the application URL, 23.2.2, 23.3.3
configuring the data source JNDI, 23.3.2
configuring the embedded LDAP server, 25.3.5
configuring the logger, 23.4
configuring the outbound email account, 23.3.7
configuring the report cache persistence manager, 23.3.5
configuring the report loading indicator, 23.2.3
configuring the server name, 23.2.4
configuring trusted domains, 23.7.3
configuring user permissions, 23.9.2
configuring viewset sharing, 23.3.4
configuring web applications properties, 23.2.1
configuring web basic properties, 23.2
defining users and groups, 25.3.1
managing, 25
managing object ownership, 25.3.7
monitoring, 24
monitoring logs, 24.6
monitoring open connections, 24.3.2
monitoring Oracle BAM active data cache, 24.2.1
monitoring performance, 24.5
monitoring the client requests in progress, 24.2.5
monitoring the enterprise message sources, 24.2.4
monitoring the event engine component, 24.2.2
monitoring the report cache component, 24.2.3
monitoring the report server, 24.3.1
monitoring web applications, 24.3
monitoring web services, 24.4
removing invalid users from Oracle BAM Administrator, 25.3.8
securing, 23.9
securing JMS resources, 23.9.5
user management, 25.3
using Oracle Internet Directory, 23.9.4
using previously seeded group members, 25.3.2
Oracle Business Process Management Suite
administration, 1.4
configuration, 1.4.1
definition, 1.3
management, 1.4.3
monitoring, 1.4.2
service components, 1.2.4
Oracle Coherence
definition, 14.5
Oracle Coherence distributed cache
architecture, 14.5.1
availability requires use of Oracle Exalogic, 14.5
configuring in the System MBean Browser, 14.5.3
configuring the storage of multiple audit trail messages in one transaction, 14.5.4
performance recommendations, 14.5.2
starting the data grid nodes, 14.5.5
storing instance and callback message data, 14.5
Oracle Data Integrator
configuring with Oracle Business Activity Monitoring (BAM), 23.3.6
Oracle Database Adapter
properties, 34.1.2.2
Oracle Enterprise Manager Fusion Middleware Control
accessing Oracle B2B, 32.2
deploying drivers, 28.1.2
logging in, 2.1
logging out, 2.3
Oracle Exalogic
definition, 14.5
Oracle Exalogic platforms
setting the AsynchAuditBatchSize property, 12.1
storing instance and callback message data in Oracle Coherence distributed cache, 14.5
Oracle File Adapter
properties, 34.1.2.3, 34.1.2.4
Oracle Fusion Middleware, 1.1
Oracle Fusion Middleware Configuration Wizard
deploying drivers, 28.1.3
Oracle HTTP Server
configuring Oracle SOA Suite and Oracle HTTP Server for SSL communication, 5.6.6
configuring with Oracle BPM Worklist, 5.2
Oracle Internet Directory
using with Oracle Business Activity Monitoring (BAM), 23.9.4, 23.9.4
Oracle JMS Adapter
properties, 34.1.2.5
Oracle Mediator service components
configuring, 15, 15
definition, 1.2.4
fault recovery, 1.4.3.1
fault recovery examples, 8.4.3
managing, 17
monitoring, 16
resequenced message purge states for, 9.3.4
setting the instance name during design time, 7.4.4
Oracle Mediator service engines
managing, 17
monitoring, 16
Oracle MQ Series Adapter
properties, 34.1.2.6
Oracle Service Bus (OSB)
invoking, 10.1
Oracle Service Registry
changing the endpoint reference and service key, 34.1.3
configuring caching of WSDL URLs, 34.1.3.1
configuring the publishing of web services to UDDI, 36.2.1
inquiry URL, 3.1
properties, 3.1
publishing to nondefault businesses, 36.2.2
publishing web services to the UDDI registry, 36.2
Oracle Single Sign-On (OSSO)
configuring, 5.1
Oracle SOA Composer
providing a nonadministrator with access, 20.10.4
Oracle SOA Suite
administration, 1.4, 2
configuration, 1.4.1
definition, 1.2
management, 1.4.3
monitoring, 1.4.2
Oracle Socket Adapter
properties, 34.1.2.7
Oracle SSL ciphers, 3.1
Oracle User Messaging Service (UMS)
accessing configuration pages, 26.3
adding or removing user messaging preferences business terms, 26.3.2
architecture, 26.1.2
client aliases, 26.6.5
components, 26.1.1
configuring, 26
configuring the email driver, 26.4.1.4
configuring the messaging extension driver, 26.4.1.3
configuring the proxy driver, 26.4.1.9
configuring the SMPP driver, 26.4.1.5
configuring the VoiceXML driver, 26.4.1.7
configuring the worklist driver, 26.4.1.8
configuring the XMPP driver, 26.4.1.6
configuring to send and receive notifications, 20.1
configuring to the LDAP user profile, 26.5
definition, 26.1
deregistering messaging client applications, 27.1.2
driver configuration, 26.4
driver properties, 26.4.1.1
enabling client security, 26.6.3
enabling security, 26.6.2
keystore configuration, 26.6.4
logging configuration, 27.2.1
managing, 28, 28
message status, 27.1.1
metrics and statistics, 27.3
monitoring, 27
monitoring drivers using the All tab, 27.1.3
securing, 26.6
securing JMS resources, 26.6.6
securing passwords, 26.4.1.2
sender and default sender addresses must match values on the Workflow Notification Properties page, 20.1
setting the storage method, 26.3.1
troubleshooting, 26.7
UMS client applications, 26.1.1
UMS drivers, 26.1.1
UMS server, 26.1.1
viewing log files, 27.2
web service security on notification, 26.6.1
Oracle Virtual Assembly Builder
description, 1.4.3
Oracle SOA Suite support, 1.4.3
Oracle wallet password, 3.1
Oracle Web Service Manager faults, 1.4.3.1
Oracle WebLogic Server
starting and stopping a managed server on which the SOA Infrastructure is deployed in the middle of BPEL processing, 7.4.3
Oracle WebLogic Server Administration Console
accessing, 2.2.5
administering security of human workflow users, 2.2.5
configuring adapter connections for composite references, 2.2.5
creating and managing data sources of adapters, 2.2.5
creating and managing JMS resources of adapters, 2.2.5
deploying human task user interfaces, 2.2.5
managing data sources of the SOA Infrastructure, 2.2.5
managing JTA settings, 2.2.5
performing Oracle SOA Suite administrative tasks from, 2.2.5
oracle.soa.local.optimization.force property
using, 3.7.2
OracleSystemUser, 25.3
oracle.webservices.local.optimization property
using, 3.7.2
ora-human-intervention action
fault policy definitions, 8.4, 8.5, 8.5
orphaned service component instances
deleting, 8.2
for which no SOA composite application instance has been created, 8.2.1
generating, 8.2
OVAB
See Oracle Virtual Assembly Builder
OWSM
See Oracle Web Services Manager

P

partial partitioning
restricting partitioning to tables with high growth rates, 9.4.3.1
partitioning
all tables of a service component and service engine, 9.4.3.1
always partition the COMPOSITE_INSTANCE table, 9.4.3.1
component tables, 9.1.2, 9.4, 9.4.3, 9.4.3.2
configuring partitions, 9.4.1
constraints, 9.4.3.1
developing a methodology, 9.2
executing the verification script, 9.4.4
groups, 9.4.3.2
limitations on, 1.4.3.5
moving long running instances to a different partition, 9.4.6
no tables of a service component and service engine, 9.4.3.1
Oracle B2B foreign key constraints must be disabled before dropping the partition, 9.4.5
partial partitioning of components, 9.4.7
range partition keys, 9.4.3.2
restricting partitioning to tables with high growth rates, 9.4.3.1
running the purge scripts before performing partitioning, 9.4
selecting the schema partition keys, 9.1.2.2
verification script, 9.4.2
verifying and dropping partitions, 9.4.5
partitions
accessing the Undeploy SOA Composite wizard, 7.3
activating all composites in a partition, 7.8.2
API management of, 10.1, 10.2
bulk lifecycle management tasks, 1.4.3.5, 7.8, 7.8.2
cannot rename an existing partition, 7.8.1
cannot restrict login access to, 7.8
cannot start, stop, activate, or retire, 7.8
cannot transfer deployed composites to a different partition, 7.8.1
composites using the same inbound resource deployed to different partitions, 7.8
creating, 7.8.1
creating with ant and WLST, 7.8.1
default partition, 1.4.3.5, 7.1, 7.8
definition, 1.2.1, 1.4.3, 1.4.3.5, 7.8
deleting, 7.8, 7.8.1
deleting and undeploying all composites in the partition, 2.2.3, 7.3
deploying a composite to a partition, 7.8.2
invalid names for, 7.8.1
issues with deploying the same composite with a human workflow into multiple partitions, 7.1
limitations on using the socket adapter, 7.8
managing, 7.8
minimum of one required for deployment, 7.1, 7.8.1
naming conventions, 7.8.1
not associated with a state, 1.4.3.5, 7.8
recreating deployed composites in another partition, 7.8.1
retiring all composites in a partition, 7.8.2
selecting during deployment, 7.1
shutting down all composites in a partition, 7.8.2
starting all composites in a partition, 7.8.2
top level entry point for partition management APIs, 10.1, 10.2
undeploying all composites in a partition, 7.3, 7.4.1, 7.8.2
valid names for, 7.8.1
passwords
changing the default password in the embedded LDAP server, 20.10.1
payload validation
BPEL process service engine, 12.1, 37.1
fault generation for invalid payloads, 7.4.2
for synchronous services, 7.4.2
SOA composite applications, 7.4.2
SOA Infrastructure, 3.1
payloads
resolving large payload errors, B.6.3
saving, 8.1
pluggable notification service, 20.4
registration, 20.4.2
policies
binding components, 36.1
BPEL process service components, 14.2
BPMN process service components, 39.2
configuring security policies for human workflow web services, 20.12
definition, 1.4.3.2
details about which policies to use, 7.6
execution of, 1.4.3.2.1
faults, 1.4.3.1
human workflow service components, 22.1
in SOA composite applications, 7.6
limitation on policy attachment errors for service binding components, 36.1
limitation on policy attachments for binding components, 36
local attachments, 7.6.2
location of errors in services and references, 36.1
multiple servers with the same policy, 36.1.1
no support for policies on event subscriptions, 33.2
Oracle Mediator, 17.2
overriding policy configuration property values, 36.1.1
policy sets, 36.1
recommendation not to use oracle/wss10_saml_token_service_policy in a production environment with human tasks, 22.1
supported categories, 1.4.3.2
policy sets
definition, 20.12, 36.1
popped ruleset, 19.7.1
ports
changing the SOA Infrastructure server URL port, 3.3
privileges
required for performing specific tasks, 1.4, C.1
process flow
for BPEL 2.0 projects, 13.1.2
monitoring a BPEL process service component, 13.1
programmatic management of SOA composite applications, 10.1
properties
actionable addresses, 20.1
actionable email account
configuring, 20.2
audit level of BPEL process service engine, 12.1
audit level of BPMN process service engine, 37.1
audit level of SOA composite application, 7.4.2
audit level of SOA Infrastructure, 3.1
audit trail threshold, 12.1, 37.1
binding components, 34.1
callback server URL, 3.1
capture composite instance state of SOA Infrastructure, 3.1
changing of specific properties with green and red arrow icons requires a restart, 3.1
chunking, 3.1
clusterDbTimeRefresh, 12.3
data sources, 3.1
dispatcher engine threads, 12.1, 37.1
dispatcher invoke threads, 12.1, 37.1
dispatcher system threads, 12.1, 37.1
dynamic assignment and task escalation functions, 20.2
for local optimization, 7.6.2
heartBeatInterval, 12.3
inbound adapters, 30.4
large document threshold, 12.1, 37.1
masteAliveThreshold, 12.3
maxMessageRaiseSize, 12.2, 12.2
nodeReapInterval, 12.3
nodeReapThreshold, 12.3
notification properties, 20.1
Oracle Service Registry, 3.1
Oracle SSL ciphers, 3.1
Oracle wallet password, 3.1
order of precedence, 3.1
order of precedence of execution, 1.4.1, 7.4.2
outbound adapters, 30.8
payload validation in SOA composite applications, 7.4.2
payload validation in SOA Infrastructure, 3.1
payload validation in the BPEL process service engine, 12.1, 37.1
qualityOfService, 14.5.2
server URL, 3.1
SOA Infrastructure, 3.1
startupRecoveryDuration, 12.2
startWindowTime, 12.2
stopWindowTime, 12.2
subsequentTriggerDelay, 12.2, 12.2
threshHoldTimeInMinutes, 12.2
UDDI Registry, 3.1
web service binding, 3.1
proxy driver
client API, 26.4.1.9.3
common properties, 26.4.1.9.1
configuring, 26.4.1.9
custom properties, 26.4.1.9.2
proxy server
best practices for setting proxy properties, B.7.3
specifying, B.7.3
purging
deleting indexes before purging large amounts of data, then adding the indexes back in, 9.3.2
deleting instances with the looped purge in parallel script, 9.3.2
deleting instances with the looped purge script, 9.3.1
deleting large numbers of instances with the purge scripts, 9.3
deleting orphaned instances, 8.2
developing a methodology, 9.2
executing the purge scripts, 9.3.6
instances, 9.3
instances states for purging, 9.3.3
purge script capabilities, 9.3
purge scripts supported on different Oracle SOA Suite releases, 9.3
purge scripts to run when upgrading, 9.3
resequenced message purge states for Oracle Mediator, 9.3.4
scripts are only supported on Oracle databases, 9.3
the instances of a specific SOA composite application, 9.3.5
when to use the Delete With Options dialog or the purge scripts, 8.2, 8.3
pushed ruleset, 19.7.1

Q

QualityOfService property
enabling or disabling Oracle Coherence cache, 12.1

R

recover
message recovery action, 14.4
recoverable activities
definition, 14.4
recovery
of master nodes, 12.3
recovery actions
abort, 8.4, 8.5, 13.1, 14.1, 14.3, 17.1, 17.3
continue, 8.4, 8.5, 13.1, 14.1, 14.3, 17.1, 17.3
replay, 8.4, 8.5, 13.1, 14.1, 14.3, 17.1, 17.3
rethrow, 8.4, 8.5, 13.1, 14.1, 14.3, 17.1, 17.3
retry, 8.4, 8.5, 13.1, 14.1, 14.3, 17.1, 17.3
redeployment
behavior of BPMN instances after redeployment, 7.2
behavior of service component instances after redeployment, 7.2
from SSO-enabled Oracle Enterprise Manager Fusion Middleware Control, 7
guidelines, 7.2
keeping current BPM composite instances running after redeployment, 7.2
limitations on selecting the option to continue instances upon redeployment, 7.2
possible reasons for failure, 7.2, 7.2
redeploying multiple composites at once is not supported, 7.2
SOA composite applications, 7.2
references
definition, 1.2.5, 4.3
displaying the endpoint addresses of, 7.4.2
displaying the WSDL files of, 7.4.2
location of policy errors, 36.1
monitoring, 4.3
Refresh Alarm Table button
resynchronizing lost jobs, 14.4
refresh icon
location, 7.4.1
rejected messages
binding components, 35.2
definition, 1.4.3.1
deleting at the SOA Infrastructure level, 8.6
deleting from the application home page, 8.7
inbound adapters, 30.2, 30.3
when to use the Delete Rejected Messages option, 8.6, 8.7
replay
recovery action, 8.4, 8.5, 13.1, 14.1, 14.3, 17.1, 17.3
reports engine
monitoring, 24.3.1
request breakdown
statistics in Oracle Mediator, 16.3.3
requests and operation statistics in human workflow service engines, 21.4, 21.5
resequencer tables
purging, 9.3.4
reset
message recovery action, 14.4
RESTful web service
security options in the Test Web Service page, 8.1
testing in the Test Web Service page, 8.1
rethrow
recovery action, 8.4, 8.5, 13.1, 14.1, 14.3, 17.1, 17.3
retiring
a default SOA composite application revision, 7.4.1
a SOA composite application revision, 7.4.1, 7.4.2
impact of retiring a default SOA composite application revision, 7.4.1, 7.4.1
impact of undeploying a default SOA composite application revision, 7.4.1, 7.4.1
retry
recovery action, 8.4, 8.5, 13.1, 14.1, 14.3, 17.1, 17.3
revisions
definition, 1.4.3.3
distinguishing the default revision from other revisions, 1.4.3.3
undeployment of default composite revision, 7.3
undeployment of default composite revision when no other active, available revisions exist, 7.3
version added to the application name, 1.4.3.3
roles
administrator, C.1
audit trail access, C.1.15
BPEL process service component home page access, C.1.10
BPEL process service engine access, C.1.6
business events page access, C.1.19
business rules service engine access, C.1.9
composite home page access, C.1.5
creating, C
decision service component home page access, C.1.13
flow trace page access, C.1.14
human task service component home page access, C.1.12
human workflow service engine access, C.1.8
matrix of role functionality, C.1.1
monitor, C.1
operator, C.1
Oracle B2B pages access, C.1.18
Oracle Mediator service component home page access, C.1.11
Oracle Mediator service engine access, C.1.7
references home page access, C.1.17
required for performing specific tasks, 1.4, C.1
services home page access, C.1.16
SOA Composite menu access, C.1.4
SOA Infrastructure menu access, C.1.3
SOA Infrastructure page access, C.1.2
System MBean Browser access, C.1.20
routing statistics in Oracle Mediator, 16.2.4
RPC/literal-style WSDL files
specifying, 8.1.1
rule execution tracing
See business rule execution tracing
rules
See business rules

S

SAML message-protected policy configuration
setting up for the SOA Infrastructure, 5.3
search criteria
setting a default search criteria to fetch recent instances and faults only within a recent duration, 3.1
Secure Socket Layer
See SSL
securing
Oracle Business Activity Monitoring (BAM), 23.9
Oracle User Messaging Service (UMS), 26.6
security
application policies, 2.2.1
application roles, 2.2.1
automatically authenticating Oracle BPM Worklist users in SAML SSO environments, 5.4.1
automatically authenticating Oracle BPM Worklist users in Windows Native authentication environments, 5.4.2
automatically authenticating Oracle Business Process Management Process Composer users in Windows Native authentication environments, 5.4.3
available documentation, 5.1
configuring for human workflow WSDL files, 5.7
configuring for two-way SSL communication, 5.6.4
configuring Oracle HTTP Server with Oracle BPM Worklist, 5.2
configuring Oracle Single Sign-On (OSSO), 5.1
configuring Oracle SOA Suite and Oracle HTTP Server for SSL communication, 5.6.6
configuring SSL between SOA composite application instances and Oracle WebCache, 5.6.7
developing new security providers for use with Oracle WebLogic Server, 5.1
enabling an asynchronous process deployed to an SSL-enabled, managed server to invoke another asynchronous process over HTTP, 5.6.9
invoking references in one-way SSL environments in Oracle JDeveloper, 5.6.5
listing Oracle Internet Directory as the first authentication provider, 5.5.1
passing security properties with messages during testing, 8.1
policies in SOA composite applications, 7.6
procedures unique to Oracle SOA Suite, 5.1
programming security for Oracle WebLogic Server, 5.1
recommendation to configure either all or no managed servers with SSL, 5.6.2
securing an Oracle WebLogic Server production environment, 5.1
securing and administering web services, 5.1
securing Oracle WebLogic Server, 5.1
securing web services for Oracle WebLogic Server, 5.1
setting up SAML message-protected policy configuration for the SOA Infrastructure, 5.3
switching from non-SSL to SSL configurations with Oracle BPM Worklist, 5.6.3
understanding Oracle WebLogic Server security, 5.1
using a custom trust store for one-way SSL during design time, 5.6.8
using SSL certificates when the SOA/BPM server is configured with an HTTPS port, 5.6.1
seeding
users, groups, and application roles with LDAP tools, 20.10
sensors, 13.1, 38.1
behavior of activity sensors in BPEL 2.0 compensate and compensateScope activities, 13.4.1
business monitors, 7.9
disabling BPEL sensors at the service engine level, 12.1
disabling BPEL sensors at the SOA composite application level, 7.4.2
displaying the current state, 7.4.2
JMS sensor values are not displayed, 13.4
monitoring, 13.4
server URL
property, 3.1
property change requires a restart, 3.1
ServerManager
top level entry point for partition management APIs, 10.1, 10.2
service and reference binding components
See binding components
service components
BPEL processes, 13, 14
BPMN processes, 38
definition, 1.2.4
human workflow, 20, 21, 22
instance IDs, 1.2.4
instances, 1.2.4
Oracle Mediator, 15
orphaned instances, 8.2
service engines
BPEL processes, 13, 14
BPMN processes, 38
definition, 1.2.6
human workflow, 20, 21, 22
monitoring at the SOA Infrastructure level, 4.1
monitoring the average request processing times, 4.2
no management pages for the spring service component, 1.2.4
Oracle Mediator, 15
service infrastructure
definition, 1.2.7
monitoring the average request processing times, 4.2
service key
changing for Oracle Service Registry, 34.1.3
services
definition, 1.2.5, 4.3
location of policy errors, 36.1
monitoring, 4.3, 36.2.2
Set Time Threshold link
definition, 4.1, 6.1
Show Details link
definition, 4.1, 6.1
shutting down
a composite revision, 7.4.1, 7.4.2
SMPP driver
client API, 26.4.1.5.4
common properties, 26.4.1.5.2
configuring, 26.4.1.5
custom properties, 26.4.1.5.3
interoperability, 26.4.1.5.1
SMTP email server
configuring, 20.1
SMTP server
restarting the SOA server after configuring, 20.1
SOA composite applications
activating a revision, 7.4.1, 7.4.2
application states after SOA Infrastructure shutdown, 3.2.2
audit level, 7.4.2
configuring for two-way SSL communication, 5.6.4
configuring Oracle SOA Suite and Oracle HTTP Server for SSL communication, 5.6.6
contents, 1.2.8
definition, 1.2.2
deleting instances, 8.2, 8.3
deployed states, 7.4
deploying, 7
deploying a revision, 7.4.1
fault recovery, 8.5
faults, 8.5
filtering by instance states, 8.2, 8.3
finding the composite and component programmatically, 10.3.2
impact of retiring a default revision, 7.4.1, 7.4.1
impact of undeploying a default revision, 7.4.1, 7.4.1
in which one BPEL process is completed and another is faulted, 8.2.2
instances, 1.2.3
lifecycle, 1.4.3.3
managing, 8
managing the application state at the SOA Infrastructure level, 7.4.1
managing the application state from the SOA composite application home page, 7.4.2
message recovery information displayed on the home page, 1.2.1, 6.1
monitoring, 6
monitoring faults, 6.1
monitoring instances, 6.1
packaging, 7
payload validation, 7.4.2
policies, 7.6
programmatically managing, 10.1
purging instances of, 9.3.5
redeploying, 7.2
redeploying a revision, 7.4.1
retiring a default revision, 7.4.1
retiring a revision, 7.4.1, 7.4.2
retrieving the composite state programmatically, 10.3
securing, 5
setting the default revision, 7.4.1
setting the instance name during design time, 7.4.4
showing the composite XML definition, 7.4.2
showing the WSDL and endpoint URI, 7.4.2
shutting down a revision, 7.4.1, 7.4.2
starting up a revision, 7.4.1, 7.4.2
Test button is disabled when a composite is stopped or retired, 7.4.2
test instances, 8.1
testing, 1.4.3.4, 7.4.2, 7.5
undeploying, 7.3
undeploying a revision, 7.4.1
undeploying the default composite revision, 7.3
SOA Composite menu
description of options, 2.2.2
navigating through, 2.2.2
SOA Governance
definition, 1.4.3.3
SOA Infrastructure
audit level, 3.1
cannot change the Infrastructure port from Oracle WebLogic Server Administration Console, 3.3
changing ports, 3.3
configuring, 3
during startup, may not be completely initialized to administer incoming requests, 4.1, 7.8
fault recovery, 8.4
faults, 8.4
managing the application state, 7.4.1
may not completely initialize to administer incoming requests until all deployed composites are loaded, 3.2.1
message recovery information displayed in the home page, 4.1
monitoring, 4
payload validation, 3.1
processing requests, 4.2
properties, 3.1
recent instances and faults, 4.1
restarting the SOA Infrastructure does not activate endpoints when a retired composite is activated, 3.2.3
starting and stopping, 3.2
startup failure when cwallet.sso includes the SOA map, 3.2.4
state of composites after SOA Infrastructure shutdown, 3.2.2
waiting for startup initialization to complete, 3.2.1, 7.4.2
SOA Infrastructure application
definition, 1.2.1
SOA Infrastructure menu
description of options, 2.2.1
navigating through, 2.2.1
SOA Partition menu
navigating through, 2.2.3
sources
message, 24.2.4
spring service components
definition, 1.2.4
no spring service engine management pages, 1.2.6
scope of support in Oracle Enterprise Manager, 1.2.4
SSL
configuring for two-way SSL communication, 5.6.4
configuring Oracle SOA Suite and Oracle HTTP Server for SSL communication, 5.6.6
configuring SOA composite applications for two-way SSL communication, 5.6.4
configuring SSL between SOA composite application instances and Oracle WebCache, 5.6.7
configuring with Oracle Business Activity Monitoring (BAM), 23.9.3
enabling an asynchronous process deployed to an SSL-enabled, managed server to invoke another asynchronous process over HTTP, 5.6.9
invoking references in one-way SSL environments in Oracle JDeveloper, 5.6.5
key alias, 5.6.4
recommendation to configure either all or no managed servers with SSL, 5.6.2
switching from non-SSL to SSL configurations with Oracle BPM Worklist, 5.6.3
using a custom trust store for one-way SSL during design time, 5.6.8
using SSL certificates when the SOA/BPM server is configured with an HTTPS port, 5.6.1
Start Time From field
setting a default search criteria to fetch recent instances and faults only within a recent duration, 3.1
starting
a managed Oracle WebLogic Server on which the SOA Infrastructure is deployed in the middle of BPEL processing, 7.4.3
starting up
a composite revision, 7.4.1, 7.4.2
startupRecoveryDuration property
definition, 12.2
startWindowTime property
definition, 12.2
stopping
a managed Oracle WebLogic Server on which the SOA Infrastructure is deployed in the middle of BPEL processing, 7.4.3
stopWindowTime property
definition, 12.2
stress testing
invoking multiple instances, 8.1
subsequentTriggerDelay property
definition, 12.2, 12.2
synchronous services
payload validation, 7.4.2
system dispatcher messages
definition, 12.1
system faults, 1.4.3.1
System MBean Browser
ASNSDriverIMAddress property, 20.1
ASNSDrivers property, 20.7
AsynchAuditBatchSize, 12.1, 14.5.4
AuditConfig property, 3.1, 3.1, 4.1, 4.1, 6.1, 6.1, 8.2, 8.3, 13.1, 13.1
BpelcClasspath property, 12.1
bpel.config.auditlevel property, 12.5
CustomNSDriverPropertyNames property, 20.1, 20.4.2
DisableAsserts, 12.1
DisableSensors, 12.1
disabling instance and fault count metrics retrieval, 3.1.1
ExpirationMaxRetry property, 12.1
ExpirationRetryDelay property, 12.1
FaxCoverPageCount property, 20.1
GlobalTxMaxRetry property, 3.1
GlobalTxRetryInterval property, 3.1
HttpProxyAuthRealm property, 3.1
HttpProxyAuthType property, 3.1
HttpProxyHost property, 3.1
HttpProxyPassword property, 3.1
HttpProxyPort property, 3.1
HttpProxyUsername property, 3.1
HttpServerURL property, 3.1
HttpsServerURL property, 3.1
InstanceKeyBlockSize property, 12.1
instructions on using, 2.2.1
invoking custom MBeans with WLST, 2.2.1
KeystoreLocation property, 3.1, 5.6.4
MaximumNumberOfInvokeMessagesInCache property, 12.1
MaxRecoveryAttempt property, 12.1
navigational path, 3.1
OneWayDeliveryPolicy property, 12.1
QualityOfService, 12.1
QualityofService, 14.5.3
RetryNotificationMessageThrottle property, 20.1
ServerURL property, 3.3
SOA Infrastructure advanced configuration properties, 3.1
StatsLastN property, 12.1
SyncMaxWaitTime property, 12.1
UddiCacheLifetime property, 3.1, 34.1.3.1

T

tablespaces
extending to avoid problems at runtime, B.6.4
task auto release
configuring, 20.2
portal realm mapping configuration, 20.2
pushback assignee, 20.2
task auto release configuration, 20.2
worklist application URL configuration, 20.2
task escalations, 20.2
task flows
deployment, 7.1.1
task forms
configuring Oracle HTTP Server for task form attachments, 20.3
task service
configuring the workflow custom classpath URL, 20.2
configuring the workflow service session timeout, 20.2
task service properties
human workflow, 20.2
test cases
contents of, 7.5
definition, 1.4.3.4
test runs
definition, 7.5
test suite
assertions, 1.4.3.4
definition, 1.4.3.4
emulations, 1.4.3.4
testing
automating the testing of SOA composite applications, 7.5
initiating a test instance, 8.1
passing security properties with messages, 8.1
restrictions on displaying payload data in the Test Web Service page, 8.1
restrictions on stress tool of Test Web Service page, 8.1
scenarios in which the Test button is disabled, 7.4.2, 8.1
specifying the XML payload data, 8.1
Test button is disabled when a composite is stopped or retired, 7.4.2
WSDL URL that does not contain the revision number is processed by the default composite, 8.1
third party application servers
instructions for using this guide, 1.4
thread dumps from all managed servers, B.1.1
threshHoldTimeInMinutes property
definition, 12.2
throughput
instance details, 13.2
timeouts
resolving, B.2.1
setting, 12.1
TopLink sessions
managing cache, 2.2.1
transaction timeouts
setting, 12.1
transient processes
definition, B.5.5
troubleshooting
additional documentation for, B.9
AMX extension issues, B.4.14
application transaction does not complete and the underlying composite is stuck in a running state, B.3.4
asynchronous transactions return with an error after a long time, B.2.4
automatic recovery of BPEL instances is not recovering a specific instance, B.3.2
best practices for starting and stopping a managed server, B.7.1
business events, B.5
design time at runtime issues, B.4.10
event delivery network, B.5
extending tablespaces, B.6.4
flow diagram display issues on lower end hosts, B.7.4
human workflow API usage issues, B.4.11
human workflow issues, B.4
identity service issues, B.4.17
increasing database connection values, B.2.2
limitations on Safari browser use, B.8.1
long running, synchronous calls to remote web services error out, B.2.4
notification issues, B.4.3
Oracle BPM Worklist/task region issues, B.4.15
Oracle JDeveloper data control/form generation issues, B.4.12
Oracle User Messaging Service (UMS), 26.7
resolving connection timeouts, B.2.1
resolving database growth caused by high transaction volume, B.6.5
resolving exception errors caused by large payloads, B.6.3
resolving message failure caused by too many open files, B.6.2
runtime diagnostics, B.3
runtime failure with a "Cannot read WSDL" error, B.3.1
service/System MBean Browser issues, B.4.13
setting log levels, B.1
slow application performance, B.6.6
SOA server startup problems, B.7.2
some composites are retried multiple tines on failure, B.3.3
task action issues, B.4.2
task assignment, routing, and escalation issues, B.4.1
task attribute mapping issues, B.4.5
task comments/attachment issues, B.4.9
task form/action issues, B.4.8
task history issues, B.4.7
task report issues, B.4.6
task view issues, B.4.4
test-to-production issues, B.4.16
updating EJB transaction timeouts, B.2.3

U

UDDI Registry
configuring the publishing of web services to, 36.2.1
inquiry URL, 3.1
properties, 3.1
publishing to, 36.2
publishing web services to, 36.2.2
UMS
See Oracle User Messaging Service
undeploying
a composite revision, 7.4.1
undeployment
deleting a partition and all its composites, 7.3
from SSO-enabled Oracle Enterprise Manager Fusion Middleware Control, 7
guidelines, 7.3
of all composites in a partition, 7.3
of an application instance does not cause the instance to complete, 13.7, 16.3.2
of default composite revision, 7.3
of default composite revision when no other active, available revisions exist, 7.3, 7.4.1
SOA composite applications, 7.3
unit tests
assertions, 1.4.3.4
distinguishing unit test instances from other instances, 1.2.3, 7.5
emulations, 1.4.3.4
of SOA composite applications, 1.4.3.4
running, 7.5
test cases, 1.4.3.4
test suites, 1.4.3.4
users
demo community, A
demo user community, A.2
seeding with LDAP tools, 20.10

V

verification script
executing, 9.4.4
for partitioning, 9.4.2
not provided for business rules, 9.4.4
VoiceXML driver
client API, 26.4.1.7.4
common properties, 26.4.1.7.2
configuring, 26.4.1.7
custom properties, 26.4.1.7.3
interoperability, 26.4.1.7.1

W

watches
creating, 11.2
web browsers
Copy details to clipboard link does not appear with Mozilla Firefox, 13.1
limitation on using the Safari Browser to view WSDL file content, B.8.1
supported, 2.1
web service binding properties, 3.1
web services
configuring, 34.1.1
WebLogic Diagnostic Framework
See WLDF
WLDF
definition, 11.1.1
WLST
creating partitions, 7.8.1
deploying drivers, 28.1.1
deployment, 7.1.2
invoking custom MBeans, 2.2.1
workflow custom classpath URL
configuring, 20.2
workflow service session timeout
configuring, 20.2
worklist driver
client API, 26.4.1.8.5
common properties, 26.4.1.8.3
configuring, 26.4.1.8
custom properties, 26.4.1.8.4
installing, 26.4.1.8.1
installing on the IBM WebSphere platform, 26.4.1.8.2
wsadmin
deploying drivers, 28.1.4
WSDL files
displaying the WSDL files of all external services, 7.4.2
human workflow, 5.7
specifying during instance creation, 8.1
specifying RPC/literal style WSDL files, 8.1.1
specifying the default revision, 8.1
WSDL URL that does not contain the revision number is processed by the default composite, 8.1
WS-Reliable Messaging
restrictions, 7.6.1

X

XML definition
of SOA composite applications, 7.4.2
XML payload data
specifying during instance creation, 8.1
XMPP driver
application archive (EAR), 26.4.1.6.4
client API, 26.4.1.6.7
common properties, 26.4.1.6.5
configuring, 26.4.1.6
custom properties, 26.4.1.6.6
definition, 26.4.1.6.1
interoperability, 26.4.1.6.2, 26.4.1.6.3