Invoke activity is an asynchronous activity that calls an operation of a process reference. The process reference can be configured to invoke another process (subprocess) or invoke an external service through a binding such as SOAP.
General
Note: The
Call Process activity serves a similar purpose as the
Invoke activity. The
Call Process activity only calls non-WSDL-based subprocesses, or direct subprocesses, and the
Invoke activity only calls WSDL-based subprocesses, or service subprocesses.
The
General tab has the following fields.
Field
|
Description
|
Name
|
The name to be displayed as the label for the activity in the process.
|
Service
|
Select the service for which to specify an operation.
|
Description
Provide a short description for the activity.
Advanced
The
Advanced tab has the following field.
Input item
|
Literal Value/Module Property
|
Description
|
Activity Timeout (seconds)
|
Yes
|
The
Invoke activity timeout in seconds. You can either select a preset timeout (Default Timeout, 30, 60,or 120 seconds) or specify a custom timeout in seconds.
Important: If the Invoke activity is configured to be
Default Timeout, then the timeout value equates to "3" minutes by default. However this default value (3 minutes) can be modified to be a different value by setting the
property
bw.engine.activity.async.waitTime
in
BW_JAVA_OPTS evironment variable. The value for the property should be specified in milliseconds.
For example:
-Dbw.engine.activity.async.waitTime=<timeout in milliseconds>
Note: When the
Invoke activity timeouts, the in-line subprocess instance called by the
Invoke activity can be cancelled before the subprocess instance completes. Hence, the business logic in the cancelled process instance may not be executed to its entirety.
|
Input
The following is the input for the activity.
Input item
|
Datatype
|
Description
|
input message
|
complex
|
The input message of the operation. This element contains all the input message parts for the operation.
|
Output
The following is the output for the activity.
Output item
|
Datatype
|
Description
|
output message
|
complex
|
The output message for the operation. This element contains all the output message parts for the operation.
|
Fault
The
Fault tab lists the possible exceptions generated by this activity.
For more information about error codes and the corrective action to take, see the
TIBCO BusinessWorks™ Container Edition Error Codes guide.
Fault
|
Generated When..
|
ActivityTimedOutException
|
A timeout has been reached.
|
Note: When used to invoke REST service with REST reference binding, it contains additional elements such as clientFault and serverFault.
Invoke for SOAP with HTTP
When used to invoke SOAP service, it displays the faults defined in the WSDL file along with the following exceptions:
Fault
|
Generated When..
|
HTTPClientException
|
The HTTP server responds with a message containing the 4XX status code.
|
HTTPServerException
|
The HTTP server responds with a message containing the 5XX status code.
|
HTTPCommunicationException
|
An HTTP exception occurred while executing the specified method, or when trying to read the response.
|
To send HTTP responses logging on the wire, set the following VM argument:
- -Dorg.apache.commons.logging.simplelog.defaultlog=DEBUG
- -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.SimpleLog
- -Dorg.apache.commons.logging.simplelog.showdatetime=true
- -Dorg.apache.commons.logging.simplelog.log.org.apache.http=DEBUG
- -Dorg.apache.commons.logging.simplelog.log.org.apache.http.wire=DEBUG
Copyright © Cloud Software Group, Inc. All rights reserved.