HP Operations Manager

Final configuration steps


The following tasks are required to complete the implementation of your remote SQL Server database. Follow these steps for final configuration:

Edit vpstat and registry keys

  1. On the management server, you can either keep the existing openview database on the management server and just disable the SQL Server (<Instance name>) database instance service, or to save disk space, you can also delete the openview database prior to stopping the database instance service:

    osql –S<management server>\<instance name> -E

    drop database openview

    go

    quit

  2. Stop and disable these services:

    SQL Server (<Instance name>)

    SQL Server Agent (<Instance name>)

  3. Edit the vpstat.conf file. Change to directory %OvDataDir%\conf\vpstat and open the configuration file vpstat.conf in your favorite text editor.

    Search for the section beginning with [SERVICELIST]. Add a hash at the beginning of the line ".service=VAR_SQLSERVER_INSTANCESQLSERVER_LOCAL."

  4. Edit the following registry keys (for remote database access):

    HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\OVEnterprise\Management Server\DBAccess\OVOWINSTANCE

  5. Reboot the management server.

The remote database configuration is now complete and ready for use with HP Operations Manager.

Remove the self-management policy VP_SM_CHK_OVODB

As the HPOM database is no longer located on the management server, you have to remove the self-management policy VP_SM_CHK_OVODB from the management server. Deploy this policy to the remote database server instead.

If the DB SPI is installed on the management server

If the HP Operations Smart Plug-in for Databases is installed on the management server, you must remove the SPI and its policies from the management server and redeploy the SPI and policies on the remote database server. This is required because the location of the OVOPS database instance has changed to the remote database server.

Related Topics: