Composition of required logical roles

Location path

Path in the assembly catalog

/era_env/priv/metadata/<SOLUTION>/roles.json

Overview

Defines the composition of logical roles of the system required on the site for the soluton to function.

It is used when checking the correctness of the system operation. An error will be logged when a site is serving a domain whose soluton requires a specific role when the role does not actually exist.

Unavailable for master domain (predefined solenoid) master).

Format:
{
  "allsites": ["mdc", ...],
  "optional": ["logstore", ...]
}
  • "allsites" – A list of roles required at all work sites.

  • "optional" – A list of roles without which the job is possible. Can be omitted. It is recommended to be specified in order to keep track of the relevance of data in the file. Appearance of new logical roles can lead to outdated information. By the content of the field the administrator can get a hint: the role is not needed or has been omitted.

Example

Example for soluschen "pbx":
{
  "allsites": [
    "b2bua",
    "broker",
    "callstore",
    "conf",
    "dms",
    "email",
    "esg",
    "im",
    "ivr",
    "huntq",
    "logstore",
    "mg",
    "mgc",
    "middleware",
    "mixer",
    "msvc",
    "recmover",
    "registrar",
    "reserver",
    "script",
    "selector",
    "sg",
    "statestore",
    "store",
    "usercenter",
    "webserver",
    "wssubscr"
  ],
  "optional": [
    "ap",
    "bgmg",
    "dfsync",
    "domstore",
    "ic",
    "mic",
    "mdc",
    "redirect"
    "rpci",
    "rpco",
    "sdc",
    "voicemail"
  ]
}