Manual MACMA configuration after setting up a new tenant

Each application integrated in Nexeed IAS brings some roles and permissions and needs some roles and permissions from other integrated applications.

The basic IAS deployment takes care of the role assignment to the applications in the default (BCI) tenant.

Since Nexeed IAS is a multi-tenant system, we have to take care of the role assignment to the applications in the newly created tenants. As this step is currently not automated, it must be done manually for the time being.

Service account roles provided by Condition Monitoring (CM)

CM provides roles that need to be set per tenant.

Machine data sender

Required	Yes
Domain	Condition Monitoring
Description	Enables actors, like the Information Router, to send measurement and machine messages via HTTP to CM.

Service account roles needed by Condition Monitoring (CM)

CM requires several roles that need to be set per tenant.

User Reader (user-reader)

Required	Yes
Domain	Multitenant Access Control
Description	Enables CM read user and tenant information.

Equipment Administrator (Admin)

Required	Yes
Domain	Master Data Management
Description	Enables CM to read, add and delete equipment master data.

Portal Registration (Portal_Registration)

Required	Yes
Domain	Web Portal
Description	Enables CM to register in the Portal.

Data Publisher Registration (DataPublisherModuleRegistration)

Required	Yes (if Data Publisher module is installed)
Domain	Data Publisher
Description	Enables CM to register data types in the Data Publisher.

Deviation Processor Detector (DeviationProcessorDetector)

Required	Yes (if Deviation Processor module is installed)
Domain	Deviation Processor
Description	Enables CM to send deviations to Deviation Processor.

Ticket Context Registrar (ticket-context-registrar)

Required	Yes (if Ticket Management module is installed)
Domain	Ticket Management
Description	Enables CM to register its domain specific attributes (ticket context) in Ticket Management.

CM Domain Context Registration in Ticket Management

Normally, domain context registration in Ticket Management is performed automatically for each tenant that includes both Condition Monitoring and Ticket Management modules during the startup of the Condition Monitoring module.

Additionally, when a new tenant and contract are created with Condition Monitoring and Ticket Management modules, or when a new contract is created with only Ticket Management for an existing tenant, the domain context registration is also handled automatically.

However, if the service account role Ticket Context Registrar is not assigned to the Condition Monitoring module after tenant creation within the retry period (default 3 hours), you must register the domain context in Ticket Management manually:

Assign the service account role Ticket Context Registrar to the Condition Monitoring module for the specific tenant to complete your tenant configuration.
Assign the Ticket Context Registrar role to your user.
Obtain a token with the Ticket Management scope.
Call the Ticket Management API for domain context registration to register manually.

MDM reload for the new tenant

Condition Monitoring (condition-monitoring-core)

Admin Rest API to control reloading of device master data from MDM for a specific tenant:

e.g. in case it is a new tenant configured after installation
e.g. you want to synchronize the device master data for this tenant
e.g. a manual change is done in MDM database
1. Get Token for Condition Monitoring
2. call POST {URL}/cm/core/v1/{ownerTenantId}/mdm/reload → needs Condition Monitoring Administrator Role

Rules Management (rule-service-app)

Admin Rest API to control reloading of device master data from MDM for a specific tenant:

e.g. in case it is a new tenant configured after installation
e.g. you want to synchronize the device master data for this tenant
e.g. a manual change is done in MDM database
1. Get Token for Condition Monitoring
2. call POST {URL}/cm/rm/rule-manager/v1/{ownerTenantId}/mdm/reload → needs Rules Management Administrator Role