Background Color:
 
Background Pattern:
Reset
Search
Home Recent Changes Show All Pages

Which License?

Not Rated Yet

There are a range of options available, when it comes to licensing scryber. If you are looking into it, and want to understand what your options are, then this post should help you

Contents

 

Why should I even get a license?

scryber is free, and it is also open source under LGPL. This means you can use it and link to it from your commercial applications and sites. But it does put the badge on each of your pages.

If your project or application is also open source, or you are happy to keep the badge on any generated documents, then by all means continue to use the library without a license. The more people know that you are using scryber, the better for us!

However, if you or your users and customers want to see their pages in full without the badge, then you should get yourself a license.

 

So which license will I need?

As mentioned, there a range of options for licensing scryber, and the first decision is based on your type of product(s)

If it is a web based application running from one or more web-servers, then we can support that with a Domain or server license

If it is an executable or set of executables that run locally on a users machine then you will be looking for an Application or executable license

 

Domain or server licenses

 

So let's suppose you have 2 domains (a main domain and 1 sub domain) being hosted by 3 web-servers and 2 more fail-over servers (physical or virtual)

 

 

We have 2 choices - license each machine, or license the domains. In this scenario it makes most sense to license the domains. So all we need to do is add 2 domain licenses to our basket with the domains identified as subsite.mysite.com and www.mysite.com

 

 

Where does my web license file go?

A single scryber license file (which will be called scryber.components.lic) will be sent back to you within 24 hours that will cover both domains within that file .This eases the administration and maintenance of the license.

Simply drop that license in the bin folders of the virtual directories where the scryber dlls reside, and it will automatically be picked up by the libraries after an app pool recycle

 

 

If new machines are added to the farm, or replaced, the same license files can be used and will cover these domains too.

However - if you want to add a new domain to these servers, then you will need to extend an existing license

 

Many Domains, few servers

But what if you have a lot of hosted sites, but only a couple of severs for a low traffic local intranet for example, and you need to regularly add sites/domains to these servers. This is a different scenario, and would be difficult to maintain as domain licenses.

 

 

For this model it is more appropriate for a 2 x  machine license, which will cover both machines and any websites running on these machines.

Again, a single scryber license file (which will be called scryber.components.lic) will be sent back to you within 24 hours of purchase, that will cover all domains served from the specified machines, and any domains that are added.

Simply drop that license in the bin folders of the virtual directories where the scryber dlls reside, and it will automatically be picked up by the libraries after an app pool recycle. (see where)

If you and or replace a machine, then you will need buy another license, or extend your existing license.

 

Large farms or gardens

 

If you are running more than 5 web applications, and more than 5 servers we do offer discounts for a bulk of 10 domains or servers, and might work out cheaper for you. We need to fill then all in one go, and they cannot be freely extended at a later date with more servers or domains, but if you do the math and it works out - go for it.

 

 

Application or executable license

 

Deploying an executable application on millions of users devices? Or just running a bunch of reporting service from a couple of machines. Then your options will be an executable license, or possibly just machine license.

 

 

If you have one or more applications that are running on users machines then the choice is really a simple one. You will need one or more executable licenses.

All you need to do is choose the quantity of applications this license should cover, and fill in the names of the application(s) including the extension in the details before adding to your basket.

 

Where does my application license file go?

A single scryber license file (which will be called scryber.components.lic) will be sent back to you within 24 hours that will cover both domains within that file .This eases the administration and maintenance of the license.

Simply drop that license in the executable folder where the scryber dlls and your exe reside, and it will automatically be picked up the next time the application is launched.

 

 

 

Checking a license File

 

If for some reason you want to know what is in your current license file or you want to extend your existing license, then it is easy to check - as it is in essence an XML file

 

 

As you can see there the actual terms and sig(nature) of the license which are encrypted and if modified will break your license file. And after this there are 2 pertinent bits of information

ID
This is the unique identifier for your license. Each license has this included in the file, and as part of the encrypted token. You will need this to extend your license to cover other applications or sites.
Coverage-Notes
The coverage gives a summary of the actual license terms. There will be one or possibly more than one Grant element that details the domains / executables / machines that are included in the license. There is one version element that has the minimum and maximum versions of the libraries that are covered - this is an inclusive range, so in the example version 0.9.9.0 will be covered, but version 0.9.9.1 will not. And finally will be an expiration date - this is normally set to 10 years, if at this point you are still using the library within the version range detailed, no charge and thank you for your continued support :-)
If you do change any of the information here, it will not change the actual terms of the license, or extend the supported license. If will simply not match the actual terms, and may cause you problems later on. We would suggest you do not modify

 

Adding a license without using a file.

 

Sometimes it is not appropriate (or possible) to set a file within the assembly directory. In this case the license details must be assigned explicitly in the application or site code before any pdf’s are generated.

This is simple to do by calling the SetLicense static (shared) method on the Scryber.Licensing class with the text details that are contained in the license file, and the type(s) that are being licensed. For the core library the type is Scryber.Components.PDFPage.
Simply open the .lic file in a text editor to view the contents. Copy all the contents of the file and add them as a string in your application that you can pass to the SetLicense method.


 

Extending your License

Keeping all your licenses together in a single file is important for you and for us. At the moment if you need to extend your file, then please add this to the description field when adding items to the basket, including your ID from the existing license file contents and we will re-issue a new file. We are looking to support this more easily in the near future

 



  Rating
Rate This Page: Poor Great   |  Rate Content |
Average rating:  No Ratings Yet   
Number of Ratings : 0
  Comments
Add Comment
James R
What is the right license for Azure Websites? What would be the machine name in an azure website setup.... Now that Azure is mainstream some kind of solution for that would be interesting,
Posted At 22-07-2015 16:13:59