Infrastructure Services landing page

Access this landing page by selecting the > Decisioning > Infrastructure > Services  menu item.

The Services configuration allows you to define the connection between PRPC and the servers running Adaptive Decision Manager and Visual Business Director. These settings are necessary so that you can perform the actions that require system interaction with the runtime (configuring adaptive model rules if the fail safe option is disabled, performing adaptive model management activities, using the VBD Planner and accessing adaptive model reports). However, with the exception adaptive model rules if the fail safe option is disabled, it is not required when defining Decision Management rules.

This page has two sections:

• Adaptive Decision Manager
• Visual Business Director

Available in applications that have access to the Decision Management rule sets through Application Rulesets or PegaDM as Built on Application.

Define the connection

Typically, the configuration in this landing page is part of the installation process that allows applications to operate with Decision Management functionality. If you do not have ADM or VBD, leave the host and port fields empty.

To define the connection to the Decision Management services:

1. Log in to the Designer Studio as the PRPC system architect user defined for your Decision Management enabled application.
2. Open the Infrastructure Services landing page and define connection and operational settings for Adaptive Decision Manager and Visual Business Director as explained in the sections below.
3. After defining or changing the necessary settings click Save to save the settings or Save & Ping to save the settings and test the connection to the Decision Management services.

The version of the client library displays at the top and the corresponding server library displays in the Status message for each service. The version follows this pattern:

<Major Version>.<Minor Version>.<Revision>.<Build Number>

Saving settings activates changes in the Decision Management service layer and in PRPC. If you have not configured the service end point(s), the propagation of data to the corresponding service(s) is turned off.

Adaptive Decision Manager

In this section you can:

• Check in the Agents section whether the UpdateAdaptiveModels agent in the Pega-DecisionEngine RuleSet is running. If it is not, start it.
• Define the name of the server in the Host field and the port number in the Port field.
• Enable the Fail Safe option, which is disabled by default. Enabling it activates ADM's fail safe mechanism (preventing loss of responses in case of ADM unavailability). If you enable this option, make sure the database data instance necessary for ADM to operate in this mode exists and that it is configured appropriately:
  • Create a new database instance named PegaADM.
  • Configure the Connection Types as follows:
    • Use JDBC Connection Pool - Recommended. In the server running PRPC, make sure you have the jdbc/admDataSource. If using a single server, the data source was configured in the process of installing ADM. Typically (in production environments), ADM and PRPC are running on different servers: you need to configure this data source in the server running PRPC.
    • Use JDBC URL - Configure the JDBC URL to point to the database containing the ADM schema and provide valid credentials to access the ADM schema.
• Configure the operation settings that affect capturing historical data for reporting purposes. In the snapshot settings for capturing model state and predictor binning, the first option (Unlimited) is required if leveraging model snapshots for time-based reporting (for example, trend detection).
  • The Data Mart Agent field shows the status of the ADMSnapshot agent (disabled, or enabled). Click the link to open the Pega-DecisionEngine's Agent Schedule data instance where, if applicable, you can change the time interval for triggering the agent (by default, it is 120 seconds) and enable or disable the agent. To avoid duplicate snapshots, make sure there is only one node enabled to run the ADMSnapshot agent when working in a multinode PRPC environment.
  • The date and time of the most recent snapshot are displayed. Click New Snapshot if you want the reports to be based on a newer view of the models and predictors in the ADM system.
  • The Model Snapshots options define how the state of the models at a particular point in time is captured and saved. Select Unlimited to never discard snapshots or Most recent to keep only the most recent state.
  • The Predictor Binning Snapshots options define how the state of the binning of predictors at a particular point in time is captured and saved. Select Unlimited to never discard snapshots, Most recent to keep only the most recent state, or None to disable capturing the state of the predictor binning.
    Note: predictor binning snapshots can lead to generating large volumes of data.

Additional settings affect ADM. These settings are in the Agents section:

• PRPC keeps a local cache of scoring models. Scoring model updates are regularly retrieved from the adaptive data store. The model update frequency is implemented by periodically triggering the UpdateAdaptiveModels agent (Pega-DecisionEngine RuleSet, PegaDM:Administrators access group). The agent runs the pxUpdateModels activity to retrieve model updates. By default, the agent is scheduled to run every 30 seconds. The agent only retrieves scoring models required for executing the strategy and the models that are different from those in the local cache.
  • The ADM Update Agent field shows the status of the UpdateAdaptiveModels agent. If the agent is disabled, the Start Agent button allows you to start the agent.
  • In the Adaptive Model Update Interval field, you can change the time interval.

  Check the Entitled to Use Adaptive Decision Manager checkbox if your software license agreement includes ADM's capability to use predictive data (that is, the ability to define predictors in adaptive model rules).

Visual Business Director

In this section, define the name of the server in the Host field and the port number in the Port field.