Difference between revisions of "Fusion Security Manager Configure"
(Created page with "Category:FSM_Install Fusion Security Manager (FSM) contains two Configuration files which are in the dist/properties folder. These are in .json format but can easily be ed...") |
m (Vmurrell moved page FSM Configure to Fusion Security Manager Configure: looks better) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
Fusion Security Manager (FSM) contains two Configuration files which are in the dist/properties folder. These are in .json format but can easily be edited using a simple tool such as notepad as long as you use the correct json syntax. | Fusion Security Manager (FSM) contains two Configuration files which are in the dist/properties folder. These are in .json format but can easily be edited using a simple tool such as notepad as long as you use the correct json syntax. | ||
| − | [[File: | + | [[File:FSM Config Files.png|800px]]<br> |
=== siteconfig.json === | === siteconfig.json === | ||
| Line 19: | Line 19: | ||
The browser_lang_[locale].json file contains a map of property name to human readable label, for example: | The browser_lang_[locale].json file contains a map of property name to human readable label, for example: | ||
| − | + | "menu.security.structure.read" : "Structure Read", | |
| − | The Language configuration file is used to decode labels on the User Interface. Any metadata (Dataflows, Concepts, Codes) used by | + | The Language configuration file is used to decode labels on the User Interface. Any metadata (Dataflows, Concepts, Codes) used by FSM come from the web service, requested in the selected locale - as such the language configuration file does not play a role in decoding values in the retrieved metadata. |
Latest revision as of 03:57, 15 September 2023
Fusion Security Manager (FSM) contains two Configuration files which are in the dist/properties folder. These are in .json format but can easily be edited using a simple tool such as notepad as long as you use the correct json syntax.
siteconfig.json
Defines where the API will find the connected Fusion Registry and defines which Locales are supported and generates a language picker in the User interface. For example:
{
"ServicesAPI" : "http://localhost:8063/FusionRegistry/ws/fusion/info/product",
"Locales" : ["en"]
}
Adding additional locales Add the appropriate code as show below
"Locales" : ["en", "he", "ru"]
browser_lang_en.json
The browser_lang_[locale].json file contains a map of property name to human readable label, for example:
"menu.security.structure.read" : "Structure Read",
The Language configuration file is used to decode labels on the User Interface. Any metadata (Dataflows, Concepts, Codes) used by FSM come from the web service, requested in the selected locale - as such the language configuration file does not play a role in decoding values in the retrieved metadata.
