Basically, we're talking asking about 1: load balancing and 2: DR/contingency (fail-over) with regard to DRAS.
1: Web Viewer currently supports load-balancing at the repository level. Users, upon repository selection, are randomly connected to one of the associated DRAS repositories (if more than one is assigned). If a particular DRAS repository is not available, Web Viewer automatically tries a different one.
2: Although DRAS can load balance/fail-over at the repository level, there is no such provision when the defined primary LPAR fails, in that it cannot balance/fail-over if the target CCI system or the primary (license/web login) DRAS task are down (or their LPAR is down). These are set in the configuration files (CCIClient.properties and WVProfile.properties) for each Web Viewer instance.
Note: Some customers have implemented DR procedures to quickly (hopefully) switch to a functioning LPAR. Basically, they swap the configuration files (CCIClient.properties and WVProfile.properties) to point to a different LPAR/DRAS task & recycle the web server. They then reverse the procedure after they recover from the disaster.