Adding the TickerTracker CDD and Configure Settings

Procedure

  1. Right-click the Deployments folder, select New > Cluster Deployment Descriptor, and click Next.
  2. In the File Name field of the New Cluster Configuration Wizard, type the name TickerTracker and click Next. You see the Object Manager Selection page of the wizard. In the Object Management Type field, select Cache and click Finish.
  3. Select the Collections tab and do the following:
    1. Select Input Destinations and click Add.
    2. In the Input Destinations Collection field (on the right), type Http and again click Add. The Select Input Destinations dialog appears.
    3. In the Select Input Destinations dialog, select /Channels/HTTP/AllOps and click OK. A Configuration panel appears.
    4. In the Input Destination ID field, type AllOperations, replacing the generated ID.
    5. In the Preprocessor field, select /RuleFunctions/PreProcessor.
  4. Select the Agent Classes bottom tab and expand the inference-class agent node on the left
  5. Select Input Destination Collections and click Add. You see the Select Input Destinations dialog. In the Reference Collections area, select Http and click OK.
  6. Still in the Agent Classes tab, configure a dashboard agent as follows:
    1. Click Add Agent. The New Agent Class window appears.

      In the Agent Class Name field, type dashboard-class.

      In the Agent Class Type field, select Dashboard.

      Click OK.

    2. In the tree on the left, select the dashboard-class agent you created. Its configuration panel displays on the right. In the Personalized Data Location field, type the following: 
            BE_HOME/examples/views/TickerTracker/personalizeddata

      You can substitute another location accessible to the dashboard agent as desired.

    3. In the Properties panel, add the following properties and their values:
      Property Value
      be.auth.type file
      be.auth.file.location BE_HOME/examples/views/FraudDetectionDashboard/config/users.pwd
      be.agent.dashboard.hostname localhost
      be.agent.dashboard.pullrequestport 9191 (As needed: the default is 8181)
  7. Click the Processing Units tab and do the following:
    1. Select the default processing unit, on the left.
    2. Check the Enable Cache Storage checkbox.
    3. In the Agents section, add the dashboard-class agent.
      Note: The Enable Cache Storage option lets you store cache data in non-cache agent processing units. In production environments, however, only use cache agents to store cache data. (Their processing units use this setting by default and it is not configurable.)
  8. Save and close the resource.