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

Manually Importing WSDL Schema and Other Resources

Manually Importing WSDL Schema and Other Resources

Define the location of the resource file containing the target namespace. Select a workspace resource, such as sample data, WSDL, or XSL file.
If you import and open a BPEL process into Process Developer before adding a WSDL file to Project Explorer, Process Developer reports unresolved references to port types because the WSDL is unknown.
The recommended practice for adding WSDL is to use Participants. For details, see
Using the Participants View
.
You can add WSDL location and namespace manually. You can also add schema and other resources as follows.
  1. From Outline view, select
    Imports
    .
  2. Right-mouse click and select
    Add > Declaration > Import
    .
  3. From the Import Types list, select a type.
  4. If you select XSL, the Type URI of the file is added. This type identifies the encoding language used in the file as shown:
    http://www.w3.org/1999/XSL/Transform
  5. In the Location group, do one of the following:
    • Select
      Project
      and browse to the Project Explorer folder containing the file.
    • Select URL and type in a Web location of a file, such as:
      http://www.tempuri.org/myFile.wsdl
      or
      http://www.tempuri.com/service.asmx?WSDL
      Note that when the process is deployed and running, this URL must be available.
    Notice that the target namespace is displayed for the WSDL or schema file. If you paste a pathname or URL into the WSDL (or Schema) file location field, you can press the Tab key to see the target namespace. Click
    OK
    when you are through.
  6. In the Outline view, right-mouse click the Imports node, and select
    Refresh Imports
    .
To modify an import, double-click it, or in Properties view, click the
Dialog (...) Button
next to Location.
Process Developer adds the target namespace to the BPEL process and associates the namespace with a default prefix. Also, the port types, operations, and partner link types defined in the WSDL are available for use in the process.
The following illustration shows how the Process Developer displays a WSDL location and namespace. Note that Process Developer adds a new namespace prefix with a default name
ns1
. See
Namespace Prefix and Declaration
for more information.
Illustration of WSDL location and namespace in Outline view
See also
Refreshing Imports
.


Updated March 30, 2020