Skip to main content Skip to complementary content
Close announcements banner

Creating a SOAP Service from a BPM process deployed on Bonita BPM Portal

About this task

Prerequisites:

  • Bonita BPM Portal is up and running.

  • The process from which you want to create a Service is deployed on Bonita BPM Portal. For details of how to deploy a process on Bonita BPM Portal, see the Bonita documentation.

Once you have selected the From BPM Portal option in the Create Service From BPM Process wizard, do the following.

Procedure

  1. In the Process tree structure, select the BPM process from which you want to create a Service.
  2. By default, all the fields corresponding to the variables defined in the BPM process are selected. If required, clear the Name check box of a field, and then choose one of the following options from the Non-request Field Type list field:
    • Custom: to leave an empty value for the field; if needed, you can specify a custom value or expression for the column corresponding to this field in the output table of the first tXMLMap component in the generated Job, to pass custom information to the BPM process, before running the Job to start the Service. This is the default option for a non-request field.

    • Security Token: use this field to pass the Security Token, if any, in the service request to the BPM process.

    • Correlation ID: use this field to pass the correlation ID, if any, in the service request to the BPM process.

  3. Select the SOAP Service option.
    The default generated information of the BPM Service is described in the Generated Wsdl Information area.
    To change these information, clear the Use default check box and update the fields according to your needs.
  4. Click Finish. The related Job and data service are created in the Repository tree view.

Results

You can now edit the generated WSDL file. For more information, see Editing a WSDL file.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!