Installing and Configuring the Persistent Mobile Foundation Analytics Server

Overview

The PMF Analytics Server is delivered as two separate WAR files. For convenience in deploying on WebSphere Application Server Liberty, PMF Analytics Server is also delivered as an EAR file that contains the two WAR files.

Note: Do not install more than one instance of PMF Analytics Server on a single host machine. For more information about managing your cluster, see the Elasticsearch documentation.

The analytics WAR and EAR files are included with the Persistent Mobile Foundation Server installation. For more information, see Distribution structure of PMF Server. When you deploy the WAR file, the PMF Analytics Console is available at: http://<hostname>:<port>/analytics/console, for example: http://localhost:9080/analytics/console.

Prerequisites

  1. Create the config.properties file at preferred location and add below variables in it:

    allowed.hostname= 
maximum.request=20 
time.window=1 

    Where,

    allowed.hostname - This property indicates single/list of whitelisted servers those are granted to send request to the application. If multiple whitelisting is needed, then each server name should be separated by comma.

    Example

    allowed.hostname= localhost, 127.0.0.1

    Above configuration would allow analytics to work only on localhost or the IP mentioned, all other request received other than the mentioned would be rejected. If no value is provided, then the default considered server name for whitelisting would be localhost.

    maximum.request and time.window - This property indicates maximum number of invalid login attempts those are granted in a configured time interval defined in a property time.window. That means if request count is set as 20 and time windows is set as 1, then 19 invalid login attempts would be allowed in a 1 minute. Post 19 requests unless configured time window of 1 minute doesn’t gets lapsed, user will not be allowed to login even with correct credentials.

  2. Create a configMap and provide a full file path of the config.properties file.

    Example

    export CONFIGURATION_FILE_PATH=/opt/config.properties

    Make sure this variable is available on a system as environment otherwise Analytics will not be able to identify user configuration and continue to run on default settings.

  3. Whenever you make any changes to properties file, restart of server instance is must to reflect the updates.

▲
Last modified on