Table of Contents

Search

  1. Preface
  2. Performance Tuning Overview
  3. Target Optimization
  4. Source Optimization
  5. Transformation Optimization
  6. Mapping Optimization
  7. Partitioned Mapping Optimization
  8. Run-time Optimization
  9. SQL Data Service Optimization
  10. Web Service Optimization
  11. Connections Optimization
  12. Data Transformation Optimization

Performance Tuning Guide

Performance Tuning Guide

Push-Into Optimization with the Web Service Consumer Transformation

Push-Into Optimization with the Web Service Consumer Transformation

With push-into optimization, the Web Service Consumer transformation receives the filter value in a filter port. The filter port is an unconnected input port that you identify as a filter port when you configure push-into optimization. The filter port has a default value that ensures that the web service returns all rows if the end-user query contains no filter. The filter port is not a pass-through port.
The filter field must be part of the root group in the web service request.
The filter field cannot be a pass-through port. When you configure a filter port, the default value of the port changes to the value of the filter condition, so the pass-though output port value changes. A filter based on the output pass-through port returns unexpected results.
You can push multiple filter expressions to the Web Service Consumer transformation. Each filter condition must be the following format:
<Field> = <Constant>
The filter conditions must be joined by AND. You cannot join the conditions with an OR.

0 COMMENTS

We’d like to hear from you!