Composition of required logical roles

Location path

Path in the build directory

/era_env/priv/sys_metadata/<SOLUTION>/roles.json (where SOLUTION: master or era)

Overview

Defines the composition of system logical roles required/expected on each site for the installed build to function.

Used when checking system operation correctness. When a site serves a domain that requires a certain microservice while it is actually absent in the configuration, an error is recorded.

Not available for the master domain (the predefined master domain type).

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

  • "optional" – list of roles without which operation is possible. May be omitted. Recommended for tracking data currency in the file. The appearance of new logical roles may make the data outdated. From the field content the administrator can get a hint: the role is not needed, or was missed.

Example

Example for a call center build:
{
  "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"
  ]
}