Introduction
Digital Sales Platform uses certain files to provide system-specific properties and ontology-based customization of the application. These files are maintained under the ‘Administration’ → ‘Content Management’ → ‘conf’. The ‘conf’ folder is required by the system and should NOT be deleted.
Maintenance
By using a text editor such as notepad++) and upload the file again into the ‘conf’ folder. The following file types are stored within the folder:
- *.properties: the general property files for Digital Sales Platform (e.g. application.properties)
- *.n3: location mapper files to find the right.owl files.
- *.owl: the ontology files located in /conf/ontology folder
Important files are listed in the following table:
|
Field Name |
Description |
|---|---|
|
application.properties |
This is the main properties file which contains the base properties for starting up Digital Sales Platform tenant. |
|
email-content.properties |
This properties file provides the keys to customize the content of notification emails such as approval and routing emails. |
|
location-mapping.n3 and location-mapping-to-empty.n3 |
These two files are used to find the exact path of the ontology (.OWL) files in the conf folder.
location-mapping.n3 is used in the load customizing and location-mapping-to-empty.n3 is used in the general start of the tenant application.
In the earlier release, the ontology files are being used to supply certain master data elements and loaded into database. The mapping was kept in location-mapping.n3 file.
However, on system start as this uploaded data will be supplied by database it is needed that the files carrying the real data not be loaded into memory as well. This can happen as files have imports to base files. To separate this data ontology files with only import information were created and to find their path the location-mapping-to-empty.n3 file is used.
Note that there is no need to supply the data from ontology files anymore.
location-mapping.n3 file is a key mapper to map file’s unique identification (URI) with relative location of it. |
|
schema.owl |
Schema.owl is the main file having all the entity definition and their relationship. It contains all Classes (Business Types, BT), Data Attributes (Business Data Attribute, BDA) and Relation Attributes (Business Relation Attributes, BRA) definition. It also contains the meta attributes (Business Meta Attributes, BMA) that are used in relation with BDA and BRA.
Additional ontology concept can also be defined in application-schema-ext.owl to further customize the product based on customer's need, such as legacy BDAs, SPARQLs, and custom data points. |
*NOTE: changes to these files with faulty code lines can cause the application not to start. For specific requirements, consult with your Customer Success Manager and/or your implementation team.