D64648GC10 Ag

These eKit materials are to be used ONLY by you for the express purpose SELF STUDY.
SHARING THE FILE IS STRICTLY PROHIBITED.
Activity Guide
D64648GC10
Edition 1.0
November 2010
D69744
Oracle University and (Oracle Corporation) use only.
Oracle SOA Suite 11g:

Administration
Copyright 2010, Oracle and/or its affiliates. All rights reserved.
This document contains proprietary information and is protected by copyright and other intellectual property laws. You may copy and
print this document solely for your own use in an Oracle training course. The document may not be modified or altered in any way.
Except where your use constitutes "fair use" under copyright law, you may not use, share, download, upload, copy, print, display,
perform, reproduce, publish, license, post, transmit, or distribute this document in whole or in part without the express authorization
of Oracle.
The information contained in this document is subject to change without notice. If you find any problems in the document, please
report them in writing to: Oracle University, 500 Oracle Parkway, Redwood Shores, California 94065 USA. This document is not
warranted to be error-free.
Restricted Rights Notice
If this documentation is delivered to the United States Government or anyone using the documentation on behalf of the United
States Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS
The U.S. Governments rights to use, modify, reproduce, release, perform, display, or disclose these training materials are restricted
by the terms of the applicable Oracle license agreement and/or the applicable U.S. Government contract.
Trademark Notice
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective
owners.
Authors
Iris Li, Glenn Stokol
Technical Contributors and Reviewers
Clemens Utschig, Simone Geib, Payal Srivastava, Vasily Strelnikov, Jukka Gardemeister, Joe
Greenwald, Gary Barg, Matthew Slingsby, Stephen McRitchie, Demed L'Her, Jay Kasi, Rakesh
Saha, Swarnapriya Shridhar, Bijoy Choudhury, Pete Daly, Meera Srinivasan, Prasen Palvankar,
Khanderao Kand, Serge Moiseev, Michael Bousamra, Greg Pavlik, Thomas Palazzolo, Heidi
Buelow, Ken Cooper, Peter Laseau, Ted Witiuk, David Mills, Steve Friedberg
This book was published using:
Oracle Tutor
These eKit materials are to be used ONLY by you for the express purpose SELF STUDY. SHARING THE FILE IS STRICTLY PROHIBITED.
Disclaimer
Practices for Lesson 1 .....................................................................................................................................1-1

Practices for Lesson 1....................................................................................................................................1-3
Practice 2-1: Review Service-Oriented Architecture Concepts ......................................................................2-4
Practice 2-2: Review Oracle Fusion Middleware and SOA Suite ...................................................................2-5
Practice 2-3: Review of Administrator Task and Tools ...................................................................................2-6
Solutions 2-1: Review Service-Oriented Architecture Concepts.....................................................................2-7
Solutions 2-2: Review Oracle Fusion Middleware and SOA Suite .................................................................2-8
Solutions 2-3: Review of Administrator Task and Tools .................................................................................2-9
Practice 3-1: Install SOA Schemas with the Repository Creation Utility.........................................................3-4
Practice 3-2: Install Oracle SOA Suite 11g (11.1.1.2.0) Patch Set 1 ..............................................................3-7
Practice 3-3: Install Oracle SOA Suite 11g (11.1.1.3.0) Patch Set 2 ..............................................................3-9
Practice 3-4: Create a WebLogic Domain for Oracle SOA Suite ....................................................................3-11
Practice 3-5: Start the Admin Server, and the Managed Servers ...................................................................3-15
Practice 4-1: Deploy a Composite Application ...............................................................................................4-4
Practice 4-2: Test a Composite Application ...................................................................................................4-7
Practice 4-3: Deploy a Composite with a Configuration Plan .........................................................................4-13
Practice 4-4: Undeploy a Composite with WSLT............................................................................................4-20
Practice 5-1: Modify SOA Infrastructure Common Properties ........................................................................5-4
Practice 5-2: Test a Composite and View Changes .......................................................................................5-7
Practice 6-1: Configure the Run-Time Database Adapter ..............................................................................6-4
Practice 6-2: Deploy and Test the Composite with a DBAdapter ...................................................................6-15
Practice 6-3: Configure Run-Time JMS Adapter Resources ..........................................................................6-18
Practice 6-4: Deploy and Test the Composites using a JMS Adapter ............................................................6-29
Practice 7-1: Deploy the Purchase Order Processing Composites ................................................................7-4
Practice 7-2: Initiate the ProcessPOFileComposite........................................................................................7-7
Practice 8-1: Deploy SOA Applications with Mediator Components...............................................................8-4
Practice 8-2: Initiate and Monitor Version [1.0] Applications ..........................................................................8-5
Practice 8-3: Deploy SOA Applications Version [2.0] .....................................................................................8-12
Practice 8-4: Initiate, Monitor, and Manage Versioned Applications ..............................................................8-14
Oracle SOA Suite 11g: Administration Table of Contents

i
Table of Contents
Practices for Lesson 10 ...................................................................................................................................10-1

Practices for Lesson 10..................................................................................................................................10-3
Practice 10-1: Configure the Embedded LDAP Server ..................................................................................10-4
Practice 10-2: Configure Human Workflow Notification Services ...................................................................10-15
Practice 11-1: Deploy a Composite with a Human Task Component .............................................................11-4
Practice 11-2: Initiate and Monitor the Human Task without a UI ..................................................................11-6
Practice 11-3: Deploy the Task Form UI Application ......................................................................................11-21
Practice 11-4: Test and Monitor a Human Task and its Task Form UI ...........................................................11-24
Practice 12-1: Deploy a BPMN Application and its Task Form ......................................................................12-4
Practice 12-2: Initiate and Monitor the BPMN Process ..................................................................................12-6
Practice 13-1: Configure the Oracle BAM Adapter .........................................................................................13-4
Practice 13-2: Import the BAM Data Object and Report.................................................................................13-10
Practice 13-3: Deploy the Composite Application with BAM Integration ........................................................13-16
Practice 13-4: Test the Composite Application with BAM Integration.............................................................13-18
Practice 14-1: Importing Metadata Using the B2B Console ...........................................................................14-4
Practice 14-2: Deploy and Test a B2B Sender Composite Application ..........................................................14-12
Practice 15-1: Deploy the Stock Update Composite and Web Service ..........................................................15-4
Practice 15-2: Test the Subscriber of the StockUpdated Event .....................................................................15-10
Practice 15-3: Deploy, Test, and Monitor Event Publishing Composite .........................................................15-19
Practice 16-1: Create a Simple Username Token Security Policy..................................................................16-4
Practice 16-2: Apply a Security Policy to a Service Endpoint .........................................................................16-10
Practice 16-3: Test Invocation of the Secured Service Endpoint....................................................................16-14
Practice 17-1: Examine Server Information in the Topology Viewer ..............................................................17-4
Practice 17-2: Observe WebLogic Server Instance JVM Performance ..........................................................17-11
Practice 17-3: Explore Metrics for Oracle SOA Suite Components ................................................................17-20

ii

Practice 9-1: Deploy a Composite with Business Rules .................................................................................9-4
Practice 9-2: Initiate and Monitor an Instance with Business Rules ...............................................................9-6

Practice 18-1: Deploy a Troublesome Composite Application .......................................................................18-4

Practice 18-2: Initiate and Troubleshoot a Composite Application .................................................................18-8
Practice 18-3: Troubleshoot Human Task Interaction ....................................................................................18-30

iii
Chapter 1
Practices for Lesson 1
Chapter 1 - Page 1
Chapter 1 - Page 2
Practices Overview
There are no practices for the introduction lesson.

Chapter 1 - Page 3
Chapter 1 - Page 4
Chapter 2
Chapter 2 - Page 1
Chapter 2 - Page 2
Practices Overview
The practices for this lesson are paper-based. They are about Service-Oriented Architecture
concepts, Oracle SOA Suite 11g software, and administration resources covered in the lesson
content. Suggested solutions are provided after all the questions have been presented.

Chapter 2 - Page 3
Overview
In this practice you answer questions about Service-Oriented Architecture (SOA) concepts.
Assumptions
You have listened to the instructor and understood the material presented in lesson 2.
Tasks
1.
2.
3.
4.
5.
How would you describe what Service-Oriented Architecture means?

What is the building block for SOA?
What enables an SOA approach? Explain your answer.
What describes a service?
For an administrator, what is the value of the Service Component Architecture (SCA)
assembly model for an SOA composite application?

Chapter 2 - Page 4
Practice 2-1: Review Service-Oriented Architecture Concepts
Overview
In this practice you answer questions about Oracle Fusion Middleware 11g and Oracle SOA
Suite 11g.
Assumptions
Material in lesson 2 has been presented or read.
Tasks
1.
2.
What two software components, aside from the Operation System, are required to run
Oracle SOA Suite 11g?
List the key software components that are installed with Oracle SOA Suite 11g?

Chapter 2 - Page 5
Practice 2-2: Review Oracle Fusion Middleware and SOA Suite
Overview
In this practice you answer questions about your role as an administrator and the typical tasks
you would be expected to perform and the related tools.
Assumptions
The administrator tasks and tools discussed in the course are basic representation of an Oracle
SOA Suite 11g administrator, and does not represent all the possibilities available.
Tasks
1.
2.
What are the administration user interfaces for Oracle SOA Suite 11g?
What other tools can be useful for an administrator? Explain your answers.

Chapter 2 - Page 6
Practice 2-3: Review of Administrator Task and Tools
1.
2.
3.
4.
5.
A simple description of Service-Oriented Architecture is: SOA is a paradigm (a way of

thinking) about a technological implementation for business applications that use services
(a standards-based distributed component) to automate their tasks. As defined by OASIS:
A paradigm for organizing and utilizing distributed capabilities that may be under the
control of different ownership domainsOrganization for the Advancement of Structured
Information Standards (OASIS) definition or stated another way An IT strategy that
organizes the discrete functions contained in enterprise applications into interoperable,
standards-based services to be combined and reused quickly to meet business
requirements
In computing terms, you can think of SOA as a standards-based method of systems
development and integration.
Services are the building block for SOA composite applications.
Note: A composite application is also a service that aggregates and coordinates access to
one or more other services to complete a business process. The main idea is reuse of
functionality to capitalize on investment, separation of concerns to enable the right tasks
to be processed in the right context, and agility to enable IT processes to keep up and in
line with changing business requirements.
Web Services standards enable SOA to be realized. The Web and Web Services
standards, such as XML, WSDL, SOAP, UDDI to mention a few, provide a common
framework for distributed heterogeneous platforms and applications to communicate in a
platform and language agnostic manner leading to a higher degree of interoperability and
reuse, neither of which is easy to accomplish without the standards in place and agreed
upon. Standards are a set of ratified agreements.
The service interface describes a service through the use of an XML-based language called
Web Services Description Language (WSDL). The WSDL for a service describes the
service operations and associated message structures used for exchange of information
over the internet channels defined by a protocol binding, such as SOAP, JMS, among
others.
For an administrator, the value of the SCA assembly model is in its ability to convey the
application structure and in particular the dependencies. You may need to ensure the
dependencies are accessible, available, and configured. Examples include:
Service references require their URLs to be accessible from the run-time environment
and may require configuration of proxy settings.
Database aware services may require JNDI and JDBC resources to be configured.
JMS services may need JMS resources to be defined and configured.

If you do not have a picture of the application assembly model, then you would have to rely
on developer supplied documentation that describes configuration and dependency
requirements that enable the application to operate in the deployed context.

Chapter 2 - Page 7
Solutions 2-1: Review Service-Oriented Architecture Concepts
1.
2.
The two software components required to enable Oracle SOA Suite 11g to run include:
a. Oracle WebLogic Server to provide the run-time environment for Oracle SOA Suite
components. Oracle WebLogic Server is a Java EE run-time platform on which Oracle
SOA Suite executes.
b. Oracle Database to provide a data source to manage Oracle SOA Suite run-time
configuration and resources. In particular, an Oracle Database is required for creating
the database schemas used by Oracle SOA Suite components to store their
configuration and run-time information.
The key components that are installed with Oracle SOA Suite include:
Oracle SOA Suite Service Infrastructure, which provides the underlying message
communication architecture for exchange of data between SOA components and
external services and systems through bindings and adapters.
Oracle Mediator engine, which executes implementation specified in Mediator

components.
Oracle Business Process Execution Language (BPEL) engine, which executes

implementation specified in BPEL components.
Oracle Business Rules engine, which executes business rules specified by Business
Rules components.
Oracle Human Task engine, which execute human workflow processes specified in
Human Task components
Oracle Business Activity Monitoring (BAM) engine, which performs real-time monitoring
of activity, message data, faults, and events processed in composite application
instances.
Note: The Oracle Business Process Management (OBPM) engine is an additional
component that can be separately installed into an Oracle SOA Suite environment.
Applications created by Oracle BPM Suite are executed in Oracle BPM engines, which may
utilize the functionality of other service engines.

Chapter 2 - Page 8
Solutions 2-2: Review Oracle Fusion Middleware and SOA Suite
1.
2.
The main administration user interface for Oracle SOA Suite 11g is Oracle Enterprise
manager Fusion Middleware Control, which is used to manage composite applications from
deployment through their run-time life cycle. You use Oracle Enterprise manager Fusion
Middleware Control to configure, manage, and monitor composite applications and their
run-time environment.
Note: Oracle SOA Suite 11g administrators also use Oracle WebLogic Server Administrator
to configure application resources, such as JDBC data sources, JMS destinations and
resources, connection factories, security services, among other lower level tasks.
The other tools that can be useful for an administrator include:
Ant and the various Oracle supplied Ant tasks for command-line management and
administration of composite applications.
WebLogic Scripting Language (WLST) scripts that enable administrators to configure

resources from command-line interfaces and simplify repetitive and complex tasks
through scripting techniques.
System MBeans that enable administrators to configure components in the run-time

environment often minimizing the need to restart applications and services.

Chapter 2 - Page 9
Solutions 2-3: Review of Administrator Task and Tools
Chapter 2 - Page 10
Chapter 3
Chapter 3 - Page 1
Chapter 3 - Page 2
Practices Overview
In the practices for this lesson the key tasks are:
Install Oracle Repository Creation Utility (RCU), and run Oracle RCU to create the
SOA Schemas
Install Oracle SOA Suite 11g 11.1.1.2.0
Install Oracle SOA Suite 11g 11.1.1.3 patch set
Create the WebLogic domain for SOA Suite and BPM
General Notes
For brevity folder names in the command-line prompt, of a Command Prompt window, are not
shown to enable most of the commands (where possible) to fit in one line. In addition, to avoid
confusion, commands that span multiple lines will not contain end of line continuation
characters.

Chapter 3 - Page 3
Overview
You install and run the Oracle Repository Creation Utility using version 11.1.1.3.0 to create the
SOA Suite database schemas in the Oracle 10g XE database instance.
While you can install the schemas using the command-line interface (as shown at the end of the
practice instructions), in this practice, you use the graphical user interface. You only do this
process once for each SOA Suite 11g installation.
Assumptions
Oracle 10g XE Database must be installed and running.
Tasks
1.
Open a Command Prompt window, and enter the following commands:

D:\> cd D:\stage\rcuHome\bin
D:\> rcu.bat
2.
After the Repository Creation Utility (RCU) application starts, use the following table of
instructions to install the SOA Schemas:
Step
Window/Page Description
Choices or Values
a.
Welcome
Click Next.
b.
Create Repository
Select the Create option, and click Next.
c.
Database Connection
Details
Hostname: localhost
Port: 1521
Service Name: XE
Username: sys
Password: oracle
Role: SYSDBA
Click Next.
d.
Repository Creation Utility
RCU performs some prerequisites checks and during this

time, because the classroom machine uses Oracle
Database 10g XE, the following warning dialog box
displays:

Chapter 3 - Page 4
Practice 3-1: Install SOA Schemas with the Repository Creation Utility
Choices or Values
For the classroom environment, you can click Ignore.
Note: Production systems should be using a supported
Oracle Database version, and therefore you would not see
this warning dialog box.
e.
Repository Creation Utility Checking Prerequisites
Verify that all prerequisite checks have passed, and click

OK.
f.
Select Components
Accept the default Create a new Prefix option and the

value DEV in the associated field.
In the Component table, select the SOA and BPM
Infrastructure check box.
Note: When you select the specified entry, the rows of the
component table are expanded and other dependencies
are also selected. The SOAINFRA schema is used for both
SOA and BPM components.
Click Next.
g.
Repository Creation Utility Checking Prerequisites
RCU performs another prerequisites check. Verify that the

operation completed OK, and click OK.
h.
Schema Passwords
Accept the default Use same passwords for all schemas

selection option, and enter the password fields as follows:
Password: welcome1
Confirm Password: welcome1
Click Next.
i.
Map Tablespaces
Accept the supplied settings for the default and temporary

tablespace selections for each schema owner, and click
Next.
j.
Repository Creation Utility
A dialog box prompts to confirm if you want to create the

tablespaces that do not already exist.
Click OK.
k.
Repository Creation Utility Creating Tablespaces
This dialog box displays while creating the tablespaces.

When tablespace creation is complete, click OK.
m.
Summary
Review the information, and click Create.

Note: The Repository Creation Utility Create dialog
box displays showing creation progress. It takes about two
minutes to create the schemas, and the dialog box is
closed.
n.
Completion Summary
Verify that each of the component schemas indicates a

success status, and click Close.
l.
3.
Optionally, close the Command Prompt window.

Chapter 3 - Page 5
Step
Optional Steps to Verify Creation of SOA and BPM Database Schemas

If you wish to view the database schemas created in the Oracle XE Database, you can
perform the following steps:
a. On the Windows Taskbar, select Start > Programs > Oracle Database 10g Express
Edition > Run SQL Command Line.
Note: Alternatively, open a new Command Prompt window and enter the following
command:
D:> sqlplus /nolog
b.
In the Run SQL Command Line window, enter the following commands:
SQL> connect sys/oracle as sysdba
SQL> select username from all_users;
Note: Among the list of names displayed you should see the following usernames:
:
USERNAME
------------SYSTEM
SYS
DEV_ORABAM
DEV_SOAINFRA
DEV_ORASDPM
DEV_MDS
17 rows selected.
c.
Close the Run SQL Command Line window.

Chapter 3 - Page 6
4.
Overview
In this practice you install the Oracle SOA Suite 11g 11.1.1.2.0 software. While this release is
known as Patch Set 1, it performs a full installation of the Oracle SOA Suite 11g software and
does not require a previous release to exist.
Assumptions
You must use the 64-bit Sun JDK for the installation. The SOA domain should not exist at this
time. The Oracle WebLogic Server 10.3.3 software must be installed in the Fusion Middleware
Home folder D:\oracle\fmw\11.1.1.3. The JAVA_HOME environment variable should be
set to reference the D:\jdk_16018x64 folder containing the Sun 64-bit JDK. The SOA
Schemas should be installed in the Oracle Database 10g XE instance. The
D:\stage\soa_ps1 folder must contain the software for Oracle SOA Suite 11g 11.1.1.2.0
(known as Patch Set 1, which is a full installation kit).
Tasks (Estimated time: 10-15 minutes including reading time)

1.
2.
If you still have the Command Prompt window open, then proceed to the next step,
otherwise open a new Command Prompt window.
In the Command Prompt window, navigate to the D:\stage\soa_ps1\Disk1 folder and
enter the setup command using the JAVA_HOME environment variable for the -jreLoc
command-line option:
D:\> cd D:\stage\soa_ps1\Disk1
D:\> setup -jreLoc %JAVA_HOME%
Note: The JAVA_HOME environment variable should already be defined to reference
the Sun 64-bit JDK folder in D:\jdk_16018x64. You can verify the value of the
JAVA_HOME environment variable before executing the command by entering the
command:
D:\> set JAVA_HOME
3.
Note: The result returned should be the following line:

JAVA_HOME=D:\jdk_16018x64
The Oracle installer opens a command window, performs some checks and launches the
installation wizard. To start the SOA Suite 11g 11.1.1.2.0 installation, perform the steps in
the following table:
Step
Choices or Values
a.
Welcome
Click Next.
b.
Prerequisite Checks
Wait for the prerequisite checks to complete (less than

5 seconds duration), and verify that checks are
successful.
Click Next.
c.
Specify Installation Location
Accept the default settings for:

Oracle Middleware Home:
D:\Oracle\fmw\11.1.1.3

Chapter 3 - Page 7
Practice 3-2: Install Oracle SOA Suite 11g (11.1.1.2.0) Patch Set 1
Choices or Values
Oracle Home Directory: Oracle_SOA1
Click Next.
4.
d.
Installation Summary
Click Install.
e.
Installation Progress
Wait for the installation to complete (approximately 6

minutes). When the installation is completed and
reaches 100%, click Next.
f.
Click Finish.
Note: Installation should not take more than 6 minutes.

Step

Chapter 3 - Page 8
Overview
In this practice you install the Oracle SOA Suite 11g 11.1.1.3.0 (Patch Set 2) into the existing
Oracle SOA Suite 11g 11.1.1.2.0 home. The Oracle SOA Suite 11g 11.1.1.3.0 (Patch Set 2) is
called a sparse installer and requires that Oracle SOA Suite 11g 11.1.1.2.0 release to be
already installed.
Assumptions
You must use the 64-bit Sun JDK for the installation. The SOA domain should not exist at this
time. The Oracle WebLogic Server 10.3.3 software must be installed in the Fusion Middleware
Home folder D:\oracle\fmw\11.1.1.3 and the Oracle SOA Suite 11g 11.1.1.2.0 software
must have been installed in the same Middleware Home as the WebLogic Server instance.
The JAVA_HOME environment variable should be set to reference the D:\jdk_16018x64 folder
containing the Sun 64-bit JDK. The SOA Schemas should be installed in the Oracle Database
10g XE instance. The D:\stage\soa_ps2 folder must contain the software for Oracle SOA
Suite 11g 11.1.1.3.0.
Tasks
1.
2.
If you still have the Command Prompt window open then proceed to the next step,
In the Command Prompt window, navigate to the D:\stage\soa_ps2\Disk1 folder and
enter the setup command using the JAVA_HOME environment variable for the -jreLoc
command-line option:
D:\> cd D:\stage\soa_ps2\Disk1
D:\> setup -jreLoc %JAVA_HOME%
3.
When the Oracle installer starts, use the following table of steps to install the SOA Suite
11g software:
Step
Choices or Values
a.
Welcome
Click Next.
b.
Prerequisite Checks
Wait for the checks to complete (it's very quick),

and verify that all checks are successful, and click
Next.
c.
Specify Installation Location
Accept the default values for:

Oracle Middleware Home:
D:\Oracle\fmw\11.1.1.3
Oracle Home Directory: Oracle_SOA1
Note: Ensure that Oracle Home Directory is the
value Oracle_SOA1.
Click Next.
d.
Click Install.
e.
Installation Progress
Wait for the installation to complete (approximately

Chapter 3 - Page 9
Practice 3-3: Install Oracle SOA Suite 11g (11.1.1.3.0) Patch Set 2
f.
4.
Choices or Values
5 minutes). When the installation is completed and
reaches 100%, click Next.
Click Finish.
Note: Installation time should not take more than 5 minutes.

Step

Chapter 3 - Page 10
Overview
In this practice you create WebLogic domain and configure it with the Oracle SOA Suite
components needed for the course.
Assumptions
The Oracle Database 10g XE instance is running and the Oracle SOA Suite 11g 11.1.1.3.0
patch set has been installed into the Oracle SOA Suite 11g 11.1.1.2.0 home.
Tasks
1.
2.
If you still have the Command Prompt window open then proceed to the next step,
In the Command Prompt window, to launch the Oracle Fusion Middleware Configuration
Wizard, navigate to D:\Oracle\fmw\11.1.1.3\Oracle_SOA1\common\bin folder and
type the following commands:
D:\> cd D:\Oracle\fmw\11.1.1.3\Oracle_SOA1\common\bin
D:\> config
3.
When the Oracle Fusion Middleware Configuration Wizard starts, use the following table of
instructions to complete the domain configuration:
Step
Choices or Values
a.
Welcome
Select the Create a new WebLogic domain

option.
Click Next.
b.
Select Domain Source
Accept the selected Generate a domain

configured automatically to support the
following products option.
Select the Oracle BPM Suite 11.1.1.0
[Oracle_SOA1] check box.
Note: The check boxes for the following
dependent product components are also
selected:
Oracle SOA Suite 11.1.1.0
Oracle WSM Policy Manager 11.1.1.0
Oracle JRF 11.1.1.0

In addition, select the check boxes for the
following two components:
Oracle Enterprise Manager 11.1.1.0
Oracle Business Activity Monitoring

11.1.1.0
Click Next.
c.
Specify Domain Name and Location
Domain name: soa_domain

Chapter 3 - Page 11
Practice 3-4: Create a WebLogic Domain for Oracle SOA Suite
d.
Configure Administrator User Name

and Password
Choices or Values
Accept the default values for other settings.
Click Next.
Name: weblogic
Password: welcome1
Confirm password: welcome1
Accept the default description value.
Click Next.
e.
Configure Server Start Mode and

JDK
Accept the default selections with the

Development Mode and Available JDKs (with
the 64-bit Sun SDK) options selected.
Click Next.
f.
Configure JDBC Component

Schema
Using the image below this row as a guide to

complete the steps in this row.
First, in the table at the bottom of the page,
select all the check boxes next to the
Component Schema column.
Second, enter the following SOA database
information in the three fields at the top-right
section of the page:
DBMS/Service: XE
Host Name: localhost
Port: 1521
Note: When you set each of these field
values, observe that the corresponding fields
in the table below change respectively for all
Component Schema selected.
Third, enter the database schema password
(which is the same for all component schemas
in this case):
Schema Password: welcome1
Note: The Schema Owners in this table must
match the value assigned to schema owners
configured by the RCU utility.
Click Next.

Chapter 3 - Page 12
Step
Choices or Values
g.
Test Component Schema
On this page, the configuration tools tests all

the data source connections. Wait until it
completes. Verify that a green tick appears in
the Status column for all Component Schema
entries.
Click Next.
Note: If there are connection errors, click
Previous and make appropriate corrections to
database connection information.
h.
Select Optional Configuration
Select the Managed Servers, Clusters and

Machines check box.
Click Next.
Note: Selecting this option enables you to
configure if components execute in separate
managed servers or within a single server
instance. You accept the default values to
create a separate managed server
configuration.
i.
Configure Managed Servers
Observe that two managed servers are

present by default, called:
bam_server1
soa_server1
Note: Observe the port numbers associated
with each managed server. These port
numbers are used to access appropriate Web
application and administration interfaces for

Chapter 3 - Page 13
Step
4.
Choices or Values
the BAM and SOA components respectively.
These ports are different to the default
WebLogic Server Administration port 7001.
Accept the default settings, and click Next.
j.
Configure Clusters
You do not create clusters in this course.

k.
Configure Machines
By default a single logical machine is created

on the localhost for the two managed servers.
l.
Assign Servers to Machines
By default the two managed servers

(soa_server1, bam_server1) are assigned to
the LocalMachine.
m.
Configuration Summary
The Domain Summary section of the page

displays the deployment details for the
domain. You can review settings and click
Previous to make changes before creating the
domain.
Click Create.
n.
Creating Domain
The progress of the domain creation is

displayed in this page. Wait for domain
creation to complete (progress reaches
100%), and click Done.
Note: You could select the Start Admin Server
check box to start the WebLogic Admin
Server. However, in this case you first create
desktop shortcuts for this purpose to be used
in the practices.
Close the Command Window.

Chapter 3 - Page 14
Step
Overview
In this practice you create three desktop shortcuts that can be used to quickly start, stop and
access the WebLogic Admin Server. You then start the Admin Server and the two Managed
Servers created by the Domain Configuration Wizard for soa_domain.
Assumptions
The Oracle Database 10g XE is running, you have installed Oracle SOA Suite 11g 11.1.1.3.
(Patch Set 2), which implies Oracle SOA Suite 111g 11.1.1.2.0 (Patch Set 1) has also been
installed, and configured the domain for the SOA, BPM, and BAM components.
Tasks
Your tasks here include:
Creating desktop shortcuts for starting and stopping the WebLogic Admin Server.
Starting the WebLogic Admin Server and using it to start the soa_server1 and
bam_server1 managed server instances.
Accessing the WebLogic Administration Server, Enterprise Manager Fusion

Middleware Control, and BAM Web Application.
Experimenting with starting and stopping the managed servers through the WebLogic
Administration Console and the command-line interface.
Create Desktop Shortcuts

In this section you create three desktop shortcuts to start, start, and access the WebLogic
Admin Server.
Note: If you prefer, you can skip to step 5 and use the command line to start the Admin Server.
1. To locate the source of desktop icons in the WebLogic Server menu, click Start > Programs
> Oracle WebLogic > User Projects > soa_domain.
Note: Using the following image as a guide:
2.
Observe that the soa_domain menu contains the following three items:
Admin Server Console, used to launch the Web browser to access the WebLogic
Server Administration Console.
Start Admin Server for WebLogic Server Domain, which does what it states, starts
the Admin Server instance for the soa_domain.
Stop Admin Server, which stops the Admin Server instance for the soa_domain.
To create a desktop icon for the Admin Server Console, click Start > Programs > Oracle
WebLogic > User Projects > soa_domain, then right-click Admin Server Console and select
Send To > Desktop (create shortcut).

Chapter 3 - Page 15
Practice 3-5: Start the Admin Server, and the Managed Servers
4.
Repeat the process of creating a desktop icon for the Start Admin Server for WebLogic
Server Domain and Stop Admin Server menu items.
Hint: Display the soa_domain Start menu, right-click the menu items and select Send To >
Desktop (create shortcut).
Confirm that you have three new desktop icons for each of the soa_domain menu items.
Use the following image as a guide (for the three icons):
Starting the WebLogic Admin Server

In this section you start the WebLogic Admin Server using the desktop icon.
5. Before you start the WebLogic Server and SOA components, perform the following steps to
check the file system and system processes:
a. To examine the file system, start Windows Explorer, navigate to the
D:\Oracle\fmw\11.1.1.3\user_projects\domains\soa_domain\servers
folder, and answer the following questions:
Note: The path prefix
D:\Oracle\fmw\11.1.1.3\user_projects\domains\soa_domain is
represented by the text DOMAIN_HOME in subsequent text. The text DOMAIN_HOME
does not exist as an environment variable and is used for brevity (where appropriate) in
these practice instructions.

Chapter 3 - Page 16
3.
2)
What sub folder(s) did you find in the servers folder, and what are these folders
used for?
Answer: The AdminServer folder is the only folder present after installation. When
the AdminServer is started additional folders are created to maintain runtime
information for the AdminServer instance.
What other sub folders and files exist in any of the DOMAIN_HOME\servers sub
folder?
Answer: The AdminServer folder contains a single folder called security, which
contains the boot.properties file. The boot.properties file contains the
obfuscated (encrypted) credentials (user name and password) for the
administration user (In this course the administration user name is weblogic).
3)
b.
Why are the folders for managed servers not present?

Answer: The soa_server1 and bam_server1 folders do not exist because those
server instances have not been started.
4) Which folder contains the configuration files for the AdminServer and the two
manager servers (soa_server1, and bam_server1)?
Answer: You can find the configuration files for the AdminServer, soa_server1,
and bam_server1 in their own sub folders contained in the
DOMAIN_HOME\config\fmwconfig\servers folder.
To view the user processes, perform the following steps:
1) Open the Windows Task Manager application by right-clicking the Windows
Taskbar and selecting Task Manager.
2) In the Windows Task Manager window, click the Processes tab, and using the list
of processes how do you know that no WebLogic Server instances (either the
Admin or Managed servers) are running?
Answer: No java.exe processes are displayed in the list of processes.

Chapter 3 - Page 17
1)
1)
After starting the AdminServer, look in the Processes tab page of the Windows
Task Manager to confirm that a java.exe process is now displayed.

Chapter 3 - Page 18
6.
Note: Let the Windows Explorer and Window Task Manager applications continue to
execute. Do not close these application windows.
To start the WebLogic Server, perform the following steps:
a. On the Windows Desktop, double-click the Start Admin Server for WebLogic Server
Domain icon.
Note: Alternatively, you can open a Command Prompt window and enter the following
commands to start the Admin Server:
D:\> cd D:\Oracle\fmw\11.1.1.3
D:\> cd user_projects\domains\soa_domain\bin
D:\> startWeblogic.cmd
In the Windows Explorer, look at the DOMAIN_HOME\servers folder. Now that the
AdminServer has been started, what are some of the changes you can observe in
the AdminServer subfolder tree?
Answer: Additional folders have been created to maintain the runtime information
for the server instance. For example, the adr, cache, data, logs, sysman, and
tmp subfolders have been created below the AdminServer folder. The logs
folder store run-time and diagnostic log information that can be useful for
troubleshooting problems.

Chapter 3 - Page 19
2)
c.
On the Start Admin Server for WebLogic Server Domain command window, wait until
you see a message similar to:
<Jun 8, 2010 5:19:10 PM GMT> <Notice> <WebLogicServer> <BEA000360> <Server started in RUNNING mode>
Minimize the Start Admin Server for WebLogic Server Domain command window, or
the Command Prompt window you used to start the Admin Server.
Viewing Server Instances

In this section you use the Web interface of the WebLogic Server Administration Console to
start and stop the Managed Servers.
7. To start the WebLogic Administration Server Console, double-click the Admin Server
Console icon on the Windows desktop. Alternatively, enter the URL
http://localhost:7001/console in a Web browser window.
8. On the WebLogic Administration Server Console login page, login as the administration
user weblogic and associated password (welcome1).
9. On the WebLogic Administration Server Console home page, to view the state of the
servers, perform the following steps:
a. On the home page in the Domain Structure, expand the Environment node, and click
Servers.
b. On the Summary of Servers page, in the Configuration tab you can observe the state
of servers in the Servers table. Is the state of each server in the server table consistent
with the state of the processes you have observed? Why?
Answer: Yes, it is consistent. The Servers table shows that the AdminServer is in the
RUNNING state and the two managed servers are in a SHUTDOWN state. Because
each server has been configured to run in its own Java Virtual Machine (JVM), the list
of processes shown in the Windows Task Manager has only one JVM (java.exe)
process running, which represents the AdminServer instance.
c. Keep the Summary of Servers Configuration page displayed in the Web browser,
because you use it to monitor the server state changes as you start them using the

Chapter 3 - Page 20
b.
Managing Servers with Command Line Scripts

In this section you start and stop the managed servers by using command-line scripts provided
with the WebLogic Server installation. You also stop the Admin server and restart it using the
command line.
10. On the Windows Desktop, open a new command window by double-clicking the Command
Prompt desktop icon.
11. To start the soa_server1 managed server, perform the following steps:
a. In the Command Prompt window, execute the following commands:
D:> set FMW_HOME=D:\Oracle\fmw\11.1.1.3
D:> cd %FMW_HOME%\user_projects\domains\soa_domain\bin
D:> startManagedWebLogic.cmd soa_server1
b.
Hint: In the cd command, instead of entering the two commands and typing the full
path name to the bin folder, from a Windows Explorer, you can locate and drag the
bin folder icon onto the Command Prompt window.
The JVM for the managed server starts and after a short time you are prompted for the
administration credentials. Enter the username and password as shown:
Enter username to boot WebLogic server: weblogic
Enter password to boot WebLogic server: welcome1
c.
While the soa_server1 managed server instance is starting up, click the Web browser
window displaying the WebLogic Administration Console Summary of Servers
Configuration page, and observe the state changes.
1) What state changes do you observe?
Answer: Some of the state changes you may observer (depending on timing) are
the STARTING and RUNNING states.
2) How do you know that the managed server is ready to be used?
Answer: Some of the ways to determine that the managed server is running are:
On the Summary of Servers Configuration page, when the managed server
state is changed to RUNNING.
On the command line window used to start the managed server when you see
the following line displays:
INFO: FabricProviderServlet.stateChanged SOA Platform is
running and accepting requests
12. When you start the soa_server1 managed server, why are you prompted for the
administration username and password?
Answer: When you create the SOA domain using the config.cmd script, which runs the
Domain Configuration Wizard, you are prompted for the security credentials of the
administrator. The configuration process stores the encrypted credentials you entered in the
boot.properties file in the run-time security subfolder of the AdminServer. However,

Chapter 3 - Page 21
command-line tools. After using the command-line tool, you use the Control tab to
manage the servers in conjunction with using the WebLogic Server Node Manager.
Answer: The soa_server1 subfolder has been created along with its child folders.
One of the child folders, called security, does not exist yet. While the domain_bak
folder may also be created, it contains one subfolder and no files yet. We are primarily
interested in the soa_server1 subfolder.
b. What file system configuration changes can you make to start the managed server
without having to manually enter the username and password?
Answer: Create the DOMAIN_HOME\servers\soa_server1\security folder, and
then create a boot.properties file, containing encrypted administrator credentials,
in the DOMAIN_HOME\servers\soa_server1\security folder (the managed
server security folder) to eliminate the requirement to manually enter administrator
credentials when starting the managed servers. There are several ways to perform this
task.
c. Terminate the soa_server1 managed server instance, by performing the following
steps:
1) In the command window where you started the managed server, press Ctrl + C.
2) At the Terminate batch job (Y/N)? prompt, press y and then press Enter.
Note: Do not close the command window.
14. To configure security to eliminate the need to manually enter administrator credentials
when starting servers, perform the following step and answer the related question:
a. By using Windows Explorer, copy the
DOMAIN_HOME\servers\AdminServer\security folder and its
boot.properties file into the DOMAIN_HOME\servers\soa_server1 folder to
create the security sub folder for the soa_server1 instance.
b.
c.
Note: Remember DOMAIN_HOME refers to the

D:\Oracle\fmw\11.1.1.3\user_projects\domains\soa_domain folder.
There are other ways to create the the boot.properties file, such as manually edit
the file with the appropriate properties in plain text. The plain text credentials are
encrypted when the managed server is next started. Alternatively, the JVM command
line option -Dweblogic.system.StoreBootIdentity=true can be use to create
the boot.properties file with encrypted copies of the credentials entered at the
prompts when starting a managed server from the command line.
When you start the Admin Server using the desktop icon, it actually executes the
startWebLogic.cmd script. Why werent you prompted for administrator security
credentials?
Answer: The DOMAIN_HOME\servers\AdminServer\security folder already
contains the boot.properties file, which is created by the Domain Configuration
Wizard.
Return to the Command Prompt window where you original started the soa_server1
managed server instance, and restart it by entering the following command:

Chapter 3 - Page 22
these credentials are not saved in the run-time security subfolder of the respective
managed servers, so you are still prompted for the administrators username and password
when starting the managed servers.
13. Using Windows Explore examine the changes to the DOMAIN_HOME\servers folder, and
answer the following questions:
a. Having started the soa_server1 managed server instance what subfolder has been
created in the DOMAIN_HOME\servers folder?
Note: When the soa_server1 instance starts, you should not be prompted for the
administrator credentials.
15. To start the bam_server1 managed server instance and create its boot.properties file,
a. Open a new Command Prompt window, and execute the following commands:
D:> set JAVA_OPTIONS=-Dweblogic.system.StoreBootIdentity=true
D:> startManagedWebLogic.cmd bam_server1
b.
c.
Note: The JAVA_OPTION environment variable is used by the

startManagedWebLogic.cmd script to pass command line options to the JVM used to
start the managed server instance. In this case, providing the command-line option
weblogic.system.StoreBootIdentity=true tells the managed server to store
the credentials entered at the prompt in its own boot.properties file in its security
subfolder.
In the Command Prompt window, where your start the bam_server1 managed server,
when prompted, enter the administration credentials. For example:
Enter username to boot WebLogic server: weblogic
Enter password to boot WebLogic server: welcome1
In Windows Explorer, navigate to the
DOMAIN_HOME\servers\bam_server1\security folder (if it exists) and verify that
the boot.properties file has been created.
Reminder: DOMAIN_HOME references the

D:\Oracle\fmw\11.1.1.3\user_projects\domains\soa_domain folder.
Note: If the security sub folder does not exist, then you can copy the security folder
from the soa_server1 tree into the bam_server1 tree so that next time you start the
bam_server1 instance you should not be prompted for the administrator credentials.
16. After the BAM Server has completely started up, you can verify that you are able to login
and view the main BAM Web application home page by performing the following steps:
a. In the Web browser window, create a new Web browser tab page (or new window),
and enter the following URL: http://localhost:9001/OracleBAM
b. On the Oracle BAM login page, enter the username weblogic and password
welcome1, and click Login.
c. If you have successfully logged into the Oracle BAM home page, you can logout and
close the page, as there is not much to do at this time.
17. Since we do not need the bam_server1 instance for some time, you can stop the
bam_server1 instance. You can press Ctrl + C to interrupt and shutdown the process in the
command window. Alternatively, in this case, you use a supplied command-line script to
shutdown the process by performing the following steps:
a. Ensure you can see (restore or maximize) the bam_server1 Command Prompt
window.

Chapter 3 - Page 23
D:> startManagedWebLogic.cmd soa_server1
Open a new Command Prompt window.

In the Command Prompt window, enter the following command to shutdown the
bam_server1 instance:
D:> stopManagedWebLogic.cmd bam_server1
Note: When the bam_server1 instance is terminated this way, the Command Prompt
window used to start it is closed. If you are still running the WebLogic Administration
Console Web application you can monitor the managed server state changes.
d. Close the new Command Prompt window you used to stop the bam_server1 instance.
18. Because the soa_server1 instance is still running, you can open a new Web browser tab
page (or window) and access the Oracle Enterprise Manager Fusion Middleware Control
Console and login as the administrator, by performing the following steps:
a. In the Web browser application, open a new tab page (or window).
b. On the new browser page, enter the URL: http://localhost:7001/em
c. On the Oracle Enterprise Manager Fusion Middleware Control Console login page,
enter the username weblogic and password welcome1, and click Login.
Note: The first time you login, you are presented with the Accessibility Preference
settings. Accept the default settings and click Continue. For example:
Note: If you require accessibility features enabled then select the I use a screen
reader option before you click Continue.
d. On the Oracle Enterprise Manager Fusion Middleware Control Console home page,
expand the SOA > soa-infra (soa_server1) nodes and examine the tree structure.
Note: You have completed this practice. While you may leave the Oracle Enterprise
Manager Fusion Middleware Control Console session logged in, there is a session inactivity
timeout of about 30 minutes after which the session is terminated by the server. The
session timeout applies to the Oracle WebLogic Administration Console. However, the
Oracle BAM Web application does not share the same session timeout.

Chapter 3 - Page 24
b.
c.
Chapter 4
Chapter 4 - Page 1
Chapter 4 - Page 2
Practices Overview
In the practices for this lesson the key tasks are to:
Deploy a composite application
Test a composite application
Deploy a composite with a configuration plan
Undeploy a composite with WLST
Deploy a composite with Ant (Optional, if you have time)
General Notes

Chapter 4 - Page 3
Overview
In this practice, you deploy a simple HelloWorldComposite application by using the Oracle
Enterprise Manager Fusion Middleware Control Console.
Assumptions
The composite application SAR file (sca_HelloWorldComposite_rev1.0.jar) exists in the
D:\labs\lesson04\HelloWorldComposite\deploy folder.
Tasks
To deploy the HelloWorldComposite application using Oracle Enterprise Manager Fusion
Middleware Control Console, perform the following steps:
1. Login to Oracle Enterprise Manager Fusion Middleware Control Console.
a. If not already visible, open a Web browser window, and enter the URL
http://localhost:7001/em
b. On the Oracle Enterprise Manager Fusion Middleware Control Console login page,
enter the username weblogic and password welcome1 and click Login.
Note: The Farm home page (called Farm_soa_domain) is displayed after you login.
2. Deploy the HelloWorldComposite application to the default partition in the SOA
infrastructure.
a. On the Farm home page, in the navigation frame, expand the SOA folder, right-click
soa-infra and select SOA Deployment > Deploy
b. On the Deploy SOA Composite > Select Archive page, perform the following steps:
1) In the Archive or Exploded Directory section, accept the default selected Archive
is on the machine where this web browser is running option, and click Browse.
2) In the Choose file dialog box, navigate to the
D:\labs\lesson04\HelloWorldComposite\deploy folder, select
sca_HelloWorldComposite_rev1.0.jar and click Open.
3) Verify that the selected JAR file is shown in the Archive is on the machine where
this web browser is running option field, and click Next.
c. On the Deploy SOA Composite > Select Target page, in the SOA Partition section
select default from the drop-down box, and click Next.
d. On the Deploy SOA Composite > Confirmation page, accept the default settings and
click Deploy.
Note: A deployment progress dialog box displays showing progress of the deployment
operation until deployment succeeds (as in this case) or fails. When deployment
succeeds, the Deployment Success dialog box closes.
e. In the (left-hand) Navigator frame, the deployed HelloWorldComposite is selected, and
the HelloWorldComposite [1.0] application page displays in the right-hand frame
containing a confirmation message indicating that the composite application was
deployed successfully. Use the following image as a guide for the expected result:

Chapter 4 - Page 4
Practice 4-1: Deploy a Composite Application

Chapter 4 - Page 5
3.
Note: The default partition has a composite application, called SimpleApproval, already
deployed. The SimpleApproval composite application exposes a Human Task
component as a service for any other SOA applications to use a generic and simple
approval human workflow task assignment service.
On the Farm navigation tree, if needed, click the HelloWorldComposite [1.0] entry, and click
the Dashboard tab. Using information in the HelloWorldComposite [1.0] > Dashboard tab
page answer the following questions:
Note: Because the HelloWorldComposite application has not been executed and therefore
there are no metrics or run-time information to see, you can collapse the Recent Instances
and Recent Faults and Rejected Messages sections on the page.
a. What are the names and types of the components in the HelloWorldComposite
application?
Answer: The following two components exist (as determined from the Component
Metrics section):
The HelloMediator component, which is a Mediator component type.
The HelloBPEL component, which is a BPEL component type.
b. What is the name of the service entry point?
Answer: The service entry point is called HelloMediator_ep (as shown in the Services
and References section). You know this is a service entry point because the Usage
column shows it is a Service type.
c. Does the HelloWorldComposite application have any dependencies? Explain your
answer.
Answer: There are no dependencies (references) in the HelloWorldComposite
application. If you look in the Services and References section, it does not contain any
rows with the Reference type in the Usages column.
Note: Other ways to verify whether a composite has dependencies or not, are to
examine the composite.xml code looking for one or more <reference> XML
elements, or look at a visual representation of the composite.xml to determine if
there are external references. For example: The following image represents the
HelloWorldComposite application in the Oracle JDeveloper Composite Editor:
Do not close the Oracle Fusion Middleware Web browser page, because you need to use
Oracle Enterprise Manager Fusion Middleware Control Console in the next practice.
4.

Chapter 4 - Page 6
Overview
In this practice you create a test instance of the HelloWorldComposite application, examine the
application Flow Trace pages to track the message flow through the composite application, and
familiarize yourselves with application and component metrics displayed in the Oracle Fusion
Middleware Control console Web pages.
Assumptions
You have successfully deployed the HelloWorldComposite application as described in the
previous practice.
Tasks
Your tasks here are to:
Initiate a composite application and view the response message.
Examine specific details about the composite application by using its Flow Trace
pages.
Initiate a Composite Application
1. On the HelloWorldComposite [1.0] home page, click Test.
Note: If the HelloWorldComposite [1.0] home page does not already displays and you are
logged into Oracle Fusion Middleware Control, expand the SOA > soa-infra > default node
in the Farm navigation tree, and then click the HelloWorldComposite [1.0] entry.
2. On the Test Web Service page, accept all default settings. However, you must provide an
input string for the test. To provide the input string and test the service:
a. On the Test Web Service page, scroll down until you find the Request tab.
b. On the Test Web Service page > Request tab page, scroll down to locate the Input
Arguments section with the default Tree View mode. In the request > input field, enter
the value: First test, and click Test Web Service.
3. On the Test Web Service page, the page is refreshed with the Response tab becoming
active and showing the response message Mediator sends: BPEL Hello: Mediator recv:
First test in the Web page, use the following image as a guide:

Chapter 4 - Page 7
Practice 4-2: Test a Composite Application
Examine the Composite Application Flow Trace Pages

4. On the Test Web Service > Response page, note the Response Time (ms) in milliseconds
and click the Launch Message Flow Trace link.
5.
By using information on the main Flow Trace page as shown in the following image:

Chapter 4 - Page 8
Note: The response message echoes the original input message with some addition prepended text that modifies the initial message for the response. You could trace the changes
to the message by using the composite application Flow Trace pages.

Chapter 4 - Page 9
Note: You may need to refresh the page by using the refresh icon (in the top right corner of
the page) to ensure you can see the results represented in the image above.
Answer the following questions:
a. Given the fact that the HelloWorldComposite service uses a synchronous (requestresponse) style message exchange, what is the order of the message flow through the
composite application components?
Answer: The sequence of the message flow from the service entry point and back to
the client (in this case the Web browser) is:
1) HelloMediator, which receives the input message from the Web service entry point
and prefixes the text Mediator recv to the input message
2) Then HelloBPEL, which adds the text BPEL Hello to the start of the message
received from the HelloMediator component
3) Finally BPEL returns its response to the HelloMediator, which adds the Mediator
sends text to the front of the entire message before it is returned to the client (the
Web browser).
Note: In summary, for a synchronous exchange the message flow is represented by
traversing down the Flow Trace tree, and back up to the initiating component (which
depends on how the composite application entry point is wired to the first component in
the application).
To drill down into each component in the flow, you can click the HelloMediator link in
the Instance column of the Flow Trace tree to examine the Audit Trail for that
component. Similarly, you can click the HelloBPEL link to examine the Audit Trail (or
visual Flow) of the BPEL process component.
The example used here is a simple use case, and keep in mind that a Flow Trace tree
may represent a more complex message flow than the example used in this practice.
The message flow pattern for an asynchronous exchange pattern is entirely different
because it may be a one-way or a two-way operation.
b. Which component takes up the most processing time?
Note: The results for your test example may (and can) vary from the results presented
in this document. The purpose of this question is to ask you to examine specific
3)
Note: the Average Processing Time (secs) value for the document example is
0.125 seconds or 125 milliseconds.
On the HelloWorldComposite [1.0] > Dashboard tab page, in the Component
Metrics section, click the HelloMediator link to drill down and view the details in its
Routing Statistics section. Expand the Route Target section as well and observe
the values for Average Processing Time and Average Invocation Time in each
section (all in millisecond values). Use the following image as a guide:

Chapter 4 - Page 10
information that can be viewed and monitored about a composite application and its
components.
Hints: To determine the answer for this questions perform the following tasks:
1) Click the HelloWorldComposte [1.0] entry in the Farm navigator frame to display
the Dashboard tab page on the composite applications home page.
2) On the HelloWorldComposte [1.0] > Dashboard tab page, scroll down to view the
Component Metrics and Services and References sections. Take note of the
Average Processing Time (secs) column for the HelloMediator_ep (in the
Services and References section). Use the following image as a guide:
5)
Note: The Average Execution time in the BPEL component does not exceed 0.016
milliseconds.
The answer for the execution sequence shown in this material indicates the
HelloMediator component took a little more time. Your answer may be different
and the timings are likely to be different.
Note: One possible reason why the HelloMediator component takes a bit more
time is because of the XSL Transformations that it has to perform on the request
and response message data. Whereas the HelloBPEL process roughly copies
received data and additional text to the response, and lacks complexity. In the real

Chapter 4 - Page 11
4)
Note: The example shows that the Mediator component averaged 0.109
milliseconds most of which was consumed by the service invocation. Return to the
HelloWorld Dashboard page by clicking the HelloWorldComposite [1.0] Locator
link in the top left corner of the page.
On the HelloWorldComposite [1.0] > Dashboard tab page, in the Component
Metrics section, click the HelloBPEL link to drill down and view the details of the
BPEL component. Comparing to the HelloMediator component, which component
consumes more time?
world it is more likely that a BPEL component will be consuming the more of the
processing time as BPEL components usually do much more work.

Chapter 4 - Page 12
Overview
In this practice you modify a configuration plan and deploy the composite with the configuration
plan using the Administration interface and Ant command-line tools.
Assumptions
The HelloWorldComposite application has been successfully deployed by performing the steps
in the section titled Practice 4-1: Deploy a Composite Application.
Tasks
1.
Your tasks for this practice are:
Deploy a composite application with its configuration plan by using the Oracle Fusion
Middleware Control Console
Test the composite and observe the results
Modify the supplied configuration plan and redeploy the application using the
command-line Ant scripts
To complete these tasks, perform the following steps:
2. If required, login to Oracle Enterprise Manager Fusion Middleware Control Console.
Note: Refer to the subsection titled Logging into the Oracle WebLogic Administration
Console contained in the Common Administrator Tasks part of the Activity Guide.
Deploy a Composite with a Configuration Plan
3. Deploy the LogHelloComposite application by using the SAR file
(sca_LogHelloWorldComposite_rev1.0.jar) in the
D:\labs\lesson04\CallHelloComposite\deploy folder. Deploy the new
application in the default partition of the SOA infrastructure.
Note: For generic steps to deploy a composite, refer to the section titled Deploying a
Composite Application with a Configuration Plan in the Common Administrator Tasks part
of the Activity Guide. Here are some specific instructions for selecting the SAR file and
attaching the configuration plan:
a. On the Deploy SOA Composite > Select Archive page, perform the following steps:
1) In the Archive or Exploded Directory section, accept the default selected Archive
is on the machine where this web browser is running option, and click Browse.
D:\labs\lesson04\CallHelloComposite\deploy folder, select
sca_LogHelloWorldComposite_rev1.0.jar, and click Open.
3) In the Configuration Plan section, select the Configuration plan is on the machine
where this web browser is running option, and click Browse.
D:\labs\lesson04\CallHelloComposite\deploy folder, select
CallHelloComposite_cfgplan.xml, and click Open.
Note: The configuration plan contains an intended run-time error that you correct
later in this practice after redeploying the composite application with a modified the
configuration plan.

Chapter 4 - Page 13
Practice 4-3: Deploy a Composite with a Configuration Plan
b.
c.
On the Deploy SOA Composite > Select Target page, in the SOA Partition section
select default from the drop-down box, and click Next.
On the Deploy SOA Composite > Confirmation page, accept the default settings and
click Deploy.
Test the Composite

4. On the LogHelloWorldComposite [1.0] home page, click Test.
Note: If the LogHelloWorldComposite [1.0] home page is not already displayed and you are
in the Farm navigation tree, and then click the LogHelloWorldComposite [1.0] entry.
b. On the Test Web Service page > Request tab page, locate the Input Arguments
section with the default Tree View mode. In the request > input field, enter the value:
Log test, and click Test Web Service.
c. On the Test Web Service > Response page, and click the Launch Message Flow Trace
link.
Note: You may need to refresh the Flow Trace page by using the refresh icon (in the
top right corner of the page) to ensure you can see the complete results.
6. On the Flow Trace page, locate and identify the error. Examine the fault information
available and explain why the composite application failed.

Chapter 4 - Page 14
5)
The run-time error condition is included to highlight that a configuration plan should
be modified to suite the deployment environment.
Verify your selections by using the following image and click Next.
To view the fault message information, perform the following steps:

a. Click the fault entry in the Error Message column of the Faults section to view the error,
for example:
b.
On the fault information pop up frame, examine the detail and summary information, for
example:
Note: You can see that there is a WSDL reading error for the HelloWorldComposite
services entry point defined in the WSDL and located at the URL
http://myhost.mydomain.com:8001. If you were to using the ping command with the
host name myhost.mydomain.com, what result would you get?
Answer: The ping command would inform you that it could not find the host name
used. For example:

Chapter 4 - Page 15
Note: You may need to refresh the Flow Trace page by using the refresh icon (in the top
right corner of the page) to ensure you can see the fault instance result.
Answer: On the Flow Trace page, you should be able to observe the fault listed in the Flow
Trace page in the Fault section and the Trace tree in the LogHelloBPEL BPEL Component
row. For example:
8.
What can you do to correct the error condition?

Answer: The possible solutions are:
Contact the developer or provider of the composite application and provide them the
error information so that they can fix the problem in the source code, or
Redeploy the application with a configuration plan that replaces the incorrect URL
with a correct URL for the HelloWorldComposite service entry being referenced by
the application. This is the easier solution to implement because you know where
the HelloWorldComposite application has been deployed.
Close the Flow Trace page for the LogHelloWorldComposite [1.0].
Note: On the LogHelloWorldComposite [1.0] Dashboard page, if you see multiple
occurrences of the same fault information, this is because the SOA Infrastructure retries the
service invocation. It could be a situation that the service URL is correct and it is temporarily
unavailable. However, while you could create a host name alias entry for the
myhost.mydomain.com in the Window hosts file to solve the problem, in this case you
redeploy the application with an updated configuration plan.
In addition, you may need to abort the instance, which is retrying the service invocation. To
abort the composite instance:
a. On the LogHelloWorldComposite [1.0] page, click the Instance tab.
b. On the LogHelloWorldComposite [1.0] Instance page, select the row containing faulted
instance ID and click Abort.
Note: If you get another Abort confirmation dialog box, click Abort again. The following
image shows the results after an instance has been aborted.

Chapter 4 - Page 16
7.
b.
Locate the XML element <reference name="LogAdapterService">, and in the

child element for <property name="hello_logdir"> modify the <replace>
element text to contain D:\temp\hello_logs instead of D:\temp. Use the following
image as a guide:
Note: The hello_logdir property is configured by the application developer as a

logical name referencing a target folder in which the log files are written to in the
deployment environment. The default value for the property is set to D:\temp. You
change the folder location value for this practice.
c. Save the changes to the configuration plan file and terminate the Notepad application.
11. Open a Command Prompt window, using the Desktop icon, and execute the following
commands to deploy the application with the modified configuration plan:
D:\> cd D:\labs\lesson04\CallHelloComposite\deploy
D:\> deploy.cmd sca_LogHelloWorldComposite_rev1.0.jar
CallHelloComposite_cfgplan.xml
Note: Use the following image as a guide to verify the command and results indicating that
the deployment is successful:

Chapter 4 - Page 17
Modify the Configuration Plan and Redeploy the Composite

9. Using Windows Explorer, navigate to the
D:\labs\lesson04\CallHelloComposite\deploy folder and open the
CallHelloComposite_cfgplan.xml file in Notepad.
Hint: Right click the XML file and select Send To > Notepad.
10. In the Notepad window, modify the configuration plan to change the following entries:
a. Locate the XML element <reference name="HelloWorldService">, and in its
child <attribute name="location"> element modify host name in the URL of the
<replace> element from myhost.mydomain.com to soa11g.example.com (or
localhost). Use the following image as a guide:
Note: If the hello_logs subfolder does not exist, the File Adapter creates it in order to
write the log files into the specified folder.
16. Open the hellomsg_*.log file with the highest sequence number, and verify it contains
the response message from the HelloWorldService in an XML format. Use the following
image as a guide:

Chapter 4 - Page 18
Repeat the Composite Test

12. On the LogHelloWorldComposite [1.0] home page, click Test.
Note: If the LogHelloWorldComposite [1.0] home page is not already displayed and you are
in the Farm navigation tree, and then click the LogHelloWorldComposite [1.0] entry.
b. On the Test Web Service page > Request tab page, locate the Input Arguments
section with the default Tree View mode. In the request > input field, enter the value:
Another log test, and click Test Web Service.
c. On the Test Web Service > Response page, click the Launch Message Flow Trace
link.
Note: You may need to refresh the Flow Trace page using the refresh icon (in the top
right corner of the page) to ensure you can see the complete results.
14. On the Flow Trace page, verify that application is completed without faults.
15. Using Windows Explorer, navigate to the D:\temp folder and verify that the hello_logs
subfolder exists and contains a log file prefixed with the word hello followed by a
sequence number, for example hellomsg_1.log.
Hint: You can compare the log file contents with the result message in the payload of the
callbackClient entry of the LogHelloBPEL component Audit Trail (accessible through the
Flow Trace page). For example:

Chapter 4 - Page 19
Overview
In this practice you undeploy a Composite application by using WSLT commands.
Note: The commands shown here use the plain text username and password of the WebLogic
administrator. This is done for simplicity and generally not good practice. Please refer to the
Toolkit of WebLogic Scripting Tool (WSLT) Commands appendix for more information about
connecting securely with WLST commands.
Assumptions
The LogHelloWorldComposite application has been previously deployed.
Tasks
1.
To start WebLogic Scripting Tool (WLST) application, perform the following steps:
a. Open a new Command Prompt window.
b. In the Command Prompt window enter the following commands:
D:\> cd D:\Oracle\fmw\11.1.1.3\Oracle_SOA1\common\bin
D:\> wlst
wls:/offline> connect("weblogic",
"welcome1", "t3://localhost:8001")
2.
To undeploy the LopHelloWorldComposite application, execute the following command at

the WLST prompt:
wls:/soa_domain/serverConfig> sca_undeployComposite(
"http://localhost:8001", "LogHelloWorldComposite", "1.0",
"weblogic", "welcome1")
wls:/soa_domain/serverConfig> exit()
3.
4.
Close the Command Prompt window.

In the Oracle Enterprise Manager Fusion Middleware Control Console, refresh the SOA
Infrastructure page, and verify that the LogHelloWorldComposite is no longer listed in the
SOA > soa-infra (soa_server1) > default tree.

Chapter 4 - Page 20
Practice 4-4: Undeploy a Composite with WSLT
Chapter 5
Chapter 5 - Page 1
Chapter 5 - Page 2
Practice Overview
In the practices for this lesson, you login to the Oracle Enterprise Manager Fusion Middleware
Control Console, change a couple of configuration properties for the SOA Infrastructure, and
observe the visible changes in the Fusion Middleware Control Console pages.

Chapter 5 - Page 3
Overview
In this practice you modify two properties in the Common Properties section for the SOA
Infrastructure. The properties affect the amount of visual information displayed in the Fusion
Middleware Control Console. The changes made reflect a choice between having immediate
access to detailed information versus display performance of Fusion Middleware Control
Console application data.
Assumptions
The Oracle WebLogic Administration Server and the SOA Suite Managed Server are running.
Tasks
1.
2.
Login to Oracle Enterprise Manager Fusion Middleware Control Console using the URL
http://localhost:7001/em. Enter the username weblogic and password welcome1.
Hint: You may want to save the URL as a bookmark or favorite in your Web browser for
use throughout the rest of the course.
Enable the Capture Composite Instance State common property so that you can view the
state of all composite applications in the various Dashboard pages of the Fusion
Middleware Control Console.
Until now when composite instances have been completed, you see a question mark in the
State column of the Dashboard tab page of the composite home page (or in the Instances
tab for the SOA Infrastructure page) as shown in the following image of the
HelloWorldComposite application:
To enable the State column to display completed instances more clearly, perform the
following steps:
a. On the Farm navigation frame, expand the SOA folder, right-click soa-infra and
selection SOA Administration > Common Properties.

Chapter 5 - Page 4
Practice 5-1: Modify SOA Infrastructure Common Properties
3.
On the SOA Infrastructure Common Properties page, select the Capture Composite
Instance State check box.
Note: There is a performance impact when rendering information in Oracle Fusion

Middleware Control Console application if you enable the Capturing Composite
Instance State check box. Therefore, avoid enabling capturing of composite instance
state on production systems. However, in some cases it may be worth the overhead to
facilitate easy of identification of composite states and instance tracking.
c. Do not apply the change yet, because you modify another property in the next step.
To improve display performance of the Fusion Middleware Control Console page display,
on the SOA Infrastructure Common Properties page, scroll down to the Data Display
Options and select the Disable fetching of instance and fault count metrics property. For
example:

Chapter 5 - Page 5
b.
On the SOA Infrastructure Common Properties page, click Apply.
5.
6.
On the Confirmation dialog box for the Save Properties prompt, click Yes.
Close the Confirmation dialog box.

Chapter 5 - Page 6
4.
Overview
In this practice, you initiate another test of the HelloWorldComposite application, using any input
string of your choice, and observe the changes to the Fusion Middleware Control Console Web
pages as a result of modifying the common properties in the previous practice.
You also clear the Disable fetching of instance and fault count metrics property check box and
apply the changes so that you can view the metrics in the Web pages for each composite. You
reset the metrics to be visible because it simplifies monitoring applications throughout the rest of
this course, with the minor cost of slower performance to refresh the pages. Over the duration of
this course you do not create too many composite application instances for performance to be a
problem.
Assumptions
The HelloWorldComposite application has been deployed and the following SOA Infrastructure
Common Properties have been applied:
Composite Instance State (Check box has been selected)
Disable fetching of instance and fault count metrics (Check box has been selected)
Tasks
1.
2.
3.
4.
On the Farm navigation frame, expand the SOA > soa-infra (soa-server1) > default tree (if
required) and click the HelloWorldComposite [1.0] entry.
On the HelloWorldComposite [1.0] > home page, click Test.
On the HelloWorldComposite [1.0] > Test Web Service > Request tab page, in the Input
Arguments field, enter any input string of your choice and click Test Web Service.
On the Farm navigation frame, in the SOA > soa-infra (soa-server1) > default tree, click
HelloWorldComposite [1.0] to view the application Dashboard tab on its home page, and
a. What is different about the information displayed in the State column for the most
recent instance?
Answer: When you look at the Recent Instances information (or the information
displayed in the Instances tab) for the composite application the State column clearly
displays the Completed status for recently completed instances. However, the question
mark icon is displayed for instances that completed prior to changing the Capture
Composite Instance State property. Use the following image as a guide:

Chapter 5 - Page 7
Practice 5-2: Test a Composite and View Changes
What do you notice about the differences in the visual appears of the metrics in the
Component Metrics section?
Answer: When you scroll down the composite application Dashboard tab page to view
the Component Metrics section instead of viewing the actual metric values in the cells
of the table for each component, an information icon is displayed. This feature enables
the component Web page to be displayed more quickly without waiting for the
application to retrieve the metric information until you desire to view the details.
c.
How can you view the metric information detail for a composite application component?
Answer: If you click the information icon for the component cell of interest to you, a
Processing: Counts dialog box is displayed containing the current information. For
example: Here is a Processing: Counts dialog box for the HelloMediator component
in the HelloWorldComposite [1.0] application. The Total Instances value may be
different in your case.
Note: If this application is still running, you can click the Recalculate link to update the
metrics to facilitate monitoring the component information. Click OK to close the
Processing: Counts dialog box.

Chapter 5 - Page 8
b.
6.
To make it easier to view the component metrics in place, perform the following steps to
clear the appropriate common property and apply the changes:
a. On the Farm navigation frame, expand the SOA folder, right-click soa-infra
(soa_server1) node and select SOA Administration > Common Properties.
b. On the SOA Infrastructure Common Properties page, deselect the Disable fetching of
instance and fault count metrics property check box, and click Apply.
c. On the Confirmation dialog box, for the Save Properties prompt, click Yes.
On the Farm navigation frame, in the SOA > soa-infra (soa-server1) > default tree, click
HelloWorldComposite [1.0] and confirm that the actual metric counts are visible in the
application Component Metrics section on the Dashboard tab page. Use the following
image as a guide:
5.

Chapter 5 - Page 9
Chapter 5 - Page 10
Chapter 6
Chapter 6 - Page 1
Chapter 6 - Page 2
Practices Overview
The purpose of this practice is to configure appropriate resources in Oracle WebLogic Server
with the Oracle WebLogic Administration Console depending on application requirements. The
two cases, selected for this practice are configuring JNDI resources for database connections
and for JMS resources. In this practice the key tasks include:
Configuring the run-time database adapter to match the design-time configuration of a

DB Adapter used by a composite application to perform database operations.
Deploying and testing the composite application that performs database operations.
Configuring JMS resources for two composite applications that communicate using the
JMS Adapter.
Deploying and testing the JMS composite applications.
General Notes
The developer of a composite application that uses some of the JCA adapters, such as the
Database Adapter and the JMS Adapter, should provide an administrator with information about
the design-time resources those applications require. For example:
For the Database Adapter, the design-time configuration must specify the name of
Java Naming and Directory Interface (JNDI) string for a connection factory that is
configured in the WebLogic Server run-time environment. In addition, the design-time
database connection name must match a JDBC resource JDNI name that is also
configured in the run-time server.
For the JMS Adapter, the design-time configuration can specify JMS resources, such
as queue (or topic) names, in terms of a JNDI name. The JNDI names for these
resources must be configured in the run-time server for the JMS adapter to enable
JMS applications to communicate message using the named queues (or topics), which
in turn depend on an associated connection factory to be configured in the run-time
server.
With the above in mind, your tasks as an administrator are to configure the run-time resources
defined by the application developers to enable the application to execute without error.

Chapter 6 - Page 3
Overview
In this practice you configure the run-time server resources required for a composite application
that uses a Database Adapter to store purchase order information in the SOADEMO database
schema ORDER and ITEMS tables. In this practice your tasks are to:
Create the SOADEMO database schema in the Oracle XE Database instance, and
populate the SOADEMO schema with tables and sample data with supplied SQL scripts.
Configure the appropriate JDBC resource required by the application.

Configure the DbAdapter component with a connection factory that uses the
appropriate JDBC resource.
Assumptions
The SQL scripts needed to create the SOADEMO schema and the database tables, and populate
the tables are in the D:\labs\sql folder.
Tasks
In this section you perform the three tasks described in the overview of this practice.
Creating the SOADEMO Database Schema
To create the SOADEMO database schema, perform the following steps:
1. On the Windows Desktop, click Start > Programs > Oracle Database 10g Express Edition >
Run SQL Command Line.
Note: Alternatively, start a Command Prompt window and enter the following command:
D:/> sqlplus /nolog
2.
3.
In the SQL Command Line command window, enter the following commands to login as the
database administrator and create the SOADEMO schema:
SQL> connect sys/oracle as sysdba
Connected.
SQL> @D:\labs\sql\soademo_user.sql
Grant succeeded.
SQL>
Note: Do not exit from the SQL Command Line application.
In the SQL Command Line command window, execute the following commands to connect
as the SOADEMO user, create and populate the database tables:
SQL> connect soademo/soademo
Connected.
SQL> @D:\labs\sql\soademo_create.sql
...
create sequence 'ADDRESS_SEQ'
Sequence created.
SQL> @D:\labs\sql\soademo_data.sql
...

Chapter 6 - Page 4
Practice 6-1: Configure the Run-Time Database Adapter
Configure the Run-Time JDBC Resource

You configure the JDBC resources by using the Oracle WebLogic 11g Administration Server
Console.
5. To login to the Oracle WebLogic 11g Administration Server Console, perform the following
steps:
a. On a Web Browser window enter the URL http://localhost:7001/console.
b. On the Oracle WebLogic Server 11g Administration Console Login page, enter
weblogic for the user name, and welcome1 for the password, and click Login.
6. To create the JDBC resource, perform the following steps:
a. On the Oracle WebLogic Server 11g Administration Console home page, in the
Domain Structure section expand the Services > JDBC tree, and click Data Sources.
b.
On the Summary of JDBC Data Sources page, click New.

Chapter 6 - Page 5
4.
Commit complete.
SQL>
Note: If you encounter errors when executing the above scripts, you can view the
messages in their soademo_create.log and soademo_data.log files,
respectively. The log files are created in the
D:\oraclexe\app\oracle\product\10.2.0\server\bin folder.
Minimize SQL Command Line window, because you use the application to execute
additional SQL scripts that query the ORDER and ITEMS database tables after deploying
and executing a database enabled composite application.
On the Create New JDBC Data Source > JDBC Data Source Properties page, enter
the following case-sensitive information and click Next.
Name: soademoDS
JNDI Name: jdbc/soademo
d.
e.
f.
Note: Accept default values for other settings.

On the Create a New JDBC Data Source > JDBC Data Source Properties page,
accept the default settings and click Next.
On the Create a New JDBC Data Source > Transaction Options page, click Next.
On the Create a New JDBC Data Source > Connection Properties page, enter the
following field values and click Next.
Database Name: XE
Host Name: localhost
Port: 1521
Database User Name: soademo
Password: soademo
Confirm Password: soademo

Chapter 6 - Page 6
c.
On the Create a New JDBC Data Source > Test Database Connection page, click
Test Configuration.
h.
On the Create a New JDBC Data Source > Test Database Connection page, confirm
that you get a Connection test succeeded. response message in the Messages
section, click Next.
i.
.
Note: If you got a connection error, then please correct the connection details before
you proceed with remaining steps of this practice.
On the Create a New JDBC Data Source > Select Targets page, select the check
box for the soa_server1 row in the Servers table, and click Finish.

Chapter 6 - Page 7
g.
On the Summary of JDBC Data Sources page, confirm the new JDBC resource has
been created. For example:
Configure the Run-Time DbAdapter Connection Factory Resource

While logged into the Oracle WebLogic Server 11g Administration Console, you create the
connection factory that associates a JNDI name used by the application with the JDBC resource
configured in the section subtitled Configure the Run-Time JDBC Resource.
7. To configure the DBAdapter connection factory, perform these steps:
a. On the Web Logic Admin home page, in the Domain Structure section, click
Deployments.

Chapter 6 - Page 8
j.
In the Summary of Deployments > Control tab page, locate the DbAdapter entry in
the Deployments table and click the DbAdapter link.
c.
d.
On the Settings for DbAdapter page, click the Configuration tab.

On the Settings for DbAdapter > Configuration tab page, click the Outbound
Connection Pools tab.
e.
On the Outbound Connection Pools tab page, click New.

Chapter 6 - Page 9
b.
On the Create a New Outbound Connection page, select the

javax.resources.cci.ConnectionFactory option, and click Next.
g.
On the Create a New Outbound Connection page, enter the following JNDI Name:
eis/DB/soademo and you must also press Enter, and then click Finish.
h.
On the Save Deployment Plan Assistant page, accept the default Path value and
click OK to save the deployment plan.

Chapter 6 - Page 10
f.
On the Settings for DbAdapter > Configuration > Outbound Connection Pools page,
(the Connection Pools tab should already be selected, otherwise click the Connection
Pools tab), expand the javax.resource.cci.ConnectionFactory entry, and click the
eis/DB/soademo link.
j.
On the Settings for javax.resource.cci.ConnectionFactory > Properties tab page, for

the Outbound Connection Properties table, click in xaDataSourceName rows
Property Value, type jdbc/soademo and press Enter. Then click Save.

Chapter 6 - Page 11
i.
8.
On the Settings for javax.resource.cci.ConnectionFactory > Properties tab page,

confirm the Messages at the top of the page indicate the changes have been activated
and successfully updated. For example:
To ensure that the outbound connection properties in the new deployment plan are
activated, you update the DbAdapter with a new deployment plan by performing the
following steps:
a. On the Domain Structure window, click the Deployments link.
b. On the Summary of Deployments page, locate and select the check box for the
DbAdapter row in the Deployments table, and click Update.

Chapter 6 - Page 12
k.
On the Update Application Assistant Locate new deployment files page, select the
Redeploy this application using the following deployment files: option, accept the
default settings for the Source path and Deployment plan path, and click Finish.
d.
On the top of the Summary of Deployments page, in the Messages section, confirm
the changes have been activated and deployments have been updated. For example:

Chapter 6 - Page 13
c.
Chapter 6 - Page 14
Overview
In this practice you deploy and execute the DBInsertPOComposite application to test if your runtime Database Adapter has been configured correctly.
Assumptions
You have performed the configuration tasks defined in Practice 6-1.
Tasks
1.
To deploy the DBInsertPOComposite application, perform the following steps:

a. In a Command Prompt window (open a new one if needed), use the SOA archive to
deploy the DBInsertPOComposite application by executing the following commands:
D:\> cd D:\labs\lesson06\DBInsertPOComposite\deploy
D:\> deploy sca_DBInsertPOComposite_rev1.0.jar
b.
2.
Note: The D:\labs\bin folder should be in your PATH, otherwise use the fully
qualified command D:\labs\bin\deploy.
Verify that deployment is successful. For example:
Before initiating the DBInsertPOComposite application, you need to check that data do not
yet exist in the ORDERS and ITEMS table. Maximize the Run SQL Command Line window
and execute the following SQL commands:
SQL> SELECT * FROM orders;
SQL> SELECT * FROM items;
Note: If you closed the Run SQL Command Line window used in Practice 6-1 to create the
soademo schema and its database tables, then you should start a new Run SQL Command
Line application window and login using the following SQL command:
When you execute the two SQL queries they should return the no rows selected result.
For example:

Chapter 6 - Page 15
Practice 6-2: Deploy and Test the Composite with a DBAdapter
b.
4.
In a Windows Explorer application window, wait for the po-medium-guitar.xml file

to disappear from the folder.
To verify that the database data has been inserted into the application database schema
tables, perform the following steps:
a. In the Web browser window with Oracle Fusion Middleware Control Console, locate
and click the DBInsertPOComposite [1.0] in the Farm navigation frame.
Note: Login to the Oracle Fusion Middleware Control Console with the username
weblogic and password welcome1, if required (due to session timeout or other
reason).
b. On the DBInsertPOComposite [1.0] > Dashboard tab page, verify that a new
application instance has been created and [hopefully] it has completed successfully.
For example:
Note: If the application instance shows a Fault, then you can be sure that the database
adapter has not been configured correctly. Then repeat the steps in practice 6-1 in this
practice.

Chapter 6 - Page 16
3.
Note: Alternatively, instead of the above SQL commands, you can execute the following
SQL*Plus script files to produce the same information:
SQL> @D:\labs\sql\show_ord.sql
SQL> @D:\labs\sql\show_items.sql
To initiate an instance of the DBInsertPOComposite application, perform the following
steps:
a. In a Windows Explorer application window, copy the D:\labs\xml\po-file\pomedium-guitar.xml file to the D:\labs\lesson06 folder
In the Run SQL Command Line window, with a final confirmation that your run-time
data source and connection factory configuration is correct, execute the following SQL
commands:
1) To check the data in the ORDERS table, execute:
SQL> SELECT * FROM orders;
Tip: If you did not close the Run SQL Command Line window, you can press the UP
arrow to recall previous entered commands to save typing.
Note: You should see the following results for data in the ORDERS table:
ORD_ID
CUST_ID TOTAL_PRICE DATE_ORDE DATE_SHIP STATUS
---------- ---------- ----------- --------- --------- ------100
2
2400 12-AUG-10
initial
2) To check the data in the ITEMS table, execute:
SQL> SELECT * FROM items;
Note: You should see the following results for data in the ITEMS table:
ITEM_ID
ORD_ID PROD_ID
PRICE
QUANTITY
---------- ---------- ------------------ ---------- ---------2
100 SKU203
450
2
1
100 SKU101
1500
1
For example:
5.
Note: To change display order of data rows, you can always add the text ORDER BY
item_id to the end of the second query to sort the rows by ITEM_ID column value.
Note: If the results you see match the document results, you can be sure that your run-time
database adapter configuration is successful.

Chapter 6 - Page 17
c.
Overview
In this practice you configure the JMS Adapter resources required for two composite
applications to communicate messages using JMS technology.
Assumptions
None.
Tasks
1.
On a Web Browser window, if you are not already logged into the Oracle WebLogic Server
11g Administration Console Web page, enter the URL http://localhost:7001/console, and
login using username weblogic and password welcome1.
Configure the JMS Queue Resource

2. To configure the demoMsgQueue JMS queue perform the following steps:
a. On Domain Structure window section, expand Services > Messaging and click JMS
Modules.
b.
On the JMS Modules page, click the SOAJMSModule link.

Chapter 6 - Page 18
Practice 6-3: Configure Run-Time JMS Adapter Resources
On the Settings for SOAJMSModules > Configuration tab page, in the Summary of
Resources table, click New.
d.
On the Create a New JMS System Module Resource page, select the Queue
(resource type) option, and click Next.

Chapter 6 - Page 19
c.
On the Create a New JMS System Module Resource page, in the JMS Destination
Properties section, enter the following case-sensitive values, and click Next when
done.
Name: demoMsgQueue
JNDI name: jms/demoMsgQueue
f.
On the Create a New JMS System Module Resource page, select

SOASubDeployment from the Subdeployments drop-down list and click Finish.
Note: When you select the SOASubDeployments value from the Subdeployments
drop-down list, the SOAJMSServer option should already be selected in JMS Server
table in the Targets section. If required, select the SOAJMSServer option before you
click Finish.
g.
On the Settings for SOAJMSModule page, in the Messages section at the top of the
page, check that the messages confirm the new JMS Queue resource has been
created successfully. For example:

Chapter 6 - Page 20
e.
b.
On the Create a New JMS System Module Resource page, for the resource type
select the Connection Factory option, and click Next.
c.
On the Create a New JMS System Module Resource > Connection Factory
Properties page, enter the following values and click Next when done.
Name: demoCF
JNDI Name: jms/demoCF

Chapter 6 - Page 21
Configure the JMS Connection Factory Resource

3. To configure the demoCF JMS connection factory perform the following steps:
a. On the Settings for SOAJMSModule page, in the Summary of Resources table, click
New.
On the Create a New JMS System Module Resource page, verify that the
soa_server1 check box is selected as the target server, and click Finish.
e.
On the Create a New JMS System Module Resource page, verify the Messages
section displays that the connection factory has been successfully created. For
example:
Create a JMS Adapter Connection Pool

4. To create a JMS connection pool and associate it to the connection factory perform the
following steps:
a. On the Oracle WebLogic Server Console home page, in Domain Structure section,
click Deployments.
b. On the Summary of Deployments > Control tab page, locate the JMSAdapter entry
and click the JmsAdapter link.

Chapter 6 - Page 22
d.
e.
f.
On the Settings for JmsAdapter page, click the Configuration tab.

On the Settings for JmsAdapter > Configuration tab page, click the Outbound
On the Settings for JmsAdapter > Configuration > Outbound Connection Pools tab
page, click New.
On the Create a New Outbound Connection page, select the

oracle.tip.adapter.jms.IjmsConnectionFactory option for the Outbound
Connection group, and click Next.

Chapter 6 - Page 23
c.
d.
On the Create a New Outbound Connection page, for JNDI Name, enter
eis/demo/Queue, and click Finish.
h.
On the Save Deployment Plan Assistant page, enter the path

D:\Oracle\fmw\11.1.1.3\Oracle_SOA1\soa\PlanJMS.xml and click OK.
i.
On the Settings for JmsAdapter page, in the Messages section at the top of the page,
verify that the changes have been activated. For example:

Chapter 6 - Page 24
g.
d.
On the Settings for oracle.tip.adapter.jms.IJmsConnectionFactory > Properties tab

page, in the Outbound Connection Properties table, enter the value jms/demoCF in
the ConnectionFactoryLocation Property Value cell, press Enter, and click Save when
done.

Chapter 6 - Page 25
Associate the Connection Pool with the Connection Factory

5. To associate the connection pools with the connection factory in new JMS Adapter
configuration plan, perform the following steps:
a. On the Settings for JmsAdapter page, click the Configuration tab.
b. On the Settings for JmsAdapter > Configuration tab page, click the Outbound
c. On the Settings for JmsAdapter > Configuration > Outbound Connection Pools tab
page, expand the oracle.tip.adapter.jms.IJmsConnectionFactory entry, locate and click
the eis/demo/Queue link.
Redeploy the JMS Adapter with the New Resources

6. To redeploy the JMS adapter with the newly configured resources, perform the following
steps:
a. On the Oracle WebLogic Server 11g Administrator Console home page, in the Domain
Structure panel, click Deployments.
b. On the Summary of Deployments page, in the Deployments table locate the
JmsAdapter entry and select the check box for the JmsAdapter, and click Update.

Chapter 6 - Page 26
e.
Note: Remember you must press Enter after entering the ConnectionFactoryLocation
property value. Do not use the Tab key.
On the Settings for oracle.tip.adapter.jms.IJmsConnectionFactory page, verify the
Messages section displays messages indicating the deployment plan has been of
successfully updated. For example:
On the Update Application Assistant page, select the Redeploy this application using
the following deployment files: option, and click Finish.
d.
On the Summary of Deployments page, verify the Messages section displays

messages indicating the deployments have been updated. For example:
Log out of the Oracle WebLogic Server 11g Administration Console. For example:

Chapter 6 - Page 27
7.
c.
Note: You can close the Oracle WebLogic Server 11g Administration Console web page.
However, you may have to return here to correct any problems if the application fails to
execute due to the JMS configuration being incorrectly configured.

Chapter 6 - Page 28
Overview
In this practice you use a supplied SOA bundle to deploy two JMS composite applications to
test that the JMS resources have been correctly configured in Practice 6-3. The SOA bundle
contains the following two composite applications:
The JMSPublisherComposite application, which accepts a simple string value on input

either from its SOAP interface or an XML file placed in the D:\labs\lesson06 folder.
The message is sent to the JMS queue (jms/demoMsgQueue) that you configured in
practice 6-3.
The JMSConsumerComposite application, which listens for messages sent to the

jms/demoMsgQueue JMS queue and writes the text message with a date and time
into the jms_messages.log file in the D:\labs\lesson06 folder.
Note: If the JMS resource configuration was correctly done by following steps in Practice 6-3,
then the message you provide to the JMSPublisherComposite application should be written to
the jms_messages.log file in the D:\labs\lesson06 folder.
Assumptions
You have performed the configuration tasks defined in Practice 6-3.
Tasks
1.
To deploy the two JMS Composite applications by using the supplied jms_soabundle.zip
file, perform the following steps:
a. In a Command Prompt window (reuse an existing one or open a new one as needed),
use the SOA bundle to deploy the JMSProducerComposite and
JMSConsumerComposite applications by executing the following commands:
D:\> cd D:\labs\lesson06\deploy
D:\> deploy jms_soabundle.zip
b.

Chapter 6 - Page 29
Practice 6-4: Deploy and Test the Composites using a JMS Adapter
b.
c.
Note: Login to the Oracle Fusion Middleware Control Console with the username
weblogic and password welcome1, if required (due to session timeout or other
reason).
On the JMSPublisherComposite [1.0] > Dashboard tab page, click Test
On the JMSPublisherComposite [1.0] > Test Web Service page, scroll down to the
Request tab and enter the text Test JMS message in the input field of the Input
Arguments section, and click Test Web Service. For example:

Chapter 6 - Page 30
2.
Note: You can close or minimize the Command Prompt window.

To initiate the JMSPublisherComposite application, perform the following steps:
a. In the Web browser window with Oracle Fusion Middleware Control Console, locate
and click the JMSProducerComposite [1.0] in the Farm navigation frame.
On the On the JMSPublisherComposite [1.0] > Test Web Service > Response tab
page, click the Launch Message Flow Trace link to display the Flow Trace. For
example:
e.
While viewing the Flow Trace page, observe and verify that the PublisherJMSService
component completes successfully, and that the JMSConsumerJMSService also
completes successfully.

Chapter 6 - Page 31
d.
b.
c.
4.
In a Windows Explorer window, verify that the jms_message.log file has been
created in the D:\labs\lesson06 folder, and open the file in Notepad to view the
message received and written to the log file.
Tip: Double-click the jms_message.log file to open it in Notepad. The file contents
should contain the data similar to the following example:
Note: The message text Test JMS message entered in the Test Web Service page
earlier, appears after a date and time string prefixed to the message text.
d. Close the Notepad window.
If you have time and wish to perform additional message test using files to input message
data, you can copy any (or all) of the supplied message XML files (msg_1.xml,

Chapter 6 - Page 32
3.
Note: The Flow Trace shows that the JMSConsumerComposite instance components
handle the JMS message produced by the JMSPublisherComposite instance. This is
possible because both applications are running in the same SOA server. If they were
running in different SOA servers (as would normally be the case) the
JMSConsumerComposite instance details would not be visible in the Flow Trace page.
f.
Close the Flow Trace window or page.
Note: If the run-time server JMS configuration was not correct, you would have received an
exception message in a dialog box as a response after clicking Test Web Service. If you
receive an exception message (or fault) in a dialog box, this indicates you need to review
and repeat the steps in Practice 6-3 and this practice before you continue.
As a final verification that the JMSConsumerComposite application received the message
data from the JMSPublisherComposite application and wrote the message to its log file,
a. In a Windows Explorer window, navigate to the D:\labs\lesson06 folder.
msg_2.xml, and msg_3.xml) from the D:\xml\jms-file folder into the

D:\labs\lesson06 folder to send one message per file through the
JMSProducerComposite application that should be received by the
JMSConsumerComposite application and appended to the jms_message.log file.

Chapter 6 - Page 33
Chapter 6 - Page 34
Chapter 7
Chapter 7 - Page 1
Chapter 7 - Page 2
Practices Overview
Deploy two BPEL processes.
Initiate the BPEL processes and monitor the process execution and activity using the
Oracle Fusion Middleware Control Console.
General Notes
The sample composite applications that are deployed demonstrate typical behavior of long
running (asynchronous) composite applications. The aim is to show you what you typically see
in the administration Web interface for such applications. The long running application is
implemented by using a BPEL wait activity that suspends processing for 2 minutes to
demonstrate a running process that waits for a response from another service without keeping
the resources overused.

Chapter 7 - Page 3
Overview
In this practice you deploy the following two composite applications.
The ValidatePayTypeComposite application, which is used to validate the payment

type used for a purchase order. Valid payment types are either paypal or credit. If
credit payment is used then the credit card type (AMEX, MCRD, VISA, and DINER)
must also be valid.
The ProcessPOFileComposite application accepts a purchase order (either from the

Fusion Middleware Control Console pages or a file in the file system) and depends on
the ValidatePayTypeComposite as a service reference to validate the payment type
specified for the order. This composite writes the results of the validation to a summary
log file in the files system.
Note: While it is possible to deploy multiple composite applications at the same time by using a
SOA Bundle (a zip file containing multiple SOA archives), you cannot use a SOA Bundle to
deploy composite applications that have dependencies. Therefore, you must deploy these two
composite applications individually. You deploy the ValidatePayTypeComposite application first,
to ensure that deployment of the ProcessPOFileComposite application can resolve its reference
to the ValidatePayTypeComposite application.
Assumptions
The files needed for deploying and testing the applications are located in the
D:\labs\lesson07 folder.
Sample purchase order files are located in the D:\labs\xml\po-file folder.
Tasks
1.
To deploy the ValidatePayTypeComposite composite applications, open a new Command

Prompt window and perform the following steps:
a. Change location to the deploy subfolder in the
D:\labs\lesson07\ValidatePayTypeComposite project folder.
b. Execute the deploy command-line script to deploy the application.
Note: The following example assumes that the D:\labs\bin folder is in your PATH,
otherwise replace the deploy command with the fully qualified name
D:\labs\bin\deploy:
D:\> cd D:\labs\lesson07\ValidatePayTypeComposite\deploy
D:\> deploy sca_ValidatePayTypeComposite_rev1.0.jar
Example: The output should look similar to the following results:

Chapter 7 - Page 4
Practice 7-1: Deploy the Purchase Order Processing Composites
To deploy the ProcessPOFileComposite composite applications in the Command Prompt

window, perform the following steps:
a. Change location to the deploy subfolder in the
D:\labs\lesson07\ProcessPOFileComposite project folder.
Hint: To minimize typing, you desktop environment may be configured to autocomplete folder and file names. Try entering the first few letters of each path or file
name and pressing Tab.
b. Execute the deploy command-line script to deploy the application.
Note: Reminder, the D:\labs\bin folder should be in your PATH, otherwise replace the
deploy command with the fully qualified name D:\labs\bin\deploy:
D:\> cd D:\labs\lesson07\processPOFileComposite\deploy
D:\> deploy sca_ProcessPOFileComposite_rev1.0.jar
3.
Ensure that both applications have been successfully deployed.

Note: In the Command Prompt window, the text BUILD SUCCESSFUL should appear in
the output results for each deployed application. You can also use Oracle Fusion
Middleware Control Console to verify that the applications are visible either in the Farm tree
as shown in the following image:
In the soa-infra (soa_server1) home > Deployed Composites tab page, you can also verify
that the composite are deployed as shown in the following image:

Chapter 7 - Page 5
2.
4.
Chapter 7 - Page 6
Close the Command Prompt window.
Overview
In this practice you copy an XML file into the folder specified as the input folder for the purchase
orders to be processed by the ProcessPOFileComposite application, monitor the execution of
the process, and observe the results in the form of a log file created by the application in a
folder specified as its output folder.
The following image shows the ProcessPOFileComposite application assembly model:
Note: The service entry points are shown on the left side of the Service Component
Architecture (SCA) assembly model (composite) diagram. From this you can see that it is
possible to initiate the ProcessPOFileComposite application from the processorderbpel_client
service entry point by using the Oracle Fusion Middleware Control Console Composite Test
Web Service page tool. However, this application has provided the ReadPOFileService entry
point to read the purchase order as an input file. The file adapter service interface avoids too
much typing to initiate the application, and simulates data input similar to the way an external
client application would provide input.
The ProcessPOFileComposite application:
Uses a BPEL process called ProcessOrderBPEL (the component in the middle of the
diagram) to process in input data.
Has the following two service references orchestrated (coordinated) by the

ProcessOrderBPEL process
The CheckPayTypeService service reference represents the interface for the
ValidatePayTypeComposite application that receives the payment type and credit
card information for validation.
The POLogService is a File Adapter service reference used to create the output file
containing a log record with the results of the payment type validation.
Assumptions
You have successfully deployed the ValidatePayTypeComposite and ProcessPOFileComposite
applications. You copy the purchase order input files provided in the D:\labs\xml\po-file
folder.

Chapter 7 - Page 7
Practice 7-2: Initiate the ProcessPOFileComposite
1.
2.
3.
Before copying a purchase order file to initiate the application, you use the information
described in the overview about the composite application assembly model and the Oracle
Fusion Middleware Control Console to answer the following questions:
a. Which folder is used by the application to read the input files?
Hint: In the ProcessPOFileComposite [1.0] home page, use the links in the
applications Services and References entries to find the po_dir property value for the
ReadPOFileService entry.
Answer: The folder for input files is set to D:\labs\lesson07.
b. Which folder is used by the application to store the log file, what is the log file name,
and why is there only one log file?
Hint: In the ProcessPOFileComposite [1.0] home page, use the links in the
applications Services and References entries to find the log_dir property of the
POLogService Reference.
Answer: The folder for the log file is set to: D:\labs\lesson07. The name of the log
file is set to po_summary.log. There is only one log file because the Append (Write)
operation is set to true. Therefore, new records are appended to the same file.
To initiate the ProcessPOFileComposite application, in Windows Explorer, you copy the file
D:\labs\xml\po-file\po-gibson-only.xml to the D:\labs\lesson07 folder.
Note: You must copy (do not move) the file because the input file adapter removes the file
from the input folder after it has been read (consumed) by the file adapter service.
To monitor the application, watch the input folder, wait for the input file to be removed as an
indication that the application has started to process the file, and then perform the following
steps:
a. Locate the composite application instance and view the Flow Trace page.
Hint: Click the ProcessPOFileComposite [1.0] link in the Farm tree to view the instance
link in the Dashboard and click the instance number link.
Note: You may have to refresh the page using the refresh icon in the top right corner of
the page (if you already had the page displayed).
b.
Using the application instance Flow Trace page, answer the following questions within
a two-minute period.

Chapter 7 - Page 8
Tasks
2)
On the Flow Trace page, click the ProcessOrderBPEL component link to locate the
currently executing activity by using either the Audit Trail or Flow tab pages. What
is the activity name?
Answer: On the ProcessOrderBPEL component Audit Trail page, while the

process is executing, the last activity displayed in the page should be waiting for
an asynchronous response. The name of the activity is called
Receive_paytypechk.

Chapter 7 - Page 9
Note: The application waits for the payment type validation to respond, which occurs
after a two-minute wait. If no actions on the questions within that time, you may not
observe the expected results.
1) What components are still executing? How do you know?
Answer: The ProcessOrderBPEL and the CheckPayTypeBPEL processes are still
running. The components State column for these components contains the
Running value. For example:
Click on the ProcessPOFileComposite [1.0] locator link at the top of the page to
navigate back to the main Flow Trace page.
4)
Click the CheckPayTypeBPEL link and identify the name of the activity executing
in its Audit Trail page, and explain how you can tell when it will complete?
Answer: The activity that is executing (provided you are viewing the page in time)
is called Wait_2_min. You know that the activity will complete based on audit trail
information (below the activity name) that indicates the expiry.

Chapter 7 - Page 10
3)
Wait for the Wait activity time to expire and the BPEL processes to complete. You can
monitor process completion by clicking the Flow Trace locator link at the top the page
to refresh the Trace tree, or confirm completion by refreshing the Dashboard (or
Instances) page in the home page for the composite application. For example: Here is
the information you may see in a refreshed Flow Trace page.
d.
Considering what you observed of the activity in the Flow Trace page, and the activities
you identified, answer the following questions:
1) Is the presence of a Receive activity waiting in a BPEL process something you
consider is a common occurrence? Explain your answer.
Answer: Yes, a Receive activity is commonly used to wait for responses from
asynchronously invoked services. Many BPEL processes are asynchronous
implementations. By implication, most (if not all) asynchronous processes are
designed to be long running implementations.
However, not all asynchronous invocations are designed return a response making
them one-way interactions. The ProcessPOFileComposite is an example of a oneway interaction, where the process receives input from a file and does not return
any response to the initiator, because there is no initiating client.
2) If you observe a Receive activity waiting for a response from service, how would
you know if it is waiting for a too long period? Explain your answer.

Chapter 7 - Page 11
c.
Viewing Metrics of a BPEL Process

4. By starting from the ProcessPOFileComposite [1.0] home page, you now learn to find
different information by examining the information presented in the Oracle Fusion
Middleware Control Console Web pages for the application and its component instances.
a. On the ProcessPOFileComposite [1.0] home > Dashboard tab page, locate the
Component Metrics section, And observe the summary values displayed for the
ProcessOrderBPEL component.
b.
Note: Do not click the ProcessOrderBPEL link yet.

In addition, on the ProcessPOFileComposite [1.0] home > Dashboard tab page, scroll
down the page to locate the Services and References section. Here you can find
throughput like information, such as in the Total Messages and Average Processing
Time columns.
c.
On the ProcessPOFileComposite [1.0] home > Dashboard tab page, scroll back to the
Component Metrics section and now click the ProcessOrderBPEL component link to
view the details for that BPEL process.
d.
On the ProcessPOFileComposite [1.0] home > ProcessOrderBPEL page, if you do not

see completed instance information, deselect the Show Only Running Instances
check box. For example:

Chapter 7 - Page 12
e.
Answer: In this case, you cannot know how long a Receive activity should wait for
a response, unless the implementation documentation or implementer provides
you with some guidelines on what to expect.
However, if you know how to track down the service reference that is expected to
return the response and it is within your own run-time environment, you could
monitor that process to find out if there are any problems. Otherwise, you would
have to wait until someone contacts you for any problems about incomplete
processes. Therefore, it is important for the process design and implementation to
provide some way of tracking or managing progress and state of a long running
business process.
Close the Flow Trace page.
Note: In the image above, the Instance Rate per Min (Real-Time Data) and
References sections are also expanded. Clicking the Table View link below the
Instance Rate per Min (Real-Time Data) graphic displays a page containing a table of
information similar to the following picture:

Chapter 7 - Page 13
e.
Note: If you click the link in Instance ID column, the Audit Trail tab page of the Flow
trace for the process is opened. Do not click the Instance ID link at this time.
On the ProcessPOFileComposite [1.0] home > ProcessOrderBPEL page, you can
collapse the Recent Faults (because there are no faults to be viewed), expand the
Activity Time Distribution section and view the Average Execution Time (in
milliseconds) for each activity executed in the BPEL process. This is a good way to
track down where a process potentially spends the most time.
Returning to the ProcessPOFileComposite [1.0] home > ProcessOrderBPEL page, you

can click the Logs icon for a given BPEL process instance to view the log file contains
for that process.
Note: On the Log Messages page, you can search for specific log messages. By
default the most recent log messages are visible. If you click a log message entry, the
full log details are displayed in the lowest frame.

Chapter 7 - Page 14
f.
Viewing the BPEL Engine Information and Statistics

5. Click the soa-infra (soa_server1) entry in the Farm tree.
6. To view the BPEL Service Engine information, on the soa-infa home page, click SOA
Infrastructure > Service Engines > BPEL.

Chapter 7 - Page 15
Note: If you click the soa_server1-diagnostics.log link you can view all the
messages in the associated log file.
On the BPEL Engine (Service Engine) page, you are presented with an overview of all the
BPEL processes in the partition. For example:
8.
To view the general statics and thread information for the BPEL Engine partition, on the
BPEL Engine (Service Engine) page, click the Statistics tab.
On the BPEL Engine (Service Engine) > Statistics tab page, you can observe Pending
Requests and Active Request initially in a graph format. For example:

Chapter 7 - Page 16
7.
View the Output Result of the ProcessPOFileComposite Application

In this section, you finally locate the output log file called po_summary.log in the
D:\labs\lesson07 folder, display the file contents, and then cross check the information
found in the log file with the information you can track in the Audit Trail and Flow pages within
the BPEL process Flow Trace page.
View the Log File Data
9. To view the log file contents, perform the following steps:
a. Open a Windows Explorer window, navigate to the D:\labs\lesson07 folder (the
output folder used by the application to store the log file data), and confirm that the file
called po_summary.log exists. Double-click the po_summary.log file to open it in
Notepad.

Chapter 7 - Page 17
Note: The example does not show anything in the Pending Requests or Active Requests
graphs because there was not much going on at the time of image captured. The Thread
Statistic section at the bottom of the page can be useful to monitor and help you decide if
you need to change BPEL Engine related thread properties.
c.
On the Notepad window, view the process results.
Note: The data is comma separated values representing the order ID, customer ID,
order total, payment type, and a status result (valid) for the chosen payment type
(respectively). In this case, the credit card type used is not shown, but it is also
validated by the process.
Close the Notepad window, and optionally close or minimize the Windows Explorer
window.
Track the Result Data in the Process Audit Trail and Flow Tab Pages
10. To track the message data for the output results in the BPEL process Audit Trail pages,
a. On the Oracle Fusion Middleware Control Console page, locate the
ProcessPOFileComposite [1.0] home page, and click the instance ID link for the
recently completed process to display the Flow Trace page (if the Flow Trace is not
already displayed). On the Flow Trace page, in the Trace section, click the
ProcessOrderBPEL link.
b.
Note: Clicking the BPEL process component link opens the Audit Trail page for the
BPEL process.
On the Instance of ProcessOrderBPEL > Audit Trail page, scroll down to the last
activity (Invoke_ordlog) and expand the <payload> entry to view the order summary
data that is sent to the POLogService and written into the po_summary.log file. For
example:

Chapter 7 - Page 18
b.
d.
To view the same information in a different format, on the Instance of

ProcessOrderBPEL page, click the Flow tab.
Note: Clicking the Flow tab causes the BPEL process activities to be rendered
(displayed) in an iconic format showing the actual run-time activities executed by the
BPEL process.
On the Instance of ProcessOrderBPEL page, click the Flow tab, after the page is fully
displayed, scroll to the end of the page (and in this case, the end of the process) and
click the Invoke_ordlog icon to view the Activity Audit Trail details.

Chapter 7 - Page 19
c.
Note: If you have any queries about the payload you observe, you can copy the
information in the Activity Audit Trail window by clicking the Copy details to clipboard
link and paste the data into a file or another application for communication with
application developer and support team (if needed).
f. Close the Activity Audit Trail window.
11. Close the Flow Trace Web page.

Chapter 7 - Page 20
e.
Note: The BPEL process activity icons, displayed in the Flow tab, resemble those that
are used in the Oracle JDeveloper BPEL Designer to implement the BPEL process.
On the Activity Audit Trail window, you can view the payload data sent to the
POLogService Write operation. For example:
Chapter 8
Chapter 8 - Page 1
Chapter 8 - Page 2
Practices Overview
In the practices for this lesson the key tasks are:
Deploy additional composite applications each containing a Mediator component with

transformations, with and without filters, with sequential and parallel routing rules.
Initiate and monitor the Mediator Engine and Mediator components in the composite
applications.
General Notes
There are two composite applications created for this practice, and each composite application
with two versions. The two applications (each with two versions) to be deployed are:
1. The SeqPOMediatorComposite application accepts a purchase order XML structure
either from a file or via a SOAP invocation, and sends the order for processing to two
different BPEL processes within the same application. The Mediator component uses
two routing rules that are configured for sequential execution order.
a. Version [1.0] contains two routing rules with a sequential processing defined
without any filters.
b. Version [2.0] modifies version [1.0] by adding filters to each of the routing rules.
Note: This application reads purchase order files copied into the
D:\labs\lesson08\seq_orders folder, and writes its output files (using a different
naming convention) into the same folder.
2. The ParallelPOMediatorComposite application is almost identical to the
SeqPOMediatorComposite application in that it accepts a purchase order XML structure
either from a file or via a SOAP invocation, and sends the order for processing to two
different BPEL processes within the same application. However, the ParallelPOMediator
component uses two routing rules that are configured for parallel execution order.
a. Version [1.0] contains two routing rules with a sequential processing defined
without any filters.
b. Version [2.0] modifies version [1.0] by adding filters to each of the routing rules.
Note: This application reads purchase order files copied into the
D:\labs\lesson08\parallel_orders folder, and writes its output files (using a
different naming convention) into the same folder.
Note: You are supplied with SOA Bundles that enable you to deploy both applications with
one deployment command. A side effect of this practice is you learn the effects of making
one of the versions the default version through the administration management of the
applications.
Additional Note: While you deploy the four SOA composite applications you do not test
them all.

Chapter 8 - Page 3
Overview
In this practice you deploy the SOA Bundle two composite applications (each containing a
Mediator component). While deployment is described by using the command-line script, you can
also deploy the SOA Bundle by using the Oracle Fusion Middleware Control Console (if you
prefer).
Assumptions
The SOA bundles are supplied in the D:\labs\lesson08 folder tree.
Tasks
To deploy the two composite applications using the deploy command-line script, perform the
following steps:
1. If required, open a new Command Prompt window by double-clicking the Command Prompt
desktop icon.
2. In the Command Prompt window, use the supplied SOA Bundle ZIP file to deploy two SOA
Composite applications by executing the following commands:
D:\> deploy POMediatorSOABundle_rev1.0.zip
3.
Note: If your PATH environment variable does not include the D:\labs\bin folder, then
use the fully qualified command D:\labs\bin\deploy. Alternatively, you can deploy the
SOA Bundle by using default options in the Oracle Fusion Middleware Control Console.
In your Web browser, open the Oracle Fusion Middleware Control Console page (if needed,
using the URL http://localhost:7001/em), verify that the following two SOA applications have
been added to the SOA > soa-infra (soa_server1) > default tree:
SeqPOMediatorComposite [1.0]
ParallelPOMediatorComposite [1.0]
Note: If the two SOA applications are not visible in the default partition tree, then refresh
the Oracle Fusion Middleware Control Console page. In the Command Prompt window, you
can also verify that the deployment is successful.

Chapter 8 - Page 4
Practice 8-1: Deploy SOA Applications with Mediator Components
Overview
In this practice, your tasks are to copy a purchase order file into:
The D:\labs\lesson08\seq_orders folder, and monitor the

SeqPOMediatorComposite application and Mediator instance created.
The D:\labs\lesson08\parallel_orders folder, and monitor the

ParallelPOMediatorComposite application and Mediator instance created.
Note: The two composite applications use BPEL components to simulation a fixed amount
of time to process each purchase order. The maximum time you would have to wait for
completion is approximately two minutes. The simulated wait time provides you with an
opportunity to view the instances while they are in a running state.
Assumptions
You have successfully deployed the version [1.0] applications either using the command-line
deployment script or the Oracle Fusion Middleware Control Console Web page.
Tasks
1.
2.
To initiate the SeqPOMediatorComposite application, perform the following steps:

a. If needed open Windows Explorer, and copy the file D:\labs\xml\po-file\pogibson-only.xml to the D:\labs\lesson08\seq_orders folder.
Note: Ensure you copy (and do not move) the file because the application consuming
the file will delete it. While the application creates a new order file, the output file format
is a different XML document structure.
b. Before you return to the Oracle Fusion Middleware Control Console Web page, with
the contents of the D:\labs\lesson08\seq_orders folder still visible in Windows
Explorer, wait until you see the po-gibson-only.xml file removed. When the file is
removed, a new application instance should have started processing the file.
To monitor the SeqPOMediatorComposite application instance data and information by
using the Oracle Fusion Middleware Control Console, perform the following steps and
answer any associated questions:
a. On the Oracle Fusion Middleware Control Console, to view the new instance ID in the
Dashboard tab page, click the SeqPOMediatorComposite [1.0] link in the SOA > soainfra (soa_server1) > default node of the Farm navigation frame.
b. On the SeqPOMediatorComposite [1.0] > Dashboard tab page, click the new instance
ID link to display the Flow Trace for the application. By using the Flow Trace page,
locate the Audit Trail for the ReadPOMediator component in the application and
1) Can the payload for any steps be expanded and viewed in the Audit Trail?
Answer: No, you cannot view the payload for any of the steps listed in the audit
trail page. You can see the steps which show the receiving of a request
(represented by the onMessage section), and the routing rules (represented by
onCase sections) with the actions performed within each step, such as
transformations and invocations.
2) What property can be changed to view the payload for each step?

Chapter 8 - Page 5
Practice 8-2: Initiate and Monitor Version [1.0] Applications
The Service Engine level , in this case the Mediator Service Engine
properties, by clicking the SOA Administration > Mediator Properties in the
SOA Infrastructure menu (also found by right-clicking the soa-infra
(soa_server1) node in the Farm navigation frame). In the Mediator Service
Engine Properties page, change the value of the Audit Level property.
Note: By default the Audit Level is set to the Inherit value. The value is
inherited from the Audit Level property value set for the SOA Infrastructure
level. Changing the Audit Level in the service engine affects all components
executed by the service engine. In this case, all new Mediator component
instances would be affected.
The composite application level, by clicking the composite application name in
the SOA > soa-infa (soa_server1) > default > tree (for example:
SeqPOMediatorComposite [1.0]), then clicking Settings > Composite Audit
Level: Inherit, and selecting one of the (Inherit, Off, Production, or
Development) options. For example:

Chapter 8 - Page 6
3)
Answer: The engine property that can be changed is the Audit Level, which can
be set to development mode. It should be in production mode by default (unless it
had been changed earlier).
At what levels can the appropriate property be set to view (or disable viewing)
payload information for each step in the Mediator components?
Answer: The Audit Level property setting can be changed at the following levels:
The SOA Infrastructure level (soa-infra (soa_server1)), by clicking SOA
Infrastructure menu (or right-click the soa-infa (soa_server1) node in the Farm
navigation frame), selecting SOA Administration > Common Properties and
selecting the Development Audit Level. Changing the Audit Level value in the
Common Properties is applied to all new composite application instances that
execute within the SOA server instance.
c.
d.
In the Confirmation dialog box, click Yes. A confirmation message about the changed
settings is displayed in the top of the composite home page.
Return to the Audit Trail page for the recently completed SeqPOMediatorComposite
application instance. Can you now view the payload for all steps in the Audit Trail now?
Why or why not?

Chapter 8 - Page 7
3.
Note: The Audit Level setting for the composite applications is inherited (by
default) from the SOA Infrastructure common property setting. Changing the
Audit Level setting for the composite application applies to all the component
instances executed in new composite application instances.
4) Which level would you choose to make the payload information visible and under
what conditions would you make that change?
Answer: The answer depends on the source of the problem you are trying to track
and where you think the cause may be. By changing the Audit Level in the
common properties of the SOA Infrastructure, you are collecting lot of extra
information for all composite instances. There is a larger processing and storage
overhead related to this choice and the size of the workload grows relative to the
amount of composite applications that executed and the size of message payloads
being processed. During development of the applications it is more likely that the
Audit Level in common properties of the SOA Infrastructure is changed to
Development. Otherwise, the choice really becomes one of helping you to isolate
problems related either to a specific Service Engine or a specific composite
application.
In this practice, you change the Audit Level for the composite application to Production, by
performing the following steps:
a. On the Oracle Fusion Middleware Control Console home page, click the
SeqPOMediatorComposite application in the SOA > soa-infra (soa_server1) > default
tree of the Farm navigation frame.
b. On the SeqPOMediatorComposite home page, select Settings > Composite Audit
Level: Inherit and click Development. For example:
5.
Answer: In this case, because the component that receives the input data is a File
Adapter, the payload in audit trail displays information about the JCA properties
set for the File Adapter, such as the input file name and the directory location from
where the file is read. For example:

Chapter 8 - Page 8
4.
Note: If you previously closed the Web browser page displaying the application Audit
Trail page, click the instance ID link in the Dashboard of the SeqPOMediatorComposite
home page and click the ReadPOMediator component link in the Flow Trace tree to
display the component Audit Trail page.
Answer: No, you still cannot view any payload information for steps of the recently
completed instance even if you refresh or reload the page. However, when you
initiate a new instance of this composite application you should see the payload
information and transformation details. Changing the setting for the Audit Level affects
new composite instances not any of the currently executing or completed instances.
e. Close the Web browser page (or window) that displays the Flow Trace for the
SeqPOMediatorComposite application.
In a Windows Explorer application window, if needed navigate to the
D:\labs\lesson08\seq_orders folder. If the SeqPOMediatorComposite application
has completed, then verify that the two files called credit_ordid_115.xml and
paypal_ordid_115.xml exist in the folder. The two files are created by the composite
application (one for each routing rule).
To initiate and monitor another instance of the SeqPOMediatorComposite application,
a. In a Windows Explorer application window, copy the D:\labs\xml\po-file\posmall-ipod.xml to the D:\labs\lesson08\seq_orders folder.
Note: Ensure you copy the file, and do not move the file.
b. Wait until the file is consumed from the D:\labs\lesson08\seq_orders folder.
c. Return to the SeqPOMediatorComposite application Dashboard page, and click the
most recent (top-most) instance ID for the application to open the Flow Trace.
d. On the Flow Trace page, click the ReadPOMediator component link to view the Audit
Trail of the Mediator component. Answer the following questions:
1) On the Audit Trail page, what differences do you notice in the way the information
is presented?
Answer: Each step now displays a payload part that can be expanded.
2) Expand the payload for the first step described as Input payload received. What
information about the input payload can be seen in addition to the order XML data
received?
7.
8.

Chapter 8 - Page 9
6.
This can be useful information if troubleshooting issues are related to data input to
a composite application.
Note: The amount of information you see differs depending on the type of entry point
used to initiate the composite application. This level of audit information, while useful,
may not be required for administration purposes, and is more valuable during the
development lifecycle of the application.
e. Close the Web Browser window (or page) displaying the Audit Trail or Flow Trace
page.
In a Windows Explorer application window, (if required) navigate to the
D:\labs\lesson08\seq_orders folder. The following two new files should be added to
the folder: credit_ordid_100.xml and paypal_ordid_100.xml. This is an indication
that the process completed successfully.
Delete all the files in the D:\labs\lesson08\seq_orders folder. For this practice, we
are not interested in the actual data in the files.
To view the Mediator Service Engine metrics, open the Mediator Service Engine page and
answer related questions by performing the following steps:
a. On the Oracle Fusion Middleware Control Console page, right-click the soa-infa
(soa_server1) node in the Farm navigator frame, and select Service Engines >
Mediator to open the Using the Mediator Engine (Service Engine) page.
b. How many instances of the ReadPOMediator component have been executed?
Answer: While there are two ReadPOMediator components present, one for the
SeqPOMediatorComposite and other for the ParallelPOMediatorComposite application,
only two instances of the ReadPOMediator in the SeqPOMediatorComposite have
been executed.
c. What other Mediator components are visible in the Components section?
Answer: The following six Mediator components visible in the Mediator Engine
Components section:
ReadPOMediator of the SeqPOMediatorComposite application
JMSPublisherMediator of the JMSPublisherComposite application
DBInsertPOMediator of the DBInsertPOComposite application
d.
e.
Note: The image above shows the first five Mediator components. If you wish to see all
Mediator components, you can click the Show All link below the Components table. In
addition, a component name is unique within its own composite application. However,
a component can have the same name as another component in another composite
application. Be sure you are tracking the appropriate component by ensuring you are
viewing the component for the correct composite application.
Where do you find the Request Breakdown statistic for Mediator components?
Answer: Click the Statistic tab in the Mediator Engine (Service Engine) home page,
and expand the Request Breakdown section. For example:
Where do you examine the Routing Statistics for the ReadPOMediator component of
the SeqPOMediatorComposite application?
Answer: First click the ReadPOMediator link for the SeqPOMediatorComponent in the
Components section.

Chapter 8 - Page 10
ReadPOMediator of the ParallelPOMediatorComposite application

JMSConsumerMediator of the JMSConsumerComposite application
HelloWorldMediator of the HelloWorldComposite application
Note: The ReadPOMediator component has two routing targets because it routes a
transformed message of the purchase order to the PayPalOrdersBPEL and to the
CreditOrdersBPEL process entry points.

Chapter 8 - Page 11
Then, on the Mediator Engine (Service Engine) > ReadPOMediator page, expand the
Routing Statistics section and expand the Route Target sub section to view the
processing times for each routing rule target of the mediator component.
Overview
In this practice you deploy the SOA Bundle containing version [2.0] of the composite
applications. In version [2.0] the Mediator components are updated to include filters on the
payment type used. Again deployment is done by using a command-line script. Alternatively you
can deploy the SOA bundle by using the Oracle Fusion Middleware Control Console.
Assumptions
The SOA bundles are supplied in the D:\labs\lesson08 folder tree.
Tasks
1.
2.
3.
4.
If required, open a new Command Prompt window by double-clicking the Command Prompt
desktop icon.
In the Command Prompt window, use the supplied SOA Bundle ZIP file to deploy two SOA
Composite applications by executing the following commands:
D:\> deploy POMediatorSOABundle_rev2.0.zip
Note: Use the command D:\labs\bin\deploy, if the D:\labs\bin folder is not in your
PATH environment variable. Alternatively, deploy the SOA bundle using default options in
the Oracle Fusion Middleware Control Console.
In your Web browser, open the Oracle Fusion Middleware Control Console page (if needed,
using the URL http://localhost:7001/em), verify that the following two SOA applications have
been added to the SOA > soa-infra (soa_server1) > default tree:
SeqPOMediatorComposite [2.0]
ParallelPOMediatorComposite [2.0]
Note: If the two SOA applications are not visible in the default partition tree, then refresh
the Oracle Fusion Middleware Control Console page. In the Command Prompt window,
verify that deployment was successful.
If you deploy the composite applications using the deploy command-line script (or default
settings in Oracle Fusion Middleware Control Console), then which version of the
application is the default version? How do you know?
Answer: The version [2.0] composite applications are the default revisions. On the home
page of the soa-infa (soa_server1) node, if you click the Deploy Composites tab, you can
see the green dot icon marker appearing before the version of a composite application that
is marked as the default revision. For example, the Deployed Composite Applications frame
on the soa-infra (soa_server1) home page shows the following information:

Chapter 8 - Page 12
Practice 8-3: Deploy SOA Applications Version [2.0]

Chapter 8 - Page 13
The version that is used to process requests depend on how composite applications are
initiated. If using the file adapter interface the default revision is initiated. If using the SOAP
interface, the answer is dependent on whether the SOAP client application specifies a
revision (version) number in the URL addresses for the application end point.
Overview
In this practice you initiate the ParallelPOMediatorComponent by copying a purchase order into
the input folder for the application. While there are two active versions of the application you use
Oracle Fusion Middleware Control Console to observe and control which version of the
application processes the purchase order.
Assumptions
You have successfully deployed the version [1.0] and [2.0] of the SeqPOMediator and
ParallelPOMediatorComposite applications.
Tasks
Both versions of the ParallelPOMediatorComposite application are configured to read an input
file from the same folder, and write the results to the same folder. The applications are designed
and deployed without changes for the purposes of this practice.
1. By using the Oracle Fusion Middleware Control Console verify that the
ParallelPOMediatorComposite [1.0] and ParallelPOMediatorComposite [2.0] applications do
not have any running or completed instances visible in their Dashboard pages.
Note: If you require the steps to do this task, then perform the following steps:
a. In the SOA > soa-infra (soa_server1) > default tree in Farm navigation frame, click on
the ParallelPOMediatorComposite [1.0] link, and confirm that the Dashboard page
does not display any instance information.
b. Click on the ParallelPOMediatorComposite [2.0] link (in the SOA > soa-infra
(soa_server1) > default tree in Farm navigation frame,) and confirm that the Dashboard
page does not display any instance information.
2. Because both versions of the ParallelPOMediatorComposite application use a thirty second
polling interval to look for new purchase order files, you first modify the polling frequency for
the ReadPOFileService File Adapter in the ParallelPOMediatorComposite [2.0] application
to sixty seconds. To change the polling frequency of the File Adapter, perform the following
steps:
a. To display the ParallelPOMediatorComposite [2.0] Dashboard page, if needed, click on
the ParallelPOMediatorComposite [2.0] link (in the SOA > soa-infra (soa_server1) >
default tree in Farm navigation frame.)
Note: The ParallelPOMediatorComposite [2.0] Dashboard page should already be
visible after performing the previous task.
b. On the ParallelPOMediatorComposite [2.0] Dashboard page, scroll down to the
Services and References section and click the ReadPOFileService link in the name
column.
c. On the ReadPOFileService (File Adapter) page, click the Properties tab.
d. On the ReadPOFileService (File Adapter) > Properties tab page, replace the
PollingFrequency (Read) value of 30 with a new value of 60 and click Apply. For
example:

Chapter 8 - Page 14
Practice 8-4: Initiate, Monitor, and Manage Versioned Applications
4.

Chapter 8 - Page 15
3.
e. In the Confirmation dialog box, click Yes.

f. In the Information dialog box, click OK.
To initiate a ParallelPOMediatorComposite application, perform the following steps:
a. In a Windows Explorer application window, copy the D:\labs\xml\po-file\pogibson-only.xml file to the D:\labs\lesson08\parallel_orders folder.
Note: Ensure you copy the file, and do not move the file.
b. Wait until the po-gibson-only.xml file is removed from the
D:\labs\lesson08\parallel_orders folder.
By using information in Oracle Fusion Middleware Control Console, which version of the
ParallelPOMediatorComposite application processed the file? Why?
Hint: Click the ParallelPOMediatorComposite [1.0] or ParallelPOMediatorComposite [2.0]
link in the soa-infra (soa_server1) > default node in the Farm navigation frame (or check
both pages).
Answer: The ParallelPOMediatorComposite [2.0] version processes the file, even though
both versions of the application are active and version [2.0] has a longer polling frequency
than version [1.0].
The reason why ParallelPOMediatorComposite [2.0] processes the file is because it is
marked as the default version.
Note: You can use the SOA Infrastructure > Dashboard (or Instances) page to determine
the answer as well. If you use these SOA Infrastructure pages, depending on your
computer screen display resolution and browser window size, you may have to resize the
columns in the Dashboard > Recent Composite Instances and Dashboard > Deployed
Composite frames to see the information clearly. For example:
Note: In the onCase CreditorsBPEL.creditordersbpel_client.process) you can see that the

evaluation of the comparison between the input payOption element value to the value
credit gave a true result. However, in the second routing rule (onCase
PaypalOrdersBPEL.paypalordersbpel_client.process) the comparison between the
payOption value and paypal string gave a false result.
This is typical example of content-based routing implemented by using filters (conditions)
that provide the application a way to route specific data to appropriate services for
processing based in a value in the input. In this case, since the input file has the payOption

Chapter 8 - Page 16
5.
Note: In the Dashboard > Deployed Composites frame, the number of instances is one for
the ParallelPOMediatorComposite [2.0] application and zero for
ParallelPOMediatorComposite [1.0].
In the Windows Explorer window, locate the D:\labs\lesson08\parallel_orders
folder and describe how many output files are created. Explain your answer.
Hint: You may need to wait about two minutes for the instance to complete. The Audit Trail
of the ReadPOMediator component has an indication of why only one output file is created
instead of two.
Answer: There is one output file (credit_ordid_115.xml) created in the
D:\labs\lesson08\parallel_orders folder.
The reason only one file is created is because the ParallelPOMediatorComposite uses a
filter to ensure that it routes the purchase order to one or the other BPEL process within the
composite application. The execution of filters is shown in the Audit Trail page for the
ReadPOMediator component. For example:
Manage Composite Component Properties and Application Life Cycle

7. Return to the ParallelPOMediatorComposite > ReadPOFileService (File Adapter) >
Properties tab page, and revert the property changes back to their default values. To do
this task, perform the following steps:
a. On the ParallelPOMediatorComposite [2.0] Dashboard page, scroll down to the
Services and References section and click the ReadPOFileService link in the name
column.
b. On the ReadPOFileService (File Adapter) page, click the Properties tab.
c. On the ReadPOFileService (File Adapter) > Properties tab page, click Revert.
d.
e.
f.
8.
In the Confirmation dialog box, click Yes.

In the Information dialog box, click OK.
On the ReadPOFileService (File Adapter) > Properties tab page, verify that the
PollingFrequency (Read) property value is 30. For example:
Note: There is no need to click Apply, because clicking Revert applied the change.
To shutdown the ParallelPOMediatorComposite [2.0] application, perform the following
steps:
a. On the Farm navigation tree, if needed, expand the SOA > soa-infra (soa_server1) >
default tree and click the ParallelPOMediatorComposite [2.0] entry.
b. On the ParallelPOMediatorComposite [2.0] home page, click Shut Down.

Chapter 8 - Page 17
6.
value credit, then the purchase order is routed to one BPEL process (CreditOrdersBPEL)
for processing the data.
Close the window containing the application Flow trace or Audit Trail page.
9.

On the ParallelPOMediatorComposite [2.0] home page, verify that the application is in
the shutdown state.
Which version of the ParallelPOMediatorComposite application is now the default version?

How do you know?
Answer: Even though you have shutdown the ParallelPOMediatorComposite [2.0]
application, it remains marked as the default revision. You can verify this by checking the
version marked as the default in the soa-infra > Dashboard page. For example:
Note: The default revision is not changed unless you:
Undeploy the version marked as the default revision.
Deploy a new version that becomes the default revision (as specified during
deployment).
Explicitly mark another version the default revision.

10. In Windows Explorer, copy the D:\labs\xml\po-file\po-small-ipod.xml file to the
D:\labs\lesson08\parallel_orders folder. This time, which application processes
the file? Explain your answer.
Note: Do not wait longer than two minutes before answering this question.
Answer: The file is not processed by any version of the application. Because the default
revision of the application has been shutdown, it no longer services or processes requests
(in this case the input file). A non-default revision that is still active cannot service a request
unless the client specifically issues a request to that version, where the end-point URL
explicitly contains the composite version number.
In this case, since the application is not initiated by a WSDL URL end-point invocation, and
instead is initiated by placing a file in the file system the environment cannot derive
version information from the file and the default version can only be used in such

Chapter 8 - Page 18
c.
d.
c.
d.
e.
Note: Read the message on the dialog box and make sure you understand what it tells
you. These messages are quite informative.
What indicates that the ParallelPOMediatorComposite [1.0] application has started to
process the input file?
Answer: On the ParallelPOMediatorComposite [1.0] > Dashboard page, when you get
the response confirmation message for making the application version as the default,
in the ParallelPOMediatorComposite [1.0] home page, you will see a new instance
created and in the Running state in the Recent Instances section. For example:
Note: In addition, you can confirm that the po-small-ipod.xml file has been
removed from the D:\labs\lesson08\parallel_orders folder.
Wait until the application instance completes, and in the Windows Explorer folder, how
many new output files are created?

Chapter 8 - Page 19
circumstances. Therefore, while the ParallelPOMediatorComposite [1.0] is still active, it

does not process the file because it is not the default application and its version cannot be
targeted when using the File Adapter for the input mechanism.
11. Now, to make the ParallelPOMediatorComposite [1.0] the default revision, perform the
following steps:
a. On the Farm navigation tree, if needed, expand SOA > soa-infra (soa_server1) >
default and click the ParallelPOMediatorComposite [1.0] link.
b. On the ParallelPOMediatorComposite [1.0] home page, click Set As Default.
e.
On the Farm navigation tree, if needed, expand SOA > soa-infra (soa_server1) >
default and click the SeqPOMediatorComposite [1.0] link.
f. On the SeqPOMediatorComposite [1.0] home page, click Retire.
g. In the Confirmation dialog box, click Yes.
h. Using the information in the soa-infra > Dashboard page in the Deployed Composites
frame, determine which revision of the SeqPOMediatorComposite application is the
default version. What do you discover?
Answer: The SeqPOMediatorComposite [1.0] revision is still the default application.
13. To undeploy the SeqPOMediatorComposite [1.0] revision, perform the following steps:
a. Right-click the SeqPOMediatorComposite [1.0] link in the SOA > soa-infra
(soa_server1) > default tree, and select SOA Deployment > Undeploy. For example:

Chapter 8 - Page 20
Answer: Two new files are created in the D:\labs\lesson08\parallel_orders

folder. The files are called credit_ordid_100.xml and paypal_ordid_100.xml.
f. Optional challenge question: If you remember what you observed in the Audit Trail
processing in ReadPOMediator component of ParallelPOMediatorComposite [2.0],
explain why two files are created by ParallelPOMediatorComposite [1.0]?
Hint: Consider reviewing the question and answer in this practice task number 5.
Answer: If you look at the Audit Trail page for the ReadPOMediator component of the
recent ParallelPOMediatorComposite [1.0] instance, you can observe that it does not
apply any filter conditions to any of its routing rules. Instead, the
ParallelPOMediatorComposite [1.0] version routes the purchase order to both its BPEL
processes irrespective of the value received in the payOption element.
12. You now start working on the sequential Mediator application implementation. To observe
how the lifecycle changes affect composite applications, you set SeqPOMediatorComposite
[1.0] as the default, and then you retire the default version of the application. To do this
task, perform the following steps and answer the questions:
a. On the Farm navigation tree, if needed, expand SOA > soa-infra (soa_server1) >
default and click the SeqPOMediatorComposite [1.0] link.
b. On the SeqPOMediatorComposite [1.0] home page, click Set As Default.
c. In the Confirmation dialog box, click Yes.
d. On the soa-infra > Dashboard page in the Deployed Composites frame, verify that the
SeqPOMediatorComposite [1.0] revision is the default. Use the following image as a
guide:
On the SeqPOMediatorComposite [1.0] > Undeploy SOA Composite page, observe the
information presented in the Default Revision and Running Instances sections, and
then click Undeploy.
c.
After the SeqPOMediatorComposite [1.0] is successfully undeployed, you get the

confirmation page displayed. What do you observ about the default revision for this
application?
Answer: The soa-infra > Deployed Composite tab page is displayed along with the
confirmation response message indicating that the SeqPOMediatorComposite [1.0] has
been undeployed. In the same page, look in the Composite column of the table
containing the list of deployed composite applications, and verify that the remaining
SeqPOMediatorComposite [2.0] revision is now marked as the default revision.

Chapter 8 - Page 21
b.

Chapter 8 - Page 22
Note: Remember that the default revision is identified by the green circle icon
appearing before the name of a revision of a composite application.
14. You can delete the files in the D:\labs\lesson08\parallel_orders folder.
Chapter 9
Chapter 9 - Page 1
Chapter 9 - Page 2
Practices Overview
Deploy and run a composite with Business Rules components.
Monitor the Business Rules Engine and instances.
General Notes
As described in Oracle documentation, the Business Rules Engine does not support any user
level configuration. Therefore, this practice follows the simple formula of deploying applications
and initiating them so that you can observe what you may see in the run-time context in related
sections of Oracle Fusion Middleware Control Console.

Chapter 9 - Page 3
Overview
In this practice you deploy the ShipPOComposite application, which contains a Business Rules
component. The Business Rules component executes two simple rules:
a) A Decision Table rule that evaluates the purchase order shipping choice value (that is:
next_day, two_day, five_day, or international)
b) An IF-THEN free shipping rule so that the shipping price is set to zero for orders with a
total greater than or equal to 1500.
The results returned to the application by the Business Rules engine are:
The shipping company name (USPS, UPS, FED_EX), which is used as a file name
prefix of the shipping request output file.
The shipping price, which is added to the order total in the shipment request output file.
Note: The application reads purchase order files from the D:\labs\lesson09 folder and
writes shipping request XML files to the same folder. Each output file name begins with the
name of the shipping company followed by an underscore and the order ID.
To make the remaining practices in this lesson more interesting, even though it is not
recommended doing so in a production context; before you initiate the application instances,
you set the composite Audit Level to Development mode. Setting the Audit Level to
Development mode makes it possible to observe more details in the application component
Audit Trail pages.
Assumptions
The files for deployment are located in the D:\labs\lesson09 folder.
Tasks
To deploy the application with the Business Rules component, perform the following steps:
1. In a Command Prompt window, use the SOA Archive (SAR) file to deploy the
ShipPOComposite application by executing the following commands:
D:\> cd D:\labs\lesson09\ShipPOComposite\deploy
D:\> deploy sca_ShipPOComposite_rev1.0.jar
2.
Note: If your PATH environment variable does not include the D:\labs\bin folder, then
change the deploy command to the fully qualified command D:\labs\bin\deploy.
Alternatively, you can deploy the SOA Archive using default options in the Oracle Fusion
To verify the deployed application is visible in Oracle Fusion Middleware Control Console,
and to change the Audit Level of the composite to Development mode, perform the
following steps:
a. In a Web Browser window, if required, login to Oracle Fusion Middleware Control
Console using URL http://localhost:7001/em with the username weblogic and
password welcome1.
b. On the Farm navigation frame, expand SOA > soa-infra (soa_server1) > default, verify
that the ShipPOComposite [1.0] application exists in the tree, and click the
ShipPOComposite [1.0] entry.
c. On the ShipPOComposite [1.0] home page, change the Audit Level click Settings >
Composite Audit Level: Inherit to Development. For example:

Chapter 9 - Page 4
Practice 9-1: Deploy a Composite with Business Rules
On the Confirmation dialog box, click Yes.

On the ShipPOComposite [1.0] home page, click the Close icon in the confirmation
message box indicating the audit level has been changed to Development.
d.
e.

Chapter 9 - Page 5
Overview
In this practice you copy four purchase order files from the D:\labs\xml\po-file folder into
the input folder of the composite application to initiate four instances so that you can monitor the
results of processing in Oracle Fusion Middleware Control Console.
Note: Because the Business Rules logic in general executes very quickly, the
ShipPOComposite application instances complete very fast. Therefore, it is unlikely that you can
monitor the processes during their Running states. However, you can view the instance
information maintained in the Oracle Fusion Middleware Control Console.
Assumptions
You have successfully deployed the ShipPOComposite application as described in the previous
practice.
Tasks
1.
To initiate the ShipPOComposite application, perform the following steps:

a. In a Windows Explorer application window, navigate to the D:\labs\xml\po-file
folder, select the following four files and click Edit > Copy (or press Ctrl+C):
po-gibson-only.xml
po-gibson-paypal.xml
po-large-ipod.xml
po-small-ipod.xml
b.
c.
In Windows Explorer, navigate to the D:\labs\lesson09 folder, and select Edit >
Paste (or press Ctrl+P).
You can wait for the four po*.xml files to be removed and replaced with four new files,
or you can continue to the next step of this practice.
Note: The following four output files should be created in the D:\labs\lesson09
folder:
Fedex_104.xml
Fedex_205.xml
UPS_100.xml
2.
USPS_115.xml
To monitor the execution of the ShipPOComposite application instances, return to the Web
browser page displaying the Oracle Fusion Middleware Control Console and perform the
following steps:
a. On the ShipPOComposite [1.0] home page, click the Refresh icon (in the top right
corner of the page). For example:
Note: If the ShipPOComposite [1.0] Dashboard tab page is not displayed, then click
the ShipPOComposite [1.0] entry in the SOA > soa-infra (soa_server1) > default tree of
the Farm navigation frame.

Chapter 9 - Page 6
Practice 9-2: Initiate and Monitor an Instance with Business Rules
On the ShipPOComposite [1.0] Dashboard tab page, confirm that you see four new
instances. Most likely each of these instances is already completed. For example:
c.
On the ShipPOComposite [1.0] Dashboard tab page, click any of the instance ID links
and examine the Flow Trace. While you answer the following questions for the instance
you selected, keep in mind that some of the results you observe may be different to the
examples shown in this document:
1) What is the name of the Business Rules component in the composite application,
and what is the name of the Decision Service?
Hint: In the Flow Trace look at the Trace tree for the Business Rules component
entry. Click the Business Rules component link in the Flow Trace tree to find the
name of the decision service.
Answer: The Business Rules component is called ShippingRules, and the
decision service is called ShippingRules_DecisionService. For example:

Chapter 9 - Page 7
b.
What is the order total for the purchase order before the business rule is
evaluated?
Hint: You need to locate the Assign_orderTotal activity in the Audit Trail page of
the BPEL component and expand its payload.
Sample Answer: For the instance ID selected in this document, the

Assign_orderTotal shows an orderTotal element contains the value 135.

Chapter 9 - Page 8
2)
For the order processed, by the composite instance you selected, what is the
shipping choice value in the input message?
Hint: Click the View XML Document link under the receiveInput activity in the
BPEL component Audit Trail page.
Note: Close the window that is opened to display the XML document.
Sample Answer: For the instance ID selected in this document, the purchase
order selected shows the shipChoice element contains the value two_day.

Chapter 9 - Page 9
3)
d.
What was the shipping company name and final order total including the shipping
price?
Hint: In the BPEL component Audit Trail page, locate the Assign_shiprequest
activity and expand its last payload entry to display all the information sent to the
output File adapter service.
Sample Answer: For the instance ID selected in this document, the shipping
request data shows the orderTotal element contains the value 145. This means
the shipping price for this order is a value of 10 given that the original order total is
135.
Close the Flow Trace page for the current instance being explored.

Chapter 9 - Page 10
4)
To view the Business Rules Engine information, right-click the soa-infra (soa_server1) node
of the SOA node in the Farm navigation frame and select Service Engines > Business
Rules. For example:
4.
On the Business Rules Engine (Service Engine) page, observe the Total Instances counts
in the Components section, and click the Statistics tab to view the information presented
about the four instances you created. For example:
5.
On the Business Rules Engine (Service Engine) Statistics tab page, locate the name of the
Business Rules operation that has the highest count. What is the name of the operation?
Hint: View the information in the Business Rules Operations Statistics section.
Answer: The name of the operation with the highest count is the callFunction
operation. For example:

Chapter 9 - Page 11
3.

Chapter 9 - Page 12
Note: The reason this is the only operation initiated by the application instances is due to
the way the decision service is invoked by the BPEL component. Depending on the
business process logic, this information may vary across different applications.
Because there is nothing more you can do to configure for the Business Rules Engine, feel free
to take a little more time (no more than five minutes) to explore the information available.
Chapter 10
Chapter 10 - Page 1
Chapter 10 - Page 2
Practices Overview
Configure the Oracle Weblogic Servers Embedded LDAP server with:

New credentials for the administrator account.
Users and groups that can be referenced by Human Workflow task services.
Configure Human Workflow Notification services and test sending email address.
Test the email driver configuration by using Human Workflow Engine notification
management tools.
General Notes
To keep the classroom environment footprint relatively small and simple, each single user PC is
configured with all the basic software required to perform all tasks defined in the practices. With
this in mind the Embedded LDAP server installed with Oracle WebLogic Server is used for
authentication services. The users and groups, required by the deployed application, have to be
configured before the application is initiated. The free JXplorer LDAP browser tool (see
http://jxplorer.org) is provided for you to accomplish this task.

Chapter 10 - Page 3
Overview
You configure the LDAP administrator user credentials for, and import user and group
information into, the Embedded LDAP server. Changing the LDAP administrator user
credentials is done in Oracle WebLogic Administrator Console and requires that you restart the
Oracle WebLogic Server and its Managed Servers, such as the SOA and BAM server
instances.
After restarting Oracle WebLogic Server, the JXplorer LDAP browser can successfully connect
to the Embedded LDAP Server for you to import the user and group information from supplied
LDIF files.
Assumptions
JXplorer is installed and the LDIF files are located in the D:\labs\ldap folder. The Start
Admin Server for Weblogic Server Domain and Stop Admin Server desktop icons have been
created (see Practice 3-5 on the page titled Practice for Lesson 3, if required.)
Tasks
Change Admin User Credentials for the Embedded LDAP Server
1. To change the credentials (password) for the Embedded LDAP server administrator
account, perform the following steps:
a. In a Web browser window, enter the URL http://localhost:7001/console to access the
Oracle WebLogic Server Administration Console page.
b. On the Oracle WebLogic Server Administration Console Welcome page, enter the
username weblogic and password welcome1 and click Login.
c. In the Domain Structure frame on the Oracle WebLogic Server Administration Console
page, click soa_domain. For example:
d.
e.
In the Settings for soa_domain frame, click the Security tab.

In the Settings for soa_domain frame, on the Security tab page click the Embedded
LDAP tab. For example:

Chapter 10 - Page 4
Practice 10-1: Configure the Embedded LDAP Server
On the Embedded LDAP tab page, enter the value welcome1 for the Credential and
Confirm Credential fields and click Save.
g.
On the top of the Settings for soa_domain frame, observer the Messages response to
the save action. For example:
h.
Note: The message indicates that two items must be restarted. In your cases, if you
have the BAM managed server running, you may have to restart 3 items. In the
example shown here, the items that must be restart are the WebLogic Server and the
SOA managed server instances.
You can verify which instances must be restarted by clicking the View changes and
restarts link in the Change Center frame on the top left corner of the Oracle WebLogic
Server Administration Console page. On the Changes and Restarts page, you can click
the Restart Checklist tab to view the servers listed. Because the node manager has not
been configured, you have to restart these servers by using the command-line
methods.
On the Oracle WebLogic Server Administration console page, click the Log Out link,
and close the Web browser window.

Chapter 10 - Page 5
f.
To restart Oracle WebLogic Server and the Oracle SOA Suite managed server, perform the
following steps:
a. If required, open a new Command Prompt window by double-clicking the Command
Shutdown the Managed Server Instances

b. To shutdown the SOA managed server instance, in the Command Prompt Window
enter the following commands:
D:\> cd D:\Oracle\fmw\11.1.1.3\user_projects\domains\soa_doma
in\bin
D:\> stopManagedWebLogic.cmd soa_server1
Note: The change directory command has been split over two lines for visual clarity.
The change directory command is not shown in the following example:
c.
d.
Note: It may take five to ten minutes to stop the SOA managed server gracefully. If you
prefer to terminate the process quicker press Ctrl+C in the Command Prompt window
where the SOA managed server is running. After shutting down the SOA managed
server, close its command window if it did not close after the shutdown operation
completes.
If you have the BAM managed server running, you may also have to shut that down.
To shutdown the BAM managed server, in the same Command Prompt window enter
the following command:
D:\> stopManagedWebLogic.cmd bam_server1
Note: After shutting down the BAM managed server, close its command window if it
did not close after the shutdown operation completes. Alternatively, press Ctrl+C in the
BAM managed server command window to terminate the instance.
Do not close the Command Prompt window in which you entered the
stopManagedWebLogic.cmd commands, because you use it to restart the managed
servers after you restart the WebLogic Admin Server.
Restart the Admin Server Instance

e. To shutdown the WebLogic Admin Server double-click the Stop Admin Server desktop
icon. For example:

Chapter 10 - Page 6
2.
Restart the Managed Server Instances.

h. Return to the Command Prompt window, in which you stopped the managed server
instances, ensure the current directory is still the
D:\Oracle\fmw\11.1.1.3\users_projects\domains\soa_domain\bin
folder, and enter the following command to start the SOA managed server instance:
D:\> start startManagedWebLogic.cmd soa_server1
i.
j.
Note: By using the start command prefix a new Command Prompt window opened,
you can start the BAM managed server from the original Command Prompt window.
Optionally, you can start the BAM managed server by entering the following command:
D:\> start startManagedWebLogic.cmd bam_server1
Note: We do not need to start the BAM server until we need it in a subsequent
practice.
Minimize the Command Prompt window you used to restart the SOA and BAM
managed servers, because you can reuse the Command Prompt to restart the SOA
managed server after changing Human Workflow Notification Server properties.
Import Users and Groups into the Embedded LDAP Server

In this section you start JXplorer LDAP browser, connect to the Embedded LDAP server as
admin user to seed the user and group information required for the Human Task Composite
application.
3. To start the JXplorer application and connect to the Embedded LDAP server, perform the
following steps:
a. On the Windows taskbar, click Start > Programs > JXplorer > JXplorer.
b. In the JXplorer window, select File > Connect.
c. In the Open LDAP/DSML Connection dialog box, enter the fields and click Save:
Field
Value
Host
localhost
Port
7001
Protocol
LDAP v3
In the Security section use

Level
User + Password

Chapter 10 - Page 7
f.
g.
Note: Double-clicking the Stop Admin Server icon opens a command window the shuts
down the Admin Server instance and closes the Admin Server instance command
window. However, the Stop Admin Server command window is not closed.
Close the command window used to stop the Admin Server.
To restart the Admin Server, double-click the Start Admin Server for Weblogic Server
Domain desktop icon.
Note: You must wait until the Admin Server is in a running state before you restart the
SOA and BAM managed servers. You can be sure that the Admin Server is in a
running state when you observe a line similar to the following example appear in the
command window:
<Jul 28, 2010 9:42:34 PM GMT> <Notice> <WebLogicServer> <BEA000360> <Server started in RUNNING mode>
User DN
cn=Admin
For example:
d.
In the Replace/Create Template dialog box, enter the value ldap_server, and click
OK.
e.
In the Open LDAP/DSML Connection dialog box, with the ldap_server template
selected, click OK.

Chapter 10 - Page 8
Password welcome1

Chapter 10 - Page 9
Note: If you enter the correct connection information, the JXplorer application creates a
successful connection with the Embedded LDAP server. The Explorer tab in the left
frame is populated with details read from the LDAP server. You can expand groups
and people nodes in the soa_domain > myrealm tree to view existing data. For
example:
To set the email address for the weblogic user, perform the following steps:
a. In the JXplorer window, if needed, expand soa_domain > myrealm > people, click the
weblogic entry.
b.
5.
Note: This populates the attributes for the weblogic entry in the HTML View tab of
the frame on the right side of the window.
In the HTML View frame (on the right-side of the window), enter
weblogic@soa11g.example.com in the Email Address field and click Submit.
To import the users and groups by using the supplied LDIF files, perform the following
steps:
a. In the JXplorer window, click the LDIF > Import File menu.
b.
In the Open dialog box, use the Look In field to navigate to the D:\labs\ldap
folder, select People.ldif and click Open.

Chapter 10 - Page 10
4.
c.
d.
To import the groups, on the JXplorer window, click LDIF > Import File from the menu.
In the Open dialog box, select the Groups.ldif file and click OK.
Note: Use the left navigation frame to verify the new groups have been added.

Note: In the left navigation frame, you can verify that a set of new users appear in the
people sub-tree. For example:
On the Summary of Security Realms page, click the myrealm link.

e. Terminate the JXplorer application window by selecting select File > Exit.
Note: Instead of using JXplorer or other command line tools, you can use Oracle WebLogic
Administration Console to create and manage user and group information in the Embedded
LDAP server. However, in the web-based approach you cannot create multiple users
quickly.
When you have time, consider logging into Oracle WebLogic Administration Console and
click the Security Realms link in the Domain Structure frame to explore the users and
groups information you imported with JXplorer. For example:
6.
On the Settings for myrealm > Users and Groups tab page, you can access the Users
and the Groups tab pages, in which you can drill down to specific user and group details
respectively.
To verify if you can login to the BPM Worklist application with one of the seeded users,
a. In a Web browser window (or tab page), enter the URL
http://localhost:8001/integration/worklistapp.
Note: Consider creating a Bookmark (or Favorites) for the BPM Worklist login page.
b. On the BPM Worklist application login page, enter the username jcooper with the
password welcome1, and click Login.

On the Settings for myrealm, click the Users and Groups tab.

c.
Note: If the Embedded LDAP server user information has been correctly seeded by the
import actions performed earlier in this practices, the BPM Worklist login should be
successful.
On BPM Worklist application page, click the Logout link.
Overview
You configure the Human Workflow Notification Service properties through Oracle Fusion
Middleware Control Console to support email notification and restart the SOA server.
Because the classroom configuration provides an email server you only configure email
notification services that require you to configure properties for the installed email driver
component.
Assumptions
You have configured the user and group information in the Embedded LDAP server, and have
restarted Oracle WebLogic Server.
Tasks
1.
To configure the Human Workflow Notification Server properties, perform the following
steps:
a. In a Web browser window, if required, enter the URL http://localhost:7001/em and login
as the weblogic user with password welcome1.
b. On the Oracle Fusion Middleware Control Console home page, expand the SOA folder
in the Farm navigation frame, right-click soa-infra (soa_server1), and select SOA
Administration > Workflow Notification Properties.
c. On the SOA Infrastructure > Workflow Notification Properties page, enter the values
specified in the following table and click Apply.
Field
Value
Notification Mode
ALL
Email: From Address
workflow.notify@soa11g.example.com
Email: Actionable Address
workflow.action@soa11g.example.com
Email: Reply To Address
no.reply@soa11g.example.com
For example:

Practice 10-2: Configure Human Workflow Notification Services
2.
On the Confirmation window, click Yes.

On the SOA Infrastructure > Workflow Notification Properties page, verify you get a
confirmation that the changes have been applied and observe the information
indicating that you must restart the SOA server.
Note: However, first configure the email driver properties as described in the next task
before you restart the SOA managed server.
To configure the Email Driver properties, perform the following steps:
a. On the SOA Infrastructure > Workflow Notification Properties page, click the Go to the
Messaging Driver page link. For example:
b.
On the usermessagingserver page, under Associated Drivers in the Local tabbed page,
click the Configure Driver (pencil) icon in the row for the User Messaging Email Driver
(Driver Type). For example:

d.
e.
On the usermessagingdriver-email > Email Driver Properties page, in the Common

Configuration section, set the following field and their values:
Sender Addresses: workflow.notify@soa11g.example.com
Default Sender Address: workflow.notify@soa11g.example.com
For example:
d.
On the same usermessagingdriver-email > Email Driver Properties page, in the DriverSpecific Configuration section, configure the email driver properties, and click Apply (at
the top of the page) only after setting all the driver properties. For example:
Note: To set the email driver properties you need to scroll down in the Driver-Specific
Configuration section to set some of the field values listed in the following table (as
some of the fields listed may already have the correct value):
Field
Value
MailAccessProtocol
POP3
OutgoingMailServer
soa11g.example.com
OutgoingMailServerPort
25
OutgoingDefaultFromAddr
workflow.notify@soa11g.example.com

c.
soa11g.example.com
IncomingMailServerPort
110
IncomingMailIDs
workflow.action@soa11g.example.com
IncomingUserIDs
workflow.action
IncomingUserPasswords
Type of Password: Indirect Password, Create New

User
Indirect Username/Key: workflow.action
Password: welcome1
Note: The password value displays asterisks when entered.
For example: The following images show the driver property settings for this course.
Note: The SMTP Server does not require authentication to send messages. This may
be different in your environment.

IncomingMailServer
f.
3.
To restart Oracle SOA managed server, perform the following steps:

a. In a Command Prompt Window enter the following commands:
D:\> cd D:\Oracle\fmw\11.1.1.3\user_projects\domains\soa_doma
in\bin
D:\> stopManagedWebLogic.cmd soa_server1
b.
c.
Note: You do not need to restart the (Oracle WebLogic Server) Admin Server instance.
Close the command window used to run the soa_server1 managed server instance if it
is not closed when the managed server is stopped.
In the same Command Prompt window used to stop the SOA managed server, enter
the following command to start the SOA managed server again:
D:\> start startManagedWebLogic.cmd soa_server1
Wait for the SOA managed server to be up and running, which may take two to five
minutes. For example when you see the following line displayed in the SOA manager
server command window:
INFO: FabricProviderServlet.stateChanged SOA Platform is running
and accepting requests

e.
Note: To receive incoming messages password authentication is required.

On the usermessagingdriver-email page, observe the confirmation message that
changes have been applied.
On the Oracle Fusion Middleware Control Console, click the Log Out link, and close
the Web browser page. For example:
c.
On the Human Workflow Engine (Service Engine) page, click the Notification
Management tab, and then click Send Test Notification.
d.
In the Send Test Notification dialog box, sending a test Email message to verify if the
email notification channel is configured correctly. Set the following field values and click
Send.
Send To: weblogic@soa11g.example.com
Subject: Notify test
Content: Admin test. Thanks!
Channel: Email
For example:

4.
Note: You can minimize the various Command Prompt windows, such as those
running the Admin and SOA servers, and optionally close the window used to restart
the SOA managed server.
To verify that the Human Workflow Notification Services have been configure correctly, you
use the Notification Management page of the Human Wokflow Engine to send a test email
to the weblogic users email address, by performing the following steps:
a. In a Web browser window, access (or refresh) the Oracle Fusion Middleware Control
Console login page (URL http://localhost:7001/em) and login with the username
weblogic and password welcome1.
b. On the Farm navigation frame, expand the SOA node, right-click soa-infra
(soa_server1) and select Service Engines > Human Workflow.
In the Send Test Notification dialog box, after clicking Send, observe the Response
information message, such as SENT (if successful). Click Cancel to dismiss or close
the Send Test Notification dialog box.
f.
On the Human Workflow Engine (Service Engine) > Notification Management tab page,
click the refresh icon to update the page.
g.
Note: The reason you refresh the Notification Management tab page is to view the
Outgoing Notifications for messages communicated through different Workflow
Notification Service channels, in this case email.
On the Human Workflow Engine (Service Engine) > Notification Management tab page,
scroll down and view the entries in the table in the Outgoing Notifications section. The
top-most message represents the test notification just sent. For example:

e.
Additional Note: You can track all notification messages for all channels in the
Notification Management tab page in the Human Workflow Engine (Service Engine)
pages. The following image shows two sections for monitoring:
Outgoing Notifications: messages sent from processes within the SOA server to
external sources
Incoming Notifications: message received from external sources for processing
within SOA processes or Human Workflow engines.
5.
To confirm receipt of the test message and view the email message sent by the Human
Workflow Notification Service to the weblogic email account, perform the following steps:
a. Start Mozilla Thunderbird using the desktop icon.
Note: If Mozilla thunderbird is already running, focus on its application window.
b. On the Mozilla Thunderbird application window, if needed, click the
weblogic@soa11g.example.com account name in the Inbox folder. The Notify
test message should appear in the message list frame. Click the email message with
the Subject Notify test to view the body in the Message Pane below the message. For
example:

Note: If you click the Sent link for the entry, a Status Description dialog box containing
a success message is displayed. For example:
Note: If the Notify test message does not appear, click Get Mail in the Mozilla
Thunderbird toolbar. The weblogic user Inbox may contain additional email
messages from BPMN application that you may have executed in earlier practices of
this course. The Subject, From, and Date columns have been resized for visual
clarity in this document.

Chapter 11
Chapter 11 - Page 1
Chapter 11 - Page 2
Practices Overview
Deploy the ApprovePOComposite application with a Human Task component without

its associated Task Form UI application.
Initiate and monitor the ApprovePOComposite application without the Task Form UI
application deployed.
Deploy the Task Form UI application associated with the ApprovePOComposite

application.
Initiate and monitor the ApprovePOComposite application with the Task Form UI
application deployed.
General Notes
The ApprovePOComposite application that is deployed checks if the total price of a purchase
order is greater than 2000.0 (configured as a BPEL property). If the purchase order is greater
than 2000.0, the application uses a Human Task component to implement a manual approval
process for the order. The Human Task component is configured with:
An assignment and routing policy that implements a serial management chain approval
assignment strategy, for one level up the management chain.
An email notification policy to notify task assignees of their task assignment.

The ApprovePOComposite manual order approval process requires two end users (jcooper
and his/her manager jstein) to view their email notification messages, and login to the Oracle
Business Process Workspace (or BPM Worklist) application to view the task assignment and
perform some action on the assigned task.
The practice example provides you with an opportunity to track the Human Task component
state changes that are visible in the Flow Trace, while acting as the end users of the BPM
Business Process Workspace (or BPM Worklist application) to perform the specified task action.
Note: The email notification messages have been configured to support actionable email
responses. This means the user can approve or reject the purchase order by clicking an action
link in the email message body and send the email response to the Human Workflow
Notification Services to process the response for that application instance. However, this
process is suggested as a practice you can experiment with if you have time.

Chapter 11 - Page 3
Overview
In this practice you deploy the ApprovePOComposite application, which contains a Human Task
component, to implement manual approval of purchase orders whose order total is greater than
or equal to 2000.0.
Note: The 2000.0 threshold value is configured as a BPEL component property called
approvalLimit. By using the system MBeans one can modify the approvalLimit BPEL
property value to alter the threshold value used to decide if the Human Task is executed for
manual approval processing. The approvalLimit property is not altered during this practice.
Assumptions
The SOA Archive is present in the D:\labs\lesson11 subfolder.
Tasks
1.
To deploy the composite application, perform the following steps:

a. In the Command Prompt window, use the SOA archive to deploy the
ApprovePOComposite application by executing the following commands:
D:\> cd D:\labs\lesson11\ApprovePOComposite\deploy
D:\> deploy sca_ApprovePOComposite_rev1.0.jar
b.
2.
Note: If your PATH environment variable does not include the D:\labs\bin folder in
your path, then change the deploy command to the fully qualified command
D:\labs\bin\deploy. Alternatively, you can deploy the SCA file using default
options in the Oracle Fusion Middleware Control Console.
Note: Keep the Command Prompt window available (do not close it).
If you wish, you can login to the Oracle Fusion Middleware Control Console to view the
deploy application in the SOA Infrastructure in the Farm navigation tree or the Deployed
Applications tab page.

Chapter 11 - Page 4
Practice 11-1: Deploy a Composite with a Human Task Component
Note: The next practice requests that you login to the Oracle Fusion Middleware Control
Console.

Chapter 11 - Page 5
Overview
In this practice you initiate the ApprovePOComposite application containing a Human Task
component, without the presence of its Task Form UI application. You act as the task assignees
that view their email notification messages, and login to the Oracle Business Process
Workspace application to perform a specified action on the task assignment.
Note: While the practice instructions make use of the Oracle Business Process Workplace
application, you can use the BPM Worklist application instead to perform an action on the task
assigned to a user configured in Human Workflow.
Assumptions
To login to the Oracle Business Process Workspace (or BPM Worklist) application, the Worklist
users should already be configured in the Embedded LDAP server.
Tasks
1.
2.
Before you initiate the composite application, start Mozilla Thunderbird and login to Oracle
Fusion Middleware Console by performing the following steps:
a. On the Windows desktop, if needed, double-click Mozilla Thunderbird icon to start the
email client application.
b. In a Web browser window, enter the URL http://localhost:7001/em and login as the
user weblogic with password welcome1.
c. In the Oracle Fusion Middleware Console Farm frame, expand the SOA > soa-infra
(soa_server11) > default tree and click the ApprovePOCompsite [1.0] entry. For
example:
Note: You are preparing the initial applications needed to monitor and interact with the
application.
To initiate the composite application, perform the following steps:
a. In a Windows Explorer application window, copy the D:\labs\xml\po-file\pogibson-only.xml file to the D:\labs\lesson11 folder, and wait for the pogibson-only.xml file to disappear from the folder.
b. In the Web browser window on the ApprovePOComposite [1.0] Dashboard tab page,
click the Refresh icon in the top-right corner of the page to update the page. For
example:

Chapter 11 - Page 6
Practice 11-2: Initiate and Monitor the Human Task without a UI
3.
Note: You view the details in the Flow Trace page after checking and responding to
the email notification message. Therefore, keep the Flow Trace page open (or
minimized).
Using the email notification for the Human Task component to view the email messages
and take action on the task assignment, perform the following steps:
a. Bring the Mozilla Thunderbird application window into focus (and if it is not running,
open the application). To view the email notification message, which is sent to the
jcooper account, select the jcooper@soa11g.example.com account in Inbox tree
of the Smart Folders frame. For example:
b.
Note: Depending on how long it takes for the Human Workflow Notification services,
the XMail server, and Thunderbird email client to communicate the email notification
message, you may need to click Get Mail (in Thunderbird) to receive the message.
After receiving the email message, in the Mozilla Thunderbird Message Pane, click the
email message entry to view the body of the message. For example:

Chapter 11 - Page 7
Note: Click the Refresh icon until a new instance of the application appears with a
Running state in the Recent Instances section. For example:
d.
e.
On the Oracle Business Process Workspace login page, enter the Username jcooper
and Password welcome1, and click Login.
On the Oracle Business Process Workspace Tasks tab page, within the My Tasks
subtab page click on the Approve Order task entry that appears. For example:

Chapter 11 - Page 8
c.
Note: answer the following questions:

1) Who is the sender of the message? And where does the sender information get
derived from?
Answer: The sender should be workflow.notify@soa11g.example.com,
which is derived from either the Human Workflow Notification Properties settings
or email driver configuration properties.
2) Can you see the actual order details in the email message? Explain your answer
as best as you can.
Answer: No, the actual order details are not visible in the body of the email
message. You can only see the basic task approval text and two action links
(Approve and Reject). The reason that the order information is not visible is
because the Task Form UI application responsible for rendering the order details
has not been deployed and is associated with the Human Task component in the
ApprovePOComposite application.
In the Mozilla Thunderbird window, in message body, click the Workspace Application
link. For example:
Note: On the Information dialog box that is displayed after performing the Reject
action, click OK.
After you click OK, the Information dialog box it is closed and the My Tasks tab page
no longer displays the assigned task because it has been processed. For example:

Chapter 11 - Page 9
f.
Note: After selecting the task entry, observer that the order details for the task are not
visible in the bottom frame. This is because the Task Form UI application is associated
with the Human Task component.
Because the order information is not visible for this order, the user jcooper does not
wish to approve the order. Therefore, acting as jcooper you select the Actions > Reject
menu option for the selected task entry. For example:
Return to the Flow Trace Web browser window you opened earlier to monitor the
ApprovePOComposite application progress by performing the following steps:
a. On the Flow Trace page, in the Trace tree click the ApprovePOBPEL component link.
For example:
b.
5.
On the Instance of ApprovePOBPEL page, scroll down to the end of the Audit Trail
and observe the last activity to appear and the state of the process. For example:
Note: The last activity is called receiveCompletedtask_ApprovePOHumanTask_1, and

it is in a pending state. This means that the Human Workflow processing requirements
have not completed. There is more to be done by the approvers that are assigned the
task for approval. This is correct, because the application implements a one-level up
management chain of approval strategy.
To monitor the status and processing performed by the Human Task component, perform
the following steps:

4.
On the Instance of ApprovePOBPEL page, click the Flow Trace locator link at the topleft corner of the page. For example:
b.
On the Flow Trace page, click the ApprovePOHumanTask component link in the Trace
tree. For example:
c.
On the Instance Detail of ApprovePOHumanTask page, what do you observe?

Answer: You can view the stages of processing in the Task Details section on the
page. For example:
Note: After the task had been initiated, it is assigned to jcooper. The user jcooper
performed the action of Reject on the task assigned to him. Now that the task
completed by jcooper is routed to the manager of jcooper, who is revealed to be
the user jstein as listed in the Routed entry of the audit trail page. In this way, if
users are complaining about processing being incomplete, you can contact the person,
in this case jstein, to help the process along if the user jstein has not already
looked at their email messages and taken actions on the task assigned to him/her.

a.
To act on the task assignment for jstein, perform the following steps:
a.
b.
In the Thunderbird application window, click the jstein@soa11g.example.com

entry in the Inbox tree under the Smart folders section in the left frame, and click the
first (possibly only) email message with the subject Routed: Approve Order. For
example:
Note: You may see multiple Routed: Approve Order email messages in jsteins Inbox
due to a 2 minute reminder email configured in the Human Task. The reminder email
should only occur once. However, for some reason, it appears that the first user in the
management chain (jcooper) receives an addition four email notification messages.
You can ignore or delete the extra notification messages.
Return to the Web browser window or tab page containing the Oracle Business
Process Workspace (or BPM Worklist) application. If you are still logged in as jcooper
then click the Logout link in the page banner. For example:
c.
On the Oracle Business Process Workspace login page, enter the Username jstein
and Password welcome1, and click Login.
d.
In the My Tasks tab page for the user jstein, click the task assignment entry and select
Actions > Reject.

6.
7.
Having performed the Reject action as jstein on their task assignment, to view the changes
in the state of the Human Task component, perform the following steps:
a. Return to the Web browser window displaying the Task Details audit trail for the
Instance Detail of ApprovePOHumanTask page, and click the Refresh icon (in the
top-right corner of the page). For example:
b.
On the Instance Detail of ApprovePOHumanTask page, observe the changes to the

Task Detail flow, and click the Flow Trace locator link (at the top-right corner of the
page). For example:

e.
f.
Note: For the same reason as jcooper had, jstein has decided to reject the order
because the order details are not visible in the task detail frame when the assigned
task is selected.
On the Information dialog box, click OK.
On the Oracle Business Process Workspace page, for the jstein user click Logout.
d.
8.
Close the Flow Trace page, and optionally observe the completed status for the
ApprovePOComposite instance in the ApprovePOComposite [1.0] Dashboard tab
page.
To (optionally) view the log information written by the ApprovePOComposite application to
the D:\labs\lesson11\order_approval.log file:
a.
In a Windows Explorer application window, navigate to the D:\labs\lesson11 folder

and double-click the order_approval.log file.

c.
Note: The last entry in the Task Details section of the page indicates that the task is
completed with the REJECT outcome.
On the Flow Trace page, in the Trace tree you can now observe that the entire
ApprovePOComposite application has completed. Because the Human Workflow
Component has completed, the entire process could continue proceed to completion
by writing the log record for the order approval outcome using the
ApprovePOLogFileService (at the bottom of the trace tree) File Adapter. For example:
9.
In the Notepad window, confirm that the order with ID 115 and order total 3000 was
logged with a Manuual: REJECT result. For example:
To examine the administration information available in the Human Workflow Component

pages, perform the following steps:
a. Return to the Oracle Fusion Middleware Control Console page displaying the
ApprovePOComposite [1.0] Dashboard page, scroll down and click the
ApprovePOHumantask link in the Component Metrics section. For example:
b.
On the ApprovePOHumanTask (Human Workflow Component) page, optionally

deselect the Show Only Running Instances check box to view the recently completed
instance information. For example:

b.
On the ApprovePOHumanTask (Human Workflow Component) page, collapse the

Recent Instances and Recent Faults section, scroll down (if needed) to view the
information in the following sections on the page:
The Business Outcomes section to view the bar chart.
The Highest Time-Consuming Assignees to track the time assignees have been
working on their task.
Expand the Notifications section to view the count for each channel used by the
Human Workflow Notification Services.
For example:
d.
To view the missing information needed by the workflow users to see the order details,
on the ApprovePOHumanTask (Human Workflow Component) page, click the
Administration tab.

c.
On the ApprovePOHumanTask (Human Workflow Component) Administration tab

page, observe the No task form URIs found message below the Application Name.
Note: When a Task Form UI application is created, deployed and associated with a
Human Task component, the task form URI appears in this Administration page. While
you can manually add the task form URI entry (for example, modify it as a result of
deployment topology changes) the information is automatically populated when you
deploy the Task Form UI application EAR (application archive) provided that the EAR
file contains a file with the appropriate configuration information.
10. To view the information displayed in the Human Workflow service engine pages, perform
a. On the Farm navigation tree, right-click soa-infra (soa_server1) and select Service
Engines > Human Workflow.

e.
c.
d.
On the Human Workflow Engine (Service Engine) page, observe information in the
Users with highest Backlog section, and view the statistics information by clicking the
Statistics tab.
Note: Because the application instance has completed, there is no useful backlog
information. However, you could also track user backlog for human workflow task
assignments on this page. This page applies to all Human Task components executing
within the same SOA server.
On the Human Workflow Engine (Service Engine) Statistics tab page, you can take a
little time to explore the information in the Operation Statistics sections. For example:
To monitor, view, and manage email message notifications on the Human Workflow
Engine (Service Engine) page, click the Notification Management tab.

b.
On the Human Workflow Engine (Service Engine) Notification Management tab page,
in the Outgoing Notification section, you can view all the messages that have flowed
from the server to external locations for the different channels used.
Note: In this case, the channel used is the Email channel. You can select a row and
click Delete to remove messages. You can also perform actions, such as resending
messages, resending similar notifications, and viewing bad addresses.
The Incoming Notifications section can be used to track incoming messages. In this
case, there are no incoming messages. However, you could experiment with
generating incoming messages by performing creating another application instance
and approve or reject the task assignment by clicking the Approve or Reject link in
email message body. This is possible because the application has enabled the
notification messages to be actionable, that is, they can be auctioned from the email
message instead of having to log into the Business Process Workspace (or BPM
Worklist) application to perform the action. Ask your instructor for guidance if you wish
to perform this additional task.
11. To (optionally) clean up possible excess email notification messages, perform the following
steps:
a. In the Thunderbird application window, in the Inbox of the jcooper account, select the
(possibly up to) four additional messages, and click Delete.

e.
b.
Select the Dont ask me again check box and click Yes.
On the Thunderbird application window, to remove the deleted messages, select File >
Empty Trash.
Note: It is recommended that you clean the user email Inbox so that it is easier to
locate messages that may need to be examined in subsequent practice instructions.

Note: Retain the first notification messaged and delete the extra reminder messages.
In addition, if you have not already removed the duplicate (reminder) message from the
Inbox of the jstein account, you may wish to delete the additional messages. If you
receive the following confirmation page:
Overview
In this practice you deploy the Task Form UI application associated with the Human Task
component in the ApprovePOComposite application, initiate a new application instance so that
you can see the order information and approve the order, while making some changes to the
order payload along the way. You verify that the Task Form UI is associated with the Human
Task Component in the ApprovePOComposite application.
Note: Invariably, most applications with a Human Task component with manual processing
(human intervention) assignment and routing policies require a Task Form UI application. The
Task Form UI application provides visual information about the task in the email notification
messages and Worklist application to help the assignee of the task to accomplish the goal
required, such as order approval.
Assumptions
You have successfully deployed the ApprovePOComposite application and tested it without the
Task Form UI application. The Worklist users have been configured in the Embedded LDAP
Server.
Tasks
1.
To deploy the Task Form UI application associated with the Human Task component of the
ApprovePOComposite, perform the following steps:
a. Return to the Command Prompt window that was used to deploy two SOA Composite
application, and execute the following commands:
D:\> deploy_ear ApprovePO_UI
b.
Note: If your PATH environment variable does not include the D:\labs\bin folder in
your path, then change the deploy command to the fully qualified command
D:\labs\bin\deploy_ear. Alternatively, you can deploy the SCA file using default
options in the Oracle Fusion Middleware Control Console.
Verify that deployment is successful. The following image as a guide:

Practice 11-3: Deploy the Task Form UI Application
b.
Note: If the Web page does not display the ApprovePOComposite [1.0] Dashboard
page, on the Farm navigation frame expand SOA > soa-infra (soa_server1) > default
tree, click the ApprovePOComposite [1.0] link.
On the ApprovePOHumanTask (Human Workflow Component) page, click the
Administration tab and verify that a URI entry now exists with the Application Name
column containing the value worklist, the Host Name column containing
soa11g.example.com and so on. For example:

2.
Note: The BUILD SUCCESSFUL message appears before the total deployment time
is displayed at the end of the command results.
c. Close the Command Prompt window.
To verify that the Human Task component is associated with its Task Form UI application,
a. In the Web browser window displaying the Oracle Fusion Middleware Control Console
on the ApprovePOComposite [1.0] Dashboard tab page, scroll down to the Component
Metrics section and click the ApprovePOHumanTask link.
Note: If the URI entry shown does not exist, then either the deployment file or the
deploy command is incomplete. Otherwise you can manually add the entry provided
you know the URI for the target Task Form UI application.

Overview
In this practice you initiate the ApprovePOComposite application again, this time with the
presence of its Task Form UI application. As before, you act as the task assignees to view the
email notification messages, and login to the Oracle Business Process Workspace application
to perform a specified action on the task assignment.
Assumptions
To login to the Oracle Business Process Workspace (or BPM Worklist) applications, the Worklist
users should already be configured in the Embedded LDAP server.
Tasks
1.

a. In a Windows Explorer window, copy the file D:\labs\xml\po-file\po-largeguitar.xml to the D:\labs\lesson11 folder.
b.
2.
Wait for the file to be removed from the D:\labs\lesson11 folder by the
ApprovePOComposite application instance that consumes it.
To monitor the Human Task component processing in composite application instance,
a. In the Web browser window displaying the Oracle Fusion Middleware Control Console,
return to the ApprovePOComposite [1.0] Dashboard tab page, and if needed click the
Refresh icon to update the page information. For example:
b.
On the ApprovePOComposite [1.0] Dashboard tab page, click the instance ID link for
the Running instance. For example:
c.
On the Flow Trace page, click the ApprovePOHumanTask Human Workflow

Component entry.

Practice 11-4: Test and Monitor a Human Task and its Task Form UI
3.
On the Instance Detail Of ApprovePOHumanTask page, what is the status reported in

the Task Details?
Answer: The onMessage contains an entry indicating that the human workflow has
been initiated and the task is presently assigned to the user jcooper.
Note: At this stage, the email notification should have been send and received by the
jcooper account.
To view the email notification message(s) and start the Oracle Business Process
Workspace application, perform the following steps:
a. On the Thunderbird application window, select the jcooper@soa11g.example.com
account in the Inbox folder of the Smart Folder frame, in the Message Pane, click the
message with subject Action Required:Approve Order.
b.
Note: If needed, start Mozilla Thunderbird from the desktop icon.

Below the Thunderbird application Message Pane, click Show Remote Content to
display the entire message body below. For example:

d.
d.
In the Thunderbird application Message Pane, you should now see the complete order
details shown in the message body due to the fact that the Task Form UI application
has been deployed.
Note: The Task Form UI application is used to display the task payload (in this case
the purchase order information) in the email notification message as well as the task
details in the Oracle Business Process Workspace (or BPM Worklist) application
pages.
To start the Oracle Business Process Workspace application, you can either click the
Workspace Application link at the top of the email message body, or enter the URL
http://localhost:8001/bpm/workspace in a Web browser window.

c.
To approve the order as jcooper in the Oracle Business Process Workspace application,
a. On the Oracle Business Process Workspace application login page, enter the
Username jcooper and Password welcome1 and click Login.
b. On the My Tasks tab page, select the Approve Order entry to display the purchase
order details in the bottom frame on the page. Observe the value of the order Status
(set to initial, as received from the input file).
Note: You change the order status before approving the order.
c.
In the purchase order detail of the bottom frame on the My Task tab page, replace the
Status field value initial with approved, and click Approve. For example:

4.
5.
Having approved the purchase order task as jcooper, return to the Web browser page
displaying the Flow Trace > Instance Detail Of ApprovePOHumanTask page to view the
changes in Task Details section of the page, by performing the following steps:
a. On the Instance Detail Of ApprovePOHumanTask page, click the Refresh icon. For
example:
b.
c.
On the Instance Detail Of ApprovePOHumanTask page, observe that the task details
show:
The Outcome Updated step, where jcooper approved the task
The Routed step, where the user jstein has been assigned the task

d.
Note: In this example, the Task Form UI application is constructed to allow the Worklist
application users to modify the payload (purchase order details). This may not be the
case for all Task Form UI applications.
On the banner of the Oracle Business Process Workspace application, click the Logout
link to logout the user jcooper.
b.
After clicking a message entry in the Message Pane, in the message body you can
observe that the Status value is approved.

6.
Note: The user jstein would have been sent an email notification about the routed
task assignment.
d. Keep this Flow Page open so that you can view the changes after jstein approves
the purchase order task.
To view the order information received in the approved purchase order that is now routed to
jcoopers manager jstein, perform the following steps:
a. If needed open Mozilla Thunderbird. On the Thunderbird application window, select
jstein@soa11g.example.com in the Inbox folder of the Smart Folders frame. Click
a message with the subject Routed:Approve Order and click Show Remote Content
in the section between the Message Pane and the message body.
Note: You may have two email notification messages due to the two-minute reminder
configured in the applications Human Task component notification properties having
expired. For example:
7.
Before you leave the Thunderbird application window, you might find that the jcooper
account has received duplicate reminder notification messages. You can select the
duplicates and click Delete. For example:
Note: You may also wish to delete the reminder message sent to the jstein email
Inbox, and click File > Empty Trash to clean the mailbox information.
d. On the Mozilla Thunderbird window, select File > Exit.
To view the purchase order task assignment as jstein in the Oracle Business Process
Workspace application, perform the following steps:
a. Either return to the Oracle Business Process Workspace application page already
present in the Web browser, or enter the URL http://localhost:8001/bpm/workspace in a
Web browser window.
b. On the Oracle Business Process Workspace application login page, enter the
Username jstein with Password welcome1 and click Login.

c.
On the My Tasks page, select the Approve Order task entry to display the purchase
order details, and click Approve. For example:
d.
On the banner of the Oracle Business Process Workspace application page, click
Logout.
e.
Now return to the Web browser window displaying the Flow Trace > Instance Detail Of
ApprovePOHumanTask page, where you can click the Refresh icon to update the
page information and observe the following entries have been added to the Task
Details:
The Outcome Updated (after the Routed entry), indicating the jstein updated the
outcome to APPROVE.
The Completed entry, indicating that the workflow assignment and routing process
has been completed.

c.
9.
To view the approval log data changes, perform the following steps:
a. In a Windows Explorer window, navigate to the D:\labs\lesson11 folder, right-click
order_approval.log and select Open.

8.
Note: In this case the workflow process is complete and the application should have
completed as well.
f. Close the Web browser window containing the application Flow Trace page.
To verify that the application has completed, return to the ApprovePOComposite [1.0]
Dashboard page, and click the Refresh icon to update the instance state information. For
example:
On the Notepad window, view the last line in the file indicating that the order ID 105
with order total 5200 has a Manual:APPROVE status. For example:
c.
Close the Notepad application window.
b.

Chapter 12
Chapter 12 - Page 1
Chapter 12 - Page 2
Practices Overview
Deploy a BPMN process application.
Deploy the Task Form user interface (UI) application used by the BPMN process.
Associate the Human Workflow component in the BPMN application with its Task Form
UI.
Test the BPMN application by initiating the process through the Oracle Business
Process Workspace application.
Monitor the BPMN process and its components.
General Notes
The Task Form UI application is identified by a specific URI. For example:
/workflow/HelloWorld_UI/faces/adf.taskflow?_id=SayHello_TaskFlow&_document=WEBINF/SayHello_TaskFlow.xml
The bold parts of the URI change based on the name of the application components involved. In
the example:
HelloWorld_UI represents the name of the Task Form UI application.
SayHello represents the name of the Human Workflow component in the BPMN
application for which the TaskFlow (Task Forms) are constructed.
This information can be used by an administrator to derive the correct URI path name for
associating the appropriate Human Workflow component with its Task Form UI.

Chapter 12 - Page 3
Overview
The purpose of this practice is to deploy a BPMN application and a Task Form user interface
required for the Human Workflow application to display the related information.
Because the BPMN application and Task Form application are deployed separately, you verify
that the Human Workflow component in the BPMN is associated with its Task Form UI in the
Oracle Fusion Middleware Control Console.
Assumptions
The BPMN application code is packaged in a SCA archive and the Task Form UI is packaged in
an EAR file. You use the deploy and deploy_ear command-line scripts to deploy the
applications.
Tasks
1.
To deploy the BPMN Application, perform the following steps:

a. If needed, open a new Command Prompt window by double-clicking on the Command
b. In the Command Prompt Window, execute the following commands:
D:\> cd D:\labs\lesson12\HelloWorldBPM\deploy
D:\> deploy sca_HelloWorldBPM_rev1.0.jar
c.
2.
Note: If the D:\labs\bin folder is not in your PATH environment variable, then add it
to your PATH or use the fully qualified deploy command: D:\labs\bin\deploy.
Ensure the application has been deployed successfully before proceeding, and keep
the Command Prompt window open. Use the following image as a guide:
To deploy the Task Form UI application, perform the following steps:

a. In the Command Prompt window, execute the following commands:

Chapter 12 - Page 4
Practice 12-1: Deploy a BPMN Application and its Task Form
b.
Note: Do not include the .ear file extension in the name when you deploy the
application EAR file. If the D:\labs\bin folder is not in your PATH environment
variable, then add it to your PATH or use the fully qualified deploy command:
D:\labs\bin\deploy_ear.
Ensure the application has been deployed successfully, and close the Command
Prompt window. Use the following image as a guide:
D:\> deploy_ear HelloWorld_UI

Chapter 12 - Page 5
Overview
In this practice you initiate the BPMN application by clicking the Task Form UI application link
that appears in the Applications frame of the Oracle Business Process Workspace application.
However, you first take a look at the Dashboard page for the BPMN application in the Oracle
Fusion Middleware Control Console.
Note: If the Task Form UI is not associated with the Human Task component, a link to the
Human Task UI application does not appear in the Applications frame in the Oracle Business
Process Workspace Tasks tab page for a Workspace application user. If this is the case, you
can manually associate the URI of the Human Task UI application with the Human Task
component.
Assumptions
You have deployed the BPMN application and its Task Form UI application so that the Task
Form UI is associated with the Human Workflow component in the BPMN application.
Tasks
1.
2.
In the Web browser window, create a new window or tab page, and access the Oracle
Fusion Middleware Control Console using the URL http://localhost:7001/em.
Note: If you need to login, on the Oracle Fusion Middleware Control Console login page,
enter the user name weblogic and password welcome1, and click Login.
On the Oracle Fusion Middleware Control Console home page, in the Farm navigation
frame expand the SOA > soa-infra (soa_server1) > default tree, and click the
HelloWorldBPM [1.0] application link.
View the Association between the Task Form UI and the Human Workflow Component
3. To associate the Task Flow UI application with the SayHello Human Workflow Component,
a. On the HelloWorldBPM [1.0] application Dashboard page, scroll down to the
Components Metrics section and click the SayHello Human Workflow component link.

Chapter 12 - Page 6
Practice 12-2: Initiate and Monitor the BPMN Process
On the SayHello (Human Workflow Component) page, click the Administration tab.
c.
On the SayHello (Human Workflow Component) Administration tab page, verify that
the URI entry with Application Name worklist is present.
Initiate the Human Workflow Task Form UI Application and BPMN Instance
4. To login to the Oracle Business Process Workspace Web application and initiate the BPMN
application through the Task Form UI application, perform the following steps:

Chapter 12 - Page 7
b.
b.
5.
6.
On the Web browser, open a new window or tab page, and enter the URL
http://localhost:8001/bpm/workspace.
On the Oracle Business Process Workspace login page, enter the user name
weblogic and password welcome1, and click Login.
On the Oracle Business Process Workplace > Tasks tab page in the Applications frame,
observe that the [HelloWorldBPM] HelloWorldBPMProcess v1.0 link appears in the
Applications frame.
Note: Before you click the link you may wish to verify that there are no instances of the
HelloWorldBPM [1.0] composite application by refreshing the HelloWorldBPM [1.0]
composite application home page in the Oracle Fusion Middleware Control Console.
On the Oracle Business Process Workspace > Tasks tab page in the Applications frame,
click the [HelloWorldBPM] HelloWorldBPMProcess v1.0 link. For example:
Note: This opens a Web page with the application user interface requesting you enter a
message. For example:

Chapter 12 - Page 8
a.
Before you enter a message return to the HelloWorldBPM [1.0] composite application
Dashboard page in the Oracle Fusion Middleware Control Console. Refresh the page to
verify that a new application instance in the Running state. For example:
8.
Return to the Task Form UI application Web page, and enter Greeting and Message text
values, and click SUBMIT. For example:
Greeting: Hello World
Message: Have a wonderful day!
Note: For the Date you can enter todays date formatted as a string similar to: Jul
19, 2010. If the date value entered causes a UI data format error message then do
not enter any text in the Date field, as shown in the following example:
Note: Do not enter any value in the Date field. If you wish to enter the date, you can enter
one in the format MMM DD, YYYY, for example: Jul 19, 2010. The Task Form UI Web
page should close when you click SUBMIT. If the page containing the Web form does not
close, then close the page.
Additional Note: In the My Tasks tab of the Oracle Business Process Workspace
application, if you were to click Refresh icon, before you submit the message in the window

Chapter 12 - Page 9
7.
Note: There is no requirement to send a message for the same task from both areas. As
soon as a message is submitted from one of the Web page sources, the task is removed
from the list in the My Tasks tab page.
Monitor the BPMN Application Process
9. To view the instance Audit Trail and Flow pages, perform the following steps:
a. On the helloWorldBPM [1.0] Dashboard, under the Recent Instances section, click the
link in the Instance ID column. For example:
b.
On the Flow Trace page, to examine the Audit Trail of the BPMN component in the
Trace tree, click the HelloWorldBPMProcess link.

that opened for the application link, the same Task Form UI is accessible in the My Tasks
tab page after you click the task entry. For example:
Expand the activity entries as desired to view process activity and execution sequence.
For example:
d.
To view the process flow diagram, click the Flow tab, and you can click on each icon
for more information.

c.
To view the information about the SayHello Human Workflow Component, click the
Flow Trace locator link (at the top left part of the page), and then in the Trace tree, click
the SayHello Human Workflow Component link and examine the pages as desired.
f. Close the Flow Trace page.

10. Optionally, if you wish you can view the message text, which entered in the Business
Process Workspace user interface. The message text is written by the BPM process into a
log file called hello_1.xml located in the D:\labs\lesson12 folder. To view the log file
contents perform the following steps:
a. Using Windows Explorer, navigate to the D:\labs\lesson12 folder, right-click
hello_1.xml and select Open. This opens the XML file in a Web browser window.
For example:

e.
On the Web browser you can view the XML data stored in the file. For example:
c. Close the Web browser window or page containing the hello_1.xml file information.
11. To view Performance Summary information for the current composite application, on the
HelloWorldBPM [1.0] page, click SOA Composite > Monitoring > Performance Summary.
12. Display the Metric Palette and add the Number of successful instances graph to the
Performance Summary information displayed for the HelloWorldBPM composite
application. To complete this task, perform the following steps:
a. On the HelloWorldBPM [1.0] > Performance Summary page, click Show Metric Palette.
b.
On the Metric Palette frame, expand HelloWorldBPM [1.0] > SOA Component Rollup
Metric > HelloWorldBPMProcess tree and select the Number of successful instances
check box. For example:

b.
View the BPMN Engine Statistics

13. To view the BPMN Engine statistic, perform the following steps:
a. On the Oracle Fusion Middleware Control Console page, with the Farm navigation tree
expanded to the SOA > soa-infra (soa_server1) entry, right-click soa-infra
(soa_server1) and select Service Engines > BPMN. For example:

c.
Note: A new graphic is added to the Performance Summary frame for each check box
group selected. The number of successful instances in this example may not match the
value you observe for your lab.
To collapse the Metric Palette frame, on the HelloWorldBPM [1.0] > Performance
Summary page, click Hide Metric Palette.
On the soa-infra > BPMN Engine page, you can view the overview and summary
information about all BPMN instances in the system. To view the statistic information,
click the Statistics tab.
c.
On the soa-infra > BPMN Engine > Statistics tab page, you can view graphical or
tabular formatted displays of statistical information. In addition, at the bottom of the
Statistics tab page you can monitor Thread Statistics. For example:

b.

Note: The Thread Statistic in this case show zero values since there are no BPMN
application instances active at the time the image is captured.
Chapter 13
Chapter 13 - Page 1
Chapter 13 - Page 2
Practices Overview
Configure the Oracle BAM Adapter in Oracle WebLogic Server
Configure the BAM Data Object and Report components
Deploy and initiate a composite application that sends purchase order information to
the BAM environment
Observe the BAM Report Dashboard being updated in real-time
General Notes
The goal of this practice is to send information from the SOA composite components to an
Oracle Business Activity Monitoring (BAM) server instance, by using the Oracle BAM Web
Service interface and BAM Sensor Actions. Data sent to the Oracle BAM Server is viewed by
displaying a BAM Report (called a dashboard) to observe order information being received and
its status changing in real-time as it flows through the BamPOComposite application. The BAM
report (dashboard) and its associated data object definitions are first imported into the BAM
Server to enable order data to be received by the BAM Server and monitored with the BAM
Active Viewer application.

Chapter 13 - Page 3
Overview
In this practice, you configure the BAM Adapter in the WebLogic Administration Server run-time
environment. The configuration involves setting connection pool properties for the SOAP
connection factory used by the BAM Adapter and BPEL sensors to communicate with the BAM
run-time environment.
Assumptions
Oracle WebLogic Admin server and Oracle SOA Managed Server instances are running.
Optionally, the Oracle BAM Managed Server may be running. However, the practice contains
instructions to the start Oracle BAM Managed Server instance if it is not already running.
Tasks
1.
2.
If the BAM Managed Server is not running, to start it, perform the following steps:
a. In a Command Prompt window (start a new one if needed), enter the following
commands:
D:\> set FMW_HOME=D:\Oracle\fmw\11.1.1.3
D:\> cd %FMW_HOME%\user_projects\domains\soa_domain\bin
D:\> start startManagedWebLogic.cmd bam_server1
Note: The start command opens a new separate command window.
b. Wait until the BAM Server is running. This could take between three to five minutes
depending on the resources on your machine. The BAM Server is considered in a
running state when you observe text similar to the following in the Command Prompt
window used to run the BAM Managed Server instance:
<Sep 1, 2009 11:20:55 PM MST> <Notice> <WebLogicServer> <BEA000360> <Server started in RUNNING mode>
c. Optionally, minimize the BAM Managed Server command window.
To login to Oracle WebLogic Server Administration Console, perform the following steps:
a. To access the WebLogic Server Administration Console, on a Web browser window,
enter the URL http://localhost:7001/console.
Note: In the development environment configuration provided for your practices, the
first time you access the WebLogic Server Administration Console after it has been
started, it is normal to observe the Deploying application for /console message before
the WebLogic Server 11g Administration Console login page is displayed. For
example:
b.
3.
On the WebLogic Server Administration Console login page, enter the Username
weblogic and Password welcome1, and click Login.
To configure the BAM Adapter component in the WebLogic Administration Server Web
application, perform the following steps:
a. On the WebLogic Server Administration Console home page, click on the Deployments
link in the Domain Structure pane.

Chapter 13 - Page 4
Practice 13-1: Configure the Oracle BAM Adapter
c.
On the Summary of Deployments page with the Control tab selected, in the
Deployments table heading, click the Next link (several times) until you find the
OracleBamAdapter entry. For example:
Note: In the classroom environment, the OracleBamAdapter appears in the list of

entries when the text appearing before the Previous | Next links displays Showing 51
to 60 of 75
Click the OracleBamAdapter link.

Chapter 13 - Page 5
b.
To configure the OracleBamAdapter settings for your environment, perform the

following steps:
1) On the Settings for OracleBamAdapter > Overview tab page, click the
Configuration tab.
2) On the Settings for OracleBamAdapter > Configuration tab page, click the
Outbound Connection Pools subtab.
3) On the Outbound Connection Pool Configuration Table tab page, expand the
oracle.bam.adapter.adc.SOAPConnectionFactory entry, and click the
eis/bam/soap link. For example:
4)
On the Outbound Connection Properties page, set the following Property Value
entries, by clicking in the Property Value cell, entering the value shown below, and
click Save when done.
Hostname: localhost
Password: welcome1
PortNumber: 9001
UserName: weblogic
Note: Accept default settings for other fields. Ensure you press Enter after typing
each value. For example:

Chapter 13 - Page 6
d.
e.
On the Save Deployment Plan Assistant page, set the Path to

D:\Oracle\fmw\11.1.1.3\Oracle_SOA1\soa\PlanBAMAdapter.xml, and
click OK.
Note: Edit the file name in the path by appending BAMAdapter to Plan. For
example:
After getting the confirmation that your deployment plan has been successfully created,
to check that the soa_server1 is the target specified for the new deployment plan,
1) On the Settings for oracle.bam.adapter.adc.soap.SOAPConnectionFactory page,
click the Targets tab.

Chapter 13 - Page 7
5)
On the Settings for oracle.bam.adapter.adc.soap.SOAConnectionFactory Targets

tab page, ensure that the soa_server1 check box is selected in the Servers
table, and click Save.
3)
4.
Confirm that the Messages response information (at the top of the page) displays
that all changes have been activated and updated successfully.
Note: While it indicates that mo server restarts are necessary you restart the
OracleBamAdapter in the next steps.
To restart your OracleBamAdapter after updating its deployment so that the run-time
environment activates the changes, perform the following steps:
a. Click the Deployments link in the Domain Structure pane.
b. On the Summary of Deployments page, in the Deployments table, click the Next link
(approximately four times) until you see the OracleBamAdapter entry.
c. To stop the OracleBamAdapter component, on the Deployments Summary page, in the
Deployments table, select the checkbox next to the OracleBamAdapter entry and click
Stop > Force Stop Now.

Chapter 13 - Page 8
2)
e.
f.
5.
On the Summary of Deployments page, in the Deployments table, click the Next link
(about four times) until you see the OracleBamAdapter entry.
To restart the OracleBamAdapter component, on the Deployments Summary page, in
the Deployments table, select the checkbox next to the OracleBamAdapter entry and
click Start > Servicing all requests.
Optionally, to confirm that the OracleBamAdapter Resource Adapter has started

successfully, by checking if the State column contains Active and the Health column
contains OK in the Summary of Deployment table. For example:
On the WebLogic Administration Server Console page, click the Log Out link, and close the
Web browser page or window.

Chapter 13 - Page 9
d.
Overview
In this practice you import the BAM Data Object and BAM Report (Dashboard) by running a
command-line script that uses the ICommand utility to import the structures from XML file into
the BAM Server.
You take this opportunity to use the Oracle BAM Web interface to view the definitions created.
Assumptions
All the scripts needed for this task are in the D:\labs\bin folder, and the BAM Data Object
and Report XML definition files are in the D:\labs\bam folder.
Tasks
1.
To create the Orders BAM Data Control Object and the PO Order Report BAM Dashboard
definition in the BAM Server, perform the following steps:
a. On the desktop, double-click the Command Prompt icon.
b. In the Command Prompt window, execute the following commands:
D:\> cd D:\labs\bam
D:\> bam_import po-import-cmd.xml
Enter Password: welcome1
Note: The import_tobam.bat script executes the BAM ICommand command with
the username weblogic commandline parameter. The password (welcome1) must
be entered at the prompt as shown in the text here. However, the password is not
echoed in the command window. For example:
Note: In the command window, you can observe that a Data Object called Orders is
created in a BAM Server folder called /Training/POProcessing, and that a Report
(a Dashboard), called PO Order Report is created in a folder called
/public/Report/Training/POProcessing.

Practice 13-2: Import the BAM Data Object and Report
2.
You can either close the command prompt window, or minimize it for use later in this
practice to deploy the composite application SOA archive used to monitor the BAM
integration.
To login to the BAM Web application interface, perform the following steps:
a. Open a new Web browser page, and enter the URL http://localhost:9001/OracleBAM.
b. On the Oracle BAM login page, enter the Username weblogic and Password
welcome1, and click Go.
c.
3.
On the Oracle BAM start page, you can view buttons of the following four BAM
components:
The Active Viewer is used to view and run real-time reports.
The Active Studio is used to create, edit, and delete reports.
The Architect is used to create and manage Data Objects and their data caches.
The Administrator is used for BAM Server administration tasks.
For example:
To view the Orders Data Object definition in the BAM Architect, perform the following steps:
a. On the Oracle BAM start page, click Architect.
b. On the Oracle BAM Architect page, in the Folders pane, expand the Training folder and
click the POProcessing folder link.

c.
On the Oracle BAM Architect page, under the Folders pane in the Data Objects pane,
click the Orders link.
d.
On the Oracle BAM Architect Orders data object General information page, observe
the description and zero row count indicating there is no data in the data object. Click
the Layout link.

c.
On the Oracle BAM Architect Orders data object Layout page, you can view (and edit)
the data object structure. In this case, you view the structure made of various columns
for information about order data. Some of the Tip Text columns provide a brief
explanation for data items that may not be intuitive. To view the contents click the
Contents link.
f.
On the Oracle BAM Architect Orders data object Contents page, you can normally view
any data received by the BAM Server for this data object. At this stage the contents are
empty, that is the data object does not contain any rows of information.
g.
Close the Architect page.


e.
To view the PO Orders Report definition in the BAM Active Studio component, perform the
following steps:
a. Return to the Oracle BAM start page, in either a separate Web browser window or
another Web browser tab page, click Active Studio.
b. On the Oracle BAM Active Studio page, to locate the public (shared) report that has
been designed to monitor the Orders data object information, click the Shared Reports
tab.
c.
On the Oracle BAM Active Studio Shared Reports page, use the following steps to
navigate to the Training/POProcessing folder containing the report:
1) On the right-hand pane, double-click the Training entry.
2)
d.
e.
On the right-hand pane, double-click the POProcessing entry.
Note: Above the right-hand pane, there is a pull-down menu that can be used to
navigate up through the folder structure you are in.
On the Oracle BAM Active Studio Shared Reports page, to view the design of the
report (also called a dashboard), double-click the PO Orders Report entry in the
Report Name column.
On the Oracle BAM Active Studio Shared Reports page, the POProcessing Orders
report is opened. In this page, you can create, modify, and delete components in the
report structure. In this case, you just view the structure shown in the following image,
which is explained briefly in the text appearing after the image:

4.

f.
Note: All sections of the report page use the Orders data object as the source of data
for results displayed (in real time) by the report when viewed in the Active View or
Active Studio. All charts and data are updated dynamically with the changes to data as
it arrives. The POProcessing Orders report has the following three sections:
1) The top section contains an updating list of order rows, which is sorted by
ascending Order ID, and updated as the data is feed into the Orders data object.
2) The bottom-left pane displays a three-dimensional pie-chart showing the total
sales, percentage of sales by payment type, order paid by credit or by using
PayPal.
3) The bottom-right pane displays a three-dimensional bar-chart showing the status
of orders and the number of orders with a given status.
4) On the Oracle BAM Active Studio Shared Reports page, close the PO Orders
Report tabbed page, or Web browser window containing the page.
Close the Web browser window or page displaying the Active Studio information.
Note: Instead of viewing the real-time dashboard in the Active Studio, you use the
Active Viewer application to view the real-time updates displayed in the report when
you initiate the BamPOComposite application.
Overview
In this practice you deploy the composite application that contains components which sending
data messages to BAM through the BAM Adapter and the BPEL BAM Sensor action.
Assumptions
You have configured the OracleBamAdapter properties as described in Practice 13-1 and
imported the BAM Data Object and BAM Report definitions into the BAM server as described in
Practice 13-2.
Tasks
1.
To deploy the composite application, perform the following steps:

a. In the Command Prompt window, use the SOA archive to deploy the
ApprovePOComposite application by executing the following commands:
D:\> cd D:\labs\lesson13\BamPOComposite\deploy
D:\> deploy sca_BamPOComposite_rev1.0.jar
b.
2.
To deploy the Task Form BamPO_UI application associated with the BamPOComposite
application, perform the following steps:
a. In the same Command Prompt window used to deploy the BamPOComposite
application, enter the following commands:
D:\> deploy_ear BamPO_UI
b.
qualified command D:\labs\bin\deploy_ear.
Verify deployment is successful. For example:

Practice 13-3: Deploy the Composite Application with BAM Integration
Login to the Oracle Fusion Middleware Control Console, you can view the deployed
application in the SOA Infrastructure in the Farm navigation tree or the Deployed
Applications tab page.

3.
Overview
In this practice you copy one and then several files to the D:\labs\lesson13 folder to create
multiple instances of the BamPOComposite application. This makes a more exciting and
interesting series of events to watch and monitor.
The BamPOComposite application ignores the orders ID values in the input files and replaces
them with the value of the composite instance ID to ensure that each order (even if it is the
same file) is uniquely identified by the order ID. The unique order ID ensures that the BAM
report (called a dashboard) are inserted and updated in their respective BAM data object as the
order status is changed through the life of the application.
Note: Each BamPOComposite application instances have different wait times designed in their
process flow (based on the number of items ordered and the choice of shipping duration). The
wait times create a simulation of different wait periods to enable you to watch the changes in
real-time. The approximate duration for any process instance is between two to five minutes
long. Orders with a total price greater than or equal to $2000.0 require manual approval from a
single user, in this case the tasks are assigned to the Worklist user jcooper. If the orders are
not approved within a one day period they are expired.
Assumptions
You have successfully performed the following tasks as described in the steps for Practice 13-1
through Practice 13-3:
Configured the appropriate OracleBamAdapter properties
Imported the BAM data object and report definitions successfully
Deployed the BamPOComposite and BamPO_UI applications
Tasks
Because there are several real-time events taking place in this practice, it is recommended that
you make good use of your screen real-estate and resize the following application windows so
that they are (at least partially) or mostly visible at the same time:
The Oracle Fusion Middleware Control Console displaying the BamPOComposite [1.0]
Dashboard page, and the BAM Server information when requested.
The Oracle BAM Active Viewer Web page that displays the real-time report.
The Windows Explorer window.

Note: Try to give the BAM Active Viewer the most space, because that is where the realtime activity is most active and visible.
To begin this practice, perform the following tasks:
1. If required, as the weblogic administration user login to the Oracle Fusion Middleware
Control Console, click the BamPOComposite [1.0], and entry in the SOA > soa-infra
(soa_server1) > default tree.
Note: You can click the small arrow on the frame divider to collapse the Farm navigation
tree, and resize the Web browser window to a smaller size while still maintaining some
context of the page contents.
Start the PO Orders Report in the BAM Active Viewer.
2. To start the display of the BAM PO Orders Report in the BAM Active Viewer application,

Practice 13-4: Test the Composite Application with BAM Integration
c.
If the Oracle BAM applications page is not open, create a new Web browser tab page
or window, and enter the BAM applications URL http://localhost:9001/OracleBAM.
On the Oracle BAM Login page, enter the User name weblogic and Password
welcome1, and click Go.
Note: Skip this step, if you are already logged into Oracle BAM.
On the Oracle BAM Start Page, click Active Viewer.
d.
In the Oracle BAM Active Viewer window, click Select Report.
e.
In the Select a Report Webpage Dialog from the Look In drop-down box, select
Shared Reports and double-click the Training folder.
f.
In the Select a Report Webpage Dialog, under the Shared Reports/Training folder,
double-click the POProcessing folder.
b.

a.
In the Select a Report Webpage Dialog, under the Shared

Reports/Training/POProcessing folder, select PO Orders Report and click OK.
Note: The Web browser opens a new window and starts displaying the PO Orders
Report, which does not show any values in the three report sections designed for the
report contents. For example:

g.
Initiate a BamPOComposite Application Instance

3. In a Windows Explorer window, copy the D:\labs\xml\po-file\po-small-ipod.xml
file to the D:\labs\lesson13 folder.
Note: The instance created to process the file does not require manual approval, because
the order total is less than 2000.0.
4. While watching the BAM Active Viewer window (and the Windows Explorer window), wait
for the po-small-ipod.xml file to be removed from the D:\labs\lesson13 folder, and
a. What changes do you observe in the BAM Active Viewer?
Answer: The POProcessing Orders report page is updated in the following three
areas:
The General Order Information frame, displays the order information where the
order ID is the same value as the composite instance ID. The status value is
initial.
The Total Sales by Payment Type frame displays a 3-D pie chart representing
the order paid by credit. Since this is the first order showed, it represents 100%
of the pie.
The Count of Orders by Status frame displays a single 3-D bar representing the
single order with the initial status.
For example:

Note: The report displayed is dynamically updated in real time when purchase orders
begin to be processed by BamPOComposite application instances.
Quickly return to the Web browser window displaying the BamPOComposite [1.0]
Dashboard tab page, and click Refresh. What do you see in the Recent Instances
section on the Dashboard tab page?
Answer: A new instance has been created and is in the Running state. For example:
c.
Return to the BAM Active Viewer Web page, wait approximately one to two minutes,
and describe the changes you observe in the POProcessing Orders report.
Answer: After a minute or so the POProcessing Orders report is updated to reflect the
change in the order status to the value processing. This change is reflected in the
following two frames:
The General Order Information frame, in the Status column
The Count of Orders by Status frame, where the bar color is changed and its
label is modified to the value processing.
For example:

b.
Keep observing the BAM Active Viewer for two more minutes (the duration it takes for
the approval processing to complete). After the two-minute period ends, describe the
changes you observe in the POProcessing Orders report page.
Answer: The following changes should be observed in the BAM Active Viewer:
In the General Order Information frame, the Status is changed to the approved
value.
In the Count of Orders by Status frame, the bar color is changed and the label
is changed to the value approved.
For example:

d.
Again, observe the BAM Active Viewer for another two more minutes (the duration it
takes for the shipping processing to complete). At the end of the wait period, the
following changes may be observed in the BAM Active Viewer:
In the General Order Information frame, the Status is changed to the shipped
value.
In the Count of Orders by Status frame, the bar color is changed and the label
is changed to the value shipped.
For example:

e.
Return to Web browser window displaying the BamPOComposite [1.0] Dashboard tab
page, click the Refresh icon and confirm that the instance has completed. For example:
6.
In the Windows Explorer window, examine the D:\labs\lesson13 folder and describe
the name of the new file created in the folder and the contents of the file.
Answer: The name of the new file created is ups.log, indicating that the order is shipped
by the UPS shipping company. Additional order records are appended to the file.
The usp.log file contains a single record representing the following order data (for example):
The order ID (140001)
The customer ID (2)
The order total (135)
The payment type (credit)
The order status (shipped)
Note: In your case, the value for the order ID is likely to be different to the value. For
example:

5.
Examine the BAM Components in Oracle Fusion Middleware Control

In this part of the practice, you view Active Data Cache information available in Oracle Fusion
Middleware Control Console. While you could use the BAM Architect to look at the data object
contents, using the BAM Architect is a manual process and not suited for monitoring purposes.
Note: You should already be logged into Oracle Fusion Middleware Control Console, however,
the login session may have timed out due to inactivity. If required, login to Oracle Fusion
Middleware Control Console as the weblogic administration user.
7. To view the BAM Server pages in Oracle Fusion Middleware Control Console, in the Farm
navigation tree frame, expand the BAM folder and click the OracleBamServer
(bam_server1) entry.
8.
On the OracleBamServer home page, the Active Data Cache tab page is displayed by
default. On the Active Data Cache page you can monitor all processing done with all data
objects or select a data object of interest to you. Perform the following steps to monitor the
Orders data object:
a. From the Data Objects drop-down list, select Training.POProcessing.Orders.
b. What is the Average Batch Size for Operations frame show?

Because the BAM Server is not a Service Engine and BAM is not a component of a Composite
application environment, you can monitor the BAM information in the OracleBamServer context
provided by Oracle Fusion Middleware Control Console and not through the BamPOComposite
[1.0] application pages.
c.
d.
What do you observe in the Total Transactions frame?

Answer: The request information sent to the BAM server is recorded as a single
completed transaction.
What do you see in the Client Requests in Progress frame?
Answer: Because there are no client requests in progress at the time you view the
contents of the Client Requests in Progress frame, the Requests in Progress line
chart stays at the zero level. The results may be different if there are many actively
applications sending many requests over time to the BAM Server.
Note: The example shown here may differ slightly from what you may observe.

Answer: The Average Batch Size of Operations indicates there is a size of 1 for the
Update operation. All other operations do not have a value represented.
Note: The example image shown here may differ slightly from what you may observe.
The BamPOComposite application performs the following two types of operations:
Insert (for the initial order status) and subsequently Update operations to reflect
changes in the order status. There is an Average Batch Size value which might not
reflect the application behavior for a single instance.
On the OracleBamServer page, click the Report Cache tab, and view the information
displayed about the Report Cache. For example:
Note: The three unshared viewsets represent each of the views in the POProcessing
Orders report.
10. On the OracleBamServer page, click the Active Data Cache tab to make it visible.
Note: Because the BamPOComposite application does not implement events, report
caches, or use enterprise message sources, there is no need to view the Event Engine and
Enterprise Message Sources tab pages in this practice.
Initiate Several Additional BamPOComposite Instances
In the part of the practice, you copy several purchase order files at the same time into the
D:\labs\lesson13 folder. While this causes a new instance per file to be created, some of

9.
po-gibson-only.xml, which is paid by credit with an order total greater than

2000. This order requires approval processing through email.
po-gibson-paypal.xml, which is paid by paypal with an order total that exceeds
2000.
po-small-ipod-paypal.xml, which is paid by paypal with an order total less
than 2000.
po-small-guitar.xml, which is paid by credit with an order total less than 2000.
12. When the file(s) are removed from the D:\labs\lesson13 folder, return to the BAM
Active Viewer Web page, and watch changes to the report in real time as each order is
processed. Here is a sample of changes you can expect to see in a five minute period:
a. All four files are processed at the same time causing the report display to be updated
with the changes similar to the following sequence:
1) The four new orders are added to the General Order Information frame, the
Total Sales by Payment Type pie chart is updated to reflect the percentage and
amount of credit compared to paypal orders, and the Count of Orders by Status
shows a new bar with four orders having the initial status.

which require human intervention that is easier to act on by using one of the (approve, reject or
defer) action links in the email notification messages.
Note: The sequence in which the files are processed and appear in the Active Viewer, the
BamPOComposite [1.0] Dashboard page, and the OracleBamServer > Active Data Cache might
vary a little from the information presented in this activity guide.
Additional Note: For the orders that require human interaction (approval processing), instead
of using Oracle Business Process Workspace applications to perform the approval process you
use the email message links to handle the order approval process.
The aim of this part of the practice is to generate a reasonable amount of activity on the server
so that you can observe the real-time changes displayed in the BAM report in the BAM Active
Viewer window, and refresh the Active Data Cache tab page in Oracle Fusion Middleware
Control Console to update the information that you can monitor.
11. In a Windows Explorer window, copy the following four files at the same time from the
D:\labs\xml\po-file folder to the D:\labs\lesson13 folder:
After a couple of minutes, the report is updated with the change in status to
processing for all the new purchase orders.
3)
The next change shows one order status changed to shipped, one still processing,
one approved, and two waiting orders.

2)

4)
Note: The wait time for the processing state is proportional to the number of items
in the order. In addition, the wait time for shipping approved orders is proportional
to the shipping choice name, such that an order with a next_day shipping choice
waits one minute, a two_day shipping choices waits two minutes, and the other
choices wait for three minutes. The application was designed like this to provide
some variation in the results so that you can observe real-time changes and
monitor information as it occurs.
The next change you may see is that the processing order status changes to
approved.
Subsequently, one of the approved orders status changes to shipped after its wait
time expires.

5)
Finally, the last approved order status changed to shipped, and are left with three
orders with a shipped status, and two with a waiting status. For example:
13. At any time when you observe the Count of Orders by Status frame showing orders with a
waiting status, you can take steps to perform an action on the task assigned to jcooper
through the human workflow system.
Note: In this case, the example has waited for four orders to be shipped (and completed),
and then to perform the defer task action on one of the two waiting orders, you can do the
following steps:
a. If required, open Mozilla Thunderbird by double-clicking the desktop icon.
b. On the Mozilla Thunderbird window, select the jcooper@soa11g.example.com
account, which may already have two Action Required:Approve PO notification
messages.

6)
d.
In the Action Required:Approve PO message body frame, in the Actions heading click
the Defer link.
e.
In the Write: Action Required:Approve PO window, for the reply message ensure that
you select James Cooper <jcooper@soa11g.example.com>" in the From setting.
Optionally, enter a comment in the Comments section of the message (as shown) and
click Send.

c.
Note: If the jcooper account does not have any new notification messages you can
click Get Mail.
In the jcooper Message Pane, select the first notification message with the subject
Action Required:Approve PO to view the message body and details.

f.
Note: The email message body contains the Defer action response near the bottom of
the message body. Do not delete that portion of the message. Sending the Defer
action causes the order status to be changed to out-of-stock, and this should be
reflected in the BAM Active Viewer window once the action is received and processed
by the composite application.
Return to the POProcessing Orders page in the BAM Active Viewer, and wait for the
status change for one of the waiting orders to change to out-of-stock. For example:

14. Return to the Web browser window with the OracleBamServer > Active Data Cache page
and click Refresh. Answer the following questions:
a. On the OracleBamServer > Active Data Cache tab page, with Data Objects set to All,
what operations have information displayed in the Operations Per Second section?
Answer: The Operations Per Second section displays information for the Insert and
Update operations. This is consistent with the way the BamPOComposite interacts with
the BAM server.
On the OracleBamServer > Active Data Cache tab page, change the Data Objects to
display information for the Training.POProcessing.Orders data object. What differences
do you observe?
Answer: The View Sets count is showing a value of 3 (instead of 4). The data object
supplying the information used for the report has three views (charts) displayed in the
POProcessing Orders report. For example:
Note: If you wish, you can view the additional files created in D:\labs\lesson13 folder for
the new orders processed. For example:

b.
When you are complete with your practice and experimentation, close the BAM Active Viewer
window, and click Logout on the Oracle BAM Start Page.

Note: The nonshipped_orders.log file contains information about deferred (or

rejected) orders. The ups.log, fedex.log, and usps.log files contain records for
respective orders that are sent to those shipping companies based on a business rule
executed in the BamPOComposite application.
You may also continue to create new orders, approve, and reject orders in a waiting state and
monitor the BAM Active Viewer and Active Data Cache information as long as your instructor
provides you with the time to do so. For example, click the reject link for the remaining order
with a waiting status by using the email message body links, and watch the changes in the BAM
Active Viewer.
Note: If you do not perform a task action on the waiting orders, they expire after one day. You
can also view the email messages sent to the weblogic email account when an order is deferred
or rejected to see the messages the task initiator receives in such situations, because the
Human Task, for the BamPOComposite application, was configured to send these notification
messages to the weblogic email account. For example:
Chapter 14
Chapter 14 - Page 1
Chapter 14 - Page 2
Practices Overview
In this practice you explore the B2B components in Oracle Fusion Middleware Control and B2B
Console interfaces, and also perform the following tasks:
Importing a ZIP file containing B2B configuration information into the SOA Server
environment. Importing the file saves you time configuring the B2B metadata needed
by a composite application to send a purchase order document to a trading partner
Deploying a composite application with a B2B binding component
Testing the composite by copying a purchase order file into the designated lesson
folder
Viewing the composite application instance and message information generated in the
administration Web applications
General Notes
Because the lesson does not provide detailed training on how to create all the B2B metadata
constructs needed for a composite application to execute document exchange operations, this
practice uses a ZIP file to import the metadata constructs. The ZIP is created by exporting the
B2B metadata from another system.
Exporting and importing data is a task that would be performed by an administrator to move
information needed for a B2B implementation from one server instance to another.
The imported data provides the definitions needed for deploying, testing, and monitoring the
B2B information collected by Oracle Fusion Middleware Control and the B2B Console.

Chapter 14 - Page 3
Overview
In this practice you login to the B2B Console and import the metadata for the entire B2B
repository contained in a supplied ZIP file that was exported from a development system. The
metadata defines the B2B trading partners, the documents, listening channels, and agreements
to enable the trading partners to transmit a custom purchase order between them. The key
tasks are:
Logging into the B2B Console as the weblogic user.
Importing the B2B repository metadata using the import function in the B2B Console
Administration page.
Examining the B2B constructs defined in the metadata.
Assumptions
The b2b_repository.zip file exists in the D:\labs\b2b folder.
Tasks
1.
2.
To login to the B2B Console, perform the following steps:

a. Open a new Browser window, enter the following URL http://localhost:8001/b2b (or
http://localhost:8001/b2bconsole)
Note: Ensure that you open a new window (not a new tab page) otherwise the B2B
login does not complete.
b. On the Oracle B2B login page, enter the Username weblogic and Password
welcome1 and click Login.
To import the B2B repository definitions, perform the following steps:
a. On the Oracle B2B home page, click the Administration link in the page banner. For
example:
b.
On the Oracle B2B > Import/Export tab page, click Browse in the Import section.

Chapter 14 - Page 4
Practice 14-1: Importing Metadata Using the B2B Console
In the Choose file dialog box, navigate to the D:\labs\b2b folder, select the
b2b_repository.zip file and click Open.
d.
On the Oracle B2B > Import/Export tab page, with the

D:\labs\b2b\b2b_repository.zip file selected, click Import.

Chapter 14 - Page 5
c.
c.
Note: You can examine the document definition and determine the XML schema that
defines the documents structure in the right frame of the page. Take a few minutes to
explore the information on the page. Do not make any changes.
On the Oracle B2B page, click the Deploy tab.

Chapter 14 - Page 6
3.
Note: Wait for the Busy dialog box that is opened to be closed.
e. In the Information dialog box, with the b2b_repository.zip was imported successfully.
message, click OK.
To view the imported B2B definitions, perform the following steps:
a. On the Oracle B2B page, click the Documents tab.
b. On the Oracle B2B > Documents tab page, expand the Document Protocols > Custom
> 1.0 > PurchaseOrder tree and click the PurchaseOrder_def document in the left
frame.
On the Oracle B2B > Deploy tab page, in the Search section select the value Custom
from the drop-down list for the Document Protocol Name field using the Equals
operation, and click Search. For example:
e.
Select the OracleServices_MusProdInc_Agr agreement entry, and click Deploy. For

example:
f.
g.
In the Information dialog box, with the Deployment Successful message, click OK.
On the Oracle B2B page, click the Manage Deployments tab and verify that the
OracleServices_MusProdInc_Agr agreement is shown as an Active deployment entry.
Note: You must ensure that the State field in the Search section has the Equals Active
settings, and you must click Search for the active deployment entries to be displayed.
For example:

Chapter 14 - Page 7
d.
To view the trading partner information in the imported B2B metadata, click the
Partners link in the Oracle B2B page banner.
i.
j.
On the Oracle B2B page, in the Partners frame, click MusProdInc.

On the Oracle B2B page, with the MusProdInc entry selected in the Partners frame,
you can click the OracleService_MusProdInc_Agr definition entry. For example:

Chapter 14 - Page 8
h.
On the Oracle B2B > Partners page, in the right frame you can view the agreement
definition for OracleServices_MusProdInc_Agr, which shows OracleServices as the
source trading partner sending a PurchaseOrder_def document type to the
MusProdInc trading partner. For example:

Chapter 14 - Page 9
k.
Optionally, while taking turns to select each trading partner entry, click their Channels
and Documents tabs to view their document and channel definitions information. For
example:
Note: The MusicProdInc Channels tab shows that a Generic-File-1.0 protocol is used
to deliver message documents and that the folder used for delivery is defined in the
Transport Protocol Parameter subtab.
Note: The Documents tab for the MusicProdInc reveals that the trading partner
receives a Custom-1.0.-PurchaseOrder- PurchaseOrder_def document, because the
Receiver check box is selected.
Note: After clicking the OracleServices partner name, the Documents tab for the
OracleServices reveals that a Custom-1.0.-PurchaseOrder- PurchaseOrder_def
document is sent by the trading partner, because the Sender check box is selected.

l.

4.
Note: The OracleServices Channels tab shows a message is sent using a GenericFile-1.0 protocol, using the Folder listed in the Transport Protocol Parameter subtab.
Minimize the B2B Console Web browser window. You will return to the page to examine
report and metric information after a document has been transmitted by a composite
application in the next practice for this lesson.
Overview
In this practice you deploy the B2BPOrderComposite application that uses a B2B binding to
send a document to a B2B trading partner using a File listening communication channel.
Assumptions
The B2BPOrderComposite application is deployed into the OracleServices trading partner
system, and emulates the business process to send a purchase order document to the
MusProdInc trading partner defined in the B2B agreement configured in the B2B repository.
Tasks
1.
Deploy the B2BPOrderComposite application by using the supplied SOA Archive file called
sca_B2BPOrderComposite_rev1.0.jar located in the
D:\labs\lesson14\B2BPorderComposite\deploy folder. Enter the following
commands:
D:\> cd D:\labs\lesson14\B2BPorderComposite\deploy
D:\> deploy sca_B2BPOrderComposite_rev1.0.jar
Note: You can deploy the SOA archive by using the deploy command-line tool or the
Oracle Fusion Middleware Control Console. For example, using the commands:
2.
3.
If required, open a Web browser window and login to Oracle Fusion Middleware Control
Console with the Username weblogic and Password welcome1.
On the Farm navigation frame, expand the SOA > soa-infra (soa_server1) > default folder,
and click the B2BPOrderComposite [1.0] entry.

Practice 14-2: Deploy and Test a B2B Sender Composite Application
On the B2BPOrderComposite [1.0] page, verify that there are no instances listed in the
Dashboard section.
5.
To initiate the B2BPOrderComposite application, copy the D:\labs\xml\po-file\pogibson-only.xml file into the D:\labs\lesson14 folder.
Note: Wait until the D:\labs\xml\po-file\po-gibson-only.xml file is removed
from the D:\labs\lesson14 folder.
After the po-gibson-only.xml file is removed, you should notice that new file with an
OracleServices_*.dat file name is created in the same folder. This file contains the
purchase order document sent to the MusProdInc trading partner by the
B2BPOrderComposite application. For example:
6.
On the B2BPOrderComposite [1.0] home page, click the Refresh icon to update the
Dashboard page with the new instance information and verify that the instance completed
successfully. For example:

4.
b.
On the B2B Infrastructure (SOA Binding) page, you monitor statistics, information
about the top 5 trading partners, Inbound Endpoints, and Outbound Endpoints at the
same time. For example:

7.
Note: You can click the Instance ID link to view the Flow Trace, however, there is not much
to view in the flow trace of this successfully completed composite instance.
To view the B2B Binding information in Oracle Fusion Middleware Control Console, perform
a. On the Farm navigation frame, right-click the SOA > soa-infra (soa_server1) entry and
select Bindings > B2B. For example:
To view the B2B Binding Component information in the B2BComposite application instance,
a. On the Farm navigation frame, click the B2BPOrderComposite [1.0] entry in the SOA >
soa-infra (soa_server1) > default tree.
b. On the B2BPOrderComposite [1.0] page, collapse the Recent Instances and Recent
Fault and Rejected Messages section, and click the B2BPoSendb2bService link in the
Services and References section.

8.
On the B2BPOrderComposite [1.0] > Reference Home > B2BPoSendb2bService (B2B

Binding) page, you can view B2B information specifically for that composite instance
component. For example:
9. Maximize (or return to) the Web browser window containing the B2B Console page.
10. To view the B2B report information in the B2B Console, perform the following steps:
a. On the Oracle B2B page, click the Reports link in the page banner.
b.
On the Oracle B2B > Reports > Business Message tab page, you can click the Result
message entry to view the details. For example:

c.
In the Business Message dialog box, view information about the specific message
delivered and click OK.

c.
On the Oracle B2B > Reports page, click the Wire Message tab to view the Result
message entry.
Note: You can optionally click the message entry to view the messaged details.

d.
On the Oracle B2B > Reports page, click the Application Message tab to view the
Result message entry.
f.
On the Oracle B2B > Report page, click the Conversation tab to view the Result
message entry, and click the message entry to display the Conversation details at the
bottom of the page. For example:
11. To view B2B metric information in the B2B Console, perform the following steps:
a. On the Oracle B2B page, click the Metrics link in the page banner.
b.
On the Oracle B2B > Metrics page, you can view the system metrics and summary
information.

e.
On the Oracle B2B > Metrics page, click the Partners tab to view metric information for
each trading partner. By default information for the first trading partner listed in the
Active Trading Partners frame is displayed. For example:
d.
On the Oracle B2B > Metrics > Partners tab, click the OracleServices trading partner
entry in the Active Trading Partners frame to displayed metrics for the OracleServices
trading partner. For example

c.

12. Logout from the B2B Console and close the Web browser window that contains the B2B
Console page.
Chapter 15
Chapter 15 - Page 1
Chapter 15 - Page 2
Practices Overview
Deploy a Web Service, implemented as an Application Development FrameworkBusiness Component (ADF-BC) Web service that provides database interaction
functionality for the SubscribeStockUpdComposite application.
Deploy the SubscribeStockUpdComposite application.
Perform an event test operation in Oracle Fusion Middleware Control Console.
Deploy the PublishStockUpdComposite application.
Initiate the PublishStockUpdComposite application and monitor events and instances

created as a result of processing a files containing stock update information.
General Notes
The ADF-BC Web application uses the jdbc/soademo data source configured in practice
associated with JCA Adapter lesson, because it contains the ADF-BC objects that interact with
the database to query, insert, update, and potentially delete rows from a database table called
EXTERNAL_STORE. Therefore, in this practice you use The SQL(*Plus) command-line utility to
query the information in the EXTERNAL_STORE table.
You are also shown how to access the ADF-BC Web service interface and test if the service is
operational and returns meaningful information, before you deploy the
SubscribeStockUpdComposite application that depends on the ADF-BC Web service.
Note: The SubscribeStockUpdComposite application uses the ExternalStoreService as a
Service Data Object, which is a form of Web service providing a data query and manipulation
interface implicitly invoked through operations performed on an XML data structure. The
database interaction through the XML structure (exposed by the Entity Variable) is done in the
context of a BPEL process. The Entity Variable is a BPEL process construct that could be
actively used by Oracle SOA Suite composite application implementations which require
database interaction.

Chapter 15 - Page 3
Overview
In this practice you deploy the ExternalStoreService, which is an ADF-BC Web application that
provides a Web service interface for the SubscribeStockUpdComposite application to perform
database operations on the EXTERNAL_STORE database table. Before you deploy the
SubscribeStockUpdComposite application you verify that the ExternalStoreService is
operational to ensure that the data source required by the application is accessible and the
service is functional.
You deploy the SubscribeStockUpdComposite application, which subscribes to a StockUpdated
event, and use the Oracle Fusion Middleware Control Console send a test event to verify that
the subscriber receives the event.
Assumptions
The Oracle Database is running and the SOADEMO schema has been created with the required
database tables and populated with the correct data. In addition, the DbAdapter configuration in
Oracle WebLogic Administration Server should have been configured with a data source
identified by the JBDC URL jdbc/soademo.
Note: All of these requirements are addressed in the practices associated with the JCA Adapter
lesson.
Tasks
1.
To deploy the ExternalStoreService ADF-BC application using the supplied EAR file,
a. In a Command Prompt window (open a new one if needed), use the EAR archive to
deploy the ExternalStoreService application by executing the following commands:
D:\> deploy_ear ExternalStoreService
b.
Tip: To save typing long file names, enter the first letters of the file name and press
Tab (and delete the file .ear extension).

Chapter 15 - Page 4
Practice 15-1: Deploy the Stock Update Composite and Web Service
prodid: GUI001
For example:

Chapter 15 - Page 5
2.
Note: You can locate the deployed ExternalStoreService application by expanding the
Application Deployments tree in the Farm navigation frame of Oracle Fusion
To test that the ExternalStoreService ADF-BC Web service interface is functional and that
the data source configuration is correct, perform the following steps:
a. In a Web browser, create a new tab or window and enter the following URL:
http://localhost:8001/ExternalStoreADFBCService/ExternalStoreService.
b. On the ExternalStoreService endpoint page, accept the default Operation
getExternalStoreVO1 (otherwise select getExternalStoreVO1 from the
Operation drop-down box if it is already selected), and after entering the following field
value click Invoke:
On the Test Result page, in Raw XML view mode you can verify that the data return
shows the prodId value of GUI001 (as entered for the input parameter, or search
criteria) and the Quantity value of 5, as retrieved from the EXTERNAL_STORE database
table by the application. For example:
Note: Alternatively, for a prettier view of the response data, click the Formatted XML
view link to display the results in a more visually pleasing formation. For example:

Chapter 15 - Page 6
c.
3.
Close the Test Result page.

Note: Web services deployed to Oracle WebLogic Server instances provide an
endpoint Web page that can be used to verify if the service is accessible and
operational and performing the correct functionality. Naturally, you must take care that
you do not invoke operations that inadvertently alters corporate data.
To deploy the SubscribeStockUpdComposite application, perform the following steps:
deploy the SubscribeStockUpdComposite application by executing the following
commands:
D:\> cd D:\labs\lesson15\SubscribeStockUpdComposite\deploy
D:\> deploy sca_SubscribeStockUpdComposite_rev1.0.jar
b.

Chapter 15 - Page 7
d.
To login to the Oracle Fusion Middleware Control Console and locate the deployed
applications, perform the following steps:
a. On a Web Browser window, (if required) enter the URL http://localhost:7001/em, and
login with the Username weblogic and Password welcome1.
b. On the Oracle Fusion Middleware Control Console Farm navigation frame, expand
Application Deployments and verify that the ExternalStoreService entry is present.
c.
d.
Collapse the Application Deployments tree in the Farm navigation frame.

On the Oracle Fusion Middleware Control Console Farm navigation frame, expand the
SOA > soa-infra (soa_server1) > default tree and click the
SubscribeStockUpdComposite [1.0] entry. In the Dashboard page, confirm that there
are no instances listed for the application. For example:

Chapter 15 - Page 8
4.
Chapter 15 - Page 9
Overview
In this practice you use the Business Event Web interface to examine the event definitions and
event subscribers, and initiate a test event for the StockUpdated event to verify that the
SubscriberStockUpdComposite application receives and processes the test event.
Note: The event test is done as a check that the event subscriber is operational before the
event publisher application is deployed and tested. By performing the steps described here you
are learning about the tools that can assist you to troubleshoot scenarios that involve
applications that use events to communicate information and initiate processing, while also
being reminded about application dependencies in the form of service references and run-time
server configuration requirements.
Assumptions
You have successfully deployed the ExternalStoreService ADF-BC application, and verified that
it is operational to confirm that the run-time data source configuration is correct.
Tasks
1.
To examine the Business Event information in Oracle Fusion Middleware Control Console,
a. If required, access the Oracle Fusion Middleware Control Console home page, and
click the soa-infra (soa_server1) entry in the SOA folder of the Farm navigation frame,
and on the soa-infra home page, click SOA Infrastructure > Business Events. For
example:
b.
With the soa-infra > Business Events page visible, answer the following questions:
1) What events are shown in the Events tab page?
Answer: The event listed in the Events tab page is called the StockUpdated event.
For example:

Practice 15-2: Test the Subscriber of the StockUpdated Event
3)
What is event subscription count?

Answer: The event subscription count is one. This is seen in the Subscriptions
column in the Namespaces and Events table.
What is the XML namespace for the StockUpdated event definition and the event
payload? Explain how you determined the information.
Answer: The event definition namespace is
http://www.example.com/events/edl/StockEventDefinitions, which
is the same namespace used for the event content namespace.
The event definition XML namespace can be seen in the Namespaces and
Events table as the parent of the StockUpdated event. The event content
namespace (specified for the payload) is the same as the event definition in this
case (although it does not have to be this way). You can find the event content
namespace by selecting the StockUpdated event and clicking Show Event
Definition. For example:
In the XML Definition: StockUpdated dialog box, you can locate the XML
namespace for the event structure in the schema-import element.

2)
Click OK to close the XML Definition: StockUpdated dialog box.

What are the XML elements needed to create a StockUpdated test event
message?
Answer: Using the Show Event Definition button and examining the XML
Definition for the event, you can only get the main element name for the event
structure. In this case, it is called ns0:StockUpdInfo, where ns0 is an XML
namespace prefix that references the namespace
http://www.example.com/events/edl/StockEventDefinitions to fully
qualify its elements.
Note: You require access to the actual XML Schema file to determine the
complete structure of the StockUpdInfo element.
In this case, the StockUpdInfo element has the following two child elements:
The productId element, which contains a product ID string value.
The quantity element, which contains an integer quantity value.
The following image is a visual representation of the XML schema defining the
StockUpdated event payload obtained from the Oracle JDeveloper XML Schema
Editor:
Note: To create an event document for this XML Schema definition you need to
qualify each element by its correct XML namespace. This is easily done by using
an XML namespace prefix defined by an xmlns attribute in the root element. For
example:
<evt1:StockUpdInfo xmlns:evt1=
"http://www.example.com/events/edl/StockEventDefinitions">
<evt1:productId>GUI001</evt1:productId>
<evt1:quantity>10</evt1:quantity>
</evt1:StockUpdInfo>

4)
2.
Note: The Search section has been collapsed in the image to focus on the Component
Subscriptions section.
Before you test the StockUpdated event from Oracle Fusion Middleware Control Console,
examine the EXTERNAL_STORE table data with the SQL command-line utility, by
performing the following steps:
a. On the Windows Desktop, click Start > Programs > Oracle Database 10g Express
Edition > Run SQL Command Line
b. On the Run SQL Command Line window, execute the following statements:
SQL> CONNECT soademo/soademo
SQL> SELECT * FROM external_store WHERE prod_id = 'GUI001';
Note: Alternatively, you can execute the D:\labs\sql\query_gui001.sql script.
The Results should be similar to the following data:
PROD_ID
QUANTITY
-------------------- ---------GUI001
5
For example:

c.
Note: In this example, the XML namespace prefix used is evt1 that is mapped to
the required XML namespace string
http://www.example.com/events/edl/StockEventDefinitions.
You can determine the XML structure of payloads for a composite by first
examining the service WSDL and then the XML schemas either inline or imported
into the WSDL. However, XSL schema documents for event messages are not
visible through the WSDL.
Where do you locate the subscriber for the StockUpdated Event?
Answer: On the Business Events page, click the Subscribers tab and look in either the
Database Subscribers or Component Subscribers sections. In this case, you only find
the SubscribeStockUpdComposite in the Component Subscribers section. For
example:
3.
Minimize the Run SQL Command Line window.

Note: Do not exit the Run SQL Command Line window, because you execute the
same SQL command again after initiating a StockUpdated event test.
To initiate a test of the StockUpdated event and an instance of the
SubscribeStockUpdComposite application, perform the following steps:
a. On the soa-infra > Business Events page, click the Events tab.
b. On the Business Events > Events tab page, select the StockUpdated event entry and
click Test.
c.
In the Test Event: StockUpdated dialog box, copy the contents of the
D:\labs\xml\events\stockupdatedevent_1.xml file into the XML Payload
field and click Publish.

c.
2)
Using the SubscribeStockUpdComposite application instance Flow Trace, identify

the composite application component that received the StockUpdated event and
explain the steps you used to locate the component.
Answer: The component that receives the StockUpdated event is the
SubscribeUpdEventMediator component. To locate the information in the Flow
Trace that identifies the component that receives the event, perform the following
steps:
a) On the Dashboard page, click the instance ID for the composite application.
b) On the Flow Trace page, you can identify the
SubscribeStockUpdMediator component received the event, because it
appears in the row immediately below the StockUpdated event entry in the
Trace tree. For example:

4.
Note: The data in this event request that the product with ID GUI001 is updated with a
quantity of 10 more of this product.
d. On the Information dialog box, with the message The Event published successfully.
click OK.
To confirm that the SubscribeStockUpdComposite application receives and processed the
test StockUpdated event, perform the following steps:
a. On the Oracle Fusion Middleware Control Console Farm navigation frame, click the
SubscribeStockUpdComposite [1.0] entry, in the SOA > soa-infra (soa_server1) >
default tree, and answer the following questions and perform the associated steps:
1) Did the new instance created for the SubscribeStockUpdComposite application
complete successfully?
Answer: Yes. When you navigate to the SubscribeStockUpdComposite [1.0] >
Dashboard tab page, the newly created instance has a Completed state. For
example:
Note: An alternative way to determine the name of subscribing component is to

view the Subscriptions tab page for the subscriber of the StockUpdated event in
the SOA Infrastructure > Business Events page. For example:

In addition, if you wish you can click the mediator component link to view the
onEvent information in the Audit Trail for the component. For example:
PROD_ID
QUANTITY
-------------------- ---------GUI001
15
In this case, the StockUpdated event payload requests an update of a quantity of 10,
which is added to the product with ID GUI001. For example:

5.
3) Close the SubscribeStockUpdComposite application instance Flow Trace page.

Note: There is no need to revisit the Business Events page because it does not display
information for successfully published events. However, if there are event failures you can
return to the Business Events page, and view information in the Faults tab and the
Subscriptions tab to locate the composite and components for which event faults have
occurred.
Maximize the Run SQL Command Line application window, and perform the following steps
to view the changes to the database data row:
a. On the Run SQL Command Line window, execute the following statement:
SQL> SELECT * FROM external_store WHERE prod_id = 'GUI001';
Note: You can press the UP arrow key to recall previous SQL statements entered in
the Run SQL Command Line window. The Results should be similar to the following
data:
b.
Overview
In this practice you deploy and test the PublishStockUpdComposite application, the final piece
of this lesson practice.
The PublishStockUpdComposite application takes the data from an input file (or a SOAP
request), copies the product ID and quantity into the StockUpdated event message, and
publishes the event. You view the results of the process instances created for the event to
ensure that the event published by the PublishStockUpdComposite is received and processed
by the SubscribeStockUpdComposite application.
Assumptions
You have successfully completed Practice 15-1 and Practice 15-2.
Tasks
1.
To deploy the PublishStockUpdComposite application, perform the following steps:

deploy the PublishStockUpdComposite application by executing the following
commands:
D:\> cd D:\labs\lesson15\PublishStockUpdComposite\deploy
D:\> deploy sca_PublishStockUpdComposite_rev1.0.jar
b.
2.
To check the database data, maximize the Run SQL Command Line application window,
and execute the following SQL statement to view the database data row for the IPOD01
product ID:

Practice 15-3: Deploy, Test, and Monitor Event Publishing Composite
PROD_ID
QUANTITY
-------------------- ---------IPOD01
20
The data before the StockUpdated event occurs is a quantity of 20 for the product with ID
IPOD01. For example:
3.
To initiate an instance of the PublishStockUpdComposite application, perform the following

steps:
a. In a Windows Explorer window, copy the
D:\labs\xml\events\stockupd_file_01.xml file to the D:\labs\lesson15
folder.
b. Wait until the stockupd_file_01.xml file is removed from the D:\labs\lesson15
folder.
Note: If you open this file, the stock update requests an addition of a quantity of 10
more for the product ID IPOD01, for example:
c.
Note: The XML namespace and XML elements for the PublishStockUpdComposite
application input file is different to the StockUpdated XML structure. They do not need
to match. The application performs a transformation to convert the data from one
structure to another.
On the Oracle Fusion Middleware Control Console page, click the
PublishStockUpdComposite [1.0] entry, in the SOA > soa-infra (soa_server1) > default
tree and confirm that a new instance ID has been created. For example:

SQL> SELECT * FROM external_store WHERE prod_id = 'IPOD01';

Note: You can press the UP arrow key to recall previous SQL statements entered in the
Run SQL Command Line window and replace the quoted value to IPOD01. Alternatively,
you can execute the D:\labs\sql\query_ipod01.sql script. The Results should be
similar to the following data:
Note: The Business Events page does not provide any information about the
publishers.

4.
Note: If required (due to session the timeout) you may need to login to Oracle Fusion
Middleware Control Console as the user weblogic.
To view the results of the PublishStockUpdComposite application instance, perform the
following steps:
a. On the PublishStockUpdComposite [1.0] home page, click the instance ID link for the
new instance to open the Flow Trace page.
b. Observing the information in the Flow Trace page, answer the following questions:
1) What is the name of the component publishing the event?
Answer: In this case, the PublishStockUpdEventMediator is the publisher of the
StockUpdated event, because the StockUpdated event entry appears below the
PublishStockUpdEventMediator component entry in the Trace tree. For example:
5.
Do you need to go to the event subscriber application page to see the results of
the completed application flow sequence? Why or why not?
Answer: You do not need to visit the SubscribeStockUpdComposite application
page. The Flow Trace displays the components involved in the entire process flow
for both composite application instances that publish and subscribe to the same
event instance. And both applications are running in the same SOA Suite run-time
environment.
c. Close the Flow Trace page for the PublishStockUpdComposite [1.0] instance.
Maximize the Run SQL Command Line application window. To view the changes to the
database data row, perform the following steps:
a. On the Run SQL Command Line window, execute the following statement:
SQL> SELECT * FROM external_store WHERE prod_id = 'IPOD01';
Note: You can press the UP arrow key to recall previous SQL statements entered in
the Run SQL Command Line window.
The Results should be similar to the following data:
b.
Exit and close the Run SQL Command Line window.

2)
Chapter 16
Chapter 16 - Page 1
Chapter 16 - Page 2
Practices Overview
Create a simple username token service security policy.
Apply the security policy to a service endpoint.
Test the application without and with credentials supplied in the client request.
General Notes
This is the practice for lesson titled Configuring Security Services and Policies

Chapter 16 - Page 3
Overview
In this practice you login to Oracle Fusion Middleware Control Console, use Oracle Web
Services Manager policy management interface to create a simple security policy that can be
applied to a service endpoint. In this case, you use a WS-Security UsernameToken security
policy template and a logging template to create the policy.
Assumptions
None.
Tasks
To create a new security policy, perform the following tasks:
1. In a Web browser window, if needed, login to Oracle Fusion Middleware Control Console by
using the following steps:
a. Enter the URL http://localhost:7001/em to access the Oracle Fusion
Middleware Control Console Web application.
b. On the Login page, enter user name weblogic and password welcome1, and click
Login.
2. To access the Web Services Policy management Web page, perform the following steps:
a. In Oracle Fusion Middleware Control Console, on the Farm navigation frame, expand
the WebLogic Domain folder and click soa_domain.
b.
On the Fusion Middleware Control page, click WebLogic Domain > Web Services >
Policies. For example:

Chapter 16 - Page 4
Practice 16-1: Create a Simple Username Token Security Policy
On the Web Services Policies page, perform the following steps to create a new policy:
a. Accept the default settings for the Category and Applies To lists, and click Create.
b.
On the Web Services Policies > Create Policy page, enter the following field values:
Name: soa11g/admin_username_token_service_policy
Description: This policy requires WS-Security credentials to be
supplied with SOAP requests.
Note: The description is optional. To save time you do not enter the description, and
accept default settings for all other fields. All policies are identified by the directory in
which the policy is located. For example:

Chapter 16 - Page 5
3.
Note: The Create button is available only for the Security and Management categories.
You cannot edit the name of a policy once the policy is created. To change the policy
name, you will need to copy the policy and assign it a different name.

Chapter 16 - Page 6
4.
Note: By default, the policy is enabled. If you want to disable the policy, clear the
Enabled box. A policy that is not enabled is not enforced at runtime. If you select (or
accept) the default value of Service Bindings for the Applies To list, you can choose
to specify whether the policy can be attached to Service Endpoints or Service
Clients. In this case, we accept the default as Service Endpoints.
To add the first policy assertion to the new policy, perform the following steps:
a. On the Web Services Policies > Create Policy page, in the Assertions section, click
Add.
In the Add Assertion dialog box, enter the Name username_token, select
oracle/wss_username_token_service_template from the Assertion Template
list, and click OK.
c.
In the Assertions section, examine the default settings and details for the new
assertion, without changing any of the settings.
Note: In the assertion details you can edit the description, specify the properties for the
assertion in the Set Settings tab page (click the Help icon for information on setting the
properties), and click the Configurations tab to set configuration options.
To add the second assertion to the new policy, perform the following steps:
a. On the Web Services Policies > Create Policy page in the Assertions section, click
Add.

Chapter 16 - Page 7
5.
b.
In the Add Assertion dialog box, enter the Name log1, select
oracle/security_log_template from the Assertion Template list, and click OK.
c.
In the Assertions section, examine the default settings for the log1 assertion (without
changing any of the settings), select the log1 entry, and click Up.
Note: The assertions are invoked in the order in which they appear in the list.
To validate and save the policy definition, perform the following steps:
a. On the Web Services Policies > Create Policy page, click Validate to verify that the
policy does not contain errors.
b.
c.
In the Information dialog box, with the Validation successful! message, click OK.
On the Web Services Policies > Create Policy page, ensure that the policy is enabled
and click Save.

Chapter 16 - Page 8
6.
b.

Chapter 16 - Page 9
d.
Note: Clicking Save closes the Create Policy page.

On the Web Services Policies page, scroll down the list and verify that
soa11g/admin_username_token_service_policy is available and that it has a
tick icon in its Enabled column. For example:
Overview
In this practice you deploy a ValidateCreditComposite application that performs credit card
validation. Before testing the application functionality, you attach the new security policy
created in Practice 16-1 to the ValidateCreditCard_ep service entry point of the
CreditCardValidation composite application. You test the service with and without supplying
security credentials.
Assumptions
You have created the WS-Security UsernameToken security policy by completing practice 16-1.
In addition, because the ValidateCreditComposite application uses a Database Adapter, which
is configure with the JDBC URL jdbc/soademo, the JDBC data source should already be
configured in the run-time environment along with its associated DbAdapter connection factory.
Note: The ValidateCreditComposite application uses the DbAdapter to query the data from the
CREDITCARDS table of the SOADEMO database schema, which should also already exist. The
steps needed to configure the database adapter and database tables are described in Practice
14.
Tasks
1.
To deploy the ValidateCreditComposite application, perform the following steps:

deploy the ValidateCreditComposite application by executing the following commands:
D:\> cd D:\labs\lesson16\ValidateCreditComposite\deploy
D:\> deploy sca_ValidateCreditComposite_rev1.0.jar
b.

Practice 16-2: Apply a Security Policy to a Service Endpoint
3.
In a Web browser window, if needed, login to Oracle Enterprise Manager by using the
following steps:
a. Enter the URL http://localhost:7001/em to access the Oracle Enterprise
Manager Web application.
Login.
To locate the policy page for the ValidateCreditComposite application and attach the policy
to the ValidateCreditCard_ep entry point, perform the following steps:
a. On the Farm_soa_domain tree, expand the SOA folder and click on the
ValidateCreditComposite [1.0] composite link.
b.
On the ValidateCreditComposite [1.0] page, click the Policies tab.
c.
On the ValidateCreditComposite [1.0] Policies page, click Attach To/Detach From >
ValidateCreditCard_ep.

2.
e.
f.
On the Attach/Detach Policies(CreditCardValidation ) page, under the Available

Policies section, select the row containing the Name
soa11g/admin_username_token_service_policy, click Attach.
Note: You can use Search feature to make it easier to locate the desired policy. In the
above example, in the Available Policies section, you select Name from the Search
drop-down box, enter username in the search field, and click the Search icon ( ) to
produce the list shown in the image. Otherwise, scroll down the Available Policies page
to locate the soa11g/admin_username_token_service_policy entry.
On the Attach/Detach Policies(CreditCardValidation ) page, under the Attached
Policies section, select the attached policy entry, and click Validate.
On the Information dialog box, with the Validation is successful message, click OK.

d.
On the Attach/Detach Policies(CreditCardValidation ) page, confirm that the

attached soa11g/admin_username_token_service_policy is enabled, and click
OK.
h.
On the ValidateCreditComposite [1.0] Policies page, you can view the policy and the
service endpoint to which the policy is attached in addition to security violation
information counters (use the horizontally scroll bar embedded in the page). For
example:
g.

Overview
In this practice you perform two tests to verify the attached security policy is functional, by using
the ValidateCreditComposite Test Web Service page to initiate an instance:
Without providing WS-Security credentials in the SOAP header.
Supplying the WS-Security credentials in the SOAP header.
Assumptions
You have created the security policy, deployed the ValidateCreditComposite application, and
attached the security policy to the SOAP entry point of the composite application as described in
Practice 16-1 and Practice 16-2.
Tasks
1.
2.
In a Web browser window, if needed, login to Oracle Enterprise Manager by using the
following steps:
a. Enter the URL http://localhost:7001/em to access the Oracle Enterprise
Manager Web application.
Login.
To perform a test of the attached security policy, perform the following steps:
a. If needed, on the Oracle Fusion Middleware Control Console Farm navigation frame,
expand the SOA > soa-infra (soa_server1) > default tree, click the
ValidateCreditComposite [1.0] entry, and click the Policies page.
b. On the ValidateCreditComposite [1.0] page, click Test.
c.
On the ValidateCreditComposite [1.0] > Test Web Service > Request tab page, in the
Input Arguments section, enter the following field values, and click Test Web Service:
CCNumber: 1234-1234-1234-1234
amount: 100
For example:

Practice 16-3: Test Invocation of the Secured Service Endpoint
2)
In the Webservice invocation failed window, expand Show Additional Trace

Information. What does it tell you? Use the following image as a guide:

d.
Note: The None option should be selected by default in the Security section.
After clicking Test Web Service what is the result of the test?
1) Answer: The Webservice invocation failed window is displayed. For example:

3.
Note: As shown in the image, the highlighted text stating error in processing the
WS-Security security header is a hint of the answer. The answer is that you did
not provide the WS-Security information (a valid username and password), which
is sent in the request header when the WS-Security information is required to
invoke the service.
An instance of the ValidateCreditComposite application is not created, which you
can verify if you look in the ValidateCreditComposite [1.0] Dashboard page.
However, first proceed with the next step of this practice.
3) Close the Webservice invocation failed window.
Because you have a log assertion in the security policy attached to the entry point of the
ValidateCreditComposite application, you can view the log messages for the SOAP request
and response body in the diagnostic.log file, located in the
DOMAIN_HOME\servers\soa_server1\logs\owsm\msglogging folder. In this case,
the DOMAIN_HOME path is
D:\Oracle\fww\11.1.1.3\user_projects\domains\soa_domain.You can open
the diagnostic.log in Notepad to view its contents. For example:
b.
On the ValidateCreditComposite [1.0] > Test Web Service > Response page, verify
that you get a return value VALID as the response value. For example:

4.
Note: Ensure that you close the log file before continuing with the next step.
To execute the second test with the WS-Security credentials provided for the WSS
Username Token style of security, perform the following steps:
a. On the ValidateCreditComposite [1.0] > Test Web Service > Request tab page, in the
Security section select the WSS Username Token option, enter weblogic in the
Username and welcome1 in the Password fields, and click Test Web Service.
Note: You can scroll down and verify that the Input Arguments retained the previous
values entered, where CCNumber is 1234-1234-1234-1234 and amount is 100, before
you click Test Web Service. For example:
Note: Remember to close the log file when you are finished examining its contents.
In the request log message, shown above, observe that the WS-Security elements for the
Username and Password are visible in plaintext. Therefore, consider adding additional
assertions to encrypt the information or use alternative policies that include already
implement encryption assertions for sensitive information.

5.
Note: The ValidateCreditComposite has a synchronous request-response invocation

style. Provided that the WS-Security credentials are supplied and authenticated, you
do get a response as shown for the CCNUmber and amount values documented.
For the successful invocation of the service with security credentials supplied, if desired,
you can view the additional log messages written to the diagnostic.log file, located in
the DOMAIN_HOME\servers\soa_server1\logs\owsm\msglogging folder, where
the DOMAIN_HOME value is
D:\Oracle\fmw\11.1.1.3\user_projects\domains\soa_domain.You can open
the diagnostic.log in Notepad to view its contents. For example:
On Oracle Fusion Middleware Control Console Web page, return to the

ValidateCreditComposite [1.0] Test Web Service page and click the
ValidateCreditComposite [1.0] link at the top of the page.
7.
To monitor the ValidateCreditComposite [1.0] application policy data , perform the following
steps:
a. On the ValidateCreditComposite [1.0] page, click the Policies tab.
b.
Note: The one completed instance listed in the Recent Instance section is for the
successful invocation of the application when the WS-Security credentials are
provided. An instance will not be created when the security credentials are absent.
On the ValidateCreditComposite [1.0] > Policies tab page, use horizontal scrollbar
below the attached policy to view the Security Violations information. For example:
Note: In this case, the initial test is recorded as a violation by the value of 1 appearing
in the Total Violations column.

6.
Chapter 17
Chapter 17 - Page 1
Chapter 17 - Page 2
Practices Overview
In the practices for this lesson, the key tasks are to explore and view:
The Topology Viewer available in Oracle Fusion Middleware Control Console.
The performance information pages available for WebLogic Server instances, SOA and
application components.
General Notes
The practice environment has not provided the tools to generate a large system load for honing
performance tuning skills. In addition, performance tuning is a multi-layered discipline that
requires an iterative monitoring and tweaking process that can take a long time to get the
desired results. Therefore, the purpose of this practice is to familiarize yourself with the various
pages in Oracle Fusion Middleware Control Console that enable you to monitor performance of
Oracle SOA Suite components and applications.

Chapter 17 - Page 3
Overview
The goal of this practice is to become familiar with the Topology Viewer available in Oracle
Fusion Middleware Control Console.
Assumptions
Oracle SOA Suite 11g (11.1.1.3) has been installed and is running.
Tasks
To explore the information provided by the Topology Viewer, perform the following tasks:
1. If required, in a Web browser window, login to Oracle Enterprise Manager by using the
following steps:
a. Enter the URL http://localhost:7001/em to access the Oracle Enterprise Manager Web
application.
Login.
2. On the Oracle Fusion Middleware Control Console home page, to access the Topology
Viewer, click Topology.
Note: the Topology Viewer is opened in a new Web browser window.

View Metrics for the SOA Server
3. In the Topology Viewer window, explorer the information available by performing the
following steps:
a. Use the mouse to drag the topology diagram so that you can see the soa_server1
component in the viewer, and click the Expand icon for the soa_server1 component.
Note: Alternatively, you can use the Navigator feature (in the bottom-right corner of the
page) to bring the soa_server1 component into view.

Chapter 17 - Page 4
Practice 17-1: Examine Server Information in the Topology Viewer
After expanding the soa_server1 component, in the Topology Viewer banner toolbar,
select the Metrics check box. For example:
c.
In the expanded soa_server1 component, you can view icon and metric information for
deployed applications. If you move your mouse over the icon next to the soa_server1
component name or let the mouse hover over the bottom of the expanded icon view
(near the Request Processing Time metric), then the soa_server1 pop-up callout box is
displayed. Click the more link to open a dialog box with more details about the
component and its metrics.
d.
In the Properties for soa_server1 dialog box, click the Metrics tab to view metric
information.
Note: You can click Refresh to update the information in the dialog box.

Chapter 17 - Page 5
b.
In the Properties for soa_server1 dialog box, click Ports to view information about
soa_server1 port usage. For example:
f.
In the Properties for soa_server1 dialog box, after viewing the port information, you
can also view general configuration information in the General tab. When you have
finished viewing the information provided, click the Close icon in the top-right of the
dialog window title bar.

Chapter 17 - Page 6
e.
h.
In the Properties for soa-infra dialog box, click the Metrics tab to view the metric
information. Feel free to examine information in the other tabs, and click Close.
Note: The metric information counts displayed in this example may differ from what
you observe on your system.

Chapter 17 - Page 7
View Metrics for the SOA Infrastructure

g. To examine the metrics for the SOA Infrastructure, move the Topology Viewer diagram
with the mouse or Navigator frame until you can locate the soa-infra icon. When you
have located the soa-infra icon, move the mouse over the icon and click the more link
in the popup callout box.
Note: You can use the Zoom In and Zoom Out options near the top-left side of the
viewer window to obtain more or less detail on the page.
j.
In the Properties for ApprovePOComposite [1.0] dialog box, click the Metrics tab to
view the application metric information available. When you are finished examining the
information, click the Close icon.
k.
In the Topology Viewer toolbar, click the Down link to display a list of components that
have been shutdown (or down for other reasons). For example:

Chapter 17 - Page 8
View Metrics for Composite Applications

In this section you view metrics for a composite application that is active (up) and one that is
inactive (shutdown).
i. In the Topology Viewer window, move the viewer with the mouse or Navigator frame
and locate a deployed composite application that is in the active state (or UP), for
example the ApprovePOComposite [1.0] application icon. Move the mouse over the
ApprovePOComposite [1.0] icon, and click the more link.
In this case, the Targets with Down Status window is displayed, showing the
ParallelPOMediatorComposite [2.0] application as the only component with the down
status. Click the ParallelPOMediatorComposite [2.0] link in the Down Target column.
m. When you click the link for the Down Target, the Topology Viewer window is
repositioned to show the icon for the selected target. This is another way you can
navigate around the Topology Viewer window. For example:
Note: That the Targets with Down Status window remains visible, so click the Close
icon in the Targets with Down Status window title bar.
n.
In the Topology Viewer window, move the mouse over the

ParallelPOMediatorComposite [2.0] icon and click the more link in the pop-up callout
box.

Chapter 17 - Page 9
l.
4.
5.
When the Properties for ParallelPOMediatorComposite [2.0] dialog box is displayed,

observe that there is no Metrics tab. If you start the application, the Metric tab becomes
visible.
Optionally, take five minutes more to explore and examine other components displayed in
the Topology window.
Close the Topology Window when you are finished your exploration.

o.
Overview
In this practice you navigate around Oracle Fusion Middleware Control Console to locate
performance information about the WebLogic Server instances, such as the Admin Server and
soa_server1 instances, and their Java Virtual Machine (JVM) performance metrics.
Assumptions
The Oracle WebLogic Server Admin Server and SOA Server instances are running.
Tasks
1.
If required, in a Web browser window, login to Oracle Fusion Middleware Control Console
by using the URL http://localhost:7001/em and providing the user name weblogic and
password welcome1.
View Performance Information for the AdminServer

2. To view the performance information for the AdminServer instance, perform the following
steps:
a. On the Oracle Fusion Middleware Control Console page, expand the WebLogic
Domain > soa_domain tree, and click the AdminServer entry to view the Summary
information about the server in the right frame of the page.
b.
On the AdminServer home page, click WebLogic Server > Performance Summary.

Practice 17-2: Observe WebLogic Server Instance JVM Performance
On the AdminServer > Performance Summary page, wait a minute while the graphs
are updated in real time. For example:

c.
On the AdminServer > Performance Summary page, use the right-hand scroll bar to
view information that may not be visible. For example, scrolling down brings the
General, Servlets and JSPs, EJBs, and Deployments sections into view.

d.
To view the JVM Performance metrics for the AdminServer instance, on the
AdminServer page, click WebLogic Server > JVM Performance.
f.
On the AdminServer > JVM Performance page, wait a few minutes while the Memory
Usage and Non Heap Usage graphs are updated with useful information. For example:

e.
On the AdminServer > JVM Performance page, scroll down the page to examine the
information about Threads executing in the JVM. This information can be useful for
monitoring Thread metrics to help you decide on settings for threading properties.

g.

View the Performance Information for the SOA Server Instance

3. To view the performance information for the SOA server instance, perform the following
steps:
a. On the Oracle Fusion Middleware Control Console page, expand the WebLogic
Domain > soa_domain tree (if needed), and click the soa_server1 entry to view its
Summary information page.
On the soa_server1 > Summary page, scroll down to view information about
application deployments, and optionally click the SOA Composites tab to view
information about the deployed composite applications.

b.
Like the AdminServer you can view the Performance Summary information for the
soa_server1 instance by clicking WebLogic Server > Performance Summary in the
soa_server1 page.
d.
On the soa_server1 > Performance Summary page, you can scroll down and view
information about the server and its deployments. For example:

c.
Optionally, you can also click WebLogic Server > JVM Performance to view the JVM
performance metrics for the soa_server1 instance.

e.
Overview
In this practice you navigate around the Oracle Fusion Middleware Control Console pages to
locate the performance metric information for different layers and components running in an
Oracle SOA Suite instance (for example, components running within the JVM instance for the
soa_server1 instance), such as the SOA Domain, SOA Infrastructure, composite applications,
and service engines.
Assumptions
The Oracle WebLogic Server Admin Server and SOA Server instances are running.
Tasks
1.
If required, in a Web browser window, login to Oracle Fusion Middleware Control Console
by using the URL http://localhost:7001/em and providing the user name weblogic and
password welcome1.
Monitoring the SOA Domain

2. On the Oracle Fusion Middleware Control Console Farm navigation frame, expand the
WebLogic Domain tree (if needed), and click the soa_domain entry.
Note: When you click the soa_domain entry you can see information in the summary page.
There is not much more information that can be obtained about the domain, which is a
named structural component for configuration purposes.
Monitoring the SOA Infrastructure
3. To monitor the SOA Infrastructure performance information, perform the following steps:
a. On the Farm navigation frame, expand the SOA folder and click soa-infa
(soa_server1). On the soa-infra home page, click SOA Infrastructure > Monitoring >
Performance Summary.

Practice 17-3: Explore Metrics for Oracle SOA Suite Components
c.
On the soa-infra > Performance Summary page, wait a minute for the graphs to update
with real-time information.
Note: You can also access the Performance Summary page by right-clicking the soainfra (soa_server1) node in the Farm tree, and selecting the Monitoring > Performance
Summary menu option.
On the soa-infra page, click SOA Infrastructure > Monitoring > Request Processing.

b.
On the soa-infra page > Request Processing page, you can view information about
request statistics and processing times for various SOA Service Engines, Service
Infrastructure, and Binding Components. For example:
Monitoring Composite Application Performance Information

4. To monitor performance of a composite application, for example the ApprovePOComposite
[1.0] application, perform the following steps:
a. On the Farm navigation frame, expand the SOA > soa-infra (soa_server1) > default
tree, and click the ApprovePOComposite [1.0] entry.
b. On the ApprovePOComposite [1.0] home page, click SOA Composite > Monitoring >

d.
On the ApprovePOComposite [1.0] > Performance Summary page, observe the

graphic display information. Because the application is not actively processing request,
there is not much to see.
Note: If you wish, you can click Overlay to add additional layers of metric information
from a large list of items that can be monitored. The choice you make depends on the
nature of the application and what you are trying to monitor.
Monitoring Java EE Application Performance
5. To monitor the performance of a Java EE application, such as the ApprovePO_UI Web
application (or Human Task Form application), perform the following steps:
a. On the Farm navigator frame, expand the Application Deployments section, locate and
click the application of interest, for example ApprovePO_UI to display its home page
with a Summary page of information. For example:

c.
To view the application performance metrics, on the application home page, click
Application Deployment > Performance Summary. For example:
c.
On the ApprovePO_UI > Performance Summary page, you can wait for the graphs to
be updated with information and scroll the page to view other details.

b.
Monitoring the BAM Server

6. To monitor the performance of the Oracle BAM Server, perform the following steps:
a. On the Farm navigator frame, expand the BAM folder, click OracleBamServer
(bam_server1) to display the OracleBamServer home page and summary information.
On the OracleBamServer home page, click BAM Server > Monitoring > Performance
Summary.

Note: You do not see much activity for the ApprovePO_UI application because of
process inactivity at this time. Consider looking at the performance information for the
Enterprise Manager application (the em entry located it in the Application Deployments
> Internal Applications tree).
On the OracleBamServer > Performance Summary page, you can view performance
information, add overlay information to display more performance metrics as required.

b.

Monitoring User Messaging Service Component Performance

7. To monitor the performance of the email driver in the SOA Server instance, perform the
following steps:
a. On the Farm navigation frame, expand the User Messaging Service folder and click the
usermessagingdriver-email(soa_server1) entry to display the usermessagingdriveremail home page.
c.
On the usermessagingdriver-email > Performance Summary page, in the graphs, you

can view and add overlay metric information that you wish to monitor.

b.
Note: If you have installed other user messaging drivers you can monitor them in a
similar way.
On the usermessagingdriver-email home page, click User Messaging Email Driver >
To view the usermessagingserver performance information, click the

usermessagingserver entry in the User Messaging Service folder in the Farm
navigation frame, and on the usermessagingserver home page, click User Messaging
Service > Performance Summary.

d.
On the usermessagingserver > Performance Summary page, you can view email
throughput and other messaging service throughput if those drivers have been installed
and are active. For example: The following page displays information about the email
performance:

e.

Monitoring Service Engine Performance

8. To monitor the performance of a SOA Service Engine, for example the BPEL Service
Engine, on the Farm navigation frame, expand the SOA folder (if needed), right-click the
soa-infra (soa_server1) entry, and click Service Engines > BPEL.
Monitoring the B2B Information

9. To view information about the B2B component, on the Farm navigation frame, right-click the
soa-infra (soa_server1) entry under the SOA folder, and click Bindings > B2B.

Note: the same steps can be done for any of the Service Engines options available in the
Service Engine menu. The performance information for each Service Engine, such as the
BPEL Engine (Service Engine) page example above, is visible in the Statistics tab page for
the Service Engine.
Chapter 18
Chapter 18 - Page 1
Chapter 18 - Page 2
Practices Overview
The practices of this lesson involve deploying and executing composite applications that fail due
to some problems. Your task is to diagnose the causes of the problems and fix them. For
example your tasks include:
Deploying a troublesome composite application
Diagnosing the cause of faults with the troublesome composite application
Determining the cause of faults with a Human Workflow scenario
General Notes
This is the practice for lesson titled Troubleshooting Oracle SOA Suite. While the practice
instructions for this lesson and their corrective actions are documented in a sequential manner,
consider trying to diagnose and take corrective action by yourself before reading the possible
solutions and corrective actions documented.

Chapter 18 - Page 3
Overview
In this practice you deploy the TroubleSomeComposite application using its supplied SOA
archive file. You login to Oracle Fusion Middleware Control Console and examine the
components that are part of the deployed application.
The application accepts a new product name and quantity in the input (request) data and inserts
the new product into the EXTERNAL_STORE database table. The input data can be sent through
the SOAP binding or the JCA binding provided by a File Adapter. The application uses the
DbAdapter to insert the new product into the database table.
Assumptions
The run-time server configuration for the DbAdapter connection factory eis/DB/soademo has
been configured to use the JDBC jdbc/soademo data source, which has also been
configured. If not, please perform steps for configuration of the database adapter as described
in Practice 6.
Tasks
1.
To deploy the TroubleSomeComposite application, perform the following steps:

deploy the TroubleSomeComposite application by executing the following commands:
D:\> cd D:\labs\lesson18\TroubleSomeComposite\deploy
D:\> deploy sca_TroubleSomeComposite_rev1.0.jar
b.
c.
Minimize the Command Prompt window.

Chapter 18 - Page 4
Practice 18-1: Deploy a Troublesome Composite Application
3.
In a Web browser window, access the Oracle Fusion Middleware Control Console with the
URL http://localhost:7001/em, and use the Username weblogic and Password welcome1
to login to the application.
To examine the deployed application components, perform the following steps:
a. On the Farm navigation frame, expand SOA > soa-infra (soa_server1) > default and
click the TroubleSomeComposite [1.0] entry.
b.
On the TroubleSomeComposite [1.0]> Dashboard tab page, use the information

available to examine the composite components and answer the following questions:
1) What are the names and types of composite service entry points?
Answer: There are two entry points as identified by the Services value in the
Usage column in the Services and References section:
NewProdFileService, whose type is a JCA Adapter.
InsProdMediator_ep, whose type is a Web Service indicating it provides a
SOAP interface.
Note: From the Dashboard there is no way to tell, other than the component
names, the type of JCA Adapter for the newProdFileService entry point. You would
have to click the component name link to view the Service component details. For
example:
2) What are the names and types of composite components?

Answer: There is only one composite application component called
InsProdMediator, which is a Mediator component. The Mediator component routes
the input message to the service reference, most likely with an XML transformation
to convert the input data into the form needed by the target of the Mediator routing
rule.
3) What are the names and types of references?

Chapter 18 - Page 5
2.
Note: The DbAdapter references (or service entry points) are listed as Custom
Adapter types in the component page. If you click the Properties tab page, the
types and names of the properties give more insight into the type of adapter being
used.
4) What are the configuration implications associated with the JCA Adapter types of
service entry points and references used?
Answer: The implications are that the associated JCA Adapter types require some
type of configuration to enable the application to work. For example:
File Adapters, for example, require properties for the file name pattern, the
folder where the files being processed are located, among other settings.
Database Adapters, for example, require run-time JDBC URL and an
associated connection factory to be defined. There is presently no way to find
out from the Web Administration interfaces the JDBC resource names and the
connection factory JNDI names that have been used by the application.
Unless you run the application and encounter errors, or you try and locate the
deployed applications .jca (adapter configuration) file, you require the JNDI
name information to be provided by the developer in addition to the physical
database resources that those JNDI names need to be mapped to.
Hint: If required, the following image of the deployed TroubleSome [1.0] application
Dashboard, can be used as a guide for the above questions:

Chapter 18 - Page 6
Answer: There is only one service reference, called InsProdDBAdapter, which is a

JCA Adapter type of component. If you click the InsProdDBAdapter link in the
Name column you can almost confirm that it is a DbAdapter type of JCA Adapter
implementation. For example:

Chapter 18 - Page 7
Note: The Recent Instances and Recent Faults and Rejected Messages sections
have been collapsed in the sample image.
Overview
In this practice you first initiate a test of the TroubleSomeComposite application by using its
SOAP binding. If you encounter problems you are required to take corrective action to diagnose
and fix the problem.
Next you initiate a couple of tests of the TroubleSomeComposite application by using the File
Adapter interface. Again, if problems arise, you are required to take corrective action.
Assumptions
You have deployed the TroubleSomeComposite application.
Tasks
In the tasks you first test the SOAP interface, take corrective action for problems, then test the
File Adapter interface again, and take corrective action if there are remaining problems. The
goal is to have a working application for all its input sources.
Test the SOAP Application Interface
1. To initiate the TroubleSomeComposite application using the SOAP interface, perform the
following steps:
a. On the TroubleSomeComposite [1.0] page, click Test.
b. On the TroubleSomeComposite [1.0] > Test Web Services page, scroll down to the
Input Arguments section in the Request tab, after entering the following field values
and click Test Web Service.
Product ID: IPAD03
Quantity: 5
c.
What was the result of this test? What type of response did you receive (if any)?
Answer: A Webservice invocation failed dialog box is displayed indicating that the
application encountered an error of some type. For example:

Chapter 18 - Page 8
Practice 18-2: Initiate and Troubleshoot a Composite Application
Where would you start looking first to troubleshoot the application?

a. When you examine the fault message what does the error information tell you?
Answer: If you expand the Show Additional Trace Information in the Webservice
invocation failed dialog box you learn that an Exception occurred when binding was
invoked. In particular the error arises from the JCA Binding execute of the Reference
operation insert failed due to: JCA Binding Connection issue. For example:
b.
c.
Note: This error clearly indicates that the problem is with a JCA Adapter service
reference in the application. From early exploration of the application component parts,
this tells you that the InsProdDBAdapter is the source of the problem. In particular
something is problem with the connection.
What else could you examine to find out more information about the source of the
problem?
Answer: If an application instance is created (depending on the style of application
interaction [synchronous versus asynchronous] and common property settings that
store all composite instance information), the application instance Dashboard and
Faults tab pages provide some additional information about faults. In the absence of an
application instance and flow trace page, you can view error information in soa_server1
diagnostic log files. If the soa_server1 diagnostic log does not provide enough
information, you may have to change the log settings to a higher number to report
more diagnostic information and test the application again to capture more fault
information.
However, for this example there is enough information in the additional trace
information, presented in the Webservice invocation failed dialog box, about the
source of the problem.
What are the possible problems with a database connection issue?
Answer: Possible scenarios include:
1) Incorrect connection factory name used by the application.
2) Connection factory has not been configured in the run-time server.
3) Incorrect or no mapping between the connection factory and the associated JDBC
resource that identifies the target physical database resources.

Chapter 18 - Page 9
2.
The possible solutions to this problem are:

1) Logging into the Oracle WebLogic Server 11g Administration Console to create the
new connection factory with the JNDI name eis/DB/demo, and also setting the
connection factory properties to reference the correct JDBC data source (if that has
been created). If the JDBC data source has not been created, you have to create
that as well. And finally, you need to redeploy and restart the DbAdapter after
modifying the configuration with the new resources. This action could affect other
applications that are executing.
Note: Depending on the application design, with this corrective action there is a
potential to take recovery actions for the fault in the existing application instance.
2) You can redeploy the application with a new configuration plan that replaces the
incorrect connection factory location resource name with an existing connection

d.
4) Incorrect database credential (or credential mapping) information configured with

the JDBC resource associated to the connection factory.
Note: If desired, you can discuss the possible corrective action for these scenarios with
your instructor.
In this case, what is the real cause of the problem and what are the possible corrective
actions?
Answer: In the expanded Show Additional Trace Information in the Webservice
invocation failed dialog box, you can find the information that indicates there is a
Resource Adapter problem with the <connection factory> elements location attribute
value. In this case, the location attribute value is eis/DB/demo, which is the JNDI
resource name the application is using for creating its database connection. For
example:
Note: In this configuration plan file, the <search> element contains the value
eis/DB/demo (the missing connection factory resource) and the <replace>
element provides the appropriate replacement value of eis/DB/soademo (the
name of an existing connection factory resource.) By using this configuration plan
you can redeploy the application and enable the application to successfully create
a database connection to insert the new data.
3) Close the Web browser window or tab page with the XML information for the
D:\labs\xml\troubleshoot\TroubleSomeComposite_cfgplan.xml file.
4) Using Windows Explorer, copy the TroubleSomeComposite_cfgplan.xml file
from the D:\labs\xml\troubleshoot folder to the
D:\labs\lesson18\TroubleSomeComposite\deploy folder.
5) Maximize the Command Prompt window used to deploy the
TroubleSomeComposite application, or open a new window as required, and
execute the following commands:
D:\> cd D:\labs\lesson18\TroubleSomeComposite\deploy
D:\> deploy sca_TroubleSomeComposite_rev1.0.jar
TroubleSomeComposite_cfgplan.xml
Note: Ensure you enter the commands on one line and that the configuration plan
is the second parameter in the deploy command line. Alternatively, use the Web
interface to undeploy the TroubleSomeComposite and redeploy with the
configuration plan.
You may not need to execute the cd command if you maximized the Command
Prompt window previously used to deploy the same application
6) Ensure the redeployment is successful, and close the Command Prompt window.
For example:

e.
factory resource name, if appropriate for that application. This action only affects
the application.
In this case, the quickest corrective action is to redeploy the TroubleSomeComposite
application with an appropriate configuration plan. To redeploy the
TroubleSomeComposite application with an appropriate configuration plan, perform
1) In Windows Explorer, navigate to the D:\labs\xml\troubleshoot folder, and
double-click the file called TroubleSomeComposite_cfgplan.xml to view its
contents.
2) In the Internet Explorer window or tab page created to display the XML file, scroll to
the end of the page to find the opening wsdlAndSchema element. For example:
Repeat the SOAP interface test to verify that you have corrected one of the application
problems, by performing the following steps:
a. On the TroubleSomeComposite [1.0] page, click Test.
Note: If required, log in to Oracle Fusion Middleware Control Console with the
weblogic user name again. If you did not need to log in again, then you may also
wish to refresh the TroubleSomeComponent [1.0] Dashboard page to ensure that the
previous faulted instance is now in the Stale state. This is an indication that you have
redeployed the application and the Stale instance cannot be recovered.
b. On the TroubleSomeComposite [1.0] > Test Web Services page, scroll down to the
Input Arguments section in the Request tab, after entering the following field values
and click Test Web Service.
Product ID: IPAD03
Quantity: 5
c.
What was the result of this test? What type of response did you receive (if any)?

3.
e.
Use the Flow Trace to verify that all components in the application flow completed
successfully.
Open a Run SQL Command Line window, and perform the following steps to verify
that the data has been inserted to the EXTERNAL_STORE database table.
1) On the Windows task bar, click Start > Programs > Oracle Database 10g Express
Edition > Run SQL Command Line.
2) In the Run SQL Command Line window, connect to the SOADEMO schema using
the following command
Connected.
3) In the Run SQL Command Line window, execute the following SQL statement to
view the new data row:
SQL> SELECT * FROM external_store WHERE prod_id like 'IPAD%';
Note: The following query result should be returned:
SQL> SELECT * FROM external_store WHERE prod_id like 'IPAD%';
PROD_ID
QUANTITY
-------------------- ---------IPAD03
5
For example:
f.
Test the File Adapter Interface

In this section, you test the File Adapter interface by copying a supplied XML file to provide input
for the application and process after the File Adapter consumes the file.
Note: There are two problems that you get to experience and solve with this File Adapter
scenario.
4. To test the File Adapter interface as input for new product data, perform the following steps:
a. Using Windows Explorer, copy the file prod_ipad01.xml from the
D:\labs\xml\troubleshoot folder to the D:\labs\lesson18 folder.
b. Wait a maximum of one minute for the file to be consumed, that is removed from the
c.
Does the prod_ipad01.xml file get removed from the D:\labs\lesson18 folder?

d.
c.
d.
On the TroubleSomeComposite [1.0] > NewProdFileService (File Adapter) page, click

the Properties tab.
On the TroubleSomeComposite [1.0] > NewProdFileService (File Adapter) >
Properties tab page, what information is missing?
Answer: The prd_dir property that is used to specify the folder for input files has not
been provided. Therefore, the File Adapter does not know which folder to poll for new
input files. For example:

5.
Answer: No the prod_ipad01.xml file does not get removed from the
D:\labs\lesson18 folder. You task is to diagnose the cause of the problem.
d. Where do you start looking first here? Is an instance created for the application? Is any
fault reported?
Answer: In this case, there no application instance is created and therefore no fault
information is available either in Oracle Fusion Middleware Control Console or in log
files.
To troubleshoot the errors with the File Adapter interface perform the following steps:
a. On the Oracle Fusion Middleware Control Console Web page, click the
TroubleSomeComposite [1.0] application in the Farm navigation frame.
b. On the TroubleSomeComposite [1.0] application Dashboard tab page, scroll down to
the Services and References section and click the NewProdFileService JCA Adapter
Service link.
6.
To fix the problem, perform the following steps:

1) On the TroubleSomeComposite [1.0] > Service Home page, for the
NewProdFileService (File Adapter) in the Properties tab page, enter the value
D:\labs\lesson18 in the prd_dir property and click Apply. For example:
2) In the Confirmation dialog box, with the Save Properties prompt, click Yes.
3) In the Information dialog box, with the message Properties have been saved
successfully, click OK.
To verify that your corrective action is successful, perform the following steps:

e.
b.
Return to Windows Explorer, and verify that the prod_ipad01.xml file no longer
exists, that is it has been consumed (removed from the folder) by the application for
processing.
Return to the Web browser window with the TroubleSomeComposite [1.0] >
NewProdFileService (File Adapter) > Properties tab page, and click the
TroubleSomeComposite [1.0] link at the top of the page.
c.
On the TroubleSomeComposite [1.0] > Dashboard tab page, verify that a third new
(top-most) instance ID has been created and shows the Completed value in the State
column. For example:
d.
On the TroubleSomeComposite [1.0] > Dashboard tab page, click the Instance ID for
the new instance and verify that the NewProdFileService JCA Adapter appears as the
first row in the Trace table on the Flow Trace page. For example:

a.
f.
Maximize the Run SQL Command Line window, and press the UP arrow key to recall
the SELECT * FROM external_store WHERE prod_id LIKE 'IPAD%' SQL
statement, and press Enter. For example:
Note: A row with the IPAD01 value in the PROD_ID column, and value 10 in the
QUANTITY column should be displayed in the query results.
Final File Adapter Test

7. To be sure that the application still reads processing input files through the File Adapter
interface, perform the following steps:
a. To make the diagnosis part of this fault easier, set Audit Level to Development for the
TroubleSomeComposite [1.0] application, by performing the following steps:
1) In the Web browser window with the Oracle Fusion Middleware control Console,
click the TroubleSomeComposite [1.0] to in the Farm navigation frame to display
the Dashboard tab paged of the composite application.
2) On the TroubleSomeComposite [1.0] home page, select Settings > Composite
Audit Level: Inherit > Development.

e.
c.
d.
e.
Does the prod_ipad02.xml file get removed from the D:\labs\lesson18 folder?
Answer: Yes the prod_ipad02.xml file is removed from the D:\labs\lesson18
folder.
Return to the Web browser window with the Oracle Fusion Middleware control Console
and click the TroubleSomeComposite [1.0] entry in the Farm navigation frame to
display the Dashboard tab paged of the composite application.
Note: If required, click the Refresh icon in the top-right section of the page.
On the TroubleSomeComposite [1.0] > Dashboard tab page, what is the State of the
latest (top-most entry) instance?
Answer: The latest instance has a Faulted State.

b.
3) In the Confirmation dialog box, click Yes.

Using Windows Explorer, copy the file prod_ipad02.xml from the
Note: Wait a maximum of one minute for the file to be removed from the
8.
What do you think is the cause of the fault condition this time? The File Adapter or
something else?
Answer: This time the File Adapter is not the cause of the fault. The problem lies
somewhere else. You need to examine the application Flow Trace to diagnose and
determine source of the problem.
To troubleshoot the application fault condition, perform the following steps:
a. On the TroubleSomeComposite [1.0] > Dashboard tab page, click the instance ID link
for the faulted instance to display the Flow Trace page.
b.
On the Flow Trace page, which component or components have a Faulted status?
Answer: All the components are marked with a Faulted status.

f.
c.
d.
In the Error Message window, you can see that the DdAdapter attempted to insert a
NULL into the PROD_ID column. Because the PROD_ID column is the primary key for
the target database table (EXTERNAL_STORE), a NULL value is not allowed.
Note: Click anywhere outside the Error Message window to close it.
How did a NULL value get into the data being inserted to the database table?
Answer: The source of the problem is not the DbAdapter, which just faithfully inserts
the data that is supplied to it from the component that invokes the DbAdapter service.
Therefore, you have to track back up the Flow Trace to the component row that
appears before the InsProdDbAdapter entry. In this case, you have to examine the
InsProdMediator component Audit Trail for an answer.
On the Flow Trace page, click the insProdMediator component link?

Note: In this case, the entire composite application was executed. The actual fault is at
the end of the flow. In this case, the InsProdDbAdapter failed. Because that fault was
not handled it was propagated to the InsProdMediator component that returned the
fault to the NewProdFileService.
In the Faults section, if you click the Error Messages starting with the text BINDING.
JCA-12563 Exception occurred when binding was invoked, then you can find out the
reason for the fault. For example: Clicking the error message displays more detail in a
pop-up window:
In the Instance Details of InsProdMediator page, expand the <payload> entry just
before the error condition that appears in the Audit Trail tab.
e.
Note: The <payload> contents reveal that the DbAdapter did indeed get empty data
values sent to it. Empty XML elements are interpreted as a database NULL value by
the DbAdapter. Taking a closer look at the processing task that owns that payload you
can see the information appears just after the Transformation step. Therefore,
something happened during the transformation to cause the input data to be converted
to empty XML elements.

To confirm that the InsProdMediator did in fact receive some data values, expand the
<payload> entry before the audit trail entry with the text beginning with
Transformed message part ExternalStoreCollection using. For example:
f.
g.
h.
From the results visible in the Audit Trail tab page, you can see that the process did
read the correct data, however, the transformation fails to populate the correct data
values needed by the DbAdapter component.
While there is NO obvious error with the transformation, what is the real cause of the
problem here?
Answer: Since the XML Transformation processing is a task that converts data from
one format to another, the implications are that there must be something wrong with
the input data.
As an administrator, what technique you use to validate data processed in a composite
application?

b.
On the TroubleSomeComposite [1.0] > Instances page, select the most recent (top
most entry) and click Abort.
c.
In the Confirmation dialog box, with the message Are you sure that you want to abort
1 composite instance(s)? click Abort.
Note: The abort action causes the Processing: Abort Instance > Abort in Progress
window to display. For example:
Note: The Processing: Abort Instance > Abort in Progress is automatically closed
when the operation is finished.

9.
Answer: As an administration, you can only enable validation of request and response
data payload structures, but not the actual data values unless the XML Schema that
defines the payload structures specifies additional data constraints. However, the XML
Schema language has limits with what can be done to validate data values.
Before you change the validation settings for the composite application and initiate a new
test instance, you can abort the latest faulted composite instance by performing the
following steps:
a. On the TroubleSomeComposite [1.0] page, click the Instances tab.
On the TroubleSomeComposite [1.0] > Instances page, close the Confirmation

message box at the top of the page.
e.
On the TroubleSomeComposite [1.0] > Instances page, in the list of instances table,
confirm that the state of the aborted instance is Terminated. For example:
10. To turn on data validation for the composite application such that you can confirm your
expectation that there is an XML data input problem, perform the following steps:
a. On the TroubleSomeComposite [1.0] page, click Settings > Payload Validation:
Inherit > Enable. For example:
b.
c.

On the TroubleSomeComposite [1.0] page, close the Confirmation message at the top
of the page.

d.
c.
On the TroubleSomeComposite [1.0] Dashboard page, do you see another Faulted

Instance?
Answer: No, a new faulted instance is not created. In fact, a new instance is not
created for the processing of the XML input file, because you have turned on XML
payload validation. When a payload validation failure occurs at a service entry point,
the Oracle SOA Server does not create a new composite application instance.
However, an error message appears at the top of the Recent Faults and Rejected
Messages section. For example:

11. To test if there is a payload (data) validation problem, perform the following steps:
a. In Windows Explorer, as before, copy the file prod_ipad02.xml from the
Note: Wait for the file to be removed from the folder to indicate that processing has
started.
b. On the TroubleSomeComposite [1.0] page, click the Dashboard tab, and then click the
Refresh icon at the top-right section of the page. For example:
On the TroubleSomeComposite [1.0] Dashboard page, click the link for the most
recently added Error Message (see previous step) to display the Error Message
information. When the Error Message pop-up window is displayed, click Show
Payload.
e.
In the Native payload of rejected message dialog box, examining the data shows the
XML payload consumed by the process. For example:
Note: While this example shows the source of the error being highlighted XML
namespace (http://www.example.org/ns/products), you cannot make this decision
without looking at the XML Schema that defines the input payload information and its
required XML namespace.

d.
b.
c.
In the Service Endpoint and WSDL dialog box, click the WSDL URL link.
Note: Clicking the WDSL URL causes a new Web browser window or tab page to open
with the XML structure of the endpoint WSDL document.
On the Web browser window or page displaying the WSDL information, you can scroll
down to locate the first <schema> element and compare the namespace attribute
value (http://www.example.org/ns/product) in the <import> element to the
value observed in the Native payload of rejected message dialog box.

f.
In the Native payload of rejected message dialog box, click OK to close the dialog.
12. To find the correct XML namespace that should be used (or XML element structure if it
were the problem) you must find the XML Schema associated with the composite entry
point and definition. In this case, the InsProdMediator_ep (SOAP entry point) in fact shares
the same XML Schema as the File Adapter interface. To determine the XML namespace
required to be used for input data perform the following steps:
a. On the TroubleSomeComposite [1.0] page, click the Show WSDL and endpoint URI
icon (next to the Settings button). For example:
13. To correct the source of the problem (the XML namespace in the input data), perform the
following steps:
a. In Windows Explorer, navigate to the D:\labs\xml\troubleshoot folder and make
a copy of the prod_ipad02.xml file.
b.
c.
d.
In Windows Explorer, rename the copy of the prod_ipad02.xml file to

prod_ipad02_copy.xml.
In Windows Explorer, to edit the XML namespace information in the new copy of the
file, right-click the prod_ipad02_copy.xml file and select Edit. For example:
In the Notepad window, delete the trailing letter s from the end of the
xmlns:prd="http://www.example.org/ns/products" text in the first line of
the file. For example:
Note: The XML namespace should be http://www.example.org/ns/product.

e. In the Notepad window, click File > Save.
f.
In the Notepad window, click File > Exit to close the window.
14. To test if your corrective action produces the correct result, that is a new composite
application that processes the data file and stores the information in the EXTERNAL_STORE
table, perform the following steps:

d.
e.
Note: This final piece of the puzzle clearly identifies the XML namespace in the input
file (prod_ipad02.xml) containing the source of the error.
Close the Web browser window that contains the WDSL information.
To close the Service Endpoint and WSDL dialog box, click OK.
b.
c.
d.
Using Windows Explorer, move the prod_ipad02_copy.xml file from the

Note: Wait a maximum of one minute for the prod_ipad02_copy.xml file to be
removed from the D:\labs\lesson18 folder.
Return to the Web browser window with the Oracle Fusion Middleware control Console
and click the TroubleSomeComposite [1.0] entry in the Farm navigation frame to
display the Dashboard tab paged of the composite application.
Note: If required, click the Refresh icon in the top-right section of the page.
On the TroubleSomeComposite [1.0] > Dashboard tab page, verify that a new most
recent (top-most) instance was created and that its State value is Completed. For
example:
As the final check for completeness, maximize the Run SQL Command Line window,
and press the UP arrow key to execute the SQL following query again:
SELECT * FROM external_store WHERE prod_id LIKE 'IPAD%'
Note: The query result should include the row with the PROD_ID value IPAD02 and
the QUANTITY column with the value 10. For example:
e.

a.
Overview
In this practice you initiate a deployed composite application containing a Human Task that
implements order approval processing. You use the email notification message links to act on
the task and troubleshoot any problems with the process.
Assumptions
The ApprovePOComposite [1.0] and its associated Task Flow UI application must have been
deployed. These applications are deployed in the Practices for Lesson 11.
Tasks
1.

a. In a Windows Explorer application window, copy the D:\labs\xml\po-file\pogibson-only.xml file to the D:\labs\lesson11 folder.
b.
c.
d.
Note: Using the D:\labs\lesson11 folder is necessary to start the

ApprovePOComposite [1.0] application.
Wait for the po-gibson-only.xml file to disappear from the D:\labs\lesson11
folder.
Go to Web browser window with Oracle Fusion Middleware Control Console, and click
the ApprovePOComposite [1.0] entry in the Farm navigation tree.
Note: Log in to Oracle Fusion Middleware Control Console, if required.
On the ApprovePOComposite [1.0] > Dashboard tab page, confirm that there is a new
instance with the Running State in the Recent Instances section. For example:
Note: You may need to click the Refresh icon in the top-right corner of the page to
update the page. For example:
Human Task Hierarchical Approval

Reminder: The ApprovePOComposite application requires two levels of approval. However, we
have a user error to deal with in this example.

Practice 18-3: Troubleshoot Human Task Interaction
3.
To receive email notifications double-click the Mozilla Thunderbird desktop icon to open
Mozilla Thunderbird.
To approve the order using the task actions in the email notification message for the task
assignee jcooper, perform the following steps:
a. On the Mozilla Thunderbird window, to view the email notification message for
jcooper, select the jcooper@soa11g.example.com account in Inbox tree of the
Smart Folders frame. For example:
b.
Note: You may have to click Get Mail in the Thunderbird toolbar to receive the email
notification message.
In the Mozilla Thunderbird Message Pane, after receiving the email message, click the
most recent email message entry (the last or bottom entry in the list) to view the body
of the message. For example:

2.
5.
In the Mozilla Thunderbird window, in message body, click the Approve link in the
Actions of the email body. For example:
d.
On the Email reply window, click Send.
Note: You can see the Approve response in the body of the reply, and the sender
email address in the From field has not been changed.
Return to the ApprovePOComposite [1.0] > Dashboard page, and click the Refresh icon.
What do you observe in the ApprovePOComposite [1.0] > Dashboard page? Is the
composite instance still executing? If yes, then why?

4.
c.
b.
On the Flow Trace page, you can see that no faults have been reported. However, you
can observe that both the ApprovePOBPEL and ApprovePOHumanTask components
are still in the Running state. Click the ApprovePOHumanTask link.
c.
On the Instance Detail Of ApprovePOHumanTask page, what do you observe?

Answer: The Human Task is still waiting for the action from the task assignee
jcooper, because the information in this page indicates that jcooper is still the
current assignee.

Answer: To determine why the application is still executing, perform the following steps:
a. On the ApprovePOComposite [1.0] > Dashboard page, click the instance ID of the
Running instance to open and examine the Flow Trace page.
b.
On the Human Workflow Engine (Service Engine) page, click the Notification
Management tab.

6.
d. Close the Flow Trace page.

What happened to jcoopers email approval response message?
Answer: To determine what happened with the email action response message, you can
a. On the Farm navigation frame, right-click soa-infa (soa_server1) and select Service
Engines > Human Workflow.
On the Human Workflow Engine (Service Engine) > Notification Management tab
page, you can find the incoming email message at the end of the Incoming
Notifications list. In the last entry, the message Status is Response Not Processed.
Click the Response Not Processed status link.
d.
Finally, here is the reason why the process has not received the task action. The
Status Description dialog box indicates that the Actionable Email/IM has been
responded from a different account.
Note: The source of the error in this case, is a human error. This could be a common
problem when a user has multiple client email accounts and responds with the
incorrect email account for a task action. In this case, jcooper (who was assigned the
task) responded with the weblogic email account. The Human Task workflow system
does not accept the response from a user other than the one it was assigned to, in this
example. Therefore, in such situations you may need to monitor the incoming email
messages in the Human Workflow Engine (Service Engine) page.
e. On the Status Description dialog box, click OK to close the dialog.
Note: Depending on how the Human Task was configured by the developer of the
composite application, an error email message may be sent to an administrative user or
another account.

c.
7.
Note: The information in the message body provide the same explanation as you have
observed through the Human Workflow Engine (Service Engine) page when you
clicked the Response Not Processed status link for the incoming message.
You can ignore the two unread email messages relating to Completed Stock Update
Event for , which were generated by applications from earlier practice sessions.
To take corrective action in this case, as an administrator you can call or notify jcooper that
they did not action the response with the correct email account. In this case, you act as
jcooper and perform the following steps to complete the correct approval process:
a. On the Mozilla Thunderbird window, click the jcooper account in the Smart Folders
frame, and select the new Action Required: Approve Order email notification
message. In the message body, click the Approve link.

In this case, the fault where the action response message was not accepted by the Human
Workflow processing system generated an email that is sent to the weblogic email account.
To view the email error notification message, perform the following steps:
1) Return to the Mozilla Thunderbird application window, and click the
weblogic@soa11g.example.com account in the Smart Folders frame.
2) In the list of message for the weblogic account, click the message with the Subject
Auto: Action Required: Approve Order to view the message body. For example:
8.
On the Write: Action Required:Approve Order email response window, change the
From field to the James Cooper <jcooper@soa11g.example.com>" email
account and click Send.
Return the Oracle Fusion Middleware Control, and click the ApprovePOComposite [1.0]
entry in the Farm navigation panel. Perform the following steps to monitor the application
progress:
a. On the ApprovePOComposite [1.] > Dashboard page, what is the State of the
application now?
Note: If needed click the Refresh icon on the page.
Answer: The application is still in a Running state. However, the response from
jcooper should have been received. The reason why the process has not completed
yet is explained later.
b. To check if the email action message has been received and processed, on the
ApprovePOComposite [1.0] > Dashboard page, click the instance ID link for the
Running composite instance. For example:

b.
On the Flow Trace page, click the ApprovePOHumanTask component link.
d.
On the Instance Detail Of ApprovePOHumanTask page, you can verify that jcoopers
action response was received. However, since this Human Task assignment and
routing policy is based on a management chain of approval, the task has been routed
to the user jstein (jcoopers manager). Therefore, the process is running smoothly
again.

c.
b.
In the message list for the jstein account, a new message with the Subject titled
Routed:Approve Order appears. Click the new message with the Subject titled
Routed:Approve Order.

9.
e. Close the Flow Trace window.

To complete the Human Task processing, perform the following steps:
a. In the Mozilla Thunderbird window, select the jstein account in the Smart Folders
frame, and click Get Mail.
d.
In the message body for the new message titled Routed:Approve Order, click the
Approve link. For example:
In the Write: Routed:Approve Order window, change the From field to the John
Steinbeck <jstein@soa11g.example.com> email account, and click Send.
e.
In the Web browser window, return to the ApprovePOComposite [1.0] > Dashboard
page, and click the Refresh icon.
f.
On the ApprovePOComposite [1.0] > Dashboard page, verify that the top-most
instance has the Completed value in the State column.

c.
In Windows Explorer, you can view the output results for the approved order in the
order_approval.log file added (or appended to) in the D:\labs\lesson11
folder.

g.
Chapter 19
Chapter 19 - Page 1
Chapter 19 - Page 2
Practices Overview
There are no practices for this lesson titled Configuring High Availability for Oracle SOA Suite.
General Notes
There are no notes.

Chapter 19 - Page 3
Chapter 19 - Page 4
Chapter 20
Chapter 20 - Page 1
Chapter 20 - Page 2
Practices Overview
There are no practices for this lesson titled Backing Up and Recovery of Oracle SOA Suite
Instances.
General Notes
There are no notes.

Chapter 20 - Page 3
Chapter 20 - Page 4

D64648GC10 Ag

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

D64648GC10 Ag

Uploaded by

Copyright:

Available Formats

These eKit materials are to be used ONLY by you for the express purpose SELF STUDY.

SHARING THE FILE IS STRICTLY PROHIBITED.

Oracle University and (Oracle Corporation) use only.

Oracle SOA Suite 11g:

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Oracle University and (Oracle Corporation) use only.

Practices for Lesson 1 .....................................................................................................................................1-1

Oracle SOA Suite 11g: Administration Table of Contents

Oracle University and (Oracle Corporation) use only.

Practices for Lesson 10 ...................................................................................................................................10-1

Oracle SOA Suite 11g: Administration Table of Contents

Oracle University and (Oracle Corporation) use only.

Practices for Lesson 9 .....................................................................................................................................9-1

Practices for Lesson 19 ...................................................................................................................................19-1

Oracle University and (Oracle Corporation) use only.

Practice 18-1: Deploy a Troublesome Composite Application .......................................................................18-4

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Oracle SOA Suite 11g: Administration Table of Contents

Oracle University and (Oracle Corporation) use only.

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Practices for Lesson 1

Oracle University and (Oracle Corporation) use only.

Practices for Lesson 1

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Practices for Lesson 1

Oracle University and (Oracle Corporation) use only.

Oracle University and (Oracle Corporation) use only.

Practices for Lesson 1

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Practices for Lesson 1

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Practices for Lesson 1

Oracle University and (Oracle Corporation) use only.

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Practices for Lesson 2

Oracle University and (Oracle Corporation) use only.

Practices for Lesson 2

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Practices for Lesson 2

Oracle University and (Oracle Corporation) use only.

Oracle University and (Oracle Corporation) use only.

Practices for Lesson 2

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Practices for Lesson 2

How would you describe what Service-Oriented Architecture means?

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Practices for Lesson 2

Oracle University and (Oracle Corporation) use only.

Practice 2-1: Review Service-Oriented Architecture Concepts

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Practices for Lesson 2

Oracle University and (Oracle Corporation) use only.

Practice 2-2: Review Oracle Fusion Middleware and SOA Suite

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Practices for Lesson 2

Oracle University and (Oracle Corporation) use only.

Practice 2-3: Review of Administrator Task and Tools

A simple description of Service-Oriented Architecture is: SOA is a paradigm (a way of

JMS services may need JMS resources to be defined and configured.

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Practices for Lesson 2

Oracle University and (Oracle Corporation) use only.

Solutions 2-1: Review Service-Oriented Architecture Concepts