Archive for the ‘Universal Configuration Management Database’ Category

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?

Reset BAC 8.x JMX-Console Password

1- Stop the HP Business Availability Center Gateway or Data Processing server.

2- Run the appropriate file, depending on the operating system in use, on either the Gateway or Data Processing server:

For Windows \tools\jmx\changeCredentials.bat

The Change Password dialog box opens, where you enter and confirm your
new password. The password change is registered and encrypted in the
following files, located on either the Gateway or Data Processing server:

1- \\EJBContainer\server\mercur \conf\props\

The syntax in this file appears as username=password.

2- \\conf\jmxsecurity.txt
The syntax in this file appears as username password.

Note: The login name cannot be changed

Upgrading a BAC 8.x uCMDB Foundation License

When you install Business Availability Center, you receive the Universal CMDB Foundation license. To obtain the file needed to upgrade to the Standard or Advanced license, contact HP Software Support, then perform the following procedure:

To upgrade your license:

1. Obtain the appropriate file (standard or advanced) from HP Software Support.
2. Replace the ucmdb_license.xml file in the \mam_lib\server folder on the Data Processing server machine .

If Business Availability Center is installed in a distributed deployment, replace the file on the Gateway Server machine.

3. Use the JMX console to force a license change:
a. Launch a Web browser and enter the address http://.:8080/jmx-console, where is the name of the machine on which BAC is installed. When prompted, enter the JMX Console authentication credentials (if you do not have these credentials, contact your system administrator).
b. Under MAM, click service=UCMDB UI to open the JMX MBEAN View page.
c. Locate java.lang.String getLicenseForCustomer() and enter the following information:

In the force parameter box, select True.
In the ParamValue box for the parameter customerId, enter 1.
Click Invoke.

Note: To verify the type of license that is installed, select False and enter the customer ID. Details about the license are displayed.

4. Restart the BAC server.

Gathering Requirements for an Application Map

The Goal:
To provide a realistic and accurate representation of the application or business service.

What’s Needed:
High level architecture diagrams of the application to be discovered and mapped
– Needs to include all application components (DB, App Servers, Load Balancers, etc).
Application Details
– Ports used
– Application details (App name, DB names, etc.)
– IP ranges of servers & devices
Access to application SME
– Needs to have detailed understanding of application environment
– Needs to understand application component configurations
Credentials for application components
– We will provide a list of whats required based upon application architecture

Application SME Involvements:
The Time Requirement:
– Should be limited to 4-8 hours total per application
– Will be Q&A type involvement
– Time will be broken up into several shorter sessions
Other Requirements
– Help troubleshoot discovery issues with non-standard configurations
– Help gather credentials
– Identify any internal processes we need to follow
The Goal:
– Validate that the maps being created are accurate representations of the application
– Ensure that we have included all relevant components and tiers
– Ensure discovery process is sustainable going forward.

Configuring PowerShell Agent for UCMDB

To Configure PowerShell:
1) Enable PowerShell remoting.
– Launch PowerShell v2.0 as an administrator.
– Run the enable-PSRemoting cmdlet:
— Starts the WinRM service and sets the statup type to Automatic
— Enables a firewall exception for WS-Management communications
— Creates a listender to accept requests on any IP address

2) To trust all hosts, run the following from the command line:

Set-Item WSMan:\localhost\Client\TrustedHosts *

To Trust only restricted IP addresses, specific the addresses in place of the asterisk (*).

3) Restart WinRM by running the following from the command line:

Restart-Service winrm

Return top