Fujitsu V8.0B10 manuel d'utilisation
- Voir en ligne ou télécharger le manuel d’utilisation
- 28 pages
- 0.36 mb
Aller à la page of
Les manuels d’utilisation similaires
-
Server
Fujitsu PRIMERGY TX150 S4
18 pages 0.22 mb -
Server
Fujitsu M9000
98 pages 3.98 mb -
Server
Fujitsu V3.0.0
102 pages 1.84 mb -
Server
Fujitsu PRIMERGY BX600 S2
173 pages 4.07 mb -
Server
Fujitsu M8000
442 pages 1.8 mb -
Server
Fujitsu SPARC ENTERPRISE M3000
560 pages 7.13 mb -
Server
Fujitsu V3.1.0
233 pages 1.32 mb -
Server
Fujitsu RX600 S5
148 pages 2.76 mb
Un bon manuel d’utilisation
Les règles imposent au revendeur l'obligation de fournir à l'acheteur, avec des marchandises, le manuel d’utilisation Fujitsu V8.0B10. Le manque du manuel d’utilisation ou les informations incorrectes fournies au consommateur sont à la base d'une plainte pour non-conformité du dispositif avec le contrat. Conformément à la loi, l’inclusion du manuel d’utilisation sous une forme autre que le papier est autorisée, ce qui est souvent utilisé récemment, en incluant la forme graphique ou électronique du manuel Fujitsu V8.0B10 ou les vidéos d'instruction pour les utilisateurs. La condition est son caractère lisible et compréhensible.
Qu'est ce que le manuel d’utilisation?
Le mot vient du latin "Instructio", à savoir organiser. Ainsi, le manuel d’utilisation Fujitsu V8.0B10 décrit les étapes de la procédure. Le but du manuel d’utilisation est d’instruire, de faciliter le démarrage, l'utilisation de l'équipement ou l'exécution des actions spécifiques. Le manuel d’utilisation est une collection d'informations sur l'objet/service, une indice.
Malheureusement, peu d'utilisateurs prennent le temps de lire le manuel d’utilisation, et un bon manuel permet non seulement d’apprendre à connaître un certain nombre de fonctionnalités supplémentaires du dispositif acheté, mais aussi éviter la majorité des défaillances.
Donc, ce qui devrait contenir le manuel parfait?
Tout d'abord, le manuel d’utilisation Fujitsu V8.0B10 devrait contenir:
- informations sur les caractéristiques techniques du dispositif Fujitsu V8.0B10
- nom du fabricant et année de fabrication Fujitsu V8.0B10
- instructions d'utilisation, de réglage et d’entretien de l'équipement Fujitsu V8.0B10
- signes de sécurité et attestations confirmant la conformité avec les normes pertinentes
Pourquoi nous ne lisons pas les manuels d’utilisation?
Habituellement, cela est dû au manque de temps et de certitude quant à la fonctionnalité spécifique de l'équipement acheté. Malheureusement, la connexion et le démarrage Fujitsu V8.0B10 ne suffisent pas. Le manuel d’utilisation contient un certain nombre de lignes directrices concernant les fonctionnalités spécifiques, la sécurité, les méthodes d'entretien (même les moyens qui doivent être utilisés), les défauts possibles Fujitsu V8.0B10 et les moyens de résoudre des problèmes communs lors de l'utilisation. Enfin, le manuel contient les coordonnées du service Fujitsu en l'absence de l'efficacité des solutions proposées. Actuellement, les manuels d’utilisation sous la forme d'animations intéressantes et de vidéos pédagogiques qui sont meilleurs que la brochure, sont très populaires. Ce type de manuel permet à l'utilisateur de voir toute la vidéo d'instruction sans sauter les spécifications et les descriptions techniques compliquées Fujitsu V8.0B10, comme c’est le cas pour la version papier.
Pourquoi lire le manuel d’utilisation?
Tout d'abord, il contient la réponse sur la structure, les possibilités du dispositif Fujitsu V8.0B10, l'utilisation de divers accessoires et une gamme d'informations pour profiter pleinement de toutes les fonctionnalités et commodités.
Après un achat réussi de l’équipement/dispositif, prenez un moment pour vous familiariser avec toutes les parties du manuel d'utilisation Fujitsu V8.0B10. À l'heure actuelle, ils sont soigneusement préparés et traduits pour qu'ils soient non seulement compréhensibles pour les utilisateurs, mais pour qu’ils remplissent leur fonction de base de l'information et d’aide.
Table des matières du manuel d’utilisation
-
Page 1
Release Notice Xprint V8.0B10 Microsoft Windows 2000 /2003 Server Copyright (c) Fujitsu Siemens Computers All rights reserved Version date: January 2008 1 General 1.1 Ordering 1.2 Delivery 1.3 Documentation 2 Software extensions, new functions 3 Technical information 3.1 Resource requirements 3.1.1 Required disk storage 3.1.2 Virtual Memory consump[...]
-
Page 2
3.5.8 Clean up of directories at the start up 3.5.9 Gateway options 3.5.10 Standard entries 3.5.11 Notification event 3.5.12 Requesting the job states with the APIs 3.5.13 Page context 3.5.14 Inter-domain notification 3.5.15 Goodies 3.5.16 Job id limit 3.5.17 Mercator Viewing 3.5.18 Options order 3.5.19 Cooperation with Wprint 4.0 3.5.20 Which PCL [...]
-
Page 3
1.1 Ordering For the use of Xprint you will need software licenses. The data media has always to be ordered separately. This product is subject to the general terms and conditions of the software product use and service agreement. The delivery unit is a licensed product and may only be used on the computer for which it has been purchased. The basic[...]
-
Page 4
Manual Pages N.A Xprint R/3 Kit X SNMP Agent X Domain Monitoring GUI Anchor X Domain Monitoring GUI Relay X Domain Monitoring GUI Server X EKS/Patch XPW80B102 X ● Xprint-NT means Xprint for Microsoft Windows Server The activation of each component depends upon the purchased license. Please see section 3.1 for the specific components of the Xprint[...]
-
Page 5
DMG view/filter management tool The purpose of this feature is to facilitate system administrators to distribute existing DMG filters and DMG views to other DMG operators. Accounting file enhancement The accounting has been enriched with new fields to give the administrator possibilities to produce more accurate accounting reports. Interface Window[...]
-
Page 6
3.1.1 Required disk storage The required disk storage capacity directly depends on how the software is installed. Xprint is distributed as a setup package containing the entire product. During the wizard execution, three kinds of installations are proposed: - Typical: represents the installation of the Basic Software, the Inter domain and the XPG/3[...]
-
Page 7
3.3 Software configuration 3.3.1 Operating system Before installing Xprint, be sure that all previous EKS (Xprint correction packages) are removed from the system. This product is dedicated to Microsoft Windows 2003 Server (tm) and to Microsoft Windows 2000 Server (tm) with service pack >= 2. It is not allowed to run the server part of the produ[...]
-
Page 8
If you install Xprint V8.0 in a domain containing hosts running older Xprint versions, be sure that only hosts running the latest version are defined as POT_MASTER. To avoid problems, define the hosts running older versions as SLAVE. When installing the first Xprint V8.0 host (H1) in a lower version domain, H1 will have to take the mastery of the d[...]
-
Page 9
3.4.2.8 Local Xprint administrator This kind of user is called a "subroot" user by Xprint. You can declare subroot users on a host when you create this host, or by modifying an existent host, with the " -sr" option. For instance, if you want that the user "usname" becomes subroot on host "OSL" you can type &q[...]
-
Page 10
Message catalogues N.A Compatibility Libraries N.A Inter domain Interoperability X Development Tool kit Manual Pages N.A Xprint R/3 Kit SNMP Agent Domain Monitoring GUI Anchor X Domain Monitoring GUI Relay S Domain Monitoring GUI Server S EKS/Patch XPW80B102 S If you select the standard installation you will get the components marked with X in the [...]
-
Page 11
o Uninstall the version 5.2 (control pannel->add/remove programs) o Uninstall the MKS Platform Components 7.x o Install the new version in the same path as the former one o Install the licence key(s) 8.0 o Restore your backed up directories into the current Xprint's root directory o In the "bin" directory of Xprint (default: "[...]
-
Page 12
If you use the R3-Kit, please save also the files for the R3 Kit configuration. These files are listed in the Xprint Reference Guide chapter 7.15.6. The files are stored in the directory $OMSPATH which is by default /var/spool/ Xprint/config/mgt/SAP. 3.4.4 SNMP On Windows 2003 and Windows 2000 server, the SNMP agent requires the Microsoft SNMP serv[...]
-
Page 13
port number GUISRV_PORT=<port_number> ex: 80 callback entry point GUISRV_PATH=<entry_point> standard: /CALLBACK/xpCallback.php DMG Relay Callback Collector host address COLLECTOR_HOST=<host_address> ex: machine02 or 192.168.1.2 Callback Collector port number COLLECTOR_PORT=<port_number> ex: 55003 DomMonGui_Collector - Callba[...]
-
Page 14
LOGFNAME is the fully qualified base name of the event collection files. This definition is mandatory and the related directory must exist. The complete name of an event collection file is created by suffixing this base name with a 'nnnnn.xml' string where nnnnnn is a 6 digit index (e.g. EventCollection000005.xml) LOGFSIZE is the file siz[...]
-
Page 15
3.4.6.4 Domain Monitoring GUI communication settings Is described in detail in the XPRINT V8.0 Domain Monitoring GUI manual and in section 3.4.5.3. 3.4.6.5 Domain Monitoring GUI installation By default the installation depends on your language environment. For English your path is C:Program Files, for German C:Programme. But you can choose anothe[...]
-
Page 16
ServerRoot Apache root directory between quotes Listen Port that apache listen to. You cannot change port for SSL (443). ServerAdmin eMail of the Administrator (optional) ServerName Full name of the server (with DNS extension) DocumentRoot Path where the DomainMonitoringGUI is. LoadModule Somewhere in the file, is this line: LoadModule php5_module [...]
-
Page 17
NB: don't forget to replace the existing CALLBACKxpIni.ini by the INI/xpIni.ini file. Your changes will take effect as soon as you'll reconnect to the GUI. 3.4.6.7 Maintenance 3.4.6.7.1 Log Files Apache logs much information into its log files. Therefore, from time to time, it is necessary to purge those log files to avoid a full file sy[...]
-
Page 18
" "C:Program Filesphp/php.exe callBackDaemon.php -install" 3.4.7 Migration procedure when upgrading from a former DMG version (8.0A to 8.0B) The migration procedure consists in deleting the former version before installing the new one. So to upgrade the DMG, you have only to execute the uninstallation procedure and afterwards the i[...]
-
Page 19
# xpkey -i "First line:second line:" Example: # xpkey -i "oo Dt xx Y4 UR vW 64 Up Hy 96 Qr Lz 9U TQ:m9 Rm Ez Wt BW 0b ?V p? cD:" No blank between the second line and the first line. Important information: The same license key cannot be installed more than once in a Xprint domain. Several installations of the same key will lead t[...]
-
Page 20
Per machine or domain, you must enter every corresponding update license key with the command "xpkey -i" . 3.5.2 Renaming the hostname in an Xprint domain Is described in chapter 6.2.1 in the Xprint 8.0 User's and Administrator's Guide and in the Xprint 8.0 Reference manual , chapter 'xppatch'. 3.5.3 Bsd filter port op[...]
-
Page 21
However, the print job will be rejected if none of the specified printers supports the additional options for the print job that are contained in the command line. 3.5.6 Logging When a same logging message is send many times consecutively, the message is written one time in the logging file and for each occurrence of this message, a '.' i[...]
-
Page 22
3.5.10 Standard entries If no supervisor or server is specified when a device is set up, Xprint automatically generates a server and a supervisor, both under the host name. The Xprint system comprises various entities, including servers and supervisors. The server controls the job database. The server also controls the supervisor. A supervisor cont[...]
-
Page 23
When trying to view a job, if the data file is no more accessible, an error message appears in Mercator. 3.5.18 Options order There is difference of the behaviour of Xprint for options order in extended or simple options. When the same option but with different values is repeated in a list of extended options (-ex) and this option is 'known&ap[...]
-
Page 24
When a new job submission occurs, the callback library will query the LDAP server to check whether a default device destination was defined for the current job originator if no explicit destination was specified by the originator. If it finds out a destination, the job will be automatically directed to this destination, otherwise, the usual process[...]
-
Page 25
❍ libCacheMan.dll ● When a user requires notifications (job, device) via the FILE method, a timestamp is now added at the beginning of the message. However, you can erase this timestamp by setting the environment variable XP_NOTIF_TIMESTAMP to NONE. ● In a domain with different versions of Xprint, only the components of the version 8.0 get th[...]
-
Page 26
3.8.7 Wprint 4.0 Wprint 4.0 can now print on Xprint redirected printers to another domain but no job management is available for this kind of printing submission. 3.8.8 SNMP ● SNMP agent does not monitor remote objects ● On an insufficient hardware configuration for the number of Xprint objects (please consult configuration advices in chapter &[...]
-
Page 27
which the apache web server will run. If the customer needs to have our DMG Web application running on different ports than the standard ones (for instance he might need to keep another existing Web server running on the same host with the standard http and https ports), then some manual operations are required after the installation of the DMG. He[...]
-
Page 28
Send the Xprint accurate version (with installed EKS) If the problem is about printing, the print file that is at the origin of the problem can help to detect the location of problem. 2. Logging Each time something wrong happens, an entry is recorded in the Event Viewer. 3. Debugging If the problem can be reproduced please recall the command with t[...]