Web service proxy

The web service proxy is a DataPower® service that can handle traffic for various endpoints that multiple WSDL files describe.

The WSDL configuration source for a web service proxy can be any combination of the following locations. For more information, see Configuration sources for a web service proxy.
  • A WSDL file in the DataPower file system, generally in the local: directory for the application domain
  • A WSDL file to retrieve from a remote server
  • A WSDL file that is a subscription on the IBM WebSphere Service Registry and Repository server
  • A WSDL file that is a saved search or named query on the WebSphere Service Registry and Repository server

After you define which WSDL files are the configuration sources, the remainder of the configuration is to fine-tune the processing to meet your business requirements.

For illustrative purposes, a web service proxy can include the following WSDL files.
  • A WSDL file for service endpoints to query accounts
  • A WSDL file for service endpoints to modify accounts
  • A WSDL file for service endpoints to manage certificates of deposit

A remote client can use the address and port from a single web service proxy to obtain services from all endpoints that the WSDL files describe. The combined WSDL file is for publishing to remote registries. The user policy controls endpoints.

Attention: The wizard for the web service proxy in the new UI is a technology preview. As a technology preview, you can use the new UI to create and manage a web service proxy with the wizards. If you must access the WebGUI because the new UI has a functional problem, change the browser URL from http://<hostname>:<port>/ui/<path> to http://<hostname>:<port>.

Configuration approaches

From the DataPower GUI, the easiest approach to create a web service proxy from WSDL files is with the wizard. After you create the service, you can modify its configuration either with or without the wizard. Generally when you want to modify the configuration, the wizard is the better approach. When the wizard does not provide the property to modify, you can modify the configuration from the object view (without the wizard).

The entry points to create a web service proxy are as follows.
With the wizard
New web service proxy, or click the Web service proxy icon on the home page.
Without the wizard
Web service proxy.
The entry points to modify a web service proxy are as follows.
With the wizard
Edit web service proxy, or click the Web service proxy icon on the home page.
Without the wizard
Web service proxy.

Restrictions

Consider the following restrictions when you configure the processing policy for a web service proxy.
  • You cannot use a processing policy that a web service proxy uses with any other DataPower service. Conversely, another DataPower services cannot use the processing policy of a web service proxy.
  • The web service proxy can accept encrypted request messages when the entire payload is encrypted. Either the root node of the message must be encrypted or the first child of the SOAP:Body element must be encrypted.
  • The web service proxy automatically decrypts the encrypted payload. Decryption uses the private key that corresponds with the certificate that encrypted the data. The certificate is identified by identification credentials or is identified by the Decrypt key property. The location of this property differs based on whether you access the configuration with or without the wizard.
    • With the wizard, define the property on the Proxy settings tab.
    • Without the wizard, define the property on the Main tab.

    The web service proxy does not automatically do field-level decryption. For more information, see Defining field-level decryption for a web service proxy.