Table of Contents

Search

  1. Preface
  2. Transformations
  3. Source transformation
  4. Target transformation
  5. Access Policy transformation
  6. B2B transformation
  7. Aggregator transformation
  8. Cleanse transformation
  9. Data Masking transformation
  10. Data Services transformation
  11. Deduplicate transformation
  12. Expression transformation
  13. Filter transformation
  14. Hierarchy Builder transformation
  15. Hierarchy Parser transformation
  16. Hierarchy Processor transformation
  17. Input transformation
  18. Java transformation
  19. Java transformation API reference
  20. Joiner transformation
  21. Labeler transformation
  22. Lookup transformation
  23. Machine Learning transformation
  24. Mapplet transformation
  25. Normalizer transformation
  26. Output transformation
  27. Parse transformation
  28. Python transformation
  29. Rank transformation
  30. Router transformation
  31. Rule Specification transformation
  32. Sequence Generator transformation
  33. Sorter transformation
  34. SQL transformation
  35. Structure Parser transformation
  36. Transaction Control transformation
  37. Union transformation
  38. Velocity transformation
  39. Verifier transformation
  40. Web Services transformation

Transformations

Transformations

Create a Web Services consumer connection

Create a Web Services consumer connection

Connect to a web service using Web Services Description Language (WSDL) and an endpoint URL. You can also enable security for the web service.
  1. In
    Administrator
    , select
    Connections
    , and click
    New Connection
    .
  2. Enter the connection details. For the
    Type
    , select
    WSConsumer
    .
    If the WSConsumer connection is not in the list of connections, in
    Administrator
    , open the
    Add-On Connectors
    page to install the connector for your organization.
    Ensure that you select WSConsumer, not Web Service. Web Service connections are used for mapplets or PowerCenter tasks.
  3. Enter the connection properties:
    1. Select the runtime environment for the web service connection.
    2. For
      Authentication
      , select one of the following options:
      • Select
        Username Token
        to enter the user name and the password to authenticate the web service. You can choose to encrypt the password by sending a digest that is derived from the password in the security token.
      • Select
        Other Authentication
        to enter the WSDL URL and endpoint URL to access the web service. If the web service is a private web service, enter the HTTP user name and password.
  4. Enter the authentication connection properties. The properties that appear depend on the authentication that you selected.
    The following table describes the properties to configure:
    Property
    Description
    WSDL URL
    The URL provided by the web service.
    If you are using a WSDL URL that has HTTP Basic authentication, download the WSDL to the machine where the Secure Agent runs. For the WSDL URL, enter the file path. For example, you can enter the following directory path:
    C:\WSDL\Human_Resources.wsdl
    Endpoint URL
    Endpoint URL for the web service. The WSDL file specifies this URL in the location element.
    Username
    Applicable to username token authentication. User name to authenticate the web service.
    Password
    Applicable to username token authentication. Password to authenticate the web service.
    Encrypt Password
    Applicable to username token authentication. Enables the PasswordDigest property which combines the password with a nonce and a time stamp. The
    mapping
    task applies a SHA hash on the password, encodes it in base64 encoding, and uses the encoded password in the SOAP header.
    If you do not select this option, the PasswordText property is enabled and the
    mapping
    task does not change the password in the WS-Security SOAP header.
    HTTP Username
    User name used to access the web service.
    HTTP Password
    Password to access the web service.
  5. Save the connection.

0 COMMENTS

We’d like to hear from you!