This document provides instructions for creating a simple business rule composite in Oracle SOA Suite. The steps include: 1. Creating a new SOA project and empty composite. 2. Dragging a business rule component into the composite, defining input and output messages by importing types from the MDS, and selecting input/output types without copying to the project. 3. Dragging a mediator to the component lane, selecting the business rule component as input and defining mappings to copy data between input/output without copying types to the project. 4. Double clicking on the business rule component to create decision tables with rules and functions to validate input and return output.

1. Business Rules Composite
Cookbook on how to create a simple
Business Rule Composite in Oracle
SOA Suite

2. Create New SOA Project

3. Enter Project Name and Directory

4. Begin with Empty Composite
(or Composite With Business Rule)

5. Drag Business Rule in the
composite.xml, enter Name and
Package and click + Input…

6. Define Input Message by importing
types from MDS

7. Do not ‘Copy to Project’ !
You don’t want to have copies of shared xsd’s (xsd’s used by
multiple composites and/or systems) scattered around in multiple
projects. Only xsd’s which are only used within a composite are
stored within a composite project.

8. Select Input Type

9. Click + Output…

10. Define Output Message by importing
types from MDS

11. Again do not ‘Copy to Project’ !

12. Select Output Type

13. Select tab Advanced to enter a nice
Service Name

14. Finally Select OK

15. Open composite

16. Drag a Mediator to the Components
lane, enter Name and select
Synchronous Interface
Always use a Mediator to expose to the outside world! It offers routing and
mapping flexibility for future changes.

17. Select as Input same type as Business
Rule Engine, so first import types

18. Again do not ‘Copy to Project’ !

19. Select same Input Type

20. Same applies for output type.
Make sure “Create Composite Service
with SOAP Bindings” is checked

21. Press OK

22. Drag the arrow of the Mediator to the
Rule Engine to wire execute method to
callFunctionStateless method

23. Double click on Mediator and click on
button to create a mapping

24. Provide meaningfull name for the new
Mapper file

25. In the mapper on the right side expand
node parameterList, right click on
NOM-details and select Add XSL Node
> copy-of

26. Select “Replace the selected Node
with the results of the copy-of”

27. Drag the NOM-details on the left side
to the copy-of

28. In the mapper on the right click, right-
click on attribute name and select Set
Text > Enter Text…

29. Enter text “NominationRulesService”
(name of the service in the business
rule engine)

30. Save all, close mapper, open mediator
again and create reply mapping

31. Copy in the same way VAL-answer
from resultList to Val-answer target

32. Save all, close mapper and mediator
and open NominationRules by double
click in the composite

33. Select Ruleset1 and Create Decision
Table

34. Click on the table name to enter a
meaningful name

35. Click on <insert condition>

36. Double click on C1 <edit condition>
and select TNOMDetails.status

37. Click on ? below R1 and select INITIAL

38. Click on button Gap Analysis…

39. Select the checkbox to fill the gap

40. Click on tab Functions

41. Click on + to create a function and
enter Name, select void as Return Type
and enter a meaningful Description

42. Click on <insert action> in the Body
part and create the following code:
assert new TVALAnswer( <edit properties> )

43. Click on <edit properties> and select
null and true as constant values

44. The same for new function
validateNOK with null and false as
constant values
Don’t worry, we’re gonna fill the error part later on.

45. Navigate back to DecisionTable
NomStatus in Ruleset1, click on <insert
action> and select Call

46. Double click on ‘A1 call(’ and select
function validateOK

47. Click on + and select Action > Call

48. Select validateNOK for A2, select A1 as
action for R1 and A2 for R2

49. Test this basic setup by deploying the
composite and using soapUI.
Retrieve WSDL url from Test tab in Enterprise Manager.

50. Create new Project in soapUI with
WSDL url

51. Fill request with test data and invoke

52. Nominaton status value ‘initial’ results
to true as nomination response

53. Open NominationRules again and
select the Facts tab

54. Select subtab Java Facts (bottom
screen), press + button, browse and
search for java.util.ArrayList

55. Select! (checkbox) and press OK

56. Select tab Functions and select
validateNOK function to change it

57. Add two arguments of type String with
the + button of the Arguments section
and name them code and message

58. With right click next to statement you
can delete, insert new statements, etc

59. Create code for function validateNOK:

60. Select Ruleset1 and double click on
action A2 to edit argument settings

61. Check Parameterized checkbox for
both arguments and press OK

62. Fill arguments for R2 with code “001”
message “Invalid Nomination”

63. Deploy and assert arguments are
returned in output

64. In decision table create two more rules
and split up R2 into separate values
and enter their arguments for A2
If you, by accident provide arguments, for unused A2 call, you can not delete them! Run
time this doesn’t matter, but you can set them to null value for readability.

65. Deploy and test again

66. Select tab Globals and with + button
create variable MaxNomAmount of
type int, value 10000 and check both
Constant and Final

67. Select tab Bucketsets and with +
button create new bucketset of type
“List of Ranges”

68. Edit this new bucketset by
selecting it and the pencil button
(or double click on bucketset icon)
and first provide a decent name

69. Use the + button to create 0 value
endpoint and again to create Endpoint
of Global value MaxNomAmount.
Uncheck checkbox Included Endpoint,
so MaxNomAmount will be allowed.

70. Press OK to save the bucketset

71. Select Ruleset1 again and add
condition with + button

72. Double click on C2 and select
TNOMDetails.totalAmount

73. Select C2 and assign
NominationAmountBuckets to it

74. Set [0..MaxNomAmount] as value for
R1 with status INITIAL and OK result

75. Enter - , a dash, as value for R2-R4
meaning ‘otherwise’

76. Create two rules for status INITIAL
with < 0 and > MaxNomAmount
buckets, assign validateNOK and
provide decent arguments

77. Deploy and test your end result