HP StorageWorks XP Command View Advanced Edition software Device Manager server installation and configuration guide (web version) (T1780-96078, March 2008)

Appendix A Overview of CIM/WBEM
238
If any service program using the same port is running, change the port number for the service
program.
If any service program is running (normally, another WBEM service program) that is using the
same port to be used by an object operation feature, the object operation feature is not
available.
If any service program is running (normally, another SLP service (or SLP daemon)) that uses
the same port (427) to be used by the service discovery feature, an attempt to start the SLP
service (or SLP daemon) for Device Manager will fail.
3. Set up and start the SLP service (or SLP daemon).
Set up the SLP service (or SLP daemon) to enable the service discovery feature. For details
about how to set up this feature, see section
A-5.
NOTE: In the SLP service (or SLP daemon), register the port used by CIM/WBEM features by
default. For the ports used by CIM/WBEM features, see subsection
A-3-2.
4. Restart the Device Manager server.
In Windows:
Select Start, Programs, XP Command View AE, Device Manager, and then Stop
Server.
When the Device Manager server has stopped, select Start, Programs, XP Command
View AE, Device Manager, and then Start Server.
In Linux:
Execute the following command:
installation-directory-for-the-Device-Manager-server/suitesrvcntl -
stop_hdvm
When the Device Manager server has stopped, execute the following command:
installation-directory-for-the-Device-Manager-server/suitesrvcntl -
start_hdvm
The following shows an example of executing the commands:
# /opt/CVXPAE/suitesrvcntl -stop_hdvm
# /opt/CVXPAE/suitesrvcntl -start_hdvm
5. Start the Device Manager service.
In the Services window, select DeviceManagerServer to restart the service.
NOTE: When upgrading Device Manager from version 1.0 to 1.1 or later, check the
httpsd.conf file. If this file contains coding that enables SSL functionality in the CIM/WBEM
features, remove or comment out the coding before performing the upgrade.
When the version of Device Manager is 1.0 or earlier, the httpsd.conf file is stored in the
following location:
•
In Windows: <common component installation folder>\httpsd\conf\httpsd.conf
• In Linux: /opt/CVXPAE/Base/httpsd/conf/httpsd.conf
The following shows the coding contained in the httpsd.conf file that enables SSL functionality
when the Device Manager version is 1.0 or earlier:
LoadModule proxy_module complete-path-name-for-the-proxy-module
Listen port-number-for-SSL-in-CIM/WBEM-features
<VirtualHost host-name:port-number-for-SSL-in-CIM/WBEM-features>
ServerName host-name
SSLEnable
SSLRequireSSL
SSLCertificateFile complete-path-name-for-the-certificate-file-from-CA
SSLCertificateKeyFile complete-path-name-for-the-private-key-file