Skip to main content

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

Interface for inbound and outbound messages

Updated on March 4, 2022

Smart Investigate for Payments comes prepackaged with the ability to send and receive many different types of Fed Service and SWIFT messages, including all the common group messages as well as the primary payment message types.

Follow the steps below to set up the interface for inbound and outbound Fed Service and SWIFT messages. See PegaRULES Process Commander — Integrating with External Systems for additional interface information.

  1. Update theCLASSPATH. Add MQ Series Java components to the CLASSPATH environment variable of the Java container application hosting the Process Commander application. Two components must be referenced in the CLASSPATH variable:
    • connector.jar
  2. Get MQ Server details. You will need values for the information listed below. The values you enter must match your system values. Queue names can be anything you want to use for identification.
    • IP Address:
    • Host name:
    • Port:
    • Channel name:
    • Queue details:
    • Inbound: PRPC.SI.SB.INB1
    • Outbound:PRPC.SI.SB.OUTB1
  3. Configure the following records:
    1. For inbound messages, configure a connect MQServer rule (of type Data-Admin- Connect-MQServer). Smart Investigate for Payments comes with a sample instance named MQMessageSwitchServer. Update the fields with the values for your MQ environment. One server can process both Fed Service and SWIFT messages.

    2. For outbound messages, configure a connect MQ rule. The following figure shows a sample configuration for SWIFT messages. Configure one MQ rule for Fed Service messages and another for SWIFT messages.

    3. Configure a connect MQListener rule for inbound messages. Part of the record key for this record is the service name. This value must match the name of the MQServer instance you created in step 3. Smart Investigate for Payments comes with a sample instance named MyCoMQMessageSwitchListener.

  4. Update the following fields in this record:
    • Node Name — name of the node on which Smart Investigate for Payments has been installed.
    • Queue Name — name of the queue on your MQ server.
    • Queue Manager — name of your Queue Manage on your MQ server.
    • Password —The password as specified for the SwiftInboundAgent operator.
  5. Configure a service MQ instance to run an activity and begin processing inbound messages. The following figure shows an example. The Service Package, Service Class, and Service Method fields in the previous figure make up the key for the new instance. Complete the Primary Page and Service Activity sections. The service activity executes when the listener collects data.

Pega Smart Investigate for Payments Implementation Guide

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us