Skip Navigation
  1. BlackBerry Docs
  2. BlackBerry AtHoc
  3. BlackBerry AtHoc Integrations
  4. CAP Publishing and Processing Guide
  5. Processing CAP events
  6. Configure the AtHoc CAP Event Processor and CAP Feed Poller Agents
  7. Set up the AtHoc CAP Event Processor agent configuration

Set up the
AtHoc
 CAP Event Processor agent configuration

  1. Change to the
    System Setup (3)
     organization.
  2. In the navigation bar, click The Settings icon.
  3. In the
    System Setup
     section, click
    Integration Manager
    .
  4. On the
    Integration Manager
     screen, click
    Cap Event Processor
    .
  5. Edit the XML in the
    Configuration
     field.
    Add the provider ID for the organization that needs the CAP Event Poller to be enabled. You can enable the agent for multiple organizations by adding their provider ID and event types.
    <CapEventProcessor xmlns="" maxDegreeOfParallelism="10" ignoreDuplicateTimeInterval="30">
            <providers>
             <provider id="
    your-provider-id
    ">
              <eventRules>
               <eventRule eventType="SG-ACTIVATION">
                <xpathQuery value="/alert/info/parameter[./valueName/text()='EventName']/value" />
                <eventMappings>
                <eventMapping eventName="E06995893A7P615ON" scenarioCommonName="ABCD" />
                </eventMappings>
              </eventRule>
             </eventRules>
            </provider>
           </providers>
          </CapEventProcessor>
  6. Switch to the organization where you enabled the agent.
  7. In the navigation bar, click The Settings icon.
  8. In the
    System Setup
     section, click
    Integration Manager
    .
  9. On the
    Integration Manager
     screen, click
    Cap Event Processor
    .
  10. Add event rules to enable the agent for multiple event types: 
    //For eventName “Tornado Warning”

     <eventRules>
       <eventRule eventType="SG-ACTIVATION">
         <xpathQuery value="/alert/info/parameter[./valueName/text()='EventName']/value" />
         <eventMappings>
          <eventMapping eventName="E06995893A7P615ON" scenarioCommonName="11475b17-47fb-4cc2-8a11-e678dcad38cb" />
         </eventMappings>
        </eventRule>
        <eventRule eventType="IPAWS">
          <xpathQuery value="//geocode[concat(valueName/text(),value/text()) = 'UGCANZ530']/../../event/text()" />
          <eventMappings>
            <eventMapping eventName="Tornado Warning" scenarioCommonName="ed41b1b7-acb4-443e-9f17-f67a93275b44" />
          </eventMappings>
         </eventRule>
        </eventRules>
    //For eventName “HoneywellCAP”

      <eventRules>
        <eventRule eventType="HoneywellCAP">
          <xpathQuery value="/alert/code" />
          <eventMappings>
            <eventMapping eventName="Fire1" scenarioCommonName="95a15f05-1723-4657-a800-c5a523045329" />
          </eventMappings>
        </eventRule>
        <eventRule eventType="SG-ACTIVATION">
          <xpathQuery value="/alert/info/parameter[./valueName/text()='EventName']/value" />
          <eventMappings>
            <eventMapping eventName="QUIET_TEST" scenarioCommonName="95a15f05-1723-4657-a800-c5a523045329" />
          </eventMappings>
        </eventRule>
      </eventRules>
    //For eventName “Special Weather Statement”

      <eventRules>
        <eventRule eventType="IPAWS">
          <xpathQuery value="//geocode[concat(valueName/text(),value/text()) = 'UGCTXZ138']/../../event/text()" />
          <eventMappings>
            <eventMapping eventName="Special Weather Statement" scenarioCommonName="WEATHER-ALERT" />
          </eventMappings>
        </eventRule>
        <eventRule eventType="SG-ACTIVATION">
          <xpathQuery value="/alert/info/parameter[./valueName/text()='EventName']/value" />
          <eventMappings>
            <eventMapping eventName="PUSH_TEST" scenarioCommonName="f4746947-f3be-42bb-a2d5-498e1a750ecd" />
          </eventMappings>
        </eventRule>
      </eventRules>
  11. Create an alert template. Copy the common name of the alert template.
  12. Configure the required placeholders in the alert template. For more information, see Configure placeholders on the BlackBerry AtHoc system.
  13. Update the configuration with the correct event name, geocode, county (if applicable), and the common name of the new alert template created in Step 11.
    The scenario common name and the alert template common name are the same.
    For detailed information about how to locate the geocode of a county, see Geocodes and counties.
    </eventRules>
       <eventRule eventType="IPAWS">
              <xpathQuery value="//geocode[concat(valueName/text(),value/text()) =
'UGCANZ53O']/../../event/text()"/>
             <eventMappings>
                   <eventMapping eventName="Hurricane Warning"
scenarioCommonName="9a52be39-b2ef-4f6b-af72-6dfa53ab714b"/>
                   <eventMapping eventName="Tornado Warning"
scenarioCommonName="9a52be39-b2ef-4f6b-af72-6dfa53ab714b"/>
             </eventMappings>
</eventRule>
     <eventRule eventType="HoneywellCAP">
            <xpathQuery value="/alert/code"/>
            <eventMappings>
                    <eventMapping eventName="Fire1"
scenarioCommonName="b32O358c-bd11-4ddO-bO5b-7f71b5ee4f1b"/>
             </eventMappings>
</eventRule>
       </eventRule eventType="SG-ACTIVATION">
       <xpathQuery value-"alert/info/parameter[/valueName/text()='EventName']/value"/>
              <eventMappings>
                     <eventMapping eventName="HE-1A-TEST"
scenarioCommonName="O3df8OO4-599O-4603-9fa6-5cO66d296fa"/>
                   <eventMapping eventName="PUSH-TEST"
scenarioCommonName="Od4O2e3f-2a5e-4509-a579-e6dda53OO73e"/>
             <eventMappings>
        </eventRule>
</eventRules>
               </provider>
       </providers>
</inboundEventsProcessor>