Migration from previous versions
Migration to 3.0.x (2023.02)
The module "Safety" was merged with Operational Routines for this release. There are a couple of things that need to be done to clean up and avoid conflicts:
Safety needs to be un-registered from Web Portal
The Safety Service (smsafety) may have been registered at Portal in a previous version. This causes issues so it should be un-registered by using the DELETE /registry/api/v1/registry/systems/{id} endpoint of the portal API. This endpoint needs to be called via postman. The required module id can be retrieved from the integration view. To call the endpoint, it is required to have either the Web Portal Operator or Web Portal Admin Role (they grant the delete privilege on the registration resource).
MACMA roles, contracts and assigned users need to be migrated manually from Safety to Operational Routines
Because all roles and resources for the Safety UI are now managed by Operational Routines, all MACMA configuration done for Safety needs to be migrated to Operational Routines.
How to update the contracts in MACMA UI:
-
add contract for Operational Routines to any tenant currently containing a contract for Safety
-
remove all contracts for Safety in MACMA UI (required for the next step)
-
delete the Safety module in MACMA UI
How to update the roles in MACMA UI:
-
Assign the new roles of Operational Routines to all users which need access
-
remove the deprecated safety-specific roles in MACMA UI (if not already deleted)
Migration to 3.1.x (2024.01)
With this version, we reworked all MACMA resources. Please delete the old resources by sending the following payload to MACMAs public delete resources API:
{
"items": [
{
"id": "urn.com.bosch.nexeed.widgets.settings",
"type": "view"
},
{
"id": "urn.com.bosch.nexeed.widgets.settings.action",
"type": "api"
},
{
"id": "urn.com.bosch.nexeed.routines.settings",
"type": "view"
},
{
"id": "urn.com.bosch.nexeed.routines.settings.action",
"type": "api"
},
{
"id": "urn.com.bosch.nexeed.dmm.settings.action",
"type": "api"
},
{
"id": "urn.com.bosch.nexeed.routines",
"type": "view"
},
{
"id": "urn.com.bosch.nexeed.routines.action",
"type": "api"
},
{
"id": "urn.com.bosch.nexeed.dmm",
"type": "view"
},
{
"id": "urn.com.bosch.nexeed.dmm.action",
"type": "api"
},
{
"id": "urn.com.bosch.nexeed.dmm.kpidetails",
"type": "view"
},
{
"id": "urn.com.bosch.nexeed.dmm.kpidetails.action",
"type": "api"
},
{
"id": "urn.com.bosch.nexeed.otherservices.action",
"type": "api"
},
{
"id": "urn.com.bosch.nexeed.facilities.management.action",
"type": "api"
},
{
"id": "eb40eb7c-27dc-44bf-91a3-d5ded3af4310",
"type": "urn:com:bosch:bci:operation:pdcacycle"
},
{
"id": "urn.com.bosch.nexeed.safety",
"type": "view"
},
{
"id": "urn.com.bosch.nexeed.safety.action",
"type": "api"
},
{
"id": "5bbe84e6-8904-4d69-a237-a6ae7b01686c",
"type": "urn:com:bosch:bci:operation:macmausers"
},
{
"id": "2c34f73e-f511-4a0c-a80d-50f059491e2c",
"type": "urn:com:bosch:nexeed:smc:operationalroutines:reaction"
},
{
"id": "5d7ff7b2-7d57-48ea-a440-297db92c3bea",
"type": "urn.com.bosch.nexeed.dmm.facilitygroups"
},
{
"id": "3a6457dd-55b0-4e74-afe9-11b5895b0ae5",
"type": "urn:com:bosch:nexeed:webviewerwidget"
}
]
}You may also want to delete the old roles for cleanup. To do this, send the following to Macmas bulk-delete application roles endpoint. Keep in mind that you need a token for the Operational Routines client with the audience of aud:macma to call this endpoint.
{
"items": [
{
"name": "OperationalRoutinesModerator"
},
{
"name": "OperationalRoutinesModuleUsers"
},
{
"name": "OperationalRoutinesReactor"
}
]
}Migration to 3.5.x (2024.02.01)
With this version, facility groups were replaced by routine configuration. Please delete the old MACMA resource by sending the following payload to MACMAs public delete resources API:
{
"items": [
{
"id": "urn:com:bosch:bci:smor:facility-group",
"type": "all"
}
]
}Migration to 2501.0.x (2025.01)
Elastic APM has been replaced with OpenTelemetry (OTEL). For detailed configuration instructions, refer to Chapter "11.5. OpenTelemetry Integration" in the central NEXEED Industrial Application System Operations Manual.
Important notes:
|
If you run any Nexeed IAS installation on Tenant ID The Tenant ID is conceptually the unique identifier for all data contained in Nexeed IAS in relation to other installations. This will lead to problems if dataflows meet on shared infrastructure (like e.g. RabbitMQ or Solace) or existing systems are to be merged on a shared installation with multiple tenants. Therefore, the Tenant ID has to be unique - for systems that have been erroneously installed with either Tenant ID The Migration instructions and scripts available from BCI are specific to that version and cannot be executed on prior or later versions. |
Migration to 2502.0.x (2025.02)
With the migration to quorum queues, Operational Routines has renamed its queue and exchange to avoid conflicts. The old queue and exchange may need to be cleaned up manually. Please delete the x.smor.integration-inbound exchange and the q.smor.integration-inbound queue if this has not happened automatically yet.