Next generation single-system management on HP-UX 11i v2 (B.11.23)

Figure 2. Consolidated architecture diagram of the HP SMH and HP SIM
The following steps describe the process of managing systems in a multisystem and single-system
framework:
1. Launch HP SIM on the web browser (Mozilla or Microsoft Internet Explorer) to manage multiple
systems remotely. HP SIM is installed on a CMS and uses the Tomcat web server.
2. Launch the HP SMH on the managed node from HP SIM. The HP SMH is installed on the managed
node and uses the Apache web server. HP SMH plug-ins are typically common gateway interface
(CGI)-based tools. You can also launch the HP SMH plug-ins from HP SAM. The HP SMH can also
be used independently of HP SIM by accessing the managed node directly, using HTTP through
port 2301.
3. Log in to the HP SMH. While the HP SMH authentication mechanism is based on operating system
users (using the Port Access Method (PAM) authentication framework), its authorization is based
on user classes to which each valid user must be associated. Valid classes are Administrators,
Operators, and Users (not only root/user). The root user is automatically assigned to the
Administrators user class.
HP SMH uses Tomcat, in addition to Apache, on the managed node. While most HP SMH
applications are CGI-based, some others like parmgr are Java™ applications that require Tomcat
to run. However, the HP SMH Java-based applications are accessed in the same way as CGI
applications. When access to a Java-based application is requested, the HP SMH Apache-based
server forwards requests to Tomcat, which is typically loaded on demand.
4. Launch a menu-drivenCLI or TUIfor various plug-ins from a telnet session or command line.
On the managed node, the HP SMH depends on WBEM for supporting the Component/Property
pages and other applications.
6