Tuesday, January 21, 2014

Install the new User Interface for Oracle Case Management

For all Oracle BPM & Case Management users a new User Interface is available (see SOA Community Blog). Below I describe briefly how to install it on a BPM environment.

To access the software please login to support.oracle.com and search for the following Patches:
  • Patch 17014142: SOA BUNDLE PATCH
  • Patch 17767877: CASE UI IN WORKSPACE

1) Read the README-files carefully and perform the following steps for both patches:

2) Set the ORACLE_HOME environment variable to SOA Home, eg:
export ORACLE_HOME=/u01/app/oracle/middleware/Oracle_SOA1/
Validate the result with => echo $ORACLE_HOME

3) Add the appropriate OPatch to the system path, eg::
export PATH=$PATH:/u01/app/oracle/middleware/Oracle_SOA1/OPatch
Validate the result with => which opatch

4) Run OPatch to apply the patch
opatch apply

Repeat the steps for the oracle_common-Home. Patch 17767877 needs to be applied on the Jdeveloper ORACLE_HOME as well.


Additionally make sure that you installed:
  • Patch 14526899
  • Patch 14791221

These two patches can be installed via Smart Update Utility. Start the tool under [MW_HOME]/utils/bsu, copy the extracted patches into [MW_HOME]/utils/bsu/cache_dir and apply the patches.

If you performed all steps successfully, you should now be able to access your case instances from BPM workspace. Have fun with it!

Friday, January 10, 2014

BPM & Integration Days 2014

Vom 24. bis 25. Februar 2014 präsentiert das Business Technology Magazin in München das große Trainingsevent für BPM & Integration.

Lernen Sie in 18 Sessions und sechs Workshops tiefgehendes Know-how für die tägliche Arbeit und für strategische Entscheidungen in Ihrem Unternehmen. Die BPM & Integration Days konzentrieren sich diesmal besonders auf die praktischen Synergien von BPM mit Systemintegration, Mobile, BI und Cloud, gepaart mit Erkenntnissen aus vielen Jahren Projekterfahrung aller Referenten. Insgesamt erwarten Sie:
  • 18 Sessions und sechs intensive Workshops mit klarem Praxisbezug. 
  • Interessante Keynote und Speaker Panel am ersten Tag. 
  • Erstklassige Speaker & Experten vor Ort erleben. 
  • Eine ideale Plattform für Erfahrungsaustausch & Networking. 
  • All-inclusive-Verpflegung mit Erfrischungen und Snacks in den Pausen, leckeres Mittagsbuffet. 
  • Come Together am Montagabend für bestes Networking - mit Freibier und Snacks. 
  • Sie erhalten alle Materialien und Codebeispiele sämtlicher Workshops und Sessions in elektronischer Form zum bequemen Download. 
  • Sie erhalten ein persönliches Entwickler-Akademie-Zertifikat, das Ihnen Ihre erfolgreiche Teilnahme bescheinigt. 
  • Gratis-Magazine, kostenloser Internetzugang, hochwertige Laptoptasche u.v.m.

Am ersten Tag freuen wir uns auf ein spannendes Programm mit drei parallelen Tracks zu "Modellierung und Ausführung", "Auswertung und Semantik", "Integration".

Am zweiten Tag werden die wichtigsten Schwerpunktthemen in vier Halbtagesworkshops und in einem ganztägigen Workshop intensiv vertieft. 

Ich freue mich als Sprecher der folgenden Sessions wieder mit dabei sein zu dürfen: 

Ein Anlass den Sie auf keinen Fall verpassen sollten! Weitere Infos finden Sie auf www.bpm-integration-days.de.

Tuesday, December 10, 2013

Create a custom Case Activity in Oracle BPM Case Management

In one of my previous posts I highlighted the new case management functionalites in Oracle BPM Suite. Case management enables you to define the different activities - a user can perform to achieve a goal - without defining the workflow process. For more details about ACM I recommend to download our "Adaptive Case Management in Practice" poster and to read the following articles:

A case is always associated with activities which are performed as part of a particular case. Among milestones, data, events, stakeholders and documents the activities are a key element in Oracle BPM 11g Case Management. In the current release you can create case activities based on a BPM process, or a Human Task, or you can create a custom case activity based on a Java class. In this post I will explain the steps to create a custom case activity.

Create a Custom Case Activity

1. Create a new "BPM Application"
2. Create a new "BPM Project"
3. Create a "Composite with Case Management" component

The above steps will result in a composite with the case and its exposed service and case rules. Now you can open the case definition and define your milestones, stakeholders, permissions, data, user events and so on. See the step-by-step "Hello World" example for more details. The Custom Activity Java class must implement the oracle.bpm.casemgmt.caseactivity.ICaseActivityCallback interface. The callback class must be part of the composite (as explained below), or must add it to the workflow customization classpath.

4. Import the oracle.bpm.casemgmt.interface.jar from

5. Import the bpm-services.jar from

6. Select File => New => Java Class and create the CustomCaseActivity Java class.

7. Organize imports and add your custom logic in the "initiate" operation.

package com.cattlecrew.acm.caseactivities;

import java.util.Map;

import oracle.bpm.casemgmt.CaseIdentifier;
import oracle.bpm.casemgmt.caseactivity.ICaseActivityCallback;
import oracle.bpel.services.bpm.common.IBPMContext;

public class CustomCaseActivity implements ICaseActivityCallback {
    public CustomCaseActivity() {

    public String initiate(IBPMContext iBPMContext,
                           CaseIdentifier caseIdentifier, String string,
                           Map<String, Object> map) {
        // Add activity logic here
        return "Called class CustomCaseActivity for activity => " + string;

8. Create the case activity based on the Java class. See chapter 31 of the Oracle Fusion Middleware Modeling and Implementation Guide for Oracle Business Process Management for more details about config options and guidelines.

9. Define your Business Rules.

10. Deploy and test the Case composite. 

Friday, November 15, 2013

New SOA material available on OTN

Listen to our 3-part podcast about "the state of SOA" and read our 13-part article series "Industrial SOA" on OTN

Today I'd like to highlight some SOA material that has recently been published.

1) Podcast Show Notes: Old Habits Die Hard in the New SOA World

During Oracle OpenWorld 2013 in San Francisco Bob Rhubart from the OTN Architect Community invited Lonneke Dikmans, Ronald van Luttikhuizen, Hajo Normann, Torsten Winterberg, Guido Schmutz and me to participate in an informal roundtable discussion of what's happening in Service Oriented Architecture today. I really enjoyed it! You can download the conversation directly from OTN ArchBeat.  

As you'll hear, the conversation ranged from the maturity of Service Oriented Architecture technology and tools, to the the lingering and typically self-imposed problems that can prevent organizations from realizing the full potential of SOA, to what SOA means in the era of *aaS, mobile computing, and big data.  

After the recording we discussed our ACM poster
[Hajo Normann, Torsten Winterberg, me and Lonneke Dikmans (L-R)]

2) Article Series "Industrial SOA" - 9 from 13 articles already published

In the last months already 9 from 13 "Industrial SOA" articles have been published on OTN and the Service Technology Magazine. The articles are covering topics like Service Categories, SOA Security, SOA and User Interfaces, Mobile Solutions and many more. The next upcoming article will be about SOA and Events. 

Download them and share your comments e.g. via twitter by using the hashtag #industrialsoa.

Tuesday, November 5, 2013

Configure Auto-Recovery in Oracle SOA Suite

Oracle SOA Suite 11g has some great features to recover faulted instances automatically. When a BPEL process flow errors out, it is retried with all its invocations. This is undesirable in some cases. For example if re-calling a composite results in duplicated data, data have been changed before the recovery is planned to be executed or you do not want to create too many composite instances in order to save the space in your SOAINFRA-schema. See below the different places where automatic recoveries are configured / disabled.

1) Change RecurringScheduleConfig (see also the screenshot below) 
  • Right-click soa-infra (SOA_cluster_name) 
  • Choose SOA Administration > BPEL Properties 
  • Click "More BPEL Configuration Properties" 
  • Click "Recovery Config" 
  • Change values for RecurringScheduleConfig 
    • maxMessageRaiseSize = 0 
    • startWindowTime = 00:00 
    • stopWindowTime = 00:00 
  • Click Apply 

2) Change StartupScheduleConfig (see also the screenshot below)
  • Right-click soa-infra (SOA_cluster_name)
  • Choose SOA Administration > BPEL Properties
  • Click "More BPEL Configuration Properties"
  • Click "Recovery Config"
  • Change values forStartupScheduleConfig
    • maxMessageRaiseSize = 0
    • startupRecoveryDuration = 0
    • subsequentTriggerDelay = 0
  • Click Apply

3) Change GlobalTxMaxRetry
The property GlobalTxMaxRetry specifies how many retries are performed if an error is identified as a retriable one. For example, after several web service invocations, if dehydration fails due to a data source error, then this is identified as a retriable error and all activities from the prior dehydration state are retried. If the activities being retried are not idempotent (that is, their state can change with each retry and is not guaranteed to give the same behavior), then multiple retries can be problematic.

You can set GlobalTxMaxRetry to 0 in the Systems MBean Browser.
  • Right-click soa-infra (SOA_cluster_name)
  • Choose SOA Administration > Common Properties
  • Click "More SOA Infra Advanced Configuration Properties"
  • Click "GlobalTxMaxRetry"
  • In the Value field, enter an appropriate value
  • Click Apply

Additional Information

Wednesday, October 9, 2013

Poster: Adaptive Case Management (ACM) in Practice

Knowledge-driven processes are typically unpredictable in their execution. Experts working on them decide what’s the next best action to take. This is in contrast to traditional BPM, in which all possible paths of a process are predetermined and modeled into the process. Case management is a way to control and implement these unstructured processes. With the poster below we'd like to bring some of the key aspects of Adaptive Case Management (ACM) on one page.

Feel free to download the PDF-version if you are interested in (login required):
  • What is ACM?
  • Why should I use ACM?
  • How can ACM user interfaces look like?
  • What are the main building blocks of an ACM solution?
  • How to visualize ACM cases with CMMN 1.0? 

Send your feedback with #acmposter:

Jürgen Kress
Fusion Middleware Partner Adoption
Oracle EMEA
Berthold Maier
Enterprise Architect
T-Systems International GmbH
Hajo Normann
Danilo Schmiedel
Solution Architect
Guido Schmutz
Technology Manager
Bernd Trops
Principal Solution Architect
Talend GmbH
Clemens Utschig-Utschig
Chief Architect Global Business Services
Boehringer Ingelheim Pharma GmbH & Co. KG
Torsten Winterberg
Business Development & Innovation

Wednesday, August 21, 2013

Remove data in Oracle MDS

The two main database schemas in the Oracle SOA Suite database repository are: <PREFIX>_SOAINFRA and <PREFIX>_MDS. Composite instance and runtime information are stored in the SOAINFRA schema. Commonly used metadata like WSDLs, XSDs, rules, fault policies, etc. as well as composite deployments are stored within the MDS schema. 

With every deployment / import of the metadata artifacts a new document version will be created in the MDS. This means that re-importing an updated WSDL-file into the MDS does not delete the previous version of the document. Furthermore we sometimes need to remove unnecessary and unwanted files from the repository. If this is not considered you might end in problems like below:

ORA-01654: unable to extend index DEV_MDS.MDS_PATHS_U2 by 128 in tablespace DEV_MDS
ORA-06512: at "DEV_MDS.MDS_INTERNAL_COMMON", line 865
ORA-06512: at "DEV_MDS.MDS_INTERNAL_COMMON", line 1021
ORA-06512: at "DEV_MDS.MDS_INTERNAL_COMMON", line 1121
ORA-06512: at "DEV_MDS.MDS_INTERNAL_COMMON", line 1216
ORA-06512: at "DEV_MDS.MDS_INTERNAL_COMMON", line 1872
ORA-06512: at line 1


In order to avoid production problems because of a full MDS tablespace you should clean up the schema from time to time. This post explains the options that Oracle SOA Suite provides to remove contents from MDS.

OPTION 1: Remove directories and files from MDS using WLST

1) Start WLST from SOA_HOME/common/bin/wlst.sh.

[oracle@soabpm-vm ~]$ cd /oracle/fmwhome/Oracle_SOA1/common/bin 
[oracle@soabpm-vm bin]$ ./wlst.sh 

2) Execute the following command: sca_removeSharedData('http://<soahost>:<soaport>', 'directory', 'user', 'password')

Example (delete folder 'interfaces' and all its subdirectories and files):

wls:/offline> sca_removeSharedData(‘http://localhost:8001’, ‘interfaces’, ‘weblogic’, ‘welcome1’)


Note: With the command above you can just remove directories and files which are stored under "apps".

OPTION 2: Remove directories and files from MDS using ANT

Oracle provides some ANT scripts which can be used to integrate the "remove" command into your central build & deploy proccess. Just search for the "removeSharedData" command in ant-sca-deploy.xml. On the server this file is located under SOA_HOME/bin. You can also find the file in your JDeveloper install folder under MIDDLEWARE_HOME/jdeveloper/bin.

1) Execute the command: ant -f ant-sca-deploy.xml removeSharedData -DserverURL=server.url -DfolderName=folder.name -Drealm=realm -Duser=user -Dpassword=password -DfailOnError=true/false

Example (delete folder 'interfaces' and all its subdirectories and files):
ant -f ant-sca-deploy.xml removeSharedData -DserverURL=http://localhost:8001 -DfolderName=interfaces"

Note: With the command above you can just remove directories and files which are stored under "apps". See the Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite for a detailed description of the parameters.

OPTION 3: Remove files from MDS using WLST

1) Start WLST from SOA_HOME/common/bin/wlst.sh


[oracle@soabpm-vm ~]$ cd /oracle/fmwhome/Oracle_SOA1/common/bin
[oracle@soabpm-vm bin]$ ./wlst.sh


2) Connect to the SOA server: connect('user', 'password', 't3://<soahost>:<soaport>')


wls:/offline> connect('weblogic', 'welcome1', 't3://localhost:8001') 

3) Execute the command: deleteMetadata(application=’application-name', server=’soaserver-name’, docs=’absolutePath’)

Example (delete all files in '/apps/interfaces' as well as the files in its subdirectories): 
wls:/...> deleteMetadata(application='soa-infra',server='soa_server1',docs='/apps/interfaces/**') 

Note: With the command above all files in directory 'apps/interfaces' will be deleted. Please note the double asterisk (**) at the end of the this parameter. The asterisk (*) represents all documents under the current directory. The double asterisk (**) represents all documents under the current directory and also recursively includes all documents in subdirectories. Furthermore see the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference for a detailed description of the valid arguments.

OPTION 4: Remove files from MDS using MBean Browser

You can call the command "deleteMetadata" also from the Enterprise Manager / MBean Browser.

1) Login to EM (http://host:port/em)
2) Expand SOA
3) Right-click on soa-infra
4) Select Administration -> MDS Configuration
5) Click Runtime MBean Browser
6) Click Operations tab
7) Click deleteMetadata operation
8) Provide parameters:
      docs - list of entries to remove (fully qualified path, eg: /apps/interfaces/**)
      restrictCustTo - default
      excludeAllCust - false
      excludeBaseDocs - false
      excludeExtendedMetadata - false
      cancelOnException - true
9) Click Invoke

Note: See the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference for a detailed description of the parameters.

OPTION 5: Purge Metadata Version History using Fusion Middleware Control

For database-based MDS, you can purge the metadata version history using the Fusion Middleware Control (Enterprise Manager). This operation purges the version history of unlabeled documents from the application's repository partition. The tip version (the latest version) is not purged, even if it is unlabeled.

1) Login to EM (http://host:port/em)
2) Expand SOA
3) Right-click on soa-infra
4) Select Administration -> MDS Configuration
5) Scroll to the “Purge” section: enter a value in the Purge all unlabeled past versions older than field and click on the Purge button
6) In the Confirmation dialog box, click Close

Note: For more details see the Oracle Fusion Middleware Administrators Guide. Section also explains how to purge metadata version history using WLST.

How to view the MDS content

After you removed files and/or directories from the MDS you might want to have a look at the actual content. The easiest way to do this is to create a MDS connection in JDeveloper. For more details see the Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite section " Create a SOA-MDS Connection".

Some additional information about the MDS