 |
» |
|
|
|
This topic describes the supporting Web-based components of
the Peripheral Device Tool, and ways to start and stop pdweb. The pdweb
Server and Client Components | |
The Peripheral Device Tool consists of two parts: - pdweb
server
The pdweb server component runs within the HP Apache-based Web Server
(also referred to herein as HP Apache). The pdweb(1M) instance
of HP Apache is also used by other system administration tools such
as kcweb(1M). | | | |  | IMPORTANT: This instance of HP Apache will not serve web pages on port 80.
It only uses port 1188, and only uses https for all communication.
Using a separate port allows any firewall to all normal web traffic
on port 80, but still block outside attempts to administer the system. | | | | |
If the HP Apache server is not already running, pdweb will start it whenever it starts the Peripheral Device
Tool. When started by the pdweb command without the -s option, the HP Apache server will
automatically close after a period of inactivity. - client Web browser
The Web browser runs on the
client system. The client system may be the same as the server system,
or it may be a separate workstation or personal computer (PC). Not
all Web browsers are supported by the Peripheral Device Tool. On
workstations and servers running HP-UX 11i v2, the Peripheral Device
Tool supports the use of the default Web browser that is installed
by the Operating Environment bundle. On PCs, the Peripheral Device
Tool supports the use of Mozilla version 1.2.1, Microsoft Internet
Explorer version 6.0 and greater, and Netscape version 6.0 and greater. If a supported Web browser has been installed somewhere
other than the default location, set the BROWSER environment variable
to the path of the browser.
Stopping
or Restarting the pdweb Server | |
You must have superuser capability to start the pdweb server. Restarting stops the pdweb server, then starts it again. To start the pdweb server on a target host system: Log into the host
system as root. Enter pdweb -s action where action is either stop or restart The HP Apache and pdweb Web servers are both stopped or restarted depending on
your action. Restarting stops the pdweb server, then starts it again.
Starting
the pdweb Server with No Timeout | |
You can start the pdweb Web server with the inactivity timeout feature disabled
using the -s option. This causes the pdweb server to run in a mode where it does not exit after
a period of inactivity. This feature is helpful in instances when
you want to use pdweb several times throughout the day but don't want to configure the
autostart capability. Individual Client Web browser login sessions
will still timeout, but you can log back in without having to restart
the pdweb Web server. Log into the host
system as root. Enter pdweb -s startssl The HP Apache and pdweb Web servers are both started.
Autostarting
the pdweb Server and GUI | |
It is possible to start both the pdweb Web server and GUI client components automatically from
a supported Web browser: Enable the pdweb autostart feature with waconf(1M): Log
into the host system as root. Enter waconf -a on
Now the pdweb autostart feature can be used. Once the autostart behavior
is configured, it remains on or off until waconf is executed to change it. The configured behavior is
remembered regardless of system rebooting. Open a Web browser on any network
client that is connected to your company intranet. Enter http://hostname:1110/pd/pd.cgi where hostname is the hostname of the target host system.
Once the pdweb Web server components have been started, the HP SAM WEB
login screen is presented so that you can log into the Peripheral
Device Tool. |
Printable version
