WSDL Activities
TIBCO BPM Enterprise version 5.x+ does not invoke or expose service operations that external clients or other processes can invoke using WSDL documents. Content and configuration relating to WSDL documents is removed on importing pre-version 5.x TIBCO BPM Enterprise projects to version 5.x TIBCO Business Studio - BPM Edition.
- Version 5.x+
TIBCO Business Studio - BPM Edition processes do not support activities with a service type of
Web Service.
- To invoke business processes from business services or pageflow processes, replace the web service tasks with a call sub-process activity and configure the sub-process activity to be invoked asynchronously.
- To invoke external clients, you must use REST services. To do this, on the General tab in the Properties View for your activity, set Service Type for your activity to REST Service.
- Incoming message activities (in other words, all those activities involved in exposing processes as web services) are no longer supported. Instead, you can use new incoming request activities (formerly receive task and intermediate untriggered or no-type events) in your process and trigger these using the generic runtime API services.
- Incoming request-with-reply patterns are not currently supported. As an alternative you may consider using an asynchronous send-two-ways pattern. The request is made from an external system via an Incoming request event (using the generic runtime API services), the 'reply' is implemented as a REST service send task that invokes a service in the external system to send the required reply data.
- Incoming request activity correlation is now only by process ID not business data. The external client or process invoking an incoming request activity using the runtime API must use the process ID. To obtain the process ID, either:
Copyright © 2021. Cloud Software Group, Inc. All Rights Reserved.