ScriptX.Addon License Deployment
This page is all about how to deploy and use the ScriptX.Addon evaluation license. After a successful evaluation, deployment of your own license is very similar.
Please read all sections to familiarise yourself with the process and the common issues you might encounter but hopefully avoid.
The license : 09df1dc1-cba3-48a8-aebe-ef2f287b51cd
.. is the current evaluation license for ScriptX.Addon and ScriptX.Services.
This is revision 4 of the license and is valid from 15 June 2020 to 15 June 2021
and validates these root URLs:
with these features enabled:
- Advanced HTML Printing, Direct/RAW Printing, PDF Printing, Enhanced HTML Formatting,
The url of interest for the evaluation license is "localhost". It enables you to fully evaluate all the features available with ScriptX with content served from a local server such as IIS Express, Node.js, Tomcat etc.
The other urls show where else we at MeadCo use this license and illustrate how a publisher license might look.
This license is fully compatible with ScriptX.Services (automatic, silent acceptance of the license is enabled).
The license file
The license is provided in a file which needs to be downloaded by MeadCo Security Manager.
In preference, client PCs should download the file from your own content server(s). So, the first job is to download the license file:
After download, copy the license file to a suitable content folder on the server for your web application.
For ease of system maintenance it is preferable to a have single current copy of sxlic.mlf located centrally. The file does not have to reside at a licensed address, simply, all client PCs must be able to access and download the file. Also see Recommended binary & license file location.
We strongly recommend against renaming the file to, for example, include a revision number. Renaming will almost certainly cause issues in the future when the license is updated/renewed.
MeadCo License Warehouse
Alternatively and subject to there being no abuse of the facility and client PCs have access to the public internet then the license can be downloaded from the License Warehouse. See below for details on how to do this.
MeadCo's Security Manager component is installed on the user's machine as part of the ScriptX.Add-on installation process.
The Security Manager add-on is embedded into a page of web content by the page author. It references the MeadCo publishing license which is located on the publisher's web server.
If ScriptX.Add-on is not yet deployed, download the latest version (22.214.171.124) of the ScriptX.Add-on installer (smsx.cab):
After download, copy smsx.cab to a suitable content folder on the server for your web application.
Nothing should be ‘installed’ on your servers - they are simply used as file storage for smsx.cab (the binaries) and sxlic.mlf (your unique publishing license).
Coding a document to use ScriptX.Addon
Include these objects on any page that uses ScriptX.Addon with this html:
Where [your path here] is a place holder for the path to your content folder(s) on your server where the .mlf and .cab files are located - see the note below for use of License Warehouse for the .mlf file.
- The unique MeadCo publishing license provided by MeadCo.
The location of the license file (.mlf) on a self hosting content server (it can be relative to the owning document) or, if client PCs have access to the public Internet, and subject to no abuse use a value of:
for client PCs to download the license from MeadCo License Warehouse.
- The current revision of the license. If this value is later than the currently cached license the the download will be forced - in otherwords this is the means to ensure a valid updated license is used.
- For those who remember the days of Windows 98 or Windows 2000 everything was installed as "administrator" and this was a default in ScriptX too until ScriptX 7. This parameter forced the use of 'PerUser' acceptance of licenses when the value is "true", but this has been the default since ScriptX 7 and so the value of "false" is required to force 'per machine' acceptance of the license. On Windows XP and later this will give rise to an elevation prompt.
- The version number of ScriptX.Addon required. The latest version is 8,3,0,4. If you have not downloaded the latest version, continue to use the version you have deployed.
Additional details are available on ScriptX.Addon Deployment
Having done that, you are ready to go and write html and script on the page to implement and evaluate a fully controlled print work-flow.
You must use a server on "localhost" for your content but the server my be Node based, Apache, IIS - anything.
These articles are a good starting point:
This section describes problems you may encouter and how to resolve them. If you canot resolve an issue then please contact our support team via email. All licensees are entitled to unlimited email based support for the duration of license.
Any issues will be either:
- There was a problem downloading the license.
- The license could not be verified and validated.
- The license is being used in an invalid context.
In each case, an error dialog will be displayed to the user, including an error code.
Issues with download
|800c0005||This error usually occurs when a bad location is given for the license file, in other words the value of the "path" parameter is wrong. To trouble shoot this, try navigating to the value used (adjusting for relative values) and ensuire that the .mlf file is downloaded by the browser.|
If the license file is served from IIS on Windows Server 2003/2008 or later then this error can occur because IIS on these systems IIS will only serve files with types that have registered MIME types. To resolve the issue, define a MIME type for the ".mlf" file type (application/octet-stream is recommended).
This error may occur if you are accessing the web application using https: and you have enabled the Internet Explorer option "Do not save encrypted pages to disk". Please see this Microsoft Support page for information on how to disable this option. Please note that once you have successfully accepted the license you can enable the option again.
A related issue can affect the use of https: with IE 8 and earlier if the server requests that the downloaded file is cached. Please see Internet Explorer Cannot Download https://something by Eric Law for a discussion of this problem.
This error may also occur when a bad location is given for the license file. See the description/advice for the error 800c0005.
|800c000b||This error means the internet connection timed out; no response was received from the web server in a reasonable time. The problem may be an intermittent one so try loading the page you were viewing again. If it still fails check your network/internet connection. If the connection is fine and other documents load fine, please contact the administrator of the web site you are using.|
Issues with license validation
This error means the license could not be fully validated.
If the license has been issued recently then this is caused by changes in validation processes that have been made in order to increase security.
To resolve this issue, update to ScriptX 7.7 or later and preferably to the latest version: 126.96.36.199
Additional troubleshooting is available by using the 'Report this issue to Mead & Company' link on the error dialog and we will assist. Alternatively please contact us for additional assistance.
Invalid HTML parameters specified for the license.
When working with the evaluation please note that the only valid domain is "localhost". If you are using "localhost" and this error occurs, please use the 'Report this issue to Mead & Company' link on the error dialog and we will assist. Alternatively please contact us for additional assistance.
Issues with context
All licenses contain a list of domains/paths that are valid origins/locations for content wishing to use ScriptX features.
If the error is "Unauthorized site, or invalid security zone" then the origin being used is not listed in the license.