Technical Design

BPM 11g Samples

Last Updated:9-Jan-13Version:1.0Status:DRAFT

Copyright 2013 Oracle Corporation All Rights Reserved

Document Control

Change Record

DateAuthorVersionChange Reference

05-Jan-13Anirban Dey1.0First draft for internal access to the samples

Contents1.Document Control21.1Change Record22.Environment Requirements53.Installation and Configuration63.1Deploying the BPM and Task Form Projects64.Samples Overview75.Running the Samples11IntroductionOracle BPM11g includes a certain Intermediate Events of catch type that can be attached to the boundary of an activity (Task or sub process) and can listen to internal as well as external triggers. These events are referred to as Boundary Events. When the Boundary Event is triggered, the process execution flows through the outgoing path, also referred to as exception flow. The boundary Event is active and listening to the trigger only as long as the activity to which it is attached is active.The Boundary Event can be of two typesinterrupting and non-interrupting. The non-interrupting Boundary Events have a dashed border to distinguish them from interrupting Boundary Events. In the interrupting case, the process execution proceeding on the normal sequence flow is interrupted and instead proceeds on the exception path. In other words, the normal execution flow and the exception flow are mutually exclusive.The Timer Boundary Event is used to handle timeout exceptions. They can be used to catch service invocation timeouts in the case of system steps or catch Human Task related events such as deadline violation in the case of human steps. When attached to the boundary of the sub process, they can be used to interrupt process execution if the time taken to execute the sub process exceeds beyond a certain time limit. In the interrupting Timer Boundary Event, the process execution along the normal sequence flow is interrupted and the execution continues on the exception flow path.This document describes an initial (small) set of samples provided to illustrate use of those Timer Boundary Events. The samples can be deployed and run on an 11.1.1.7 environment.

Environment RequirementsThe samples require JDeveloper version 11.1.1.7 with the SOA Composite Editor and BPM Studio extensions installed. A standalone server with BPM Suite 11.1.1.7 and a domain configured with BPM Suite is required for deployment and running the samples.There are no external configuration requirements (e.g. database connections).The BPM project is configured with swimlane role Employee mapped to the user jcooper, and swim lane role Manager mapped to the user jstein.

Installation and ConfigurationThe samples are provided as a zipped JDeveloper application. The application can be unzipped into any location where the path name does not include spaces. To open the application, use the Application Open menu and locate the file: TimerEventSamples.jws. The application contains TimerEventSamples BPM project that includes processes and human tasks and timer events.

Deploying the BPM and Task Form ProjectsFrom the Application Navigator deploy the BPM and the Task Form Projects. Samples OverviewA simple BPM process is provided to illustrate features and usage of the BPM11g Timer Boundary Events.

The process starts with a Timer Start Event Schedule Process. The Timer Start Event is used to trigger the process instances based on some schedule. It can be a fixed timestamp or a regularly occurring event or a combination of both. For example, a process can be scheduled to occur at the end of the month, at New Year, or bi-weekly, or every hour, every 10 minutes etc. Configuring the Timer Start Event :-Right-clicks on Timer Start Event Schedule Process and choose Properties. This brings up the Properties wizard. Go to the Implementation tab.- To schedule the process instance to kick off every 10 minutes choose the Time Cycle option and enter 0 Months 0 Days 0:10:0 to represent a 10 minute interval.

There are two boundary timer event attached to the human task Create Order. These boundary timer events are of two types:-Non-Interrupting Boundary Event (see the dashed border boundary event on the human task create order) which allows to continue the process flow and only sends an escalation/notification to the next level i.e. to the swim lane role Manager if the task Create Order doesnt get completed as per the time cycle of 5 minute.-Configuration of the Non-Interrupting Boundary Event: From the BPM component pallet, select a Timer Catch event:

Drag-and-drop the Timer event from the Catch Events section on to the Create Order step in the TimerEventSamples model. Enter timeout for Name. Right-click and select Properties to bring up the Properties editor. Do not click on the Interrupting Event Checkbox. Select the Time Cycle option. Type in 5 minutes for the time cycle.

Right-click on the Non Interrupting Boundary Timer Event and select Add Default Sequence flow option and connect it with the Escalation FYI Task.

Interrupting Boundary Event, which interrupts the normal process flow of Create Order in case it is not completed by 10 minute and instead the execution takes the alternate path of Create Order by Supervisor. Configuring the Interrupting Boundary Event: Drag-and-drop the Timer event from the Catch Events section on to the Create Order step in the TimerEventSamples model. Right-click and select Properties to bring up the Properties editor. Click on the Interrupting Event Checkbox. Select the Time Cycle option. Type in 10 minutes for the time cycle.

Right-click on the Interrupting Boundary Timer Event and select Add Default Sequence flow option and connect it with the human task step Create Order by Supervisor.

Running the SamplesInside BPM Workspace, log in as swim lane role Employee, user id jcooper.Click on the task. The system launches a Task UI. Fill the details of the order. Click on the submit button.Inside the BPM workspace, login after 10 minutes as swim lane role Manager, user id jstein.The user jstein should be able to see the task submitted by employee for approval and clearance.Click on the approve button.

Oracle Confidential. For authorized use only. Do not distribute to third partiesPage 6 of 11