Applying Production License for ReportFactory Lite

Overview

ReportFactory Lite runs in Always FREE mode by default, which limits usage to 15 requests per hour with automatic counter reset. To unlock unlimited report generation for production use, you need to apply a production license.

Always FREE Mode Limitations

When deployed without a production license, ReportFactory Lite operates with the following restrictions:

  • Maximum 15 report generation requests per hour

  • Counter automatically resets every hour

  • All functionality available for evaluation purposes

License Application Process

For New Customers

  1. Place Purchase Order
  • Contact Maathra sales team to place a purchase order
  1. Payment Processing
  • Complete payment as per purchase order terms

  • Wait for payment confirmation from Maathra

  1. Request License
  • After payment confirmation, proceed to license request step

For Existing ReportFactory Customers

Existing customers using the previous ReportFactory version can request ReportFactory Lite licenses directly without placing a new purchase order.

License Request Steps

Step 1: Obtain Unique Instance ID

  1. Access the Unique Key Endpoint Navigate to your ReportFactory Lite instance:
    https://your-server.com/report-factory-lite/unique-key

  2. Copy the Unique ID The system will display a unique identifier similar to:
    02-00-17-00-13-3A

  3. This ID is specific to your installation and server environment.

Step 2: Submit License Request

  1. Send Email to Maathra
  1. Include Required Information
  • Your unique instance ID (e.g., 02-00-17-00-13-3A)

  • Company name and contact information

  • Purchase order number (for new customers)

  • Existing customer reference (for upgrade customers)

Step 3: Receive License Key

Maathra will generate and send you a license key similar to: C/JSjL9/OIsPfeG364pzui+2breTDNeYp4UXVsTWO2w=

License Installation

Step 1: Locate Configuration File

Navigate to the ReportFactory Lite configuration directory:
Tomcat-Directory>/webapps/report-factory-lite/WEB-INF/classes

Step 2: Edit Application Properties

  1. Open application.properties file in a text editor

  2. Add the license key by adding the following line:
    app.license-key=C/JSjK9/OIsPfeG564pzui+2breTDNeYp4ULVsTWO2w=

  3. Sample application.properties file

    spring.application.name=report-factory-lite
    # API Key
    app.api-key=C3E91D6B7A2F549E80DCCB6F
    
    # Report locations
    app.report.template-location=/opt/tomcat9/arflite/templates/
    app.report.output-location=/opt/tomcat9/arflite/reports/
    app.report.delete-after-generation=Y
    
    # security
    app.aes.encryption-key=A3F67C9D8E0B2451F68C3E91D6B7A2F549E80DCCB6F1E392A3D5C7F8421B6D3E
    app.aes.encryption-iv=F1B27498D2E3A6C75089F4BA3D65C2E7
    app.aes.enabled=0
    
    app.license-key=C/JSjK9/OIsPfeG564pzui+2breTDNeYp4ULVsTWO2w=
    

Step 3: Restart Server

  1. Stop Tomcat server

  2. Start Tomcat server

  3. Verify the application loads correctly

License Verification

Check License Status

After restart, verify that the production license is active:

  1. Monitor server logs for license activation messages

  2. Test report generation beyond the 15-request trial limit

  3. Verify unlimited report generation capability

Troubleshooting

License Not Recognized

  • Verify the license key is copied correctly without extra spaces

  • Ensure the unique instance ID provided matches your server

  • Restart Tomcat after making configuration changes

Invalid License Error

  • Confirm you're using the correct license key for your instance

  • Check that the unique ID hasn't changed due to hardware modifications

  • Contact support if the issue persists

Important Notes

  • One license per server instance: Each ReportFactory Lite installation requires a separate license

  • Hardware binding: Licenses are tied to the unique instance ID of your server

  • License portability: Contact Maathra support if you need to migrate to different hardware

  • Backup recommendations: Keep a copy of your license key in a secure location

Updated on