Depending on the role of the server on which you are installing the pipeline, the following pipelines are the default configurations for the deployment. In the sections below, the required session agents are listed in the order of appearance in the pipeline.
Processing Server without HBR
For a Processing Server (Canister) without a Health-Based Routing (HBR) server in front of it, the following pipeline is the default pipeline.
Configuring the Transport Service:
- Drop data session agent
- Extended decouple session agent
- Inflate session agent
- Privacy session agent
- Reference session agent
- Canister session agent
Processing Server with HBR
For a Processing Server with an HBR server in front of it, the following pipeline is the default pipeline. When HBR is enabled, the HBR Server contains most of the processing session agents.
PrivacyEx) for child pipelines that have HBR enabled. If HBR and PrivacyEx are enabled for a child pipeline, the service can run out of memory and cause the service to restart unexpectedly. Configuring the Transport Service:
- Drop data session agent
- Extended decouple session agent
- Session router session agent
- Canister session agent
HBR Server
For the Health-Based Routing (HBR) Server in your environment, the following pipeline is the default configuration.
Configuring the Transport Service:
- Drop data session agent
- Extended decouple session agent
- Inflate session agent
- Privacy session agent
- Reference session agent
- Health-based routing (HBR) session agent