Running the Pulse Demo Utility

Running the Pulse Demo Utility

This guide will show you how to execute the Pulse demo data utility. The demo data is intended for demonstration and training purposes only.

Do not run this utility on a production server, as it makes extensive updates to the database that are difficult to reverse.

Before executing the utility, please go through the prerequisites carefully

Download the utility

For Pulse v7.3.0 and lower, use pulse-demo-v2.0.0

For Pulse v8.0.1 and above, use pulse-demo-v3.0.0

What you can demo with the utility

The utility builds a realistic Pulse environment on your own machine. It creates two TM1 instances, dev and fin, loads them with about 30 minutes' worth of past activity, and can also generate live activity so there is something happening on screen during a demo.

Commands

Command

What it does

Command

What it does

pulse-demo-utility.exe -i

Creates the dev and fin TM1 instances.

pulse-demo-utility.exe -d

Fills in past data. Takes about 30 minutes, or longer on a slower laptop. Setting the Pulse OpenSearch JVM to 2 GB speeds it up.

pulse-demo-utility.exe -f

Generates live activity on the dev instance, such as processes running, so the monitor shows real-time movement.

What you can show once past data is loaded (-d)

  • User sessions: who has been connecting. Go to Reports > User Analytics > User Sessions.

  • Change tracking: a full change history on dev. Go to Change Tracking > Change History > Dev, select General Ledger.RUX and click History to see every change made to the General Ledger rules.

  • Pulse Explorer dashboards: there are 10 default dashboards. Select 7 days of data for the best results. Good ones to start with:

    • Pulse – User – License Report: who uses the application and which tools they use.

    • Pulse – Chore / Process History: past chore and process executions.

    • Pulse – Errors Analysis: errors across all applications.

What you can show live (-f)

  • A wait in real time: right after running -f, open the TI process Cub.GeneralLedger.Demo.pro and make a small edit, such as adding a comment. This locks the object and creates a wait.

  • A wait alert by email: if a Wait Alert is set up, it fires after about 15 seconds and sends an email. Make sure SMTP is configured correctly in your local Pulse installation.

  • Finding the source of a wait: in Dashboard > Pulse – Live Monitor, set the range to the last 24 hours, zoom into the Wait Time chart, filter to the dev instance, then zoom in again to where the wait starts. The waiting thread shows in red and the thread holding the lock shows in blue.

Step-by-step guides