Interface
The two halves talk to each other over a narrow HTTPS interface. This chapter describes how they do it – for setup and for troubleshooting.
What is this for?
- Set up the access.
- Understand which data flows in which direction.
- Recognise what happens when a request is repeated.
How to set it up
- The app creates one connector key per shop, shown only once. The app itself stores only a hash of it – if it is lost, a new one is created.
- The NCS-Webservice keeps address and key encrypted in the interfaces.
- From SAP to the app: articles, stock, customers, customer-specific prices and fulfillment notices.
- From the app to SAP: orders – and cancellations of orders that were already taken over.
- Longer tasks are accepted as a job; the webservice asks for its state later and receives a result per record: created, updated, unchanged, skipped or failed.
- Every writing request carries an idempotency key. If the same request arrives twice it is not executed twice – the original result is returned instead. That is the protection against a repeated run duplicating orders or articles.
Worth knowing
The connection runs outbound only, from your site. The app never calls in. For the firewall that means outbound HTTPS is enough; nothing has to be reachable from outside.