Back ForwardMore about HTTP connector rules

About Connect HTTP rules
XXXXXXXXXXXXXXXXXX mention binary attachments support GRP-5257-1.

Calling activity

An HTTP connector is called by a connector activity — an activity with the Activity Type set to Connect that applies to a class derived from the Work- base class. Such activities can be referenced in an Integrator shape (Integrator) in a flow rule.

Connector activities have the following kinds of steps:

Asynchronous execution by the Pega-IntSvcs agents

To perform HTTP connector processing asynchronously: 5.5 GRP-255

  1. Create a Connector Request Processor data instance that defines the characteristics and classes of queued requests. Associate this data instance with the RuleSet that contains the Connect HTTP rules.
  2. On the Service tab of the Connect HTTP rule, select queuing in the Intended for field and identify the Connector Request Processor created in step 1. Leave the Response tab blank; it is not used.
  3. Update one or more Data-Agent-Queue instances to ensure that the ProcessConnectQueue agent entry within the Pega-IntSvcs agent is enabled with an appropriate time period.
  4. In the activity steps that execute the Connect-HTTP method, set the Execution Mode parameter value to Queue.
  5. Test.

Performance Statistics

For information on gathering performance information about this connector see PDNTesting Services and Connectors, a document on the Integration pages of the Pega Developer Network.

Simulation and debugging

You can simulate an HTTP connector when the external system is unavailable or when you need to test an application but lack a test environment.

For more information on testing connectors, see PDNTesting Services and Connectors, a document on the Integration pages of the Pega Developer Network.

Related topicsCreating Connector Simulations
Connect-HTTP method
How to detect lengthy connector executions

UpAbout Connect HTTP rules