Skip to main content

Configuring a Subscription for an Offline Volume License

Subscription (modern) licenses are required to communicate with the Fluent License server, however we provide options ofor Pro and Flex licenses to be configured for offline usage in environments that cannot communicate with our license server.

note

If you are looking for information on Offline Pro Licenses, head over here

Advantages of an Offline Volume License

  • No communication to an external service from your system is necessary to process templates through a Fluent Engine. Some highly security sensitive industries disallow this type of communication.
  • Zero data transferred out of your network.

For more detailed information, please read about the Fluent License Server.

Disadvantages of an Offline Volume License

  • Updating offline license keys is a manual process.
  • A local usage server must be setup.
  • Manual usage reporting must be provided to our support team as required in your sales agreement.

Instructions for Setting Up Offline Pro Licenses

Before setting up Offline Licensing, you must make a support request to Windward. To submit a ticket please send an email to support@windward.net or visit our support site here.

  1. Follow instructions for setting up the offline license server
  2. You will then need to configure your engine or designer to point at the offline license server.
    -  For the Java Engine or RESTful engine (only the Java version of the RESTful engine is supported): add the property `local-report-usage-server={offline-license-server-url}` to your WindwardReports.properties file. Replace `{offline-license-server-url}` with the URL for your deployment of the offline license server.
    - For the .NET engine add this line to the WindwardReports section of your config file (app.config, web.config, ect). For example
    ```
    <WindwardReports>
    [[Other Values]]
    <add key="local-report-usage-server" value="{offline-license-server-url}"/>
    </WindwardReports>
    ```
    - For the Designer: Locate the Autotag2013.dll.config file (C:\"Program Files"\"Windward Studios"\Windward\AutoTag2013.dll.config) and add the same property as for the .NET engine above.
    note

    Replace {offline-license-server-url} with the URL for your offline license server, e.g. http://hotsname/, http://localhost:8080/, http://0.0.0.0/

  1. Restart the engine/designer to ensure the property is read and applied.
  2. Ensure you are using the Offline License Key provided by the store portal or Apryse Sales/Support.
  3. Output will automatically be added to the local storage of the usage server.
  4. When you are ready to send usage info to Apryse, you need to make a GET Request to the following endpoint: {offline-license-server-url}/vi/usage/{license-id}
    • The offline license server is designed not to return the same data from this end point more than once. If you wish to retrieve this same data again make a request to {offline-license-server-url}/vi/usage/archived
    • This will return a list of time stamps. Find the time stamp that matches when you made your previous request and make a GET request to {offline-license-server-url}/vi/usage/archived/{time-stamp}
  5. The response to this reqiuest can be saved as a json file and sent to Apryse as required in your sales contract.

::: Replace {license-id} with the id for your license. To find your License Id login to the licensing portal, and you will see it near your license. :::