Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • PowerExchange Adapters for PowerCenter 10.5.9
  • All Products

Table of Contents

Search

  1. Preface
  2. Understanding PowerExchange for Web Services
  3. Configuring PowerExchange for Web Services
  4. Web Service Sources and Targets
  5. Web Services Consumer Transformation
  6. Creating and Configuring Web Service Workflows
  7. Appendix A: Datatype Reference

PowerExchange for Web Services User Guide for PowerCenter

PowerExchange for Web Services User Guide for PowerCenter

Back Next

WSDL File Component Hierarchy

WSDL File Component Hierarchy

WSDL files contain numerous components that describe interface, datatype, binding, and addressing information necessary for accessing and using a web service. PowerExchange for Web Services displays the following WSDL file components in the Import from WSDL (Web Services Consumer) window when you import a web service operation:
  • Service.
     Contains groups of related ports. Each port defines an endpoint, which enables remote systems to connect to the service. The services section of the WSDL file defines each port’s type, binding, and SOAP network address. Services contain one or more ports.
  • Port.
     Defines the connection between bindings and the information required and returned by the web service. Each port defines a binding.
  • Binding.
     Defines a protocol and data format for each operation. Each binding defines the format for one or more operations.
  • Operation.
     Describes a program that performs an action, such as retrieving an order number. PowerExchange for Web Services supports request-response and one-way operations. Web service operations contain input and output messages. Input and output messages in the WSDL file contain the XML data that PowerExchange for Web Services uses to determine the groups and columns in the web service source and target definitions and Web Services Consumer transformations.
The following figure shows the relationship of WSDL file components:
A web service can contain numerous ports, which can contain numerous web service operations. The web service provider can make the same operation accessible from different ports. For example, the provider can bind an operation to a WSDL file with both a SOAP interface and an HTTP GET interface. This requires that two different ports contain the web service operation.
When you import a web service operation, you see the WSDL file component hierarchy in the Import from WSDL (Web Services Consumer) window so that you know which port contains the operation. You import a web service operation for a web service source definition, a web service target definition, and a Web Services Consumer transformation.
The legend in the Import from WSDL (Web Services Consumer) window indicates services, ports, bindings, and operations. You can only import web service operations. Services, ports, and bindings are not available to import.
0 COMMENTS
We’d like to hear from you!