Deploy ScriptX.Add‑on for FREE
The basic features of ScriptX.Add‑on are available for no charge, for example, the ability to specify print headers and footers, margins and orientation. You are free to deploy the binaries provided to your servers on your intranet or the public internet.
Deploy ScriptX.Add‑on with a publishing license
A paid-for publishing license is provided to registered customers. This unlocks the full power of ScriptX.Add‑on from your own root URLs. Your publishing license will work with every existing and future version of ScriptX.Add‑on, and by request can be extended to include ScriptX.Services. It does not have to be updated when the ScriptX software is updated. All publishing licenses are renewable and valid for one or more years.
Deploy ScriptX.Add‑on for FREE
The basic features of ScriptX.Add‑on are available for no charge. This includes for example the ability to specify print headers and footers, margins and orientation. You are free to deploy the binaries provided to your servers on your intranet or the public internet.
Browser-based deployment
You will need:
- or
smsx.cab should be copied to a suitable location on your web server(s), then include this object on your pages:
<!-- MeadCo ScriptX -->
<object id="factory" viewastext style="display:none"
classid="clsid:1663ed61-23eb-11d2-b92f-008048fdd814"
codebase="http://[your_path]/smsx.cab#Version=8,3,0,4">
</object>
or, if you wish to make use of MeadCo's version of the IE7 ‘scale to fit’ print template, independent of your user's version of Internet Explorer, do this:
<!-- MeadCo ScriptX -->
<object id="factory" viewastext style="display:none"
classid="clsid:1663ed61-23eb-11d2-b92f-008048fdd814"
codebase="http://[your_path]/smsx.cab#Version=8,3,0,4">
<param name="template" value="MeadCo://IE7" />
</object>
where [your-path] is a placeholder for the location of smsx.cab on your own servers.
The <object> code shown above should appear on ALL your ScriptX‑enabled pages, including those dynamically created on the server via ASP Classic, ASP.NET, PHP etc. You cannot use CreateObject or new ActiveXObject to call ScriptX client‑side.
When scripting, you should call ScriptX in all cases by the ID of the ScriptX object on the page - in the above example ‘factory’.
Administrator pre-install
Alternatively you may wish to pre-install ScriptX.Add‑on over an intranet, in which case you will need:
- or
A local administrator should run ScriptX.msi on each client machine on your intranet as an alternative to having the add‑on download automatically the first time a user hits a ScriptX‑enabled page. This approach will be more suitable if your users don't have the privileges to run installers themselves.
Once deployed in this manner, ScriptX is made available on your pages as described in Browser‑based deployment. If you know that ScriptX has already been deployed the codebase parameter should be removed.
Deploy ScriptX.Add-on with a publishing license
If you are a registered ScriptX.Add-on customer you can use the download links below for deployment, however you will need to refer to the installation instructions that you received with your publishing license.
Browser-based deployment
You will need:
- or
- your publishing license file sxlic.mlf, as described in your email notification of license availability
This file should be copied to a suitable location on your web server(s), then include these objects on your pages:
<!-- MeadCo Security Manager -->
<object id="secmgr" viewastext style="display:none"
classid="clsid:5445be81-b796-11d2-b931-002018654e2e"
codebase="http://[your_path]/smsx.cab#Version=8,3,0,4">
<param name="GUID" value="{[YOUR_LICENSE_GUID]}">
<param name="Path" value="http://[your path]/sxlic.mlf">
<param name="Revision" value="[your license rev]">
</object>
<object id="factory" viewastext style="display:none"
classid="clsid:1663ed61-23eb-11d2-b92f-008048fdd814"></object>
where [your-path] is a placeholder for the location of smsx.cab on your own servers, and [YOUR_LICENSE_GUID] and [your license rev] are details that will have been provided to you in your email notification of license availability.
The <object> code shown above should appear on ALL your ScriptX‑enabled pages, including those dynamically created on the server via ASP Classic, ASP.NET, PHP etc. You cannot use CreateObject or new ActiveXObject to call ScriptX client‑side.
When scripting, you should call ScriptX in all cases by the ID of the ScriptX object on the page - in the above example ‘factory’.
Administrator pre-install
Alternatively you may wish to pre-install ScriptX.Add‑on over an intranet, in which case you will need:
- or
- your publishing license file sxlic.mlf, as described in your email notification of license availability
A local administrator should run ScriptX.msi on each client machine on your intranet as an alternative to having the add‑on download automatically the first time a user hits a ScriptX‑enabled page. This approach will be more suitable if your users don't have the privileges to run installers themselves.
Once deployed in this manner, ScriptX is made available on your pages as described in Browser‑based deployment. If you know that ScriptX has already been deployed the codebase parameter can be removed.