Welcome to Intershop Order Management 3.2!
Intershop Order Management (IOM) is an application of the Intershop Commerce Suite (ICS) that is designed to combine omni-channel commerce processes into one system. It automates and streamlines the life cycle of orders and payments. IOM 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.
IOM 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 ICS, it utilizes the suite's transaction, PIM and merchandising features.
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.
Term | Description |
---|---|
API | Application Programming Interface |
Docker | An operating system-level virtualization software. Also see Kubernetes and Helm. |
Helm | A package manager for Kubernetes. Also see Docker. |
ICM | Abbreviation for Intershop Commerce Management |
IOM | Abbreviation for Intershop Order Management |
Kubernetes | An open-source system for automating deployment, scaling, and management of containerized applications. Also see Docker and Helm. |
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 |
In combination with IOM Helm Charts 1.2.0 it is now possible to control the creation of access log messages.
See Public Release Note - IOM Helm Charts 1.2.0 and Guide - Operate Intershop Order Management 3.X.
IOM 3.2 uses Adopt OpenJDK 11.0.9.1+1 now.
Also, see System Requirements - Intershop Order Management 3.2.
A new property DOCKER_PROXY was added to the tool caas2docker. This property can be used to avoid direct access to Docker Hub.
The DOCKER_PROXY property can be filled with the name of an alternative Docker repository, which acts as a proxy for Docker Hub.
See also the example property files provided with caas2docker.
In combination with IOM Helm Charts 1.2.0 it is now possible to set a timeout for importing test data at runtime by using the new Helm parameter caas.importTestDataTimeout.
See:
Setup & Configuration
For installation instructions see:
Docker-images are available at:
For a complete list of all interfaces please see Overview - Intershop Order Management REST API and Overview - IOM Interfaces.
Key | Summary |
---|---|
IOM-10737 | Deprecated import.properties as part of test-data in projects, use new Helm parameter caas.importTestDataTimeout instead |