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
  • PowerCenter 10.5.9
  • All Products

Table of Contents

Search

  1. Preface
  2. Web Service Concepts
  3. Understanding the Web Services Provider
  4. Using the Web Services Hub Console
  5. Batch Web Service Operations
  6. Writing Client Applications
  7. Working with Web Service Sources and Targets
  8. Editing Web Service Sources and Targets
  9. Working with Web Service Mappings
  10. Working with Web Service Workflows
  11. Appendix A: Web Service Sample Client Applications
  12. Appendix B: Configure the Web Browser

Web Services Provider Guide

Web Services Provider Guide

Back Next

Web Services Provider Architecture

Web Services Provider Architecture

The Web Services Provider consists of the Web Services Hub and the batch and real-time web services hosted by the Web Services Hub. The Web Services Hub works with the Integration Service and the Repository Service to process web service requests.
The following figure shows the Web Services Provider architecture:
The Web Services Provider architecture consists of the Web Services Hub, Integration Services and Repository Service.
The Web Services Hub processes requests for real-time web services and batch web services in similar ways.
The following process describes how the Web Services Hub processes web service requests:
  1. A web service client sends a SOAP message to the Web Services Hub to run a web service.
  2. For batch web services, the Web Services Hub authenticates the web service client based on the session ID generated during the login.
    For protected real-time web services, the Web Services Hub authenticates the web service client based on the user name token.
  3. The Web Services Hub generates a message ID for the request.
    If the request is for a real-time web service, the Web Services Hub sends the message to the Integration Service.
    If the request is for a batch web service operation, the Web Services Hub sends the message to the Integration Service or the Repository Service based on the type of request. For example, if the request is to run a workflow or to start or stop the Integration Service, the Web Services Hub sends the message to the Integration Service to process. If the request is to get a list of workflows in a the repository, the Web Services Hub sends the message to the Repository Service to process.
  4. The Integration Service or Repository Service processes the request.
    If the request is for a real-time web service, the Integration Service sends the processed data to the Web Services Hub which uses the message ID to correlate the request with the response.
  5. The Web Services Hub sends a SOAP response to the web service client.
The Integration Service and Web Services Hub communicate with the Repository Service throughout the process.
0 COMMENTS
We’d like to hear from you!