- Menu
- Sitemap
Introduction
Welcome to the Intershop Order Management 2.2!
Intershop Order Management is an Intershop Commerce Suite application that is designed to combine omni-channel commerce processes into one system. It automates and streamlines the life cycle of 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.
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.
Dependency Version Information
| Intershop Order Management | Intershop Commerce Management B2X | IOM Connector | |
|---|---|---|---|
| Version | 2.2 | 7.9 | 5.0 |
Glossary
| Term | Description |
|---|---|
| API | Application Programming Interface |
| B2B | Business-to-Business |
| FTP | File Transfer Protocol |
| Gluster-FS | A scale-out network-attached storage file system |
| HA | High availability |
| ICM | Abbreviation for Intershop Commerce Management |
| IOM | Abbreviation for Intershop Order Management |
| IMPEX | Import/ Export |
| 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 |
| URL | Uniform Resource Locator |
| Watchdog | A tool of IOM to monitor and manage the availability of IOM application servers |
General Information
- System Requirements - Intershop Order Management 2.2
- Guide - Intershop Order Management - Technical Overview
- Guide - Setup Intershop Order Management 2.2
- Guide - IOM Database Migration (2.0 - 2.17)
- Overview - IOM 2.2 - 2.2.1 Migration
Additional Information
- Guide - IOM Job Scheduling
- Guide - IOM Watchdog
- Concept - IOM Server Health Check
- Concept - IOM Synchronization of Java-based Caches
- Concept - IOM Aggregated Invoices
- Public Release Note - IOM Connector 5.0
New Features and Enhancements
High Availability
High availability can be defined as follows. The system is designed for highest requirements in terms of performance and reliability. Several platform capabilities allow easy scaling without downtimes.
From version 2.2 Intershop Order Management is ready for High Availability.
Symmetric HA Nodes
The major approach is that high availability can be provided by using symmetric high availability nodes. The configuration of all high availability nodes is identical so every server node is able to replace any other. It follows the whole system will be able to answer requests, as long at least one active and working node exists. A selected backend server is active at a time that will handle business processes exclusively. Additionally a server monitoring tool, IOM Watchdog, is used to manage the availability of application servers and also switches to another backend server to be active in case of errors. Also see Guide - Intershop Order Management - Technical Overview for more detailed information.
The following diagram shows an example of high availability nodes. Gluster FS is used to replicate data between FTP-servers. High availability database and server monitoring is not shown in this picture.
To support this architectural approach the IOM was improved and extended. The following list gives a short overview.
Frontend Applications Servers
Applications servers that are acting as frontend servers were proved to support session failover. Additionally load balancing and sticky sessions are tested using one approach on Apache HTTP Server.
Backend Application Servers
The new management of cluster jobs implemented by Quartz Clustering with JDBC-JobStore ensures single machine job handling. See Guide - IOM Job Scheduling for more information.
IOM Watchdog
This new tool was implemented to manage the availability of application server nodes. Using IOM server health checks which was added to each application server Watchdog can be configured to start/ stop/ restart applications servers if required. Additionally Watchdog switches to another backend server to be active in case of errors. Also see Guide - IOM Watchdog 2.2 - 2.11.
FTP-servers
The Ftp-servers are enabled to synchronize between each other. One tested approach is GlusterFS, but any other solutions can be used too.
Further Changes
- Ensured automated reconnect of JMS and Database connections if connection was lost/ broken
- Introduced multiple addresses for database cluster and jms hosts
- Support of port-offsets
- Ensured distributed cache management for the application cluster. See Concept - IOM Synchronization of Java-based Caches.
- Server health check URLs (REST) are introduced to return the 'healthiness' of an application server. An additional REST service returns the current status of all applications servers within a cluster. Also see Concept - IOM Server Health Check.
- The log directory is configurable now
- Export jobs resistant to server restarts
- More intuitive naming of application server nodes
PostgreSQL HA Cluster
IOM supports access to PostgreSQL HA clusters but has always connect to the master database.
A PostgreSQL HA cluster usually consists of one master server and one or more hot-standby servers. The master-server is the only one, which is allowed to change data. An additional witness-server is needed by the fail-over process when the total number of servers (master + standbys) is odd. The database connection address of IOM consists of a hostlist which supports a number of one or more database host addresses which ensures a connection to the database as long as at least one of these addresses are pointing to a working PostgreSQL HA clusters. Please see Guide - Intershop Order Management - Technical Overview for more detailed information.
Improvements of the User Interface
Changed URL of OMT
The URL of the OMT application, the user interface, was cut down from /bakery.omt/app/ to /omt/app/ only and has no visual relation to the technical deployment artifact any longer.
Note
The URL /bakery.omt/app/ does not work any longer and has no redirect to the new URL.
New Icons for Menu
Icons for the main menu were replaced to more fit the represented content.
Improvement of Page Header
The page header of OMT was improved. Therefore the quick search was moved to it to be able to quickly search for orders, customers and items any time. Additionally icons to reach the user profile of the current user and to logout was introduced.
Enhanced Business Features
Support of Night Shipping Information at Shipping Addresses
Customer shipping addresses has been extended by the attribute night shipping. It indicates, if night shipping and delivery for a customer address is permitted. Thus, a call center agent can configure whether night shipping is enabled for a selected customer shipping address.
The new version of SOAP web service CustomerService/v1.1 and ExportCustomer/v1.1 supporting the new attribute nightShipping. Also see Reference - IOM SOAP Web Services
Note
Export Customer (based on CustomerService-v1.0.xsd) is no longer available.
Improvements of the Invoice View
On the invoice detail page the information about settled state is now shown on top too.
Additionally a comment can be added to the invoice.
Net Values for Manual Credit Notes on B2B Shops
On the invoice detail page it is possible to grant manually a credit note to a customer. For B2B shops the amounts now can be entered as net value. For B2C shops gross values still is required.
Delivery Note Number for Accounting Interfaces
The delivery note number from the supplier can now passed though the accounting interface of IOM to connected accounting systems. Following it is possible to match several deliveries from a supplier to aggregated invoices from a supplier.
Also see Reference - IOM ImpEx Interfaces. The new attribute is named DeliveryNoteNo.
Configuration of Aggregated Invoices
Aggregated invoices allows to generate one invoice for all orders/ dispatches within a certain time frame for a customer. Aggregated invoices now can be configured at the customer details page. Set here if an aggregated invoice should be generated and it's time frame.
For more information see Concept - IOM Aggregated Invoices.
Configurable Default Return Quantity
It is now possible to set the default quantity of the items that are possible to return within the dialog of OMT for the return confirmation. The default value can be the maximum returnable quantity or zero (0). For configuration use the cluster property is.oms.default.max.return.quantity. If not set zero (0) will be used.
See section Cluster Properties of Guide - Setup Intershop Order Management 2.2.
View of Discounted Amounts, Promotions and Discounts
With the enhancement of the OrderService v1.2 also improvements of the user interface were made. Therefore all amounts are now showing discounted values for an all-over consistently view. Discounts and promotions are shown separated.
The affected pages are:
- Order detail page
- Order return confirmation modal panel
- Order return position list
- Order position details
- Invoice position tab
- Credit note creation modal panel
Also email templates and PDF document templates were updated.
Consolidated View of Charged Values at Invoices
To have a more clear view about the several types of booked order values improvements were made on the invoice list.
Therefore the column paid was removed from the customer invoice list and the order invoice view. Further on the invoice details view the label paid was renamed to captured, the status for paid/ charged/ captured was removed. The status for booked remains.
Customization
Configurable Quartz Jobs
With the new management of cluster jobs as mentioned in section HA of this document, the configuration of cluster jobs was moved to etc/ of the application server. Using the files quartz-cluster.properties and quartz-jobs-cluster.xml cluster jobs can now be configured without any build of deployment artifacts before. Please see Guide - IOM Job Scheduling for more information.
Customizable Email Validation
Using the cluster property is.oms.validation.pattern.email it is now possible to customize the email validation using the given pattern. See section Cluster Properties of Guide - Setup Intershop Order Management 2.2.
Customizable Password Validation
Using the cluster property is.oms.validation.pattern.password
it is now possible to customize the password validation rule using the given pattern.
With is.oms.validation.pattern.password.hint the displayed note, where you can explain the rules for OMT users, can be customized. Both values can be set independently from each other.
See section Cluster Properties of Guide - Setup Intershop Order Management 2.2.
External Interfaces
Enhanced OrderService v1.2
The OrderService to submit new orders was enhanced to:
- Better support different calculation models
- Support further order information next to the order level and order position level
- Support multiple shipping addresses and multiple freight classes
- Display more information in the UI, emails and PDF documents
Therefore the OrderService was updated with following information:
- Additional discounted amounts on different order levels
- Additional unit information for items, e.g., meter, liter, piece
- Promotions on order and order position level, e.g., 10% off
- Cost center on order and order position level. Additionally a project can be noted.
- The former reserved properties payment, delivery_address, billing_address and reservation became part of the interface.
Note
- Currently the IOM supports only one shipping address per order. The new OrderService is well prepared to handle different shipping addresses (Position / Shipping attribute shipToAddress). But until the time has come, all positions should point to the same shipping address otherwise the system takes the information from the first position (shipToAddress) during the processing.
- The attribute shippingMethod (Position / Shipping) pretends that a client can define shipping methods per order position. But that is not the case. We do not recommend to use this attribute.
- The IOM OrderService v1.1 is declared as deprecated and will disappear in a future IOM version.
Also see Reference - IOM SOAP Web Services
CustomerService v1.1 Supports Night Shipping
Customer delivery addresses has been extended by the attribute night shipping. It indicates, if night shipping and delivery for a customer address is permitted. Also see Support of Night Shipping Information at Delivery Addresses and Reference - IOM SOAP Web Services
Note
Export Customer (based on CustomerService-v1.0.xsd) is no longer available.
Setup & Configuration
The distribution package that contains the binary distribution of Intershop Order Management 2.2 is available in the Product Calendar and consists only of this file:
- IOM_2.2.0.0.tgz
For installation instructions please read:
- System Requirements - Intershop Order Management 2.2
- Guide - Intershop Order Management - Technical Overview
- Guide - Setup Intershop Order Management 2.2
Please note that the installation requires installed and preconfigured:
- JDK 8
- WildFly 9
- Postgres 9.6
Interface Descriptions
REST API
SOAP API
The commented WSDLs are part of the IOM distribution package and can be found in this directory /doc/SOAP.
Asynchronous Interfaces
- Guide - IOM Product Import 2.2
- Guide - IOM Product Export (from 2.1 to 2.2)
- Reference - IOM ImpEx Interfaces
Deprecations
Removals
Fixed Defects
Changelog
Version Intershop Order Management / 2.2.8
Overview - IOM 2.2.7 - 2.2.8 Migration
Fixed Defects
Version Intershop Order Management / 2.2.7
New Features
| Key | Summary |
|---|---|
| IOM-7774 | Added Moldova to CountryDefDO |
| IOM-7702 | Health check caches responses |
| IOM-7567 | Interface for GDPR compliant customer data collection |
Fixed Defects
Version Intershop Order Management / 2.2.6
New Features
Fixed Defects
Version Intershop Order Management / 2.2.5
New Features
Fixed Defects
Version Intershop Order Management / 2.2.4
Fixed Defects
Version Intershop Order Management / 2.2.3.1
Fixed Defects
Version Intershop Order Management / 2.2.3
Fixed Defects
Version Intershop Order Management / 2.2.2
New Features
| Key | Summary |
|---|---|
| IOM-7177 | Enabled automation of database migration |
| IOM-7166 | Enabled all partners in PartnerReferrerDO to be receiver of a transmission |
Fixed Defects
Version Intershop Order Management / 2.2.1
Please see Overview - IOM 2.2 - 2.2.1 Migration for migration guidelines.
New Features
Deprecations
Fixed Defects
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.