Configure the Platform Analytics Project for High Throughput or Advanced Architecture

The Platform Analytics project must be created via one of the Intelligence server nodes in a cluster, connecting to the repository, which is machine 7 in this example.

• Create a Platform Analytics Project Using the Configuration Wizard

• Load Object Telemetry to the Platform Analytics Data Repository

• Load Project on Other Nodes

• Troubleshooting

Create a Platform Analytics Project Using the Configuration Wizard

1. Open the Configuration wizard on your Intelligence server.

2. On the Welcome screen, select Create Platform Analytics project.

   

3. In DSN, choose the Platform Analytics repository. If DSN does not appear, click New to create a new DSN linking to the Platform Analytics repository of your choice. In this example, you are connecting to the repository on machine 6.

4. Enter your credentials for the database.

5. Click Next.

   

6. Click Apply. The Configuration wizard automatically applies the following configuration files:

   • PlatformAnalyticsConfigurationNew.scp

   • PlatformAnalyticsConfigurationNew_PostgreSQL.scp

   • PlatformAnalyticsConfigurationUpgrade.scp

   • PlatformAnalyticsConfigurationUpgrade_PostgreSQL.scp

7. If an error appears about being unable to automatically apply project settings to Platform Analytics, you must manually update the project settings. See Platform Analytics Project Configuration Scripts for more information.

There is no need to re-create the Platform Analytics project via the remaining Intelligence server nodes (machine 2, 3, and 4) since you are connecting to the same metadata for a clustered environment. You only need to load the Platform Analytics project into Intelligence server memory for the remaining nodes.

Load Project on Other Nodes

Repeat the following steps for machines 2, 3, and 4.

1. Launch Developer.

2. Navigate to Administration > System Administration > Project > PlatformAnalytics > Administer Project > Load.

   The PA project loads and is ready to use.

   

Troubleshooting

If Apache ZooKeeper cannot be restarted, ensure Kafka is fully configured.

1. Open the kafka-logs folder located in C:\Program Files (x86)\MicroStrategy\Messaging Services\tmp.

2. Open the myid file and ensure the broker.id is the same as it appears in server.properties. If they are different, this may be why Apache ZooKeeper is not starting.

3. If there is no telemetry in the Kafka topics, check if statistics are enabled for Platform Analytics projects by running the following command in Command Manager:

   Copy

   LIST ALL PROPERTIES FOR PASTATISTICS IN PROJECT "Platform Analytics";

4. If the command returns False, run:

   Copy

   ALTER PASTATISTICS BASICSTATS ENABLED DETAILEDREPJOBS TRUE DETAILEDDOCJOBS TRUE JOBSQL TRUE COLUMNSTABLES TRUE IN PROJECT "Platform Analytics";

   BASICSTATS must always be enabled. Select what kind of advanced stats are needed by changing the parameter after it to true/false. See List Platform Analytics Statistics Properties Statement for more information about basic versus advanced statistics.