This guide lists all migrations required from Intershop Order Management 4.5 to 4.6. The document is aimed at project developers.
This database migration from 4.5 to 4.6 can only be performed when the application is down. It is expected to run under 5 minutes.
With the new endpoint to retrieve the last modified orders, you may need to adapt your custom code for the case when you bypass the registration of order states changes.
However, changes are collected internally on given state modifications of objects appearing in the order states. It is hence likely that code modification is not required. Refer Cookbook - IOM Order API.
IOM REST API - Health Service 1.0 deprecates endpoint health/clusterstatus and will be removed timely
Moreover, the application-server status check is now synchronized.
Two cluster properties should be adjusted:
Every 6 hours (the feature is obsolete and will be removed)
Deprecated (since="4.6.0", forRemoval=true
), use a large default interval (6 hours) until removal of /system-property=is.oms.healthcheck.recurringtime: "21600000"
Deprecated (since="4.6.0", forRemoval=true
), /system-property=is.oms.healthcheck.cachelivetime: "21700000"