| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:ContentDescription 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" xmi:id="-7skHLaUfQVh3R2DzJN4YGw" |
| name="decision_service,_M0nWsAsYEdyPCr4G1Tb79A" guid="-7skHLaUfQVh3R2DzJN4YGw" |
| authors="Jerome Boyer" changeDate="2008-09-03T15:49:37.994-0700"> |
| <mainDescription><a id="XE_decision_service" name="XE_decision_service"></a> 
 |
| <p>
 |
| <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-weight: bold">A software component that encapsulates
 |
| run-time rule processing elements. The component instances provide a "ready to run" business rule application. A
 |
| decision service offers a business interface with methods used by a business application leveraging or not a BPM
 |
| product. The implementation of the interface is calling a business rule engine.</span>
 |
| </p>
 |
| <p>
 |
| <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-weight: bold">A decision service component is mostly
 |
| stateless and simplifies the process of integrating business rules with popular application platforms such as JSE, JEE,
 |
| and a Web service.</span> In the context of a BRMS application it is also named rule service.
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
