| United States-English |
|
|
|
![]() |
Ignite-UX Administration Guide: HP Computers with HP-UX 10.x, 11.0 or 11i > Chapter 5 Installing
HP-UX with Ignite-UX on Clients from a ServerViewing and Printing a Manifest |
|
From the Ignite-UX screenTo view a system manifest from Ignite-UX, select a client icon and click: Actions -> View/Print Manifest. This is also available from the Client Actions menu (right-click on client icon). The system search may take a moment.
The manifest provides customer order information for the selected target system. You can view or print the manifest when a target client is "Complete", as indicated by the Client Status screen. The online information is scrollable. The manifest contains the following information:
Using the print_manifest commandTo print the system manifest from the server command line, enter: /opt/ignite/bin/print_manifest The ASCII file is printed to stdout using format instructions from the manifest template file (explained below). Location of manifest filesManifest files are saved on the server in: /var/opt/ignite/clients/LLA/manifest/manifest.info and on the target client system in: /var/opt/ignite/local/manifest/manifest.info If the client data is moved to history, that data includes both the client's manifest and config file. Both these files can be recalled at a later time. Customizing manifest outputAdd printer formatting — Include the -e option to add PCL control codes to the output, adding bold headings, etc. to the output. Print an existing manifest file — Include the -s option to use previously stored data, rather than starting a new system search. Specify a template file —Use the -t option to specify a template file to customize the manifest output to your needs. A sample template file is: /var/opt/ignite/local/manifest/template.def. The template uses pcl3 formatting commands (similar to printf), allowing you to structure the output as desired. To create your template, be sure to edit a copy of this file, not the original. For example, if you want a condensed, machine-readable output, you can remove all blank lines and headings from your template. This will also speed-up the manifest generation. This command prints a condensed manifest using the existing manifest file and referencing a template you created named condensed.def: print_manifest -s -t /var/opt/ignite/local/manifest/condensed.def You can also access the raw manifest data via a script or program. This file is updated on the Ignite-UX server each time print_manifest is run without the -s option: /var/opt/ignite/clients/LLA/manifest/manifest.info |
||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||