Internet Printing

Document Sample
Internet Printing Powered By Docstoc
Web Based Printing

       Microsoft provides integrated internet printing with the IIS services. This means,

       a) one can publish printers on the web, making them available for
             valid users,

       b) valid users can connect to a hosted web site and install the published
              printer on their pc or laptop (wifi or hardwire)

       c) valid users can use this printer as any other, with the output being sent
              across the web to the host.

      Details of the aforementioned are contained in a MS document, which can be
downloaded from the OCS ftp server at:


          folder: ocs\ipp

          File: InternetPrint.doc

       OCS has integrated this technology into an internet printing package that
optionally provides a user popup interface, thereby allowing print jobs to be correlated to
users with various types of identifiers and be accordingly managed.

       Users can send print jobs from anywhere, across the web, to an OCS server and
then subsequently vend these print jobs, at a convenient time, from within the institution.


Server Configurations

      There are several configurations.

      Hosted by Customer

             IIS Services and Print Management Services on one Server

             This design requires the customer to have a Windows Server 2003, or
             equivalent, running IIS services to support the user/web access
             to defined printers.

             OCS’s print management software (OCS_PMGS) runs concurrently the
             same server, managing all print jobs. Print jobs are sent to the OCS server
             via the web or via conventional non-web interfaces.


             Print jobs are vended by users from within the institution.

             IIS Services on one Server with Print Management on XP Stations

             This configuration supports

                     a) conventional lan connections between XP stations and
                            the web server, or
                     b) no conventional lan connections between XP stations and
                            the web server. Here the print files are downloaded
                            to the XP stations across the internet.

      Hosted by OCS

             This design does not require the customer to have a Windows Server.

             OCS Inc provides the services that support the processing of user print
             jobs across the web and the delivery of such jobs back to the institution,
             for vending by the user. OCS’s print management software (OCS_PMGS),
             supporting the vending of print jobs on site (and the related SQL
             database) runs, at the institution, on a XCP computer (in workgroup or
             domain environment).

             Print jobs are sent to OCS Inc’s servers across the web.Print jobs are
             vended by users from within the institution.

Client Configurations

      OCS WebPrint provides two client configurations.

      1) No client, no popup. One simply connects to the web based printers
            and prints to them. Print jobs are located, at release stations, on
            the basis of the individuals logon name.

             This configuration applies when each user has his or her specific
             logon credentials.

      2) Small auto-loaded client providing a popup. This configuration applies
           When one wants to correlate jobs to users on the basis of name,
           account or Jobid.


      Simplicity of Installation and Operation

      Users who have valid credentials on the IIS server can install, on their own, the
      web printers and the OCS client, using internet explorer, with a few mouse clicks.

      Correlates Print Jobs to Users

      Supports the use of accounts, names or jobids to associate each print job to a
      user, thereby making it simple and easy for a user to locate and vend their
      print jobs.


      The printer connections and OCS client operate on demand only. If the user is not
      printing to the web printers, the client is basically invisible.


      If the internet is accessible, users can print and send their jobs to the server.

      Integrates with Non-Web Systems

      OCS supports concurrent use of web printing and printing using direct
      connections to institutional networks.


      The system supports multiple OCS_PMGS modules per site. As such, one
      can support any quantity of workstations per site without the use of a server
      operating system. This is attractive when addressing print management in
      satellite or smaller facilities.


Basic Operation from the User’s Perspective

a) Installation:

       a. Using internet explorer and assigned credentials (logon name and password)
          the user installs a BW or Color (or both) web printer.

       b. Using internet explorer the user selects an ftp site and runs the OCS
             Client which auto installs.

b) Usage:

       The user prints to the BW printer or Color Printer is provided with a popup
       (below), allowing them to enter an Account or Name or JobID.

       The user press the Proceed and Send button and the job is transmitted to the
       IIS server.

To vend the print job(s) the user enters the institution and uses conventional facilities,
such as a Print Release Station (PRS).

File Delivery Configuration

Configuring the processing of incoming web print jobs at the IIS server and at the site
servers is accomplished with the same utility. It is accessed with the “Web Host
Download Config” button in Advanced Configs and Utilities (ocsmanager, install and
configure, advanced settings).

File Delivery Configuration

   (a) FTP Site: address used by site servers to contact ftp services running on
       the IIS server (mandatory on site server config).

   (b) Services Move to Folder: Local IIS folder, used as base folder by OCS services
       provisionally storing incoming print jobs .

   (c) Base Folder for Checking: Used by OCS services on site servers for basic
       queries for files.

   (d) FTP Logon User Name: Admin access only, user name used by site site servers
       to login in to (IIS) ftp server.

   (e) Password and confirmation are related to (d).

   (f) Institution Brand or Satellite Name: A user can print to the IIS server by using
       the direct connection to the web printer or by printing to the local printer installed
       by the client software (ocsact).

       When printing directly, the print job, is identified by the user’s logon name. In
   this case, one can set the Brand to any character string (20 bytes), on the IIS server

and the site server. The system will create a folder with the brand name and all
incoming direct print jobs (and processing information) will be provisionally moved
into this folder. Periodically, the site servers will download and process these files,
thereby making them available to a user for vending.

    When printing with the client (ocsact) the behaviour is similar. Each customer is
provided with a client (ocsact) which is stamped with a specific brand. This
configuration field will be completed with this brand. In this case, the user prints to a
local printer which is called either BWPrinter or COLORPrinter (created by the client
during its autoinstall) and subsequently is provided with a popup, as below. After
completing the ID and/or changing the name, the user sends the job to the IIS server,
where it is processed and provisionally moved to the brand folder.

The Institution Brand field is used when you have 1 web server and 1 site server.

If you have 1 web server and several sites, then (on the IIS server) you should click
the Use Satellite Brands (on) and add the names of the satellite brands. In this case,
each site, you would enter the applicable satellite brand (or sitename) directly into the
Brand field. The web server will place incoming print jobs in a folder for each
satellite site and each site server will download from that specified folder.

   (g) Check for print jobs (every x minutes): You can define the time, in minutes
   or fractions thereof, intervals for the ftp queries to be executed from the site servers to
   the IIS server.

   (h) Downloading – Active/Inactive: This should be off only when you are
   supporting both web printing and normal LAN printing on the same server.

   (i) Delete Server Files on Download: This is normally checked (on). When setting
   up the system you can uncheck this just to confirm the movement of files.

   (j) This is the IIS Server: On if yes.

   (k) IIS used only to process incoming web prints…: When this is checked, the
   OCS services running on the IIS server are reduced to a minimum, using only the
   ActivePort and the TimeSyncPort.

   (l) Correlate BW and Color Web Printers…: OCS uses virtual printer groups to
   group various types of printers. These fields allow you to correlate the incoming
   print jobs from either a ServerBW or a ServerColor printer

Printer Naming Conventions

On IIS server (base): The name will contain ‘BW’ or ‘COL’. For example one can
                      Create printers and share names such as:


Client auto creates:


        The correlation of the server printer jobs to the location of the print management
server is a function of the ocsact client which contains a unique brand, eg ‘Location01’
or ‘Location02’, etc.


Installation of IP Printers by User

       There are two methods, single step or user select.

Single Step

        In this method, the administrator provides OCS with xx pieces of information per
printer to be installed per site:


               DisplayPrinterName on http - this the name of the actual ipp printer
                      That will appear on the users computer

                        Eg- "ServerBWLJ5 on"

               Name of the printer on the server – this is the printer share name on the
                     IIS server.


               Name of the printer driver

                        Eg- “HP LaserJet 5”

       OCS will provide a compiled ocsact containing the specifics. The user simply
executes the program ocsact. Ie – single step.

User Selects Printers

       Users will be given the following information by the institution.

       a) A url for the web site that hosts the web printers that the user
          will install on their PC.

            Eg -

       b) An account and password to use to authenticate when connecting

   to the above url.

   Eg -    Account: JohnDoe Password: Welcome!

         The account can include the server address,

         Ie ocshost/JohnDoe

c) The names of the printer or printers to be used.

   Eg.     ServerHPCOL4725E or ServerBWLJ5

d) A url for the web site that supplies the user with the OCS client
      if it is being used for popups.

         Eg -

e) A brief instruction sheet.

Actual Installation

       The user will open internet explorer and enter the (a) url


The system will immediately challenge the user to enter their credentials, from (b)
above, in a dialog screen similar to the following.

After entering the data and pressing OK, the system will return a screen showing all
printers on the specific site. This will vary with sites.

The user will locate either one or two printers, as specified in (c) above. Each printer
must be individually installed.


To continue, the user selects and clicks on, for example, ServerKyoceraCOL2525E. The
system will respond with a screen similar to the following.

The user then double clicks on the ‘Connect’ tab.

The system will respond with a prompt to proceed, as follows.

When the Yes button is pressed the system responds with a validation screen.

The user is already known by the web host. This second prompt would be filled in with
the provided name and/or the servername\provided name.

We want to select: Use the specified user account then enter the data.

       Eg      ocshost\JohnDoe

       The system will start installing the printer. In some cases the user may see the
following screen. Press the button labeled ‘Continue Anyway’ and proceed.

        The system will continue installing the printer. When it completes the
installation, the user will repeat the process for the second printer, if required.

To do this click on ‘All Printers”, (on the image on the next page) select the next printer,
press ‘Connect’ and proceed accordingly.


At this point, the printers are installed on the system and can be used as any other printer.
The only difference is the routing of the print jobs. Jobs sent to the web printers are sent
to an OCS server and vended (paid for) by the user, at kiosks within the institution.

If the institution has told to the user to not install the local client then we are finished the


Installing the Popup Client

        When the user has been provided with the client url, previously (d) above, he or
she will open internet explorer and enter the provided url,

Eg -

       The system will respond with the following dialog prompt.

       The user will respond by pressing the ‘Run’ button to proceed.


      Again, the user will respond by the pressing the ‘Run’ button to proceed.

The system will present a EULA.

When the user presses the ‘I Agree’ button, the client will install to the startup folder and
then add local printer(s) named BWPrinter and ColorPrinter. When using the
client, the user prints to these local printers and not to the web printers directly. All jobs
forwarded to the web printers are discarded.

You will see a “P” icon in the system tray when the client is operating.

Installing Client for Vista

       At this point the IP printers are installed.

        To install the client on a Vista O/S, make a folder c:\ocs then copy the programs
ocsact.exe and ocsactv.exe into this folder.

       Execute ocsact.exe -install      and follow instructions.

        The service will be installed and a batch file (client.bat) will be placed in the
startup folder.

Local Printing Option

        The ocsact client can be configured to test the size of print jobs and forward the
output directly to a locally managed OCS virtual print queue, when the print job exceeds
the defined size. Using this option, large jobs are not sent across the network but rather
are processed locally. This can improve response times significantly. If you are using
XP as the O/S you need to ensure that the concurrent license connections are not


Shared By: