A request and its matching response are bundled together as a hit in the CX Passive Capture Application. After the PCA captures a hit, it is forwarded to the Transport Service or the Health-Based Routing machine for disposition to the appropriate Short Term Canister.
After the hit is stored in Canister memory, it is passed through each of the sequential session agents in the pipeline until the final or terminal session agent completes the processing. The Experience Analytics pipeline is a configurable set of Windows-based pipelines composed of a sequence of agents, each of which performs data manipulation and processing of hits.
Hits in the Transport Service or HBR
After a request has been matched with the corresponding response and passed through the PCA internal pipeline, the PCA forwards the bundled hit to the Windows™ servers for processing.
Depending on your Experience Analytics deployment, the receiver can be either of the following:
- Transport Service - This service receives hits from the PCA and manages their processing through the Windows pipeline.
- Health-Based Router - In multi-Canister deployments, HBR can be deployed to manage spooling and load balancing between Canisters. You can monitor the status of HBR through the System Status page in the Portal.
At the top of the Windows pipeline, the Extended Decoupler session agent manages the rate at which hits are fed into the pipeline.
- Through the Portal, you can monitor the status of the session agent through the System Status page.
- The Extended Decoupler session agent can be configured to send statistics hits for insertion into the Experience Analytics database, where they are aggregated for reporting.
You can monitor the activities of the Windows pipeline and the aggregated hit statistics of content being passed through individual session agents through TMS.
In the Pipeline Status tab, you can review current statistics on hit counts and data size as content is passed through each session agent.
Short term canister
After a hit has been successfully processed through the Windows pipeline, it is retained in the Short Term Canister, an in-memory database where hits from active sessions are accumulated until the session is closed.
Long term canister
When a session is closed by user exit, session timeout setting, or event, the session is moved from the STC to the Long Term Canister (LTC), which is a disk-based database of sessions. Sessions in the LTC are marked for indexing, which is executed as a separate process at predefined intervals. Indexing can be monitored through the Canister Status report in the System Status page.
Sessions are stored in the Long Term Canister for a predefined number of days. Depending on data volumes of your site, you may need to monitor the current day's storage volume and anticipated storage requirements for the time period in which sessions are stored in the LTC.
Sessions in the LTC can be searched through the Portal and RTV. Reporting on search effectiveness is available for user groups. cxReveal users can review dashboard charts on search effectiveness.