Importing the WSDL that Defines the Required BPM Service

See the BPM Developer’s Guide for detailed information about the services and operations provided by the BPM runtime, and the WSDLs and XSDs needed to access them.

  • You can access the WSDL for a particular BPM service in two ways:
    • You can generate it directly from the Administrator interface in the BPM runtime. Data types used by this WSDL are defined in an embedded schema.
    • You can use the BPM public web service API. Data types used in the WSDL files are defined in external, shared XSDs. (See the BPM Developer’s Guide for more information about how to obtain the BPM public web service API.)
  • If you are developing:
    • a large application that needs to access multiple BPM services, using the BPM public web service API may be preferable.
    • a lightweight application that accesses only a limited number of services, using generated WSDLs may be preferable. (This prevents namespace clashes within the workspace if the same common schema is included in two of the WSDLs.)

      This tutorial uses only a single BPM service, so uses a generated WSDL.

  • When you import BPM WSDLs into your Workspace, TIBCO recommends that you put them in their own project (or projects), separate from projects containing the processes that will use them. This will reduce overhead when process projects are built.
  1. Generating the WSDL for the EntityResolverService
  2. Importing the EntityResolverService WSDL into the Project
Next topic: Configuring the Web Service Call