Application deployment
How Management Center discovers, configures, and starts product applications from descriptor files.
Management Center discovers product applications from descriptor files when it starts. Each application has its own descriptor and configuration.
Descriptor location
Section titled “Descriptor location”Management Center searches each subdirectory under internal/applications for a file named descriptor.json.
For Windows and Linux installations, the descriptor is located at:
<installation path>/internal/applications/<application>/descriptor.jsonIn the standard container image, the corresponding path is:
/opt/fortified/servers/mgmt-server/internal/applications/<application>/descriptor.jsonThe <application> directory identifies the Management Center product application, such as access or control.
Configure the environment text
Section titled “Configure the environment text”Every Management Center application can show a configurable environment or instance name in the right side of the header, immediately before the status indicator. Use it to distinguish, for example, development, test, production, customer, or server instances.
Add environment_text to the application's config object in descriptor.json:
{ "config": { "environment_text": "Production" }}Keep all other existing properties in the descriptor unchanged. Restart Management Center after changing the descriptor, then reload the browser page.
If environment_text is omitted, is null, is empty, or contains only whitespace, no environment text is displayed. The hostname is not used as a fallback.
Container deployment
Section titled “Container deployment”Persist a customized descriptor by mounting it into the container. Replace <application> with the product application's directory name:
services: management-center: volumes: - ./descriptor.json:/opt/fortified/servers/mgmt-server/internal/applications/<application>/descriptor.json:roRestart the container after changing the mounted file.