Licensing

Obtaining Hardware ID for License

- Download the following License4J jar file
- Copy the file "LICENSE4J-HardwareID-Viewer.jar" to the machine you want to obtain the license for
- From the command line run:

java -jar LICENSE4J-HardwareID-Viewer.jar

- This will launch the app and display the hardware ID’s with output similar to

- Alternatively, to just print out to the terminal:

java -jar LICENSE4J-HardwareID-Viewer.jar display

- Or, print to a file

java -jar LICENSE4J-HardwareID-Viewer.jar display-debug filename

Install License

1. Stop StreamWeaver process
2. Replace the license file (or contents of the license) file: /opt/streamweaver/conf/licenses
3. Start StreamWeaver process

Pricing Metric

StreamWeaver pricing is computed by the number of Active Source System Instances and includes both “volume tapers” (the unit price per source decreases as the number of sources increase) and term discount options. Active Source System Instances equate to concurrent, non-named sources.

For example, a customer may have subscribed for 2 source licenses. In this scenario, the customer could have 10 source systems configured but only 2 sources can be active at any one time. Production, Staging, and Development licenses enable the ability to switch between Active Source System Instances without the need to re-license.

Active Source System Instances, examples:

2 AppDynamics instances = 2 sources (active at any one time)
1 AppDynamics + 1 Dynatrace instance = 2 sources (active at any one time)
2 CA APM instances + 1 Splunk instance + 2 SolarWinds Instances = 5 sources (active at any one time)

Types of Licenses

StreamWeaver currently supports three licensing types:

(1) Perpetual: traditional software vehicle providing a right-to-use license in perpetuity which can be accounted for as a depreciable Capital asset. Such licenses are accompanied by an annual maintenance fee.

(2) Term: provides a right-to-use license for a specified period. Term licenses are accounted for as an Operating Expense and do not have a separate maintenance fee component.

(3) SaaS: a subscription for a specified period. SaaS subscriptions are accounted for as an Operating Expense and do not have a separate maintenance fee component.

Licenses apply to usage of the Platform in production, development and staging environments, enabling the ability to switch between Active Source System Instances without the need to re-license.

Standard Packages

Term Commitments

StreamWeaver offers either a 1-year or 3-year subscription.

In exchange for a 3-Year subscription on Term Licenses (payment up-front), StreamWeaver offers a 33% discount (“buy 2 years ... get 1 year free”).

On Perpetual Licenses, customer can avoid annual increases in Maintenance fees by pre-purchasing up to 3-years of Maintenance at the initial Maintenance fee price which will not increase during the purchased term, excepting additional license purchases during the term.

Maintenance

StreamWeaver pricing contains a separate maintenance fee for Perpetual license offers (Term licenses and SaaS Subscriptions have Maintenance fees included in the pricing). The Maintenance fee covers after-delivery modifications to the StreamWeaver Platform designed to improve performance, availability, and usability. It includes Support (covered below), Requests for Enhancements (RFEs), software updates, and bug fixes.

The Maintenance fee is always calculated at 20% of the perpetual license cost and are incurred beginning the first year. The fee in-creases at a rate of 5% per renewal. Multi-year support contracts are available for up to 3 years providing no built-in increase.

Max Sources (per single instance)

Maximum number of Active Source System Instances authorized within the Package. For example, StreamWeaver Platform Premium Package has a limit of 20 Active Source System Instances; customers could have mediators built for 30 sources but only 20 would be permitted to run at any one time.

Adding Sources

Any time between the initial agreement and a renewal, customers can add source tools. If such a purchase changes the customer’s source-based pricing tier (example: 6-10) into another (example: 11-15), all sources would be priced from that point on at the new source-based tier (11-15).

Term license customers would pay a pro-rata portion of the difference in price for the remaining term. Customer with a Perpetual license would pay the difference in license cost, although, Maintenance fees would follow the same logic as above. The contract term for the added sources will run concurrently with the original agreement.

For example: customer initially purchases a 6-10 source-based tier license and decides a few months later to add 4 sources. The additional sources may push the customer into a new source-based tier (11-15 source-based tier). From the date of the additional purchase, all sources would be priced at the new source-based pricing tier. Upon contract renewal, assuming no changes, all sources would be priced at the 11-15 source-based tier price point.

Max Destinations (per single named instance)

Maximum number of destination instances authorized within the Package. Destinations are named, not concurrent.

Adding Destinations

Any time after the initial agreement, customers can add destination tools up to the limit defined in the Package.