Mock TSSA

A stand-in TrueSight Server Automation server you run on your own computer, so you can demo and test BMC Helix Automation Console without a real TSSA install.

Unofficial community test tool. Not made, endorsed or supported by BMC. It contains fake servers and fake data, and doesn't manage anything real.

Quick start

You need Node.js 18 or later. Nothing else has to be installed by hand.

Windows

  1. Download the ZIP and unzip it.
  2. Double-click start-windows.bat.
  3. If SmartScreen appears, choose More info, then Run anyway.

macOS

  1. Download the ZIP and unzip it.
  2. Control-click start-macos.command, choose Open, then confirm.
  3. If that's blocked, open Terminal in the folder and run bash start-macos.command.

The first run downloads cloudflared from Cloudflare, starts the mock and opens the console at http://localhost:9842. The window then shows the host name to give HAC. Press Ctrl+C in that window to stop.

To run it locally with no tunnel and no download:

node start.js --no-tunnel

Connect Helix Automation Console

Configure the connector in HAC first, then download and run it. Use a sandbox or demo tenant: the mock's 24 fake servers are added to whatever assets HAC already has.

  1. Start the mock and note the Host Name in its window.
  2. In HAC, go to Configuration > Connectors and click Add a Connector.
  3. Choose the Server Automation Connector type and click Create.
  4. Fill in the values below and save.
  5. Download the connector package HAC gives you and unzip it on a computer with Java.
  6. Run run.bat on Windows, or run.sh on macOS or Linux.
  7. Check that the connector shows Running under Configuration > Connectors.
  8. Open API Inspector in the mock console to watch every call arrive.
HAC fieldValue
Truesight Server Automation Host NameThe Host Name from the mock's window
Truesight Server Automation Application Port443 (9843 if you're not using the tunnel)
Truesight Server Automation Role NameBLAdmins
Truesight Server Automation Version26.3.00.130
User Name / PasswordBLAdmin / password (test values for the mock only)
RoleBLAdmins
Authentication MethodSecure Remote Password
Collection Mode10 minutes

Already have a connector? Open its Action menu, choose Edit, enter these values and click Update. Write down the old values first so you can switch back.

The tunnel's address is public while the mock runs, and the mock has default credentials. Use it for test data only, and stop it when you've finished. The tunnel host can change after a restart. If it does, change Host Name with Action > Edit, restart the connector and click Update.

What you can do

Patch policies

Under Manage > Patch Policies, use Execute Now, wait for the run, then click Sync. HAC shows the scan run, asset status, logs and the dashboard's Patch tab. Create a remediation operation to install patches.

Compliance

Under Manage > Compliance Scan Policies, create a policy from a template such as CIS - Windows Server 2022, then Execute Now and Sync. You get asset rule counts, each asset's rules, logs and the dashboard's Compliance tab.

To fix findings, select the policy on the Compliance tab and click Remediate. After that operation runs, a new scan shows those servers as compliant. Undo compliance remediation under Settings in the mock console resets this for the next demo.

Ad hoc jobs

Under Operations > Create Operation > Adhoc Job Selections, pick from 15 NSH script jobs, 7 deploy jobs and 5 batch jobs. HAC schedules Execute Now about 90 seconds ahead.

The mock console

Browse servers, depot content, catalogs, jobs and live job logs. Under Settings you can change run speed and the failure rate, or reset all data.

What works

AreaStatusNotes
Patch scan, results, logs, dashboardWorksNeeds Sync after each run. HAC gets at most 250 patch rows per run.
Patch remediation operationsWorksReally removes the patches from the mock's data.
Compliance scans and dashboardWorksAn asset's rule list shows sample rules, so it won't match the full counts.
Compliance remediationWorksTested through HAC's Remediate flow.
Ad hoc NSH and batch operationsWorksBatch results appear under each member job.
Ad hoc deploy operationsPartlyThey create and run, but Sync fails, so HAC stays at Awaiting Execution.
Per-host patch countsShows 0The asset table's Missing and Installed columns stay 0. Open an asset to see its patches.
Daily, weekly and monthly schedulesNot runThey save and display, but only one-time schedules and Execute Now run.
Automatic results without SyncNot yetHAC rejects the run-finished callback. Auto-Sync below is the workaround.

Tested on Windows against one HAC 26.3 tenant. The macOS launcher hasn't been run on a Mac yet.

Auto-Sync

HAC doesn't show a run's results until someone clicks Sync. The HAC Auto-Sync page in the mock console gives you a script to paste into the browser console of a signed-in HAC tab. It calls Sync every 30 seconds while that tab stays open, and stops after 8 hours. If your HAC session expires, reload HAC and paste it again.

Options

SettingDefaultWhat it does
MOCK_HTTP_PORT9842Console port
MOCK_HTTPS_PORT9843TSSA API port
MOCK_TUNNELcloudflareoff disables the tunnel
MOCK_TUNNEL_TOKENnoneUse a named Cloudflare tunnel, which keeps a fixed host
MOCK_CONNECTOR_ZIPnewest in DownloadsConnector zip for the built-in Helix worker

The README has every setting and the full list of API shapes HAC expects.

Troubleshooting

"Node.js is required"

Install the LTS version from nodejs.org, then start again.

HAC can't reach the mock

VPNs can block the tunnel. Run node server.js --stop-tunnel, start the mock again, and enter the new host in HAC.

A run finished but HAC shows nothing

Click Sync, or use Auto-Sync. If a compliance Sync fails, HAC keeps that run's partial data, so start a new run.

Start over

Use Settings > Reset all data in the mock console.