How to Use MetaLAN License Manager Import Tool: Step-by-Step
Overview
The MetaLAN License Manager Import Tool migrates or imports license records (keys, activations, entitlements) into a MetaLAN License Manager instance from CSV or other supported formats. This guide assumes CSV input and a running MetaLAN License Manager server accessible to you.
Prerequisites
- Access: Admin account for the MetaLAN License Manager with import privileges.
- Backup: Export or snapshot existing license data before importing.
- CSV file: Properly formatted CSV (UTF-8) with headers matching import fields.
- Network: Connectivity to the MetaLAN server and necessary firewall ports open.
- Tool: MetaLAN Import Tool binary or script installed on your workstation or server.
- Dependencies: Any required runtime (e.g., Java, Python) installed.
Step 1 — Prepare CSV (required columns)
-
Ensure UTF-8 encoding.
-
Include at minimum these columns (adjust to your schema):
- license_key
- product_id
- license_type (perpetual, subscription)
- issued_to (customer identifier or email)
- issue_date (YYYY-MM-DD)
- expiry_date (YYYY-MM-DD or blank for perpetual)
- activationsallowed (integer)
- notes (optional)
-
Validate dates and numeric fields; remove duplicates.
-
Save as .csv.
Step 2 — Test with a small sample
- Create a CSV containing 5–20 records representing typical variations (perpetual, expiring, different products).
- Run the import tool in “dry-run” or “validate-only” mode (if available) to check parsing and mapping without modifying the database.
Step 3 — Configure import settings
- Set target environment (staging or production).
- Map CSV headers to MetaLAN fields if the tool requires manual mapping.
- Choose conflict handling: skip, overwrite, or append. Prefer skip or append for initial imports.
- Enable logging and set log file path.
- Set batch size (e.g., 500–2000 rows) to balance performance and memory.
Step 4 — Run import
Command example (adjust to your tool):
Code
metalan-import –file licenses.csv –env staging –map map.json –mode dry-run –batch 1000 –log import.log
- Remove
–mode dry-runto perform actual import. - Monitor console output and import.log.
Step 5 — Verify results
- Check import logs for errors/warnings.
- Query MetaLAN License Manager for a sample of imported records to confirm fields, dates, and activations.
- Verify counts: expected vs imported.
- Spot-check license activation flow by performing a test activation for at least one imported license.
Step 6 — Post-import tasks
- Reconcile and resolve any records skipped or errored.
- Re-run import for corrected rows (use conflict policy to avoid duplicates).
- Notify stakeholders and update inventory documentation.
- Keep import logs and the original CSV securely stored for audit.
Troubleshooting (common issues)
- Encoding errors: Re-save CSV as UTF-8, remove BOM.
- Date parsing failures: Ensure ISO format (YYYY-MM-DD) or set parser format.
- Duplicate keys: Use “skip” or pre-run dedupe script.
- Timeouts: Reduce batch size or increase tool/server timeouts.
- Permission denied: Confirm admin credentials and API keys.
Quick checklist
- Backup taken ✅
- CSV validated ✅
- Dry-run successful ✅
- Logs enabled ✅
- Post-import verification done ✅
If you want, I can generate a CSV template or a sample import command tailored to your MetaLAN tool version and environment; tell me your environment (OS, tool CLI name, MetaLAN version).
Leave a Reply