Welcome to Intershop Order Management 2.12!
Intershop Order Management is an Intershop Commerce Suite orders and payments. Intershop Order Management processes orders from multiple touch points (web shop, mobile shop, call center and more), allocates them to multiple fulfillment solutions (fulfillment centers, drop-ship distributors, physical stores and more), and tracks all order and payment transactions. that is designed to combine omni-channel commerce processes into one system. It automates and streamlines the life cycle of
Intershop Order Management offers a centralized platform for managing distributed inventory, order, invoice and payment life cycles, and provides call center functionality, enabling real-time visibility into customers' purchasing behavior, stock levels, payments, and more. As part of Intershop Commerce Suite, it utilizes the suite's transaction, PIM and merchandising features.
Intershop Order Management (IOM) offers the possibility to tailor your business models as flexible and free as you need and depict them in your e-commerce environment. The order management system adjusts the order processing for various sales channels and suppliers and can be seamlessly integrated with existing components of your IT environment.
|Intershop Order Management||Intershop Commerce Management B2X||IOM Connector|
|API||Application Programming Interface|
|FTP||File Transfer Protocol|
|ICM||Abbreviation for Intershop Commerce Management|
|IOM||Abbreviation for Intershop Order Management|
|OMS||Abbreviation for Order Management System, the technical name of the IOM|
|OMT||Abbreviation for Order Management Tool , the graphical management tool of the IOM|
|REST||Representational State Transfer|
|SOAP||Simple Object Access Protocol|
Additional tabs can now be configured and will be displayed on the order detail page. Also see Cookbook - IOM Custom Order Detail Tabs in OMT.
The following image is showing the custom order detail tabs Limits and Stock Information that include views from another application.
The user profile page was changed to enable that useless actions are not shown any longer.
Now all applications (scalable and singleton) are running in one IOM server of the new type cluster. This new server type uses Wildfly mechanisms to manage singleton applications. A detailed description of the newly used mechanisms can be found in Guide - Intershop Order Management - Technical Overview.
With the introduction of the new central shared file system, a new health check was added to enable IOM to react to errors. The various shared file systems that were used before were not checked, except for the two file systems used by the (now obsolete) FTP servers.
For more information please have a look at Guide - Intershop Order Management - Technical Overview and Guide - Setup Intershop Order Management 2.12.
Required migration steps can be found in Guide - IOM 2.12 Migration to Central Shared Filesystem.
IOM is now supporting PostgreSQL 11. When using Ansible4IOM to setup IOM, the according variable PG_VERSION now accepts the value '11', too.
For more information see:
The default value of OMS_LOG in $OMS_ETC/installation.properties has changed from "$OMS_VAR/log" to "/var/opt/$OMS_USER.log".
The advantage of this change is that the separation of OMS_VAR and OMS_LOG. OMS_LOG will not be removed any longer when uninstalling IOM. But you have to make sure to provide sufficient disk space at the new position of OMS_LOG.
Ansible4IOM 1.2 adds support for management of IOM installations of version 2.12 and older. The architectural changes of IOM 2.12 (see above) are reflected in Ansible4IOM by the new server groups oms_cluster_node and oms_azure_cluster_node, which have to be used for IOM 2.12.
More information can be found in Overview - Ansible4IOM.
Ansible4IOM v 1.2 supports now watchdog-less installations of IOM 2.12.
As of IOM 2.12 server type standalone was removed, hence a suitable setup of IOM suitable for developers was lost. To enable developers again to setup a system according to their needs, a new Ansible4IOM configuation variable in roles/oms_config/defaults/main.yml was added: WATCHDOG_ACTIVATED (default set to
true). The deactivation of watchdog is supported for installations consisting of a single oms_cluster_node only.
See section OMS in Reference - Ansible4IOM Variables
The following enumerations are now expandable by customization:
Also note that the new delivery option 'Delivery on same day' was added to the default values of
For more details see:
For installation instructions please see:
Please note that the installation requires installed and preconfigured:
For a complete list of all interfaces please see Overview - IOM Interfaces
|IOM-8932||Removed property OMS_SERVER_TYPE from $OMS_ETC/installation.properties|
|IOM-8927||Removed FTP-servers and according cluster properties 'is.oms.media.*', 'is.oms.pdf.*' and 'is.oms.pdf.healthcheck', is.oms.media.healthcheck|
|IOM-8862||Removed support for server-groups oms_ha_node, oms_azure_node, oms_single_node in Ansible4IOM|
|IOM-8859||Removed server types 'standalone', 'backend' and 'frontend'|
|IOM-8962||Manual credit notes break credit note process for returns|
|IOM-8921||Online help shows outdated state of user profile|
|IOM-8911||Localization issue "Great Britain" should be called "United Kingdom"|
|IOM-8870||Duplicate Check for Payment Notifications is too strict|
|IOM-8858||NullPointerException when creating return for shops without Order validation|
|IOM-8857||Address Additions are printed as "null" in customer emails|
|IOM-7138||Viewing the customer details page additionally requires the permission 'View Order'|
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.