Oracle Policy Modeling projects contain the following types of files:
| File type | File extension | Description | Location in Development folder |
|---|---|---|---|
| Project | .xprj | The master project file records the file and folder structure of the project. | \ |
| Microsoft Word | .doc | Microsoft Word files contain rules. | \Rules |
| Microsoft Excel | .xls | Microsoft Excel files contain rules. XLS files are also used for translation mappings. | \Rules or \Translations |
| Generated rule format | .xgen |
An XGEN file contains the generated rule format for a rule document. These XGEN files are used to build rulebase files for use with the Oracle Determinations Engine. Each time a Word or Excel rule file is compiled, the XGEN file corresponding to that file is overwritten with a new one containing the updated set of rules. Each translation document also has an associated XGEN file. XGEN files are in XML format. |
\Rules or \Translations |
| Screens | .xint | Screens files contain screen definitions. | \Interviews |
| Properties | .xsrc |
Properties files contain attribute, entity and relationship properties. |
\Properties |
| External data model | .xsrc | Source files contain data models compiled from an external application such as Siebel. | \ |
| Visualization | .dml | Visualization files contain visualizations of the rules in the form of tree diagrams. | \Visualizations |
| Test script | .tsc | Test script files are XML files which contain test cases and the set of outcome attributes that will be used by the test cases. | \Test Scripts |
| PDF files, such as policy documents, can be included as necessary in the project. | \Documents | ||
| Screens | .exs | The EXS file is an XML file which contains information relating to the screen definition in the rulebase (ie the data about question screens, summary screens, screen orders and screen flows). The EXS file only provides deployment information for Oracle Web Determinations investigations. | \output |
| Language | .stxt | The STXT file is the XML language file which contains information on the presentation form to be used for all attributes. (For boolean attributes, this is the positive, negative, question and uncertain forms.) | \output |
| Flows | .flows | The flows file is an XML file which describes any flows defined for the project. | \output |
| Metadata | .metadata | The metadata file contains any metadata which has been defined about the project or attributes. This is an XML file. (Metadata information about screens or controls is contained in the EXS file.) | \output |
| Rulebase | .xml | The rulebase file is the compiled rulebase file created in Oracle Policy Modeling. It is an xml file describing the rules and is required by the Oracle Determinations Engine. This file contains a definition for all attributes and rules (only basic attribute identifiers are available) and as such is the primary file which acts as an anchor for any other required files. | \output |
| Interface | .xrbd | The XRBD file is the automatically generated interface file that is loaded when you link a module to a project. It is included in the .RMOD file when you build it. | \output |
| Module | .rmod | The RMOD file is a ZIP file of the project that contains the external data model (ie all entities and relationships, and attributes that have public names). This module file allows the rulebase to be shared with other rulebases. | \output |
| Compressed (zipped) folder | .zip |
Building a project in Oracle Policy Modeling will automatically build a <project>.zip file in the output folder. This package of all of the individual output components of a rulebase is the preferred method of deploying rulebases rather than as individual files. Additionally, any files in the include folder will be added to the rulebase zip. See Include extra files in the build. |
\output |