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 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.
Cookbook - IOM Order API, endpoint order-states/modified
The endpoint health/clusterstatus is deprecated since IOM 4.6.0 and will be removed timely. Moreover, the application-server status check is now synchronized.
Two cluster properties should be adapted:
Every 6 hours (the feature is unused and should be removed in the next version)
forRemoval=true), use a large default interval (6 hours) until removal of
The information provided in the Knowledge Base may not be applicable to all systems and situations. Intershop Communications will not be liable to any party for any direct or indirect damages resulting from the use of the Customer Support section of the Intershop Corporate Web site, including, without limitation, any lost profits, business interruption, loss of programs or other data on your information handling system.