That's correct, it was a typo in my question, but my real configuration is correct and everthing is working as expected when I aggregate 2 services. But that's not what I want to do:
Do you know if it's possible to connect more than one NIP to an ADH via RSSL in order to publish on the same service without aggregating 2 different services? ie NIP1 and NIP2 both configured to publish on MYNIP.
Here are the results of my tests:
My question:
Do you know if it's possible to connect more than one NIP to an ADH via RSSL in order to publish on the same service? Or do I have to publish on two different services, then aggregate them via the ADH with this kind of configuration:
*adh*aggregateServiceList : MYNIP*adh*NIPUAT*nonInteractiveSourceList : MYNIP_A, MYNIP_B
Refer to ADH installation guide regarding Source Aggregation, the ADH can aggregate one or more publisher application services into a single server.
The configurations for aggregation services are:
*adh*aggregateServiceList : LOCAL_PUB, VALUE_PUB*adh*LOCAL_PUB*nonInteractiveSourceList : LOCAL_PUB*adh*VALUE_PUB*nonInteractiveSourceList : VALUE_A, VALUE_B, VALUE_C
From your configurations, the aggregation service is MYNIP but it uses NIPUAT in nonInteractiveSourceList configuration. The correct one should be:
*adh*aggregateServiceList : MYNIP*adh*MYNIP*nonInteractiveSourceList : MYNIP_A, MYNIP_B
With these configurations, the first NI provider should publish to MYNIP_A service while the second provider should publish to MYNIP_B service.
Typo:
Please try this one:
*adh*aggregateServiceList : MYNIP*adh*MYNIP*nonInteractiveSourceList : MYNIP
Each NIP must have an unique instance ID.
You may also set markGroupsSuspectOnPublisherDown to False so that the ADH will not generate group outage notification when publisher applications within the source list of an aggregate service go inactive. All items will remain in cache and the state of the items will remain unchanged.
*adh*MYNIP*markGroupsSuspectOnPublisherDown : False
This is working. Thanks a lot!
