PaaS Partner Community

  • October 4, 2014

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

Juergen Kress
PaaS & Middleware Partner Adoption

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
The TestCase for this blogpost is also available on GitHub. It’s a small composite containing a simple case called TestCase.
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.
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.
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

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.