Introduction

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

Prerequisites

• Knowledge of (PL/)SQL and handling CSV files
• Take some time to get familiar with the IOM - Guide - Intershop Order Management - Technical Overview

• Ensure that the system meets the according requirements - Overview - IOM System Requirements

  For the following step, in order to see the log messages for the product import explained later on, please change the system.std.properties file prior to applying it when described in the installation document by replacing all occurrences of WARN to INFO.

• Proceed with IOM installation as described here - Guide - Setup Intershop Order Management 2.2 or Guide - Setup Intershop Order Management 2.9

References

• Guide - IOM Product Import 2.2
• Guide - IOM Product Import
• Guide - Generic Interfaces for External Accounting Systems

Glossary

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:

Configuration

Database Configuration

1. Download the attached demo data, i.e., inSPIRED_B2X_5.0.zip or inSPIRED_B2X_6.0_IOM_2.9.zip.
2. Start the application server. This will replicate JAVA Enums to corresponding database tables.
   Without this step the following sql scripts will throw some errors.

3. 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/set_env.sh
   psql -U $PGUSER -h $PGHOST -p $PGPORT -d $PGDATABASE < 01_Shops_Supplier.sql
   ...
   psql -U $PGUSER -h $PGHOST -p $PGPORT -d $PGDATABASE < OPTIONAL_IOM_XML_Export.sql

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 _ABCGN.zip (e.g., 10000_10001_20160725000000_ABCGN.zip) into the directory $OMS_VAR/importarticle/in.

   Note

   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 _ABCGN.zip 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.