Guide - IOM Demo Data Setup for IOM Connector

Table of Contents

Product Version


Product To Version




This guide illustrates how to configure Intershop Order Management - from now on referred as IOM - for a seamless communication between Intershop Commerce Management and IOM for inSPIRED demo data. As a result, you will be able to prepare inSPIRED demo data in the IOM. This document is mainly addressed to

  • Partners or customers, who are responsible for setting up the IOM
  • Pre-sales, marketing, or sales team, who present IOM to a potential customer





ICMThe abbreviation for Intershop Commerce Management
IOMThe abbreviation for Intershop Order Management
OMSThe abbreviation for Order Management System, the technical name of IOM
SQLStructured Query Language
PL/SQLProcedural Language/Structured Query Language

Channels and Shops

Both ICM and IOM follow the same hierarchical concept of organization having expandable entities. However, these entities differ. In ICM one sales organization might have multiple channels while in IOM one organization might have multiple shops. It is recommended to consider ICM channel and IOM shops as equals in context of your integration. Albeit not exactly the same, they are in close relation to each other.

As mentioned, IOM Services, albeit not mandatory, should be created in context of a channel. This way you can ensure that the data exchange between ICM and IOM is realized on a similar level.

At the IOM side, the relations between the shop and the suppliers will be as follows:


Database Configuration

  1. Go to the sub directory SQL and execute all the provided SQL queries in the numerical order using the psql client.

    Login as $OMS_USER
    . bin/
    psql -U $PGUSER -h $PGHOST -p $PGPORT -d $PGDATABASE < 01_Shops_Supplier.sql


Refer to the section General Configuaration in Guide - Generic Interfaces for External Accounting Systems to know where and how to execute the following SQL queries.

Product Import

The inSPIRED demo data to be imported is already provided as CSV files (provided by zip files).

  1. Go to the directory CSV.

  2. Copy all zip files whose name end with (e.g., into the directory $OMS_VAR/importarticle/in.


    At the moment there is no GUI where the users can check the progress and result of the import process.

    Hence, it is recommended to check the log information located at $OMS_LOG/ bakery*.log and $OMS_LOG/server*.log.

    Exit code 0 means that the import process was successful for each file (in our case six files) being placed. If there are any exceptions thrown or any other exit code is mentioned, the import was not successful.

Now you should be able to log into the IOM as admin / !InterShop00! to view the imported products in the menu 'Items'.info.


Although the product import has been simplified by providing CSV files, it is worth to refer to the document Guide - IOM Product Import 2.2 or Guide - IOM Product Import to learn more about this topic.


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.

Customer Support
Knowledge Base
Product Resources