📄️ What is a web service component?
The use of web services on the World Wide Web is expanding rapidly. Web services make it possible for diverse applications to discover each other and to exchange data via the Internet. A web service is a software system identified by a URI (Uniform Resource Indicator), whose public interfaces and bindings are defined and described using XML. Its definition can be discovered by other software systems. These systems can then interact with the web service, using XML-based messages.
📄️ How to import web service definitions
To import web service definitions:
📄️ Calling a web service using an INVOKE statement
You can call a web service component by using an INVOKE statement. This is the straightforward way to call a web service component:
📄️ Calling a web service using a component table
You can call a web service by performing a query on a component table. This component table represents the parameter values of a web service method. Component tables can be used under the following conditions:
📄️ Using XSL transformations for web service component tables
When performing a query on a component table that represents a web service method, the following steps are executed:
📄️ The USoft component table XML format
The syntax of the USoft component table XML format is:
📄️ Finishing creating a web service component table
After you have created a component table for a web service component, you have to perform some final steps.
📄️ Proxy server settings
A Proxy server is located between a client application, for example a Web browser, and a real server. It intercepts all requests to the server to see if it can fulfill them. If not, it forwards the request to the server. To use a Proxy server, a client needs to specify a proxy address and a proxy port number (the proxy settings).
📄️ How to modify existing web service components
To modify existing Web Service components:
📄️ Web service component details
There are three situations when a Web Service component definition is stored in the repository:
📄️ Setting a timeout value when calling a web service
To specify a timeout value when calling a web service, modify the constructor method of the web service component by adding the following line:
📄️ DIME messages support
Direct Internet Message Encapsulation (DIME) is a Microsoft-proposed internet standard for sending and receiving SOAP messages along with additional attachments like binary files, using standard transfer protocols like HTTP.
📄️ How to implement DIME messages
To implement the use of DIME messages, you must add a new parameter after importing a Web Service Component into your repository. This parameter must be the last parameter in the list. This parameter will be used for file names that will be sent as attachments along with the SOAP message in the web service call. The parameter must have InList mode and Variable data type.
📄️ MTOM (Message Transmission Optimization Mechanism Support)
MTOM is the W3C Message Transmission Optimization Mechanism, a method for efficiently sending binary data to and from web services. It uses XOP (XML-binary Optimized Packaging) to transmit binary data. XOP is the W3C XML-binary Optimized Packaging, a method of efficiently embedding binary data in XML.
📄️ Debugging web service components
For debugging purposes, you can make a BenchMark profile when calling a web service component. This profile then contains the soap messages that are sent to and received from a web service.
📄️ The sendSoapMessage function
In certain circumstances, there are limitations using a web service component. For example, USoft does not support soap headers when importing a web service component from WSDL.