SOAP Connector Form
Completing the Advanced tab
|
|
Use the Advanced tab to change which version of Axis or SOAP is used, to associate a compensating action with the connector, to specify the model rules that define the schema, and to enable Web Service Security for the connector.
The Process Commander SOAP connector architecture uses an Axis client to make the SOAP call and process the SOAP response. Use the fields in this section to specify settings for the Axis client.
Field |
Description |
| Axis Version |
Connect SOAP rules created in V5.5 or later use AXIS version 2. |
| SOAP Version |
|
| HTTP Version |
Because HTTP Versions are backward compatible, it is recommended to set the HTTP Version to the lowest known compatible version. For example, if it is not known if the server is 1.1 compatible, set the connector HTTP Version to 1.0. |
Field | Description |
| Use Authentication? | If selected, authentication credentials are included in the HTTP header of the SOAP request message. If your application requires SOAP headers that conform to a WS-Security format rather than using HTTP Basic/NTLMv1 authentication, you can define such header contents using the Request tab. |
| Authentication Profile | Required. If Use Authentication? is selected, select the Authentication Profile that contains the authentication details required by the remote service. |
C-500 If you used the Connector and Metadata accelerator
to generate the SOAP connector rule and the WSDL file of the Web
service contains a schema description with complex types, this section
of the Advanced tab specifies the model
rules that define the schema of the incoming and outgoing XML objects.
(Typically, this indicates that the SOAP operation style is
document-literal.)
On the Request and Response tabs, the Data Type of the
XML objects described by the models specified on this tab is set to
XML Page.
Field |
Description |
| Page Key |
|
| Class Name |
|
| Model Name |
In most cases, the generated model specified in this field is appropriate. However, the generated models list every property in the class; you may not want to map a value for every property in the class. If you do not need all the properties, create a new model that specifies the properties to map in the order they are to be mapped. Then select that model rule in this field. |
Optional. Use the Compensating
Action and Compensating Action Data section
of this tab to associate a compensating action with a work object when
the connector rule succeeds. For more information, see 
Using Compensating Actions, a document on the
Integration section of the Pega Developer Network.
Field |
Description |
| Work Page Name |
C-766 R-11238 Optional. Specify the name the page
that holds the work object. Typically this is
|
| Action Label |
Optional. Enter a string that describes the purpose of the compensating action. For example, "Cancels Flight Reservation." PublicAPI methods can use this label to identify this compensating action within a Java step of an activity. |
| Action Activity Class |
|
| Action Activity Name |
|
| Compensating Action Data |
Click the none button and enter the name of a parameter used by the compensating action activity. Then, in the value field, select the property that is to be the source of the parameter value. |
Client
Properties
Specify which version of the SOAP specification is
implemented by the Web service this connector communicates
with. If you used the Accelerator to generate this connector,
it is set to 
Identify the clipboard page
that contains the data values to be mapped to or from the XML
object.