A Classic ASP/ASP.NET web application may handle an HTTP GET or POST request and print a report (a different HTML page) as part of some server-side application logic. In this case, the print-out will take place on the server side and will go to a printer which is physically attached or networked to the server. The browsing user who originated the HTTP request may not ever see the printed output nor know that printing has taken place.
Server-side licensing confers NO client-side printing capabilities.

Please review our introduction to the technology carefully before ordering a server-side publishing license.

How to license a server

Your server-side license will be 'bound' to the computer name(s) of the server(s) on which you want to enable fully-functional ScriptX printing. It is issued to you in the form of a file which - when run on the server(s) whose computer name(s) it validates - will write the required licensing information to that machine's registry. All server-side publishing licenses are renewable and valid for one or more years.

Installing the ScriptX binaries

To deploy ScriptX on your server, run either ScriptX.msi or ScriptXx64.msi as appropriate for your environment. Note that with IIS 7 and later, the Application Pool can be configured to run either as 32bit or 64bit on 64bit Editions of Windows. It is important to install the appropriate Edition or the ScriptX components will not be visible to the server code and will result in "Class not registered" errors.

Once installed, further configuration and testing steps are required. Please refer to the documentation and notes provided with your server-side publishing license.

 If you are upgrading from a previous version of ScriptX:

  • You must shut down the web server. Please shut down rather than restart because if it's a live server, just restarting may mean that users log on and start a print job - in which case the ScriptX component DLLs may become in-use and locked again.
  • If the previous version was installed using the 'smsx.exe' installer, we recommend using the cleanup utility cleansx.exe before running ScriptX.msi/ScriptXx64.msi. Note that once IIS loads the ScriptX implementation DLLs it can hold onto them until it is restarted. If IIS has loaded the DLLs, it doesn't matter how many times you run the cleanup utility cleansx.exe it will fail to remove the DLLs with an access denied error (error code 5). 
  • During the upgrade, any launch identity for MeadCo Tri-Print Server configured via DCOM configuration (Component services) will be lost and must be re-entered.
Scripting server-side ScriptX

To print, the configuration parameters of the ScriptX Printing object may be used to set properties such as the printer to be used and headers and footers. To perform the print, the PrintHTML method is used, for example:

 ' Apply licensing - the license must already be installed.
 set secmgr = CreateObject("MeadCo.SecMgr")
 secmgr.Apply "","{XXXX-XXXX-XXXX-XX}",X

 ' the object is dynamically created and destroyed
 set factory = CreateObject("ScriptX.Factory")
 factory.printing.header = "Report printed on the server"
 factory.printing.footer = "Printed on &D"
 factory.printing.PrintHTML "http://localhost/order.asp?number=" 
    & Request.Form("number")

 ' After use, shut down the object to ensure that resources
 ' are released in a timely manner
 set factory = nothing