More about Connect Java rules

Calling activity

A Java connector is invoked from 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 in a flow rule.

When you use the Connector wizard, the wizard generates a connector activity. You may need to fine-tune settings or steps in the generated rule. If you create a Java connector manually, you must also create the connector activity.

Connector activities have the following kinds of steps:

  • A step that creates a named page for the class that the connector rule applies to. This page becomes the primary page for the connector.
  • A step that sets property values and input parameter values that serve as the input for the connector's invocation of the external application or Java class.
  • A step that calls the connector rule. This step uses the Connect-Java method. The step page is the primary page of the connector.
  • A step that processes the data that the connector rule receives.

Performance statistics

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

Simulation and testing

To debug your application before the Java connector is working, you can simulate a Java connector when the external system is unavailable or lacks a test environment. Create an instance of the Data-Admin-IS-Services class and appropriate simulation activities.

For more information on testing connectors, see Testing Services and Connectors, a document available on the Integration pages of the Pega Community.

Calling a Windows DLL

This rule type is useful when your application needs to call a capability provided by a Windows DLL. See How to call a Windows DLL Library.