Use the Connect-dotNet method to invoke a Web service identified in a Connect dotNet rule (an instance of the Rule-Connect-dotNet rule type).
This method operates on a named clipboard page that is the source and destination of data mappings. Make sure the Step Page column that calls this method contains the non-blank name of such a page.
This method has two parameters:
|ServiceName||Enter the Service Name (second key part) of a Connect dotNet rule ( Rule-Connect-dotNet rule type). To find the Connect dotNet rule, rule resolution uses the class of the step page as the first key part of the Connect dotNet rule.|
Select if this connector is intended to run in parallel as a child requestor
of the current requestor. If selected, include the Connect-Wait method later in the
current or a follow-on activity to access results from the connector.
Do not select this box if the Connect dotNet rule supports compensating actions.
|EndPointURL||Optional. Enter an endpoint URL value to override the value in the Connect dotNet rule.|
The Connect-dotNet method works as follows:
- Using rule resolution, the method locates the Connect dotNet rule identified by the parameter.
- Uses request information to assemble a SOAP request for the Web service.
- If the step page does not exist, creates a new page, of the class identified in the Pages & Classes tab.
- Checks whether simulation is in force for this rule. If so, the simulation stub activity is called.
- (If simulation is not in force) sends the SOAP message (or calls the simulation activity), in a temporary separate requestor session if the RunInParallel box is selected. (This temporary requestor has the same access group and clipboard as the original. At most 10 such child requestor sessions can be active at once.)
- Processes the response message when it is received.
Checking the method status
This method updates the pxMethodStatus property. See How to test method results using a transition.
Design the activity to detect and handle exceptions. If the Connect-dotNet method with the
RunInParallel check box selected fails in a way that causes the Connect-Wait method to be
skipped, the child requestor can be left hanging. If the limit of parallel requestors is
then eventually reached, the parent requestor will fail as well. By default, the limit is 10
requestors in parallel; you can establish a higher or lower value in the
prconfig.xml file or dynamic system settings using the