License File Management (LFM)

Use License File Management (LFM) to view, edit, and deploy license files for your license servers. LFM centralizes license file management so you can test changes safely, track history, and keep license servers consistent.

What you can do with LFM

• View all license files in one place. LFM collects license files from Broker Hub and shows you the latest version.
• Work safely with drafts. Create a draft, edit the license text, and save changes without touching the active file.
• Deploy changes with control. Push a draft to one Broker or to all Brokers in a triad cluster.
• Track history. Review past versions of license files and drafts for up to two months.
• Stay informed. Get alerts if deployments fail or if a draft is rejected.

Overview

• Without triad: Deploy changes to a single Broker.
• With triad: Deploy the same license file to all three Brokers for redundancy. If one server fails, the others continue to serve licenses.
• Draft-first workflow: You always work with drafts before pushing changes to production.
• Automation: LFM integrates with Broker Hub and communicates over Kafka to send updates.
• Audit and alerts: LFM stores change history in the database (retained for two months) and integrates with audit and alert services.

info

Files changed directly on the local machine are detected automatically.
The Broker periodically sends updates to Broker Hub, so LFM stays in sync.

Viewing license files

• LFM automatically retrieves license files from Broker Hub.
• You can see the current file text, history, and whether a draft exists.

Creating a draft

1. Open the license file you want to modify.
2. Start a new draft.
3. Enter or edit the license file text.
4. Save the draft as many times as needed.

tip

You can compare a draft with the original file.
Differences are highlighted for clarity.

Deploying a draft

If your Broker is not in a triad

1. Open your draft.
2. Click Push Draft.
3. The draft replaces the old file on that broker.

If your Broker is in a triad

1. Open your draft.
2. Click Push Draft.
3. The draft replaces the file on all three Brokers in the cluster.

caution

For triads, file paths must match across all Brokers.
If file paths differ, deployment will fail.

Deployment notes

• Status awareness. LFM does not check if Brokers are up before sending. Failures are reported afterward.
• Error handling. If a Broker cannot apply the file, the error appears in the deployment response.

Tracking changes

• License file history: Stores older versions whenever a file is updated or deleted.
• Draft history: Records pushed drafts, including text, time, and status.
• Audit service: Notes and push events are logged for traceability.
• Alerts: If a deployment fails, LFM notifies you.

Example scenario

You need to update a vendor license file:

1. Open the license file in LFM.
2. Create a draft.
3. Edit or paste the new license text.
4. Save the draft until you are ready.
5. Push the draft:
   • If single Broker → file updates directly.
   • If triad → file updates across all three Brokers.
6. Review deployment results and alerts.