The CX Pipeline is composed of a series of modules that you enable and configure to perform a specific set of operations on captured data.
Each module, called a session agent, performs a specific manipulation on the captured data and forwards it to the next session agent. At the end of a CX pipeline, a terminal agent performs final pipeline disposition of the session data, which may include forwarding to a Short Term Canister (canister in the diagram below), to an archive, to another port on the server for processing by a different pipeline, or to the NULL session agent, which discards the data.
After traffic has been captured by the CX Passive Capture Application, it is forwarded to the Processing Server, where captured data is passed into the pipeline. Data is passed from one session agent to the next one in the pipeline, with each agent performing one or more manipulations on the data. The output of session agent #1 is the input of session agent #2.
Note: The DOM Capture Virtual Hit session agent is needed only if you are going to perform DOM capture. Additionally, if you decide to perform DOM capture, the DOM Capture Virtual Hit session agent must be configured after the Inflate session agent and before the Privacy session agent.
Tealeaf session agents in the pipeline can modify the data with no effects on the visitor.