The third type of integration is the Web Service.
Web Services connections allow the integrated systems to call directly to each other using the common Hypertext Transfer Protocol Secure, recognizable as the "HTTPS" that precedes most website URLs.
Unlike SFTP, Web Services is a communication protocol, not a connector protocol. It uses Secure Sockets Layer (SSL) to establish an encrypted link between the web server and a web browser, which eliminates the need for an SFTP server.
With Web Services, the client or a designated third party controls the integration schedule, and the connector is specified whenever a connection is established.
Web Services Connections
Web Services connections work in the following manner:
- The client/supplier system "calls" the SAP Fieldglass Web Service to trigger the respective connector.
- For an upload request, the call sends formatted data to SAP Fieldglass. SAP Fieldglass responds with a message indicating either the success or failure of the upload. For a download request, the client's call indicates the connector you want to trigger, and then SAP Fieldglass sends that data back to the client/supplier system. The client system extracts and processes the data.
Web Service Connection.
Web Services Methods
But that’s a general example. The actual connection process depends on which of the two Web Services methods WorkingNet would use:
- API, or