The Order History Microservice is used to transfer order information from Microsoft Dynamics 365 to Intershop Commerce Management (ICM).
This document provides important product information, including version information and dependencies. It also outlines the basic setup and configuration steps.
|Intershop Commerce Management
|Microsoft Order Submission Microservice
|22.214.171.124 - 126.96.36.199
The source code can be downloaded from https://repository.intershop.de//mvn-orderhistory-releases/.
The order history connector is implemented as Microservice.
Setup instructions can be found at Cookbook - Microservice Deployment (valid to 7.10) and Cookbook - Eureka Deployment and ICM Configuration (valid to 7.10).
Following configuration data has to be provided to Order History Microservice. Currently the properties have to be specified in a file that is within the Java classpath of the Microservice.
Configuration for getting an access token from Azure Active Directory (AAD) necessary for OData access to Microsoft Dynamics 365 for Finance and Operations:
# Azure Active Directory credentials
Configuration for the number of threads used to process requests from ICM:
# Concurrency configuration
How the methods of payment in Microsoft Dynamics 365 are mapped to Intershop payment methods can be extended and adjusted in the file
Configuration for mapping of ICM payment methods to related ones specified in Microsoft Dynamics 365 for Finance and Operation's Contoso demo:
# Payment method mapping configuration
# pattern: intershop.orderhistory.mapping.payment.method.<dyn365-name>=<icm-name>
intershop.orderhistory.mapping.payment.method.ELECTRONIC=ISH_INVOICE intershop.orderhistory.mapping.payment.method.CASH_DELIV=ISH_CASH_ON_DELIVERY intershop.orderhistory.mapping.payment.method.CASH_ADV=ISH_CASH_IN_ADVANC
The referenced payment methods have to be created and configured before in Dynamics 365 and ICM.
In order to connect the Order History Microservice with the ICM, a managed order history service has to be configured.
The microservice allows configuration of one Dynamics 365 tenant. If this maps to one ICM sales channel, create the managed service at channel level.
If multiple sales channels (within one ICM organization) are connected to the same Dynamics 365 tenant, you can also create the managed service at organization level and enable sharing.
To create a service configuration (set technical configuration):
Microservice URI e.g., Eureka service URI 'service://orderHistory'.
All orders of a customer will be displayed in the order list in the My Account section.