1
votes

We are trying to use cloud hot folder functionality and in order to do so we are modifying our existing hot-folder implementation that was not implemented originally for usage within cloud.

Following the steps on this help page: https://help.sap.com/viewer/0fa6bcf4736c46f78c248512391eb467/SHIP/en-US/4abf9290a64f43b59fbf35a3d8e5ba4d.html

We are trying to test the cloud functionality locally. I have on my machine azurite docker container running and I have modified the mentioned properties in local.properties file but it seems that the files are not being picked up by hybris in any of the cases that we are trying.

First we have in our local azurite storage a blob storage called hybris. Within this blob storage we have folders master>hotfolder, and according to docs uploading a sample.csv file into this should trigger a hot folder upload. Also we have a mapping for our hot-folder import that scans the files within this folder: #{baseDirectory}/${tenantId}/sample/classifications. {baseDirectory} is configured using a property like so: ${HYBRIS_DATA_DIR}/sample/import

Can we keep these mappings within our hot folder xml definitions, or do we need to change them?

How should the blob container be named in order for it to be accessible to hybris?

Thank you very much,

I would be very happy to provide any further information.

2

2 Answers

1
votes

In the end I did manage to run cloud hot folder imports on local machine.

It was a matter of correctly configuring a number of properties that are used by cloudhotfolder and azurecloudhotfolder extensions.

Simply use the following properties to set the desired behaviour of the system:

cluster.node.groups=integration,yHotfolderCandidate

azure.hotfolder.storage.account.connection-string=DefaultEndpointsProtocol=http;AccountName=devstoreaccount1;AccountKey=Eby8vdM02xNOcqFlqUwJPLlmEtlCDXJ1OUzFT50uSRZ6IFsuFq2UVErCz4I6tq/K1SZFPTOtr/KBHBeksoGMGw==;BlobEndpoint=http://127.0.0.1:32770/devstoreaccount1;

azure.hotfolder.storage.container.hotfolder=${tenantId}/your/path/here

cloud.hotfolder.default.mapping.file.name.pattern=^(customer|product|url_media|sampleFilePattern|anotherFileNamePattern)-\\d+.*

cloud.hotfolder.default.images.root.url=http://127.0.0.1:32785/devstoreaccount1/${azure.hotfolder.storage.container.name}/master/path/to/media/folder

cloud.hotfolder.default.mapping.header.catalog=YourProductCatalog

And that is it, if there are existing routings for traditional hot folder import, these can also be used but their mappings should be in the value of

cloud.hotfolder.default.mapping.file.name.pattern

property.

0
votes

I am trying the same - to set up a local dev env to test out the cloud hotfolder. It seems that you have had some success. Can you provide where you located the azurecloudhotfolder - which is called out here https://help.sap.com/viewer/0fa6bcf4736c46f78c248512391eb467/SHIP/en-US/4abf9290a64f43b59fbf35a3d8e5ba4d.html

Thanks