Table of Contents

Connect HTTP form – Completing the Service tab


Only available versions of this content are shown in the dropdown

Use the Service tab to identify the external system with which this connector rule communicates.

Connect HTTP rules are deprecated. After an upgrade to Pega Platform 8.6 and later, you cannot create new Connect HTTP rules. However, existing Connect HTTP rules will continue to function. Use Connect REST rules instead. For more information, see Creating a REST integration by using the Create REST integration wizard.

Service properties

Field Description
Endpoint URL Enter the URL of the external system to which this rule connects.
This URL can change over time, or can change when you move between a test system and a production system. However, after the ruleset version containing this connector rule is locked, you cannot update this field. If your application needs to override the value in this field, complete the EndPointURL parameter of the Connect HTTP method in the connector activity that calls this connector rule.

This field supports the Global Resource Settings syntax (=PageName.PropertyName).

Resource path Enter the location in the WSDL that describes the operation.
HTTP method Select which HTTP method to use to send the string: GET or POST.
HTTP version Select a version compatible with the server that this connector is connecting to. As a best practice, because HTTP versions are backward compatible, set the HTTP version to the lowest known compatible version. For example, if it is not known whether the server is 1.1 compatible, set the connector HTTP Version to 1.0.
Request only When the HTTP method is set to POST, select to indicate that Pega Platform is to send the message and close the connection without waiting for a response.
Allow redirects Select to enable the connector to retry a request using a different service address.
Call is read-only Used for auditing of licensing, leave cleared in most cases.

Select this check box to to indicate that each use of this service is not to count as a service invocation under the terms of your license agreement.

Integration system

Select the integration system to use as the system of record.


Field Description
Use authentication If selected, Pega Platform includes authentication credentials in the HTTP header of the message.
If you open a Connect HTTP instance configured in a version prior to Version 6.2, the rule form will contain 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 will be replaced with the Authentication profile field populated with a new profile.
Authentication profile Required, if Use authentication is selected. Select the Authentication profile that contains the authentication details required by the remote service.

This field supports the Global Resource Settings syntax (=PageName.PropertyName). The default property name for this field is pyAuthenticationProfile.

Security settings

Configure the truststore and keystore settings to secure your connection with the external system.

Field Description
Truststore Select or create a truststore record that contains the server certificate to use in the TLS/SSL handshake.
Keystore Select or create a keystore record that stores the Pega Platform client's private/public key pair that is used by the server to authenticate the client.


Use the fields in this section only when the Request only field is cleared.

Field Description
Response timeout Optional. Enter the number of milliseconds after which this rule times out with a failure message if it does not receive a response. Enter zero or leave blank to wait indefinitely.

This field is disabled and ignored at run time when the Intended for field is set to queuing.

This field supports the Global Resource Settings syntax (=PageName.PropertyName). The default property name for this field is pyHTTPTimeout.

Maintain session Select to use HTTP token-passing as the mechanism for maintaining a stateful session with the Web service provider. If selected, enter a Connection ID value.

This field is disabled and ignored at run time when the Intended for field is set to queuing.

Connection ID Optional. If the external system uses HTTP token passing to maintain stateful session data between requests, you can use this field to specify that a group of logically related connectors are to share a single session. Enter an arbitrary text value in this field, and enter the same text value in the other HTTP connector rules that are to share the session data.

Error handling

Field Description
Status value property Optional. Select a property to hold the status code of the Connect HTTP method. You can use the standard property @baseclass.pyStatusValue. The literal value Good identifies success.
Status message property Optional. Select a property to hold status descriptions or return values from the external system returned by the Connect HTTP method. You can use the standard property @baseclass.pyStatusMessage.
Error handler flow Optional. Identify a flow rule to route work items that cannot continue in its current flow because this connector rule was unable to connect to the external system. The default flow rule Work-.ConnectionProblem provides one approach for handling such problems.

Processing options

You can allow connector requests from this Connect HTTP to be processed asynchronously in parallel with the calling activity, or in background by an agent. The mode of execution of each connector request is determined by the Execution mode parameter of the Connect HTTP method, as enabled by the values in these two fields.

Field Description
Intended for Optional. Select:
  • immediate execution — the HTTP connector executes synchronously; the calling activity waits for results.
  • queuing (response will not be available ) — the HTTP connector executes asynchronously, with calls placed in a queue. The calling activity continues without waiting for results.
    Must also be specified in the Connect-HTTP method
Request processor Optional. If you selected queuing for the Intended for field, identify here a Connect Request Processor data instance that defines the classes and other characteristics of the queued connector requests, and for which the ruleset key part matches the ruleset of this Connect HTTP rule.

Testing and simulations

Field Description
Test connectivity After you complete and save this rule, click this button to test whether Pega Platform can connect to the external system. Pega Platform verifies the connectivity to the service URL/endpoint. It does not confirm the ability to authenticate with the service.

The system presents test results in a separate window, identifying the parameters used in the test, the steps attempted, and the outcome of each step.

Simulations Click to create a simulator for this connect rule.
Did you find this content helpful?

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.