This guide illustrates how to configure Intershop Order Management 2.1 - from now on, referred as IOM -, for a seamless communication between Intershop Commerce Management 7.6 (up to 7.8) 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
Ensure that the system meets the according requirements - System Requirements - Intershop Order Management 2.1
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.
|ICM||The abbreviation for Intershop Commerce Management|
|IOM||The abbreviation for Intershop Order Management|
|OMS||The abbreviation for Order Management System, the technical name of IOM|
|SQL||Structured Query Language|
|PL/SQL||Procedural Language/Structured Query Language|
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:
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
Refer the section General Configuaration in Guide - Generic Interfaces for External Accounting Systems to know where and how to execute the following SQL queries.
The inSPIRED data to be imported is already provided as CSV files. Download and extract the provided inSPIRED_B2X.zip file.
Go to the sub directory CSV.
As $OMS_USER, copy all six files, whose name end with _A.csv (e.g., 10000_10000_20160224165437_A.csv), into the directory /var/opt/oms/importarticle/in.
Currently 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_VAR/log/bakery.log and $OMS_VAR/log/server.log. Exit code 0 means that the import process was successful for each file (in our case, six _A.csv files) being placed. If there are any exceptions thrown or any other exit code is mentioned, the import was not successful.
Although the product import has been simplified by providing CSV files, it is worth to refer to the document GU - IOM Product Import - obsolete 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.