Hybris provides industry’ leading Omni-channel commerce solutions, combined with SAP’s strength in enterprise applications and technology, will enable business to optimize customer engagements. SAP and hybris form a powerful combination, enabling clients to create a robust digital commerce experiences.
The big question comes in as to what data from ECC needs to be presented to customers in real time and what can be transferred to hybris asynchronously on scheduled basis to show it to customers anytime quickly.
Datahub is hybris’ preferred approach to asynchronously transfer data from one system into another. Hybris has built pre-integrated connectors allowing the data to flow from SAP directly through the datahub and into hybris. Now if the clients have the PI Middleware already in place, which is routing the ECC data to other third parties, then clients prefer to let PI do the task to transfer the ECC data to datahub (which will send it to hybris) without making the code/functional changes at ECC end.
Here, let us just quickly see how to configure ICO in PI to send the data to datahub successfully. The datahub and hybris
ECC configuration : Create a RFC destination, port and logical system for PI . and configure the partner profile. Here let us do it for Product Data .
PI configuration :
- Check for ECC system present as business system in PI.
- Create Idoc sender channel.
- Create a business component with datahub.
- Create a HTTP_AAE receiver channel pointing to Datahub.
- Configure the ICO (here no OM is used, the Idoc XML would be posted to Datahub)
For the HTTP_AAE receiver channel, in the target host put the host name for Datahub server, update the target port with the corresponding port and the path is always same for Idoc end point as shown in screen-print following. Do update the character encoding and content-type as well.
Save the ICO, and trigger a test MATMAS.MATMAS05 Idoc from ECC.and it would flow to Datahub through PI successfully.
In the datahub server, browse to the bin location under tomcat directory, there a log file would be created with the name logFile.<date>. In that the idoc xml can be found.