Archive for the ‘Enterprise Software’ Category

Upgrade UCMDB License

When you install HP Universal CMDB, you receive the Universal CMDB Foundation  license. To obtain the file needed to upgrade to the Integration Only or DDM Advanced  Edition license, contact HP Software Support, then perform the following procedure: To upgrade your license:

  1. Obtain the appropriate file from HP Software Support.
  2. Replace the ucmdb_license.xml file in the "C:\hp\UCMDB\UCMDBServer\conf\" folder.  The name of the file must be ucmdb_license.xml.
  3. Use the JMX console to force a license change:

    1. Launch the Web browser and enter the server address, as follows:http://<UCMDB Server Host Name or IP>:8080/jmx-console.
    2. When prompted, enter the JMX Console authentication credentials (if you do not have these credentials, contact your system administrator). The default user name and password are sysadmin/sysadmin.
    3. Under UCMDB, click service=Server Services to open the Operations page.
    4. Locate getLicense and enter the following information:  In the Value box for the customerID parameter, enter 1.
    5. Click Invoke.

Information about the license type, customer name, permitted packages, and whether any applications are blocked is displayed.

uCMDB 9.05 Multi-Tenancy: How To

Option I

Go to JMX Console

  1. Search for "UCMDB:service=Customer and States Services"
  2. Select "addCustomer"
  3. Input "CustomerID:  2"
  • customerName:  SecondCustomer
  • configId:  <empty>
  • clusterId:  <empty>
  • Invoke (may take 10-15 minutes)

Option II

Create new customer configuration

From: C:\hp\UCMD\UCMDBServer\tools\server_management.bat

  1. Go to Customer Configurations link
  2. Click new customer config button
  3. Create new schemas
  4. Create new customer
  5. Click Customers link
  6. Click New Customer button
  7. ID:  2
  • Name:  SecondCustomer
  • Configuration:  The one we just made..
  • Cluster:  <empty>

Note: Option II does not appear to work in uCMDB 9.05 CUP1

Validating the BSM EUM Model


The following steps will navigate you to the EUM model validation JMX bean:

  1. Login to gateway server jmx console http://<Gateway>:8080/jmx-console/
  2. Under Topaz, Click “service=EUM Administration Service” then find “validateEumModel()”

Enter the following:

  • customer id: 1
  • Eum Model: ALL
  • Full Model Scan: "yes"
  • Fix Model If Needed: "yes" ;

Why is my CMDB NOT Accurate!?

Many times CMDB projects encounter a situation where the CI's contained in the CMDB become unreliable, and thus the value is lost.  Typically this occurs after a period of time has elapsed from the initial deployment.

The Configuration Librarian.

The Configuration Librarian's responsibility is "…maintaining up-to-date (and historical) records of configuration items.." There is a lot of work implied between the lines in that  description. Regardless, without at least one dedicated Librarian, the CMDB will never be accurate. My experience is CMDB customers usually expect the entire CMDB scope to be automatic. And no matter what your Sales Rep tells you, its simply not true.

And that makes perfect sense. What other Enterprise solution maintains itself without administration? CMDB is no different and requires at the least a nominal investment in time and resources. Honestly, I'd say its much lighter in this regard than most other Enterprise solutions out there. Further, I would suggest a point of contact be made available from every organization involved in the scope (servers, networks, databases, apps, etc).

What separates the HP uCMDB from competitors is the high level of customization available to meet the needs of a unique Enterprise. If OTB discovery and enrichments are not sufficient, the capability is certainly there to expand those functionalities, based upon your own needs. However, this requires knowledgable resources… which comes back to the original point above; time and resources are required (just like any other Enterprise Solution).

Here is a breakdown of the Librarians' Key Activities:

  • Assist "ABC" in planning for Configuration Management databases and activities
  • Identify Configuration Items under "ABC" management
  • Control Configuration Item information
  • Perform status accounting
  • Perform verification and audit of Configuration Management databases
  • Provide management information about Configuration Management quality and operations
  • Maintain quality of CI information entered into "ABC" CI Databases
  • Collect information about the current state of CIs
  • Receive and obtain announcements of significant changes in the state or condition of CIs
  • Respond to requests for CI changes and updates from Change Management
  • Provide CI information upon request

With at least one dedicated Librarian, depending on scale, you are on the right path to having an accurate CMDB.  Can you spot the gap in your deployment above?

Integrating Sitescope to HP Operations Manager (BSM)

  1. Stop Sitescope Service on host
  2. Launch Configuration Tool from Start Menu (run as administrator)
  3. Install the Operations Agent
  4. On the SiteScope server (where the OM agent is running):

    1. Execute "ovconfget sec.core CORE_ID" from command line. Copy the results.
  5. On the BSM DPS machine: (<coreid> is output of step A)

    1. Execute "ovcert -exporttrusted -file \dps" from command line
    2. Execute "ovcm -issue -file \sitescope00 -name:  <sitescope_server_FQDN> -coreid <coreid>" from command line
    3. Copy the created files from DPS to SiteScope server
  6. On SiteScope server:

    1. Execute "ovcert -importtrusted -file \dps" from command line.
    2. Execute "ovcert -importcert -file \sitescope00" from command line.

Note: One reason you might perform this kind of manual integration is if port 383 is not open between the SiS and DPS servers.

Return top