10 Decision Management Setup Files
The following diagram shows the main Decision Management metadata and database setup files, as released with Oracle RTD Base Application.
Terminology:
The following terms are used throughout this chapter:-
Core - refers to the basic elements required for all Oracle RTD Decision Management applications
-
Base Marketing (or Ref) - refers to the elements for the RTD for Marketing Optimization application
This chapter contains the following topics:
Note:
The Base Marketing with Slices application is based on the Base Marketing application and contains some additional metadata. For more information on the Base Marketing with Slices application including the additional metadata, see Section 2.3, "Configuring and Deploying Base Marketing with Slices" in the Oracle Real-Time Decisions Base Application Decision Management Installation and Configuration Guide.10.1 Core Metadata Files
The Core metadata files in this section all appear under the directory 22.
This section contains the following topics:
The Core config.xml file contains general configuration settings:
-
workbenchService: the url of the Oracle RTD server running in the same host server as Oracle RTD Decision Management.
-
inlineService: the name of the Core Inline Service (RTD_CLM_Core) that is released with Oracle RTD Base Application.
-
decisionCenter: the base URL to access embedded decision center reports.
-
ownership-mode: special mode, which when switched on, allow users (typically administrators) to take ownership control of choices when choices are edited. Initial value after installation is "off".
-
display-name: the name of the application as it appears on the Decision Manager login page and at the top of the main page.
The Core perspectives.xml file acts as the base file for adding your application perspectives. The Core perspective file contains no specific perspectives.
The Core project.xml file acts as the base file for adding your application projects. It contains the create/edit/view pages for the special choice group Project, and the attributes Name and Description for the Overview page.
The Core security.xml file contains the configuration entries for the three application roles CLMConsumer, CLMAuthor, CLMAdministrator, and the choice group, project, and perspective permissions selected for those application roles. It contains no entries for any enterprise roles nor users.
10.2 Base Marketing (ref) Metadata Files
The Base Marketing (ref) metadata files in this section all appear under the directory clm/Build/metadata.
This section contains the following topics:
The Base Marketing (ref) config.xml file contains general configuration settings. For details, see Section 2.2.2.1 "Config XML File" in the Oracle Real-Time Decisions Base Application Decision Management Installation and Configuration Guide:
The Base Marketing (ref) perspectives.xml file contains the properties for the perspectives released with the RTD for Marketing Optimization application: Campaigns, Tags, Channels, Slot Types, Draft Campaigns, Pending Approval Campaigns, and Approved Campaigns.
The Base Marketing Choice Group xml files
For each of the choice groups defined in the RTD for Marketing Optimization application - Campaign, Offer, Creative, Tag, Channel, Placement, Slot, Slot Type, Project, Segment, Decision - there is a corresponding choice group XML file in the ref directory.
Each choice group XML file contains the properties to define the choice group and its attributes. Other properties control whether the choice group appears in Decision Manager dropdown lists, and whether its attributes appear by default in Decision Manager Advanced Search screens. Type restriction associations are defined for several attributes in the Campaign, Offer, Creative, and Project choice groups.
Each choice group XML file also contains the create/edit/view pages that define the pages that appear when the choice group is created, edited, or viewed in the RTD for Marketing Optimization application.
The Base Marketing Choice Group XML files have been updated to add two new tabs to display Model Reports; that is, the Performance tab and the Analysis tab.
Each choice group XML file also contains tabs that define the pages that appear when the choice group viewed in the RTD for Marketing Optimization application.
The following code sample shows the metadata changes as updated to display tabs and model reports.
<tab id="<id>" type="<type>"> <model-report reportType="<type>"/>
Where type is: choiceHistory, predReport, bestFit, drivers, modelQuality.
To include a tab in a choice group, add the following code to the respective choice group's XML (such as campaign.xml, channel.xml, and so on) in the metadata folder. Each page should have one <page id="" viewType="view/edit/create"> element. For instance, if a tab displays four pages, it should contain four page attributes within the <tab> element; for example:
<tab id="<id>" type="type">
<name>Name</name>
<description>Description</description>
<page id="" viewType="view/edit/create">
<name></name>
<description></description>
<page-attributes-group>
<model-report reportType="<type>"/>
</page-attributes-group>
</page>
</tab>
If <name> and <description> are not defined in tab then id would be used for the display.The Campaign/Offer/Creative/Channel/Slot/Placement/SlotType choice group performance tab has two sub tabs/pages; that is, Dashboard and Model Counts.To include a Performance tab in a choice group, add the following code to the respective choice group's XML (such as campaign.xml, channel.xml and so on) in metadata folder; for example:
<tab id="Performance" type="report">
<name>Performance</name>
<description>Performance</description>
<page id="PerformanceDashboard" viewType="view">
<name>Dashboard</name>
<description>Dashboard</description>
<page-attributes-group>
<bi-dashboard path=""/>
</page-attributes-group>
</page>
<page id="ChoiceHistory" viewType="view">
<name>Model Counts</name>
<description>Model Counts</description>
<page-attributes-group>
<model-report reportType="choiceHistory"/>
</page-attributes-group>
</page>
</tab>
The following <bi-dashboard> metadata allows you to integrate the BI dashboard with in a tab. <path> is the path to the dashboard in the web catalog.
<bi-dashboard path="<path>"> <parameter name="<name>" value="<value>"/> ... </bi-dashboard>
<path> is the path to the dashboard in the web catalog; for instance, path="/shared/Decision Analytics - Base Marketing/<ChoiceGroupName>/_portal/<ChoiceGroupName> Performance Dashboard">.The Campaign/Offer/Creative/Channel/Slot/Placement/Slottype/Tag choice group Analysis tab has four sub-tabs/pages; that is, Predictiveness, Best Fit, Drivers and Model Quality. To include an Analysis tab in a choice group, add the following code to the respective choice group's XML (such as campaign.xml, channel.xml and so on) in metadata folder; for example.
<tab id="Analysis" type="report">
<name>Analysis</name>
<description>Analysis</description>
<page id="PredReport" viewType="view">
<name>Predictiveness</name>
<description>Predictiveness</description>
<page-attributes-group>
<model-report reportType="predReport"/>
</page-attributes-group>
</page>
<page id="BestFit" viewType="view">
<name>Best Fit</name>
<description>Best Fit</description>
<page-attributes-group>
<model-report reportType="bestFit"/>
</page-attributes-group>
</page>
<page id="Drivers" viewType="view">
<name>Drivers</name>
<description>Drivers</description>
<page-attributes-group>
<model-report reportType="drivers"/>
</page-attributes-group>
</page>
<page id="ModelQuality" viewType="view">
<name>Model Quality</name>
<description>Model Quality</description>
<page-attributes-group>
<model-report reportType="modelQuality"/>
</page-attributes-group>
</page>
</tab>
The Base Marketing (ref) project.xml file contains the extra attribute "type", and the pages associated with projects. In addition to the Overview page, which appears during project creation, editing, and viewing, the pages are defined for listing active and deployed projects.
The Base Marketing (ref) relationship-types.xml file describes the relationship types between the choice groups in the RTD for Marketing Optimization application.
For each relationship, the "from" and "to" choice groups are defined as well as the cardinality of the relationship.
In addition, there are properties to control the Delete logic (whether the delete applies just to one of the choice groups, or "cascades" to delete choices of the related choice group), rule propagation, and event propagation.
The Base Marketing (ref) security.xml file contains the configuration entries for the three application roles CLMConsumer, CLMAuthor, CLMAdministrator, and the choice group, project, and perspective permissions selected for those application roles. It contains no entries for any enterprise roles nor users.
ref/sql/insert ils data.sql and ref/sql/insert marketing data.sql
The insert ils data.sql and insert marketing data.sql files contain instructions to load some sample data for the Oracle RTD Decision Management database. These scripts are for demonstrations only.
10.3 Database Files for Core and Base Marketing
The database files for Core and Base Marketing in this section all appear under the directory clm/Database.
This section contains the following topics:
The sql/drop core.sql file contains instructions to drop all the generic metadata for a Oracle RTD Decision Management database - the tables, views, and sequences that provide the infrastructure for Oracle RTD Decision Management application data.
The sql/load core.sql file contains instructions to create and initialize all the generic tables, views, and sequences required for a Oracle RTD Decision Management database. These tables, views, and sequences provide the infrastructure for Oracle RTD Decision Management application data.
The sql/ils/drop core.sql file, as released with Oracle RTD Base Application, contains instructions to drop all the tables and views specific to the individual choice groups defined in the released application RTD for Marketing Optimization.
Note:
After choice groups or choice group attributes are added to, removed from, or have their definition properties altered in any Oracle RTD Decision Management application, and the application is then regenerated, the sql/ils/drop core.sql file is overwritten, and then reflects the new proposed data structure. The file is not automatically run after application regeneration.The sql/ils/load core.sql file, as released with Oracle RTD Base Application, contains instructions to create and initialize all the tables and views that implement the choice groups and the inter-choice group relationships defined in the released application RTD for Marketing Optimization.
Note:
After choice groups or choice group attributes are added to, removed from, or have their definition properties altered in any Oracle RTD Decision Management application, and the application is then regenerated, the sql/ils/load core.sql file is overwritten, and then reflects the new proposed data structure. The file is not automatically run after application regeneration.