| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:TaskDescription xmi:version="2.0" |
| xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.5/uma.ecore" |
| xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.0" xmlns:rmc="http://www.ibm.com/rmc" |
| rmc:version="7.5.0" xmi:id="-G84eS7wnll4Jn8DpfP2lSw" |
| name="integrate_bre,_6-p2EH_BEd2YWI_0AZcMOA" guid="-G84eS7wnll4Jn8DpfP2lSw" authors="Jerome Boyer" |
| changeDate="2008-09-25T13:42:29.484-0700"> |
| <mainDescription><p>
 |
| The Rule Engine as an executable class, callable using proprietary API or the JSR94 API. Rule Engine can be an embedded
 |
| component or deployed within a pool as reusable components.
 |
| </p>
 |
| <p>
 |
| When designing a SOA and the different decision services, the architect should focus and apply the same design pattern
 |
| as other business services. The rule engine technology choice is an implementation decision not a service design one.
 |
| The service design has to address:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| the service definition: one or more operations linked to the same data semantic
 |
| </li>
 |
| <li>
 |
| the operation call approach: synchronous/ asynchronous, stateless/stateful, header based or carrying payload, use
 |
| of faults or not
 |
| </li>
 |
| <li>
 |
| the exception reporting
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| The service implementation using a rule engine has to look at:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| the transaction propagation
 |
| </li>
 |
| <li>
 |
| the reference data caching
 |
| </li>
 |
| <li>
 |
| the parsing of input message: the claim data
 |
| </li>
 |
| <li>
 |
| the loading of the related data: the policy related to the claim, or the insured person profile
 |
| </li>
 |
| <li>
 |
| the preparation of the output message: the result and may be some other technical data
 |
| </li>
 |
| </ul></mainDescription> |
| </org.eclipse.epf.uma:TaskDescription> |
