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

Adding Policy Assertions

Adding Policy Assertions

Select a service containing the binding information for the endpoint reference. Select the Policy Assertions tab to add one or more policy assertions for the endpoint reference.
The WS-Policy specification allows Web service providers and clients to express a broad range of capabilities, requirements, and preferences in a standard way through
policy assertions
. If desired, you can add one or more policy assertions to the partner link's endpoint reference section of a process deployment descriptor file.
You can add a policy assertion to both the
Partner Role
partner link and the My Role partner link in the Deployment Descriptor wizard.
Many policy assertions specify both an
inbound
and
outbound
direction.
  • An inbound assertion governs messages received by the BPEL process, such as messages for receives and replies from invoked services.
  • An outbound assertion governs messages sent by the process, such as requests to an invoked service and replies matching receives.
Policy assertions apply to static endpoint references for partner roles in the PDD wizard. For a dynamic endpoint reference, you can manually add the details to the appropriate copy operation in an assign activity.
The supported policy assertions are described in the following table:
Policy
Description
WS-Security Policy Assertions
Credentials required for access to a serve
Describes the parts of a SOAP message to encrypt
Describes the parts of a SOAP message to sign with an XML Signature, using an X.509 Certificate token
Adds a <Timestamp> element to the SOAP header of a message
Other Policy Assertions:
Retry (Partner Role)
Describes when and how many times to retry an invoked service that does not reply
A My Role policy assertion that directs the Process Server to use WS-Addressing to transmit replyTo endpoint references during transmissions to the Partner Role partner link
Specifies that a partner link participates in an industry-standard protocol that supports guaranteed delivery of messages
JMS Delivery Options (Partner Role--
Informatica Process Developer only
)
Used for REST-based invocations
REST Enabled (My Role)
Used for REST-based invocations
The Security Assertions Markup Language (SAML) is an OASIS standard that enables loosely coupled and federated identity integration.
Provide fine-grained validation of WSDL messages for a partner link to enable faster processing
Set an amount of time to wait for a specific Web service to time out
Invoke Recovery (Partner Role)
Select whether to suspend a process with a pending invoke when the process recovers from a failed server
Explicitly add addressing to invokes
Applicable for a my role partnerlink to refer to a WSDL binding instead of RPC or Document
A workaround for suppressing schema validation in SOAP messages, useful for dealing with legacy services that cannot handle
xsi:type
attributes
For subprocess invoke only. Add a user name to stand for the process initiator. Useful for a subprocess that contains a People activity that can request the name of the process initiator.

To add one or more policies to a partner link

  1. In the Deployment Descriptor wizard, navigate to the Partner Links page. See Creating a Process Deployment Descriptor File for details on opening the New Deployment Descriptor dialog.
  2. For a partner role partner link, select static as the Endpoint Reference Type.
  3. Select the Dialog button at the end of the Endpoint Reference text box.
  4. Select the Policy Assertions tab, as shown here.
  5. Select the
    Add
    button to open the
    Policy Assertion
    dialog.
  6. From the Policy Template list, select the policy you wish to add, and fill in all the required information. For details, select a name from the supported policies listed at the top of this topic.
  7. Select
    OK
    .
  8. Select
    Add
    again to add additional policies.
  9. Add My Role policy assertions by doing the following:
    1. Select a My Role partner link.
    2. Select the My Role Policy tab.
    3. Select applicable policies, as described above, for the My Role service.


Updated March 30, 2020