Enabling Elasticsearch Metrics to connect to a Component Pack server
For the Elasticsearch Metrics component to work with HCL 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
Procedure
-
If your single sign-on solution includes IBM Security Verify
Access (formerly Security Access Manager)r, 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 Verify Access, see Enabling single sign-on for Security Verify Access.
- For SiteMinder, see Enabling single sign-on for SiteMinder.
- For SPNEGO with SiteMinder, see Enabling SPNEGO single sign-on for SiteMinder.
-
In the LotusConnections-config.xml file, you must point to the
correct version of Elasticsearch by changing the value of
the following parameter to 7:
<genericProperty name="elasticsearch.eSmajorVersion">7</genericProperty>
For more information on making changes to the LotusConnections-config.xml file, see Editing configuration files.
-
Run the config_blue_metrics.py script as follows:
On the Connections Component Pack system, from the extractedFolder/microservices_connections/hybridcloud/support directory, call the script by running the following Linux command:
python config_blue_metrics.py --skipSslCertCheck true --pinkhost hostname.ibm.com
- You must use --skipSslCertCheck (set to true) on systems that use self-signed SSL certificates.
- Set --pinkhost to the FQDN of the Kubernetes master (this would be the fronting Kubernetes master load balancer or virtual IP in a HA environment).
- Use --namespace on an Connections Component Pack deployment where connections is not the Kubernetes namespace to use.
Here is a sample of the output from the script:
[Adminuser@Server127 ~]$ python config_blue_metrics.py --skipSslCertCheck true --pinkhost Server127.yourDomain.com Updating Metrics settings on: https://Server127.yourDomain.com/metricssc/configsetter {"c2.export.elasticsearch.baseurl7" : "https://Server127.swg.usma.ibm.com:30098"}
- Restart MetricsEventCapture and MetricsUI through the WebSphere Integrated Solutions Console.
-
To ensure a secure connection, retrieve the PKCS12 and CA Signer certificates by running the
following commands on the Component Pack master node:
kubectl get secret elasticsearch-7-secret -n connections -o=jsonpath="{.data['chain-ca\.pem']}" | base64 -d > chain-ca.pem kubectl get secret elasticsearch-7-secret -n connections -o=jsonpath="{.data['elasticsearch-metrics\.p12']}" | base64 -d > elasticsearch-metrics.p12
-
Copy the certificate files to the Deployment Manager in a common location readable and writable
by all WebSphere Application Server nodes.
For example, copy the 2 files chain-ca.pem and elasticsearch-metrics.p12 from the Component Pack master node to the following directory: /opt/IBM on the Deployment Manager.
-
Now configure Elasticsearch metrics within Connections by completing the following steps:
What to do next
Deploy Elasticsearch-based metrics for Connections as explained in Deploying Elasticsearch Metrics.