In order to activate overlay reports for your site, you
need to configure some security-related settings.
About this task
To allow connections with the report provider, you need to
configure the AJAX Proxy. Proceed as follows:Procedure
- Add the IBM® Coremetrics Web Analytics site
to the default dynamic policy. To do this, proceed with
the following steps:
- Open the WebSphere® Integrated Solutions Console.
- Click .
- Use the property name wp.proxy.config.urlreplacement.default_policy.1 and
the value https://welcome.coremetrics.com/* .
Note: If this name is already in use, increment the counter
of the key wp.proxy.config.urlreplacement.default_policy .
- Click Apply.
- Click Save.
- Import the Coremetrics certificate
into your server truststore. You can complete this step
either by using the wsadmin command retrieveSignerFromPort of
the AdminTask object, or manually as described here:
- Open the WebSphere Integrated Solutions Console.
- In a stand-alone enviroment: Click .
In a portal cluster environment: Click . By alternative, you can also select each node individually and apply the following
settings to each node in the cell.
- Fill the fields as follows:
- For the host: welcome.coremetrics.com
- For the port: 443
- For the alias: coremetrics or another identifying
string of your choice.
- Click Retrieve signer information.
- Click Apply.
- Click Save.
- Store your Coremetrics user
information in a credential vault slot as described under Configuring
credential vaults for overlay reports.
- Restart the portal server for the changes to take effect.
- Optional: If required, configure the limit
of outbound HTTP connections. The data for the overlay
reports is retrieved through the AJAX proxy. The AJAX proxy has a
configuration parameter for setting the maximum number of concurrent
outbound connections. This limit also affects the number of overlay
reports that can be retrieved from the Coremetrics API server concurrently.
If you want to have more overlay reports retrieved, configure the
limit as described under Configuration metadata for outbound
HTTP connections.
What to do next
Note: Additional to the limit set by the AJAX proxy, Coremetrics also enforces
a limit on the number of concurrent connections from the same host.
When that limit is reached, the portal displays message EJQGB0000E instead
of the overlay report. In this case the user can refresh the portal
page until the error message disappears; the successful analytics
results are cached in the browser.