Connect dotNet form
Completing the Service tab

Field

Description

Specify the SOAP operation style for the messages:

• Choose RPC for RPC-encoded.
• Choose Document for document-literal.

Optional. If you selected RPC, enter the name of the SOAP RPC method called on the remote server.

Optional. Enter the Uniform Resource Identifier for the namespace, starting with uri: or urn:. This need not correspond to a file at that location.

Optional. Enter the value of the SOAPAction HTTP header that is sent with the request message.

Select to specify the connector is to send the message and end the connection without waiting for a response (operate asynchronously). Clear this option to cause the connector to wait for a response (operate synchronously).

If you select this option, the connector does not wait for a response even if you configure data mappings on the Response tab.

If selected, PRPC includes authentication credentials in the HTTP header of the dotNet request message.

If your application requires dotNet headers that conform to a WS-Security format rather than using HTTP Basic, NTLMv1 or NTLMv2 authentication, you can configure the header directly on the Request tab.

If you open a Connect dotNet rule configured in a version prior to Version 6.2, the rule form contains a Username Property and Password Property field. To update the rule to use the Authentication Profile, save the rule and refresh rule form. The Username Property and Password Property fields are replaced with the Authentication Profile field populated with a new profile.6.2

Required, if Use Authentication? is selected. Select the Authentication Profile that contains the authentication details required by the remote service.

Enter the URL of the remote service provider to which the request message is sent.

This field supports the Global Resource Settings syntax (=.PageName.PropertyName). The default property name for this field is pySOAPURL. For more information, see Using the Global Resource Settings feature.

Optional. Enter a number of milliseconds after which — if no response is received — this rule times out with a failure message. Enter zero or leave blank to wait indefinitely.

Optional. Use this field to maintain an HTTP connection to the Web service provider after the method is called. Enter an arbitrary text value (a group key identifier) here, and also in other Connect dotNet rules that are to share a single connection (for one requestor).

This capability can improve system performance, as the HTTP connection is saved and reused. In addition, this field is a requirement for session maintenance through token passing.

If you leave this field blank, PRPC creates a new HTTP connection each time this Connect dotNet rule executes, and destroys it after the first use.

Select to use HTTP token-passing as the mechanism for maintaining a stateful session with the Web service provider. Most public services are stateless, as maintaining correct state information can be complex and expensive in terms of computational resources. If selected, enter a Connection ID value in the previous field.

The properties in this section hold status and exception information returned by the Connect-dotNET method. To map SOAP fault messages returned by the external web service to the clipboard, use the Faults tab.

The system places error details on a temporary clipboard page of the Log-Connect-Error class. , including the Status Value Property and Status Message Property.

Optional. Specify a Single Value Identifier property to hold the status code that the Connect-dotNET method returns. When you generate a connector rule with the Accelerator, this field is set to the standard property @baseclass.pyStatusValue. The literal value Good identifies success.

Optional. Specify a Single Value Text property to hold the status description for the status code that the Connect-dotNet method returns. When you generate a connector rule with the Accelerator, this field is set to the standard property @baseclass.pyStatusMessage.

Optional. Specify a property of mode Java Object to contain the exception object, if any are thrown during the execution of the connector.

C-1075 Optional. Identify a flow rule that is to be started when this connector rule is started by a flow rule but fails. The default flow rule Work-.ConnectionProblem provides one approach for handling such problems. See Handling connector exceptions.

After you complete and save this rule, you can test connectivity to the host of the Web service by clicking this button. This does not call the Web service.

Click to create a simulator for this connect rule. See Creating Connect Simulators.