CCO Manager Central Synchronization

[mohamed_abdelsattar]

Hello Experts,

gunther.sandtner2 anderson.schmitt

We have below setup for one of our customers

1) 1 branch with 20 POS terminals
2) CCO manager locally installed to handle central receipt parking
3) SAP Business One is our backend

Concern: we don't want each POS to sync items, customers, discounts... separately
Question: can we let CCO Manager performs the sync job centrally; get/store all updates from SBO? Then each POS get the data from CCO Manager directly?

Awaiting your replies.

BR,
Mohamed

[JoergAldinger · Accepted solution]

Hello Mohamed,

This is not currently possible, but it is on the (long-term) roadmap of CCO. I have heard some partners have developed a sync mechanism from B1 to CCOM, but I'm not sure of the scope, reliability and customizability of this integration.

I would suggest you implement the standard sync now, and migrate over to CCOM when that becomes available, which will most likely 1 year +.

Hope this helps,

Joerg

[mohamed_abdelsattar · Accepted solution]

Thanks Joerg for the usual support.

From your experience, what are the best practices for the sync (specially for items and discounts) to save the load on B1if and get the updates as soon as possible?

- Let's say we have around 5 branches with 30 POS each (a total of 150 machines)

- All should sync the updates at the same time due to changes in pricing and other staff (items count is 100,000)

- We usually use cron expressions to define lag times between branches and between each POS in the same branch (this won't work if we need all machines to sync at the same time - business needs)

- I'm not sure if the random delay feature (schedule sync screen) would do the trick

Thanks again 🙂

[JoergAldinger · Accepted solution]

Hello Mohamed,

I think the key to your success will be to dimension the B1iF server appropriately. We don't have any installations that large (maybe other partners can contribute with recommended specs?), but make sure you start with enough resources and monitor them closely. A large enough group of DI Proxies will be important for sure.

Since the sync is differential, the total item count should not matter that much. It will be more important to know how many item changes (I guess mostly prices) are going to be happening throughout the day.

As a calculation help for the DI proxies, if you have 150 terminals and want to sync every 5 minutes, you will have (on average) one request every 2 seconds. If the average item sync request takes 10 seconds, you should have at least 5 DI Proxies. But since you probably cannot control the average to that extent make sure you consider more (plus, you have other stuff that passes through the DI Proxies as well). I'd start with 10 or more.

Also for syncing you will need to set up a CRON expression. If you manage to get the time of all your terminals synced with a time server (shouldn't be difficult), then you can specifically tell each CCO terminal to sync at a slightly different time, so that in effect each terminal will sync one ofter the other in 2 second intervals. I think that might be better than using the "random delay" option.

As for the "business needs" of syncing at the same time, I'm not sure how stringent or mandatory that is. I would try to work around if it possible. E.g. does "at the same time" allow you to cover a 5-minute window? Or a 1-minute window? That will increase your resource (and bandwidth) requirements by five...

Hope this helps.

Best regards,

Joerg.

[mohamed_abdelsattar · Accepted solution]

Thank you joerg.ceo.

[gunther_sandtner · Accepted solution]

Hello,

I just wanted to confirm that also to my knowledge the move to a central B1 integration in CCO manager is on the long-term product roadmap.

Kind regards,

Gunther