HP WBEM Services Software Developer's Kit for HP-UX Provider and Client Developer's Guide A.01

Client Implementation
Client Development Use Cases
Chapter 5 107
Special Considerations
Clients may be able to simplify their discovery processing to identify that
the appropriate namespace and schema elements are present on the
target platform. Also, it may be useful to check the version of the
provider to ensure that it can support the client requests.
Best Practices
It is useful to perform appropriate discovery operations during initial
connection to a target platform. Also, be careful not to over-simplify error
checking.
Command Line Clients
Description
Command line clients can be implemented to make underlying WBEM
instrumentation transparent to the end user. WBEM clients can be
implemented to replace existing CLIs.
Special Considerations
Because WBEM is based on HTTP, it is possible to implement command
line clients that access remote hosts. In such cases, a remote host name
will probably be a part of the command line or otherwise furnished to the
client.
It is important to consider the security model of the command line client.
If the client is on the same host as the CIM Server, the local connection
mechanism can be used. However, if the CLI permits a user to access a
remote platform, a username and password will need to be supplied for
the remote CIM Server to authenticate.
Best Practices
If the command accesses a CIM Server on a remote host, include a
command line argument to specify the host to be accessed (managed).
Command lines may include the ability to specify a user. However, it is
inadvisable to include a command line argument for the password since
this argument can show up as plan text in the argument list. Prompting
the user for the password or using some authentication brokering
scheme are better approaches.