Configuring the Elasticsearch Metrics component

Configure the Elasticsearch offering of the Component Pack for IBM Connections™ to provide Metrics data.

After you have configured Elasticsearch, review the topic on Backing up and restoring data for Elasticsearch-based components

Removing SSL settings that were configured for type-ahead search
Temporarily remove SSL settings that were configured for type-ahead search in an IBM Connections deployment, so that you can successfully enable Metrics.
Granting access to global Elasticsearch Metrics
Configure the metrics-report-run security role to grant users the authority to view and interact with global metrics.
Granting access to Elasticsearch Metrics for communities
Configure the community-metrics-run security role to grant users the authority to view community metrics using static reports.
Changing the number of shards for the Elasticsearch Metrics index
If your environment requires, you can change the default number of shards that will be assigned to the Elasticsearch Metrics index when it is created.
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.
Deploying Elasticsearch Metrics as your first use of metrics
Deploying Elasticsearch-based metrics for IBM Connections™ involves testing the environment and then switching users to the Elasticsearch Metrics component.
Deploying Elasticsearch Metrics with the data migrated from the metrics relational database
If you previously used Cognos® to provide Metrics data for your IBM Connections™ deployment, Metrics events data is stored in your RDBMS, while older data is stored in the Cognos Power Cube. You can deploy Elasticsearch Metrics with the existing Metrics events data in your RDBMS. The procedure involves migrating the events data, testing the environment, and then switching users to the Elasticsearch Metrics component.

Parent topic: Configuring the Component Pack