Migration from previous versions
Important notes before upgrading to 4.6
Update and run version 4.5.x before upgrading to 4.6 and later.
Important notes when upgrading to 4.11
|
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. |
An update to (or past) 4.11 does not support zero-downtime. Therefore, a downtime is required.
This is because version 4.11 introduces a more efficient data storage structure, to which all existing data needs to be migrated, which will reduce current and future storage space requirements. The duration of the upgrade depends on the size of the database and other factors like system load.
No running ERP Connectivity instance shall be connected to the database while it is being upgraded, as this could lead to data-loss!
Important notes when upgrading to 4.13
Version 4.13 removes the use of previously deprecated RabbitMQ features. To perform this migration, ERP Connectivity will create the following new RabbitMQ elements as successors to their old counterparts:
| Element type | Old name | New name |
|---|---|---|
Exchange |
x.erpconn.domain |
x.erpconn.v2.domain |
Queue |
q.erpconn.tenantremoval |
q.erpconn.v2.tenantremoval |
Queues |
q.erpconn.* |
q.erpconn.v2.* |
The old elements will not be removed automatically and should be deleted by hand after a successful upgrade, for example using the RabbitMQ management web interface.
Note that there can be any number of queues starting with q.erpconn. (even none at all), depending on the installed Connector Packages.
The ERP Connectivity upgrade must be fully completed with all old pods stopped before commencing this manual intervention.
The most important old element to delete is the x.erpconn.domain exchange, otherwise it will keep copying incoming messages to the old queues where they would pile up and lead to wasted space.
After the old exchange is deleted, the queues can be deleted at any time.
|
Before deleting any queue, make sure there are no consumers connected to it! You can display the number of consumers per queue by clicking the A number greater than 0 means the queue is currently in active use by a running pod, which should not be the case for old queues after the migration. |
If any of the old queues have messages left in them after the upgrade, they can be moved to their respective new queue by following the instructions in the RabbitMQ documentation "Migrating from Mirrored Classic Queues to Quorum Queues", section "Shovel remaining messages to the new vhost": https://www.rabbitmq.com/blog/2023/03/02/quorum-queues-migration#shovel-remaining-messages-to-the-new-vhost
|
In our case, messages are not shoveled to a new vhost, but rather to a new queue within the same vhost. Take care to parametrize the command accordingly. |
Important notes when upgrading to 2502.2.x and later versions
When updating ERP Connectivity to 2502.2.x and later versions please take care to update Packaging Control (if in use) to at least IAS version 2025.02.02.x since there is a breaking change in the dependency between Packaging Control and ERP Connectivity!
Additionally there are some updates to Packages required. In case of any questions contact BCI Application team.
Affected Packages (incl. minimum version required for ERP Connectivity version 2502.2.x and later):
| Package Area | Package Name | Package Version | Target System |
|---|---|---|---|
Master Data |
Material Basic Data Reception |
1.2 |
SAPS4Bosch |
Master Data |
Material Plant Data Reception |
1.4 |
SAPS4Bosch |
Packaging |
Packaging Confirmation |
3.1 |
SAPS4Bosch |
Packaging |
Packing Confirmation Cancellation |
2.0 |
SAPS4Bosch |
Packaging |
Packing Instruction Download |
2.1 |
SAPS4Bosch |
Packaging |
Packing Instruction Download |
1.1 |
SAPR3Bosch |
Production |
Production Confirmation Cancellation |
2.0 |
SAPS4Bosch |
Warehouse |
Packing Unit Task Creation |
3.0 |
SAPS4Bosch |