Commercial License

English | 简体中文

Applies to DecisioWorks v1.4.0

Commercial License

The Commercial Edition uses license.rkey to control authorization level, validity period, resource limits, and available capabilities. The file is created through the formal issuance process from a device request. Source visibility supports understanding, integration, and extension; it does not remove commercial licensing and authorization requirements.

Standard flow

1. Generate a license-request JSON on the target device and in the intended runtime environment.
2. Send the complete request JSON to the issuer. Do not manually change hardware, platform, or runtime values.
3. The issuer validates the request and creates license.rkey.
4. Place the file in the location specified by the distribution, normally the distribution root.
5. Start the Web cockpit or runtime entry and check status, level, expiry, and resource limits.
6. Run a SolverReady dataset to confirm that the license supports real controlled solving, not only file discovery.

The request JSON filename is not fixed. Identify each request by its contents, source device, and generation time so that files from different customers, devices, or environments are not mixed.

Use and migration notes

• Authorization may depend on the device, platform, Python version, or protected runtime component. Do not assume that an environment issued for Linux can be moved to Windows or another device unchanged.
• Solving time, thread count, and functional scope are determined by the active authorization state and displayed limits.
• Before changing the operating system, Python version, hardware, or distribution, confirm whether a new request is required.
• Do not edit the internal content of license.rkey or repackage it.

Validation checklist

• Status is valid rather than a preselected edition label.
• Level, expiry, thread limit, and solving-time limit match the issuance record.
• A normal dataset completes a real run.
• Out-of-scope use returns an explicit error rather than silently falling back.
• Expired, device-mismatched, and damaged-file negative cases are blocked.

Support information

Include authorization status, error code, distribution version, operating system, Python version, request generation time, and necessary diagnostics. Limit production data and logs to the redacted material required for diagnosis.

See Quick Start and Security and Support.