Take the following steps to configure target routing.
1. Create a rule to route to the notifications target group by setting Path is to /connect/X_DataDirect_Notification_Server.
Note: For load balancers that support routing with HTTP headers, the header X-DataDirect-OPC-Host:X_DataDirect_Notification_Server should be used.
2. For each node running the Hybrid Data Pipeline service, create a rule to route to the corresponding on-premises access target by setting Path is to /connect/<opa_routing_key>.
Note: The format of the <opa_routing_key> is opa_<hosturl>_<opaport> where <hosturl> is the hostname specified during installation with dot characters replaced by underscores, and <opaport> is the On-Premises Access port number. For example, the routing key for nc-d2c02.americas.test.com on port 40501 would be opa_nc-d2c73_americas_test_com_40501.
3. Create a default routing rule. The Forward to attribute should be set to the Hybrid Data Pipeline service API target group.
Important: Setting the default rule for routing requests to the Hybrid Data Pipeline service API must be completed after creating the rules for routing to the On-Premises Access and Notifications servers.
