General property and ontology files
- 11 Jun 2024
- 1 Minute to read
- Print
- DarkLight
General property and ontology files
- Updated on 11 Jun 2024
- 1 Minute to read
- Print
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
Zilliant CPQ uses specific files to store and maintain application system properties and ontology-based customization of the application.
Access properties and ontology files
- From the application left navigation area, select Administration.
- From the top navigation bar, select Content Management .
- Select conf.
Important
The conf folder is required by the system. Do not delete it.
- Download the properties file you want to configure.
- Use a text editor to make and save changes.
- Upload the file.
The conf folder contains the following types of files:
- .properties—General property files for Zilliant CPQ. For example, application.properties.
- .n3—Mapping files to find the .owl files.
- .owl—Ontology files located in /conf/ontology folder.
Note
For more information, consult with your Zilliant representative or your implementation team.
Files in the conf folder
- application.properties—The main properties file. It contains the properties for starting up a Zilliant CPQ tenant.
- email-content.properties—Provides keys to customize the content of notification emails such as approval and routing emails.
- location-mapping.n3 and location-mapping-to-empty.n3—Use to find the exact path to the ontology .owl files.
- location-mapping.n3—A key mapper to map file’s unique identification (URI) to its location.
- location-mapping-to-empty.n3—Use when starting a tenant application.
- schema.owl—Entities definition and their relationship.
- Contains Classes (Business Types, BT), Data Attributes (Business Data Attribute, BDA) and Relation Attributes (Business Relation Attributes, BRA) definitions.
- Contains meta attributes (Business Meta Attributes, BMA) that are used together with BDA and BRA.
Additional ontology concepts can be defined in application-schema-ext.owl to further customize the product based on customer needs. (Examples: legacy BDAs, SPARQLs, custom data points.)
Was this article helpful?