Manage rules and responsibilities
Secure rulebases from unauthorized access and tampering
Oracle Policy Modeling provides tightly integrated source control for projects to support best practice on both individual and team-based projects. The source control functionality provided allows a great deal of flexibility.
Oracle Policy Modeling uses the Microsoft Visual Studio .Net SCCAPI to provide integration with a range of source control technologies.
To use Oracle Policy Modeling with Visual SourceSafe, simply install Visual SourceSafe on your development machine and set Visual SourceSafe as the default source control client for that machine (you do not need to do this if no other source control clients are installed).
To use Oracle Policy Modeling with other source control software, that software must work with the Microsoft .Net SCCAPI. Oracle Policy Modeling has been tested using Source Offsite and Rational ClearCase, but other products using the SCCAPI should also work without any issues.
If you are using an alternative for source control, you must ensure that your source control client is set as the default source control client for your machine.
When a rulebase is deployed to Oracle Web Determinations or Determinations Server, it will either be inside the web application war file, or on a location in the file system that you have designated.
In order to ensure integrity of the application and the rules you should secure access to web application (Web Determinations or Determinations Server), the rulebase if it exists in a separate location. Only system administrators or those with responsibility for updating the deployed web application should have permission to access these files.
It is possible to restrict access to the operations of the Determinations Server through the security implemented on the application server on which the Determinations Server is running.