Server-side licensing is required where ScriptX is to be used with Microsoft's Internet Information Server (IIS) and Active Server Pages to print HTML documents on the server side.
An Active Server Page (ASP) 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 click here and read the server-side deployment notes carefully before ordering a server-side publishing license.
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.
Note that server-side license deployment has changed slightly with the introduction of ScriptX version 6.2. Please click here and read the revised server-side deployment notes to learn more.
Run smsx.exe to install the ScriptX binaries on your server(s). The most current version of smsx.exe is always available from the ScriptX site here
Here is a typical example of an ASP script which calls ScriptX advanced printing:
<% set factory = CreateObject("ScriptX.Factory") factory.printing.Printer = "HP LaserJet IIISi" factory.printing.portrait = True factory.printing.header = "Report" & Request.Form("number") factory.printing.PrintHTML "http://localhost/orders/order.asp? number=" & Request.Form("number") factory.printing.header = "file.htm" factory.printing.PrintHTML "c:\temp\file.htm" factory.ShutDown set factory = nothing %>
Please note that you can NOT use the ASP calls CreateObject or new ActiveXObject to call ScriptX from any client-side ScriptX-enabled page. You *must* call ScriptX by the ID of the on-page ScriptX <object>.