Comment 12 for bug 484094

A "majority opinion" of T4Bi developers is that this looks very similar to a problem GHO experienced a few weeks ago - resolved John Rawlinson and Steve Moore, by changing the parameters required by the Indicator Metadata Registry.

We had previously hard-coded the parameters used when calling that service (from the Flex client) but moved them into the Flex config.xml, which is now generated from /who_gho/deployments/config_templates/WAR_config.xml, and uses the following 2 metadata-related settings:

 <flexProxy_olapMetadataServlet>/OlapMetadata</flexProxy_olapMetadataServlet>
 <flexProxy_externalIndicatorMetadataServlet>/ExternalIndicatorMetadata</flexProxy_externalIndicatorMetadataServlet>