Enabling Elasticsearch Metrics to connect to a Component Pack server
For the Elasticsearch Metrics component to work with IBM Connections Component Pack, you must run a script on the Component Pack system to set the Elasticsearch server base URL in Highway. Also, WebSphere Application Server, which hosts the Metrics component, must run Java 8 and use an SSL client certificate when sending HTTPS requests to Elasticsearch on the Component Pack system.
Before you begin
Important: Elasticsearch Metrics
requires that the WebSphere Application Server is running Java 8. If you have a new Filenet
deployment and you temporarily switched to Java 6 to update Filenet components after applying
Connections 6.0 CR1, make sure that you switch back to Java 8 before you start the following
procedure.
Procedure
-
If your single sign-on solution includes IBM Security Access Manager, SiteMinder, or SPNEGO
with SiteMinder, update the URLs that require basic authentication to include
/metricssc/configsetter by referring to the appropriate topic:
- For IBM Security Access Manager, see Enabling single sign-on for IBM Security Access Manager.
- For SiteMinder, see Enabling single sign-on for SiteMinder.
- For SPNEGO with SiteMinder, see Enabling SPNEGO single sign-on for SiteMinder.
-
Run the configuration script as follows:
- Restart MetricsEventCapture and MetricsUI through the wasadmin console.
-
To ensure a secure connection, retrieve the PKCS12 and CA Signer certificates from these
locations on the Component Pack server:
/opt/elasticsearch/elasticsearch-metrics.p12
/opt/elasticsearch/ca/chain-ca.pem
- Copy the certificate files to the Deployment Manager in a common location readable and writable by all WebSphere Application Server nodes.
-
Now, run some wsadmin commands:
- Copy the updated elasticsearch-metrics.p12 file from the Deployment Manager to the common location on the WebSphere Application Server nodes.