Introduction To Oracle Policy Automation And Key Principles

Posted on

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 legislation and policy documents into easily executable business rules that focus on calculation of benefit entitlements and payment amounts.

THREE TECHNOLOGIES

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 Oracle Determinations Server are supported on a wide variety of application servers like Apache Tomcat, Microsoft IIS, IBM WebSphere AS and WebLogic Server. CRMIT suggests users to take advantage of some other exciting features, as well like integrated test case execution, debugging capabilities and the definition of interviews rule based assessments.

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. These versions 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.

KEY PRINCIPLES

When dealing with OPA, it is crucial to consider some key principles while designing the policy model for an Oracle Policy Automation project:

  • Policy model design and development fits in with any software development methodology. Oracle Policy Automation 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 fill more than one role, though at minimum the rule author and tester roles are usually filled by separate individuals.
  • Rule architect creates the design for the policy model component. 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 within Oracle Policy Modeling can be organized independently of the rule content.
  • Keeping intact with these policies can assist you while working 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 the readers. These are some initial steps that can facilitate you in creating effective OPA projects.