Fusion Middleware 12c – Embracing the power of Maven by Roger Goossens

 

clip_image002I recently started to build a small project in JDeveloper 12c to learn how to make use of Custom Activities in an Adaptive Case Management project. The results of this  project will be posted in my next blog. When I started the project, I wanted to do it the Maven way (since JDeveloper 12c has built-in Maven support).

Being able to deploy a case as a Maven artefact requires a little initial setup. The bulk of the initial setup can also be found in a blogpost referenced in this Whiteblog from colleague Dirk Janssen. I decided that the complete setup justified a blogpost on its own. So in this post I’ll demonstrate how to deploy the (skeleton of the) case application via Maven. In the next blogpost I’ll enhance the case application with custom case activities.

Creating the application

First things first, let’s create a new BPM application CustomActivitiesDemo and add a project called CaseWithCustomActivities to the application. Choose Composite With Case Management as the project type. After you’ve created the project, you get 2 POM files for free. One aggregate POM file for the application and the POM file for the case project. Per default the groupId equals the application name (CustomActivitiesDemo). I don’t like that, so let’s change the groupId into something more structural, like nl.whitehorses.acm.

If you take a look at the generated project POM file you’ll see that it has a reference to a parent pom com.oracle.soa:sar-common. As you can see in the picture below, the curly lines indicate that the parent POM can’t be found right now. So let’s fix that, by adding the necessary artefacts to our Maven repository. Read the complete article here.

SOA & BPM Partner Community

For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn image[7][2][2][2] Facebook clip_image002[8][4][2][2][2] Wiki

Adaptive Case Management – Exposing the API – part 2 by Roger Goossens

In the previous blogpost we’ve built a custom java API on top of the ACM api. In this blogpost we’ll make a service of this API exposing its public methods and test it against a small test case.

TestCase somposite
TestCase
The TestCase for this blogpost is also available on GitHub. It’s a small composite containing a simple case called TestCase.
Milestones
We’ve got 2 milestones in the case, one called caseStarted, which is set after the case has started, and the other is called testUserEventFired signalling that the user event testUserEvent has been fired.
Stakeholders
The only stakeholder for the case is called CustomStakeholder of which the user weblogic is a member.
User Events
We’ve defined a user event called testUserEvent. This is the event we’ll be firing via our exposed API later on.
Organization
The CustomStakeHolder Role has been added to the project with the weblogic user as its member.
Business Rules
The TestCase contains 2 business rules for setting milestones. Read the complete article here.

SOA & BPM Partner Community

For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn image[7][2][2][2] Facebook clip_image002[8][4][2][2][2] Wiki