Deploy multiple traffic managers with load balance data publisher failover data receiver pattern.

Sending all the events to several receivers

This setup involves sending all the events to more than one Traffic Manager receiver. This approach is mainly followed when you use other servers to analyze events together with Traffic Manager servers. You can use this functionality to publish the same event to both servers at the same time. This will be useful to perform real time analytics with CEP and to persist the data, and also to perform complex analysis with DAS in nearly real time with the same data.

Similar to load balancing between a set of servers, in this scenario you need to modify the Data Agent URL. You should include all DAS/CEP receiver URLs within curly braces ({}) separated with commas as shown below.

<DataPublisher>

           <Enabled>true</Enabled>

           <Type>Binary</Type>

<ReceiverUrlGroup>{tcp://127.0.0.1:9612},{tcp://127.0.0.1:9613} </ReceiverUrlGroup>

<AuthUrlGroup>{ssl://127.0.0.1:9712},{ssl://127.0.0.1:9713}</AuthUrlGroup>

           <!--AuthUrlGroup>ssl://${carbon.local.ip}:9712</AuthUrlGroup-->

           <Username>${admin.username}</Username>

           <Password>${admin.password}</Password>

           <DataPublisherPool>

               <MaxIdle>1000</MaxIdle>

               <InitIdleCapacity>200</InitIdleCapacity>

           </DataPublisherPool>

           <DataPublisherThreadPool>

               <CorePoolSize>200</CorePoolSize>

               <MaxmimumPoolSize>1000</MaxmimumPoolSize>

               <KeepAliveTime>200</KeepAliveTime>

           </DataPublisherThreadPool>

       </DataPublisher>