Table of Contents

Search

  1. Preface
  2. Welcome to Informatica Process Developer
  3. Using Guide Developer for the First Time
  4. Getting Started with Informatica Process Developer
  5. About Interfaces Service References and Local WSDL
  6. Planning Your BPEL Process
  7. Participants
  8. Implementing a BPMN Task or Event in BPEL
  9. Implementing a BPMN Gateway or Control Flow
  10. Using Variables
  11. Attachments
  12. Using Links
  13. Data Manipulation
  14. Compensation
  15. Correlation
  16. What is Correlation
  17. What is a Correlation Set
  18. Creating Message Properties and Property Aliases
  19. Adding a Correlation Set
  20. Deleting a Correlation Set
  21. Adding Correlations to an Activity
  22. Rules for Declaring and Using Correlation Sets
  23. Correlation Sets and Engine-Managed Correlation
  24. Event Handling
  25. Fault Handling
  26. Simulating and Debugging
  27. Deploying Your Processes
  28. BPEL Unit Testing
  29. Creating POJO and XQuery Custom Functions
  30. Custom Service Interactions
  31. Process Exception Management
  32. Creating Reports for Process Server and Central
  33. Business Event Processing
  34. Process Central Forms and Configuration
  35. Building a Process with a System Service
  36. Human Tasks
  37. BPEL Faults and Reports

2. Designer

2. Designer

Endpoint References and WS-Addressing Considerations

Endpoint References and WS-Addressing Considerations

At deployment time, you need to specify the location information for each partner link endpoint reference. Also, you can assign an endpoint reference dynamically, detailed in the Copy Operation Dynamic Endpoint Reference Example.
One of the main protocols to specify location information for an endpoint reference is based on the Web Services Addressing (WS-Addressing) specification.
The WS-Addressing specification standardizes the format for referencing a Web service allowing you to create uniquely identified Web services and Web service instances that are not bound to a specific transport mechanism, such as HTTP. Using WS-Addressing, the endpoint information is added to the header of a SOAP request and not to the URL specified in the SOAP body.
Having endpoint reference information in a SOAP header means that you can do the following:
  • Specify Web service instance IDs
  • Select
    Reply To
    and
    Fault To
    addressees
  • Select
    From
    endpoint references in the case where an acknowledgement needs to be sent back to the sender
Note that in Process Server, you can specify other mechanisms besides SOAP over HTTP. For details, see
Custom Service Interactions
.
The basic WS-Addressing syntax is as follows:
<wsa:EndpointReference> <wsa:Address>anyURI</wsa:Address> <wsa:ServiceName PortName="portname">Service QName </wsa:ServiceName> </wsa:EndpointReference>
where:
  • Address
    is a mandatory element that identifies an endpoint. It can be a network address or a logical address.
  • ServiceName
    is the qualified name, or QName, for the service being invoked. This service must be defined in a WSDL file that is deployed with the process or one that is available in Process Server's resource catalog.
  • PortName
    identifies the service port being invoked. Note that you can specify a port binding of SOAP 1.1 or SOAP 1.2.
You can add credential details to the endpoint reference, described in
Endpoint References Requiring Credentials for Access
.
For information on setting and endpoint reference when deploying to Informatica Cloud, see
.
The following versions of the WS-Addressing specification are supported:
  • http://www.w3.org/2005/08/addressing
    This is the default version that the PDD uses. For changing the default, see
    Process Developer Preferences
    .
  • http://schemas.xmlsoap.org/ws/2004/03/addressing
  • http://schemas.xmlsoap.org/ws/2004/08/addressing
  • http://schemas.xmlsoap.org/ws/2003/03/addressing
You can review the WS-Addressing specification at
http://www.w3.org/2005/08/addressing
/.


Updated March 30, 2020