Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Configuring synchronization with the Pega Process Fabric Hub

Updated on November 9, 2021

If you host your applications on Pega Platform version 8.1 or 8.2, ensure that queue processors and the AsyncProcessor requestor run correctly so that the Pega Process Fabric Hub can successfully synchronize data with your application.

Note: Configuring queue processors and the AsyncProcessor requestor applies only to applications that you host on Pega Platform versions 8.1 and 8.2. If you host your application on Pega Platform version 8.3 or later, omit configuring queue processors and the AsyncProcessor requestor, and continue with configuring OAuth 2.0 authentication. For more information, see Creating a secure connection with the Pega Process Fabric Hub by configuring OAuth 2.0 authentication.

Queue processors and the AsyncProcessor requestor synchronize assignments, operator to work queue mappings, and work queue metadata. After you install the Pega Process Fabric Hub connector component, your remote application includes the following queue processors:

  • pyPF_PublishAssignment
  • pyPF_PublishBulkAssignments
  • pyPF_PublishBulkOperators
  • pyPF_PublishBulkWorkQueues
Note: Because queue processor and requestor settings affect your entire Pega Platform instance, the configurations that you apply in one application also affect other applications in your environment.
  1. In the navigation pane of Dev Studio, click Records.
  2. Expand the SysAdmin category, and then click Requestor Type.
  3. In the list of requestor type instances, click the ASYNCPROCESSOR requestor type for the system that hosts your application.
    For example: Select the Asyncprocessor requestor type for the Pega system:
    AsyncProcessor type in the list of requestor types
    A list of requestor types that includes AsyncProcessor requestor type
  4. Define how the requestor type runs in the system:
    ChoicesActions
    Use an access group
    1. In the Define this requestor type list, select an Application-based Access Group.
    2. Click Add item.
    3. In the Access Group Name field, enter an access group from your application that you want to register with the Pega Process Fabric Hub.
    4. Make the application access group active by clicking the radio button next to the access group name.
      Result: The AsyncProcessor requestor type can communicate with the Pega Process Fabric Hub based on the access group, as in the following example:
      AsyncProcessor requestor type configurations based on access group
      Configurations for AsyncProcessor requestor type based on access group
    Use rulesets and roles
    1. In the Define this requestor type list, select list of RuleSets and Roles.
      Note: AsyncProcessor requestor type configuration that is based on rulesets and roles is deprecated. Use the rulesets and roles option only if your AsyncProcessor requestor type is already configured to support rulesets and roles.
    2. In the Starting rulesets column, create a list of rulesets by clicking Add row and entering the following rulesets in this order: Pega-ProCom:01-01, Pega-IntSvcs:01-01, Pega-WB:01-01, and Pega-RULES:01-01.
    3. Click Add row, and then add the Pega Process Fabric ruleset for a version that matches your version of Pega Platform.
      For example: For Pega Platform 8.1, enter Pega-ProcessFabric:08-01.
    4. In the Starting roles field, enter PegaRULES:AsyncProcessor.
      Result: The AsyncProcessor requestor type can communicate with the Pega Process Fabric Hub based on the list of rulesets, as shown in the following example:
      AsyncProcessor requestor type configurations based on rulesets and roles
      A list of rulesets and roles that support running of the AsyncProcessor requestor type.
  5. Click Save.
What to do next: Improve the security of the connection between your system and the Pega Process Fabric Hub. For more information, see Creating a secure connection with the Pega Process Fabric Hub by configuring OAuth 2.0 authentication.
    • Previous topic Configuring a token profile for a remote application
    • Next topic Creating a secure connection with the Pega Process Fabric Hub by configuring OAuth 2.0 authentication

    Have a question? Get answers now.

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

    Did you find this content helpful?

    Want to help us improve this content?

    We'd prefer it if you saw us at our best.

    Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

    Close Deprecation Notice
    Contact us