![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
The Invoke activity invokes a partner service. The partner service can be local (a service within the same project), it can be a third-party service invoked by way of SOAP over the Internet, or it can be an internal service invoked by way of SOAP over the corporate intranet.
You can specify a binding to a concrete WSDL to invoke a specific partner service, or you can use an abstract partner portType and use a Partner Link Configuration resource to bind the invocation request to the correct partner service within the Service resource. See Partners for more information about using partner services.You can also enable WS-Security for the Invoke activity by associating a security policy with a service endpoint operation defined for a Partner Link in the Partner Link Configuration resource. When a security policy is associated, the WS-Security processing is enabled and performed according to WS-Security guidelines for the outbound, inbound, and inbound fault message exchange specified in the Security Policy Association resource.Security policies in TIBCO ActiveMatrix BusinessWorks BPEL Extension are associated in exactly the same way as in TIBCO ActiveMatrix BusinessWorks. For more information on how to associate a security policy, refer to the TIBCO ActiveMatrix BusinessWorks documentation.
The partner declared on the Orchestration Process that you wish to invoke. See Partners for more information about declaring partners. Invoke Message Correlations Correlations for the outgoing message to the partner service. See Correlations for more information about correlations. Reply Message Correlations Correlations for the reply message received from the partner service. This field is only available when the operation selected contains a reply message. See Correlations for more information about correlations.The Join Condition tab allows you to define an expression based on the values of the incoming transitions to the activity. If the expression evaluates to true, the activity is executed, if the expression evaluates to false, either the activity is bypassed or a fault is thrown. See Transitions and Join Conditions for more information about join conditions.
Specifies what action to perform if the join expression evaluates to false. The following options are available:
• Inherit setting — use the default action specified within the current scope. The current scope is either the current group containing the activity or the orchestration process if the activity is not within a group.
• Bypass activity if false — skip the processing of the activity, set the outgoing transition conditions to false without evaluating them, and resume processing.
• Throw fault if false — throw a joinFailure fault and switch control to an error-handling routine configured to catch all unhandled exceptions. If the exception is not caught, the fault is propagated to the calling environment. The expression to evaluate to determine if the activity should be executed. The only data available to this expression is the value of any transitions into the activity. You can use the XPath Formula Builder to create the join expression.The Input Variable tab allows you to specify whether you will use the contents of a process variable as input to this activity or you will use the Input tab to specific input bindings as XPath expressions. If you choose to use a process variable, the schema of the variable must match the input schema of the activity exactly.
• Use Input Variable — specifies that you will select an input variable to use as input for the activity. The schema of the variable must match the input schema of the activity or an error is thrown when this activity is executed.
• Use Input Binding Tab — specifies that you will use the Input tab to create mappings and XPath expressions to provide input for this activity. When Use Input Variable is selected in the Input Style field, this field allows you to select from a list of process variables to use as the input for the activity.The Input tab is only enabled if Use Input Binding Tab is selected in the Input Style field on the Input Variable tab. See TIBCO ActiveMatrix BusinessWorks Process Design Guide for more information about mapping and transforming input data.
The input message for the desired operation on the partner service. The schema depends upon the message defined in the WSDL for the partner service.
The output message for the desired operation on the partner service. The schema depends upon the message defined in the WSDL for the partner service.The output variable tab allows you to select a process variable to contain the output of the activity. The schema of the process variable must match the schema of the output for the activity shown on the Output tab.
This exception is thrown when the invoked service replies with a fault. The fault message is returned in the faultName/MessageFault/fault/Error/Message element.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |