Configuring Web Services

After completing this lesson, you will be able to:

After completing this lesson, you will be able to:

  • List and explain the methods for automating integrations through a Web Services connection.
  • Set up a simple object access protocol integration.

Web Services

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:

  1. The client/supplier system "calls" the SAP Fieldglass Web Service to trigger the respective connector.
  2. 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
  • SOAP.


The first type of Web Service integration is API.

An API is an Application Programming Interface, a customizable part of a server that receives requests and sends responses. Basically, it's an interface that allows specific types of data to be interpreted by other systems.

Transactions through API are sent in real-time on a per transaction basis, providing a more seamless integration experience than the other methods.

Because of the complexity of API-based integrations, setup is not a function available within Configuration Manager.


SOAP, or Simple Object Access Protocol, is an XML-based messaging protocol for exchanging the data that Fieldglass uses for batch integrations.

Specifically, SOAP uses an XML protocol called Web Services Description Language, or WSDL. The WSDL is basically the format and ‘instructions’ for how to connect or integrate; it describes the specific web service as collections of network endpoints.

Basically, SOAP is the manner in which the systems will use the web to connect, and WSDL provides the instructions for how SAP Fieldglass will connect with the specific WorkingNet system.

SOAP Web Service Set up

Set Up a SOAP Web Service

Setting up a Web Services integration occurs in the Connectivity step of the Connector Setup Wizard.

Starting from that point, here’s how you’d create a new Web Services integration for the Active Worker Single Line Download connector for WorkingNet.

Log in to track your progress & complete quizzes