Introduction To Oracle Policy Automation And Key Principles
Upcoming SlideShare
Loading in...5

Introduction To Oracle Policy Automation And Key Principles



Visit for more info

Visit for more info



Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

Introduction To Oracle Policy Automation And Key Principles Introduction To Oracle Policy Automation And Key Principles Presentation Transcript

  • Oracle Policy Automation, well-known as OPA is an innovative yet scalable software product that deploys business rules within enterprise applications. It is exclusively designed to fit well into current enterprise architecture. OPA has been designed to adapt legislationand policy documents into easily executable business rules that focus on calculation of benefit entitlements and payment amounts.
  • There are three technologies that work with OPA, Oracle Web Determinations, Oracle Determinations Server and Oracle Determinations Engine. The best part is that first two options, Oracle Web Determinations and OracleDeterminations Server are supported on a wide variety ofapplication servers like Apache Tomcat, Microsoft IIS, IBMWebSphere AS and WebLogic Server. CRMIT suggests usersto take advantage of some other exciting features, as welllike integrated test case execution, debugging capabilities and the definition of interviews rule based assessments. View slide
  • Apart from the initially released, ORACLE OPA VERSION 10.1.0, users can also try their hands on ORACLE OPA VERSION 10.2 and ORACLE OPA VERSION 10.3. Theseversions have a connector to integrate with Siebel and SAP and also support users to make custom function that can be used-in while writing rules, respectively. View slide
  • When dealing with OPA, it is crucial to consider some keyprinciples while designing the policy model for an Oracle Policy Automation project:
  • Policy model design and development fits in with any software development methodology. Oracle PolicyAutomation is well-suited to being used on agile projects, but it works equally well with traditional waterfall methodologies.
  • Roles on an OPA project team typically include rule architect, rule author, technical architect, technical developer, test manager and tester. One person may fillmore than one role, though at minimum the rule authorand tester roles are usually filled by separate individuals.
  • Rule architect creates the design for the policy modelcomponent. The technical architect creates the design for any components outside of the compiled policy model. The test manager creates the test strategy.
  • Physical file structure of the folders, documents etc withinOracle Policy Modeling can be organized independently of the rule content.
  • Keeping intact with these policies can assist you whileworking with OPA projects, before you get into the core of your design. As you begin with the designing part, try to give a simple and descriptive name to your document. If you find a design template you can use, be prepared to add sections from the template and use headings throughout your design document to better assist thereaders. These are some initial steps that can facilitate you in creating effective OPA projects.
  • one-time-offer-software/