Donate Paypal

Lan Core :: Thin Client
[ english | español | русский
RSS

Cyber User Configuration Guide

Written by Félix Cubero Fernández, student at Technical University of Madrid (see about us).

Download this guide in PDF format.

Making rates' file

The rates are showed in the XML file called prices.xml. The file's structure is defined in another file called prices.dtd. In this file, has been defined the content and structure that prices.xml must fulfill. Both files are needed in the same path where the Cyber is executed. The content of prices.dtd is as follows:

<!ELEMENT prices (section+, day_on_offer*, season*)> <!ELEMENT section (#PCDATA)> <!ATTLIST section lower_index NMTOKEN #REQUIRED upper_index NMTOKEN #REQUIRED price_section NMTOKEN #REQUIRED type_billing NMTOKEN #REQUIRED> <!ELEMENT day_on_offer (#PCDATA)> <!ATTLIST day_on_offer day CDATA #REQUIRED discount NMTOKEN #REQUIRED> <!ELEMENT season (#PCDATA)> <!ATTLIST season hours NMTOKEN #REQUIRED money NMTOKEN #REQUIRED>
DTD-XML

The first element defined is the label prices. It's the first component that must be appear in the XML file. This component is called root and cannot be part of any other element. In label prices are defined the following elements: section, day_on_offer and season.

  1. section: Element used to define a time slot. It's make up of lower index, lower_index, and superior index, upper_index, to delimit the time slot defined. These indexes only admit positive and whole number values. In addition, the upper index also supports the string END, indicating that time slot has not upper limit. The price, price_section, associated with the time slot, will depend on type_billing. This price allows decimal and positive numbers. Finally, type_billing shows the way in which the price associated will be applied to the time slot. It allows three possible values: F, whose meaning is a fixed price, i.e., to all those connection times included in the limits of the time slot, will apply the amount that indicate price_section; V, variable, i.e. the amount is calculated multiplying the minutes of connection by the price indicated in price_section. Finally, M, whose meaning is that the amount associated with the time slot will be applied only in the first round. At least must be defined a time slot and all the elements defined in the section are required.

  2. day_on_offer: Element that is used to identify possible bargain days. Consists of: day: day in which is applied the offer, and discount: discount to apply in the final amount to pay for the user. It allows integer numbers, in a range from 1 to 99. That element is not required, but when this element is defined, then, day and discount, are required.

  3. season: Element that is used to offer some hours with a fixed price. It consists of hours: integer numbers, no more than 24 and money: decimal and positive number. That element is not required, but when this element is defined, then hours and money are required.

These tables show some valid examples of XML, according to the structure described by the DTD:

<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE prices SYSTEM "C:cyberprices.dtd"> <prices> <section lower_index="0" upper_index="5" price_section="0.5" type_billing="M"/> <section lower_index="5" upper_index="15" price_section="0.75" type_billing="V"/> <section lower_index="15" upper_index="30" price_section="1.25" type_billing="F"/> <section lower_index="30" upper_index="60" price_section="2" type_billing="F"/> <day_on_offer day="Monday" discount="20"/> <day_on_offer day="SATURDAY" discount="30"/> <season hours="3" money="5"/> <season hours="5" money="8"/> </prices>
Example XML valid (1)

<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE prices SYSTEM "C:cyberprices.dtd">? <prices> <section lower_index="0" upper_index="5" price_section="0.5" type_billing="M"/> <section lower_index="5" upper_index="15" price_section="0.75" type_billing="V"/> <section lower_index="15" upper_index="30" price_section="1.25" type_billing="F"/> <section lower_index="30" upper_index="60" price_section="2" type_billing="F"/> </prices>
Example XML valid (2)

Activation fees' file

Cyber accounting menu
Accounting menu

Once created the file of rates, it's necessary to be activated. For this, must be select the file created through the menu: Accounting->Prices and select the file made.

Sending's configuration

For carrying out the sending's files where they are stored the connections is necessary to run config.bat in Windows or in case of using Linux, writing to the console config.sh.

Once set up, will ask for some questions to make the configuration file called config_client.txt.

  • Path where the files are placed. The User will put the path where the Cyber is running.

  • Files' name to send. It will be necessary to write billing to send information recorded by the Cyber-cafe.

  • Periodicity of sending in seconds.

  • Information about the servers:

    • Server's name.

    • Connection port.

    • Destination's user name.

  • Information about the SMTP mail servers:

    • SMTP server name.

    • E-mail address from.

    • E-mail address to.

  • Confirm setup test.

You can provide the number of servers that you wish, for each kind of sending. The transfer was carried out to all servers provided in the configuration file.

Thin Client

Thin Clients :: Thin Client Hardware :: Thin Client Papers
PXE Protocol :: Remote Desktop with RDP :: Multiple Remote Desktop Sessions in Windows
Lan Core © 2009-2010 Lan Core: Thin Client Server and Operating System

Valid XHTML 1.0 Strict Valid CSS! Icono de conformidad con el Nivel Doble-A, de las Directrices de Accesibilidad para el Contenido Web 1.0 del W3C-WAI