Archive for the ‘Universal Configuration Management Database’ Category

RTSM to CMS Sync – Step by Step Guide

This activity is one of the most commonly sought-after and often confusing HP Integrations.  Finding the correct documentation is usually the biggest hurdle to overcome.  For example, the documentation provided for this activity that ships with UCMDB/BSM is incomplete and/or blatantly incorrect.  The Software Solutions Now guides are far more comprehensive, however, the best outline can be found ironically in the Release Control Detect to Correct Value Stream interactive guide.
 
What follows are the steps from that guide:

UCMDB – BSM Integration Configuration

Overview
This configuration synchronizes the configuration item (CI) records between HP Universal CMDB (UCMDB) and Run-Time Service Model (RTSM). Apart from the convenience synchronizing the configuration between UCMDB and RTSM provides, we make sure that the CIs across all three systems (UCMDB, HP Service Manager (SM), and HP Business Service Management (BSM)) are identical and have the same GlobalID generated by UCMDB.

Create UCMDB to BSM Integration Point in BSM

Deploy Package CSM_to_RTSM_Sync.zip on BSM
  1. Copy the file CMS_to_RTSM_Sync.zip located on the BSM-DPS machine file system under HPBSM\odb\conf\factory_packages to the file system on the UCMDB machine.
  2. Open the UCMDB user interface.
  3. Select the Administration tab.
  4. Select Package Manager.
  5. Select Deploy Packages to server (from local disk).
  6. Click Add button and selec the file CMS_to_RTSM_Sync.zip through the file system browser.
  7. Select Deploy

Enable the CMDB 9.x Integration Point

  1. Open the BSM admin user interface and select the RTSM Administration.
  2. Select the Data Flow Management tab.
  3. Select Integration Studio.
  4. Create a new Integration Point according to the following table:

     

     

    Name
    Recommended
    Value
    Description
    Integration
    Name
    <user defined> The name you give to the integration point.
    Adapter UCMDB 9.x Select the adapter type from the drop-down list.
    Is Integration
    Activated
    selected Select this check box to create an active integration point.
    Hostname/IP <user defined> The name of the UCMDB server.
    Port <user defined> The port through which you access UCMDB.
    Credentials <user defined>

    If UCMDB credentials appear in the Credentials column, select them.

    If no UCMDB credentials appear, select Generic Protocol and click the Add new connection details for
    selected protocol type button.
     
    Enter the following information:
    • Description. Enter UCMDB.
    • User Name. Enter the UCMDB user name. The default value is admin.
    • User Password. Enter and confirm a password.
    Probe Name <user defined> Select the probe you configured previously from the dropdown list.
     
  5. Click the Add icon on the right side of the window and add Job definitions as follows:

     

     

    • Name the Job definition.
    • Select the Allow Delete check box.
    • Click the Add icon in the Job definition window.
    • From the pop up window, browse to root – CMS sync, select the ActiveDirectory_sync job and click OK.
    • Select the Scheduler definition check box.
    • In the Repeat window, select Cron.
    • For the Cron expression, enter the following string: * 0/10 * * * ? *
    • Adjust other settings as needed.
    • When finished, click OK and save the integration.
    • Repeat steps a to i and configure the following jobs:

       

       

      • FailoverCluster_Sync
      • IIS_Sync
      • SOA_Sync
      • BusinessAndFacilities_Sync
      • ExchangeServer_Sync
      • Virtualization_Sync
      • Siebel_Sync
      • Credentials_Sync
      • Basicinfrastructure_Sync
      • J2EE_Sync
      • SAP_Sync
  6. Browse to UCMDB on port 8080 (for example, http://yourUCMDBhost.domain:8080), and select the JMX Console
  7. Log on to the JMX console.
  8. From the UCMDB section, select UCMDB:service=Multiple CMDB Instances Services.
  9. Invoke:

     

     

    • setAsNonGlobalIdGenerator for customer ID 1 and verify it succeeded.
    • getGlobalIdGeneratorScopes for customer ID 1 and verify it succeeded.
  10. Browse to your BSM administration UI.
  11. Select Data Flow Management tab.
  12. Select Integration Studio from the options.
  13. Select the Integration Point that you have configured.
  14. In the Job definition section, click Synchronize All to run the synchronization.
The integration point should be active and the jobs are displayed properly.

Configure BSM 9.x Integration Point

Deploy Package CMS_to_RTSM_Sync.zip on BSM
  1. Copy the file CMS_to_RTSM_Sync.zip located on the BSM-DPS machine file system under HPBSM\odb\conf\factory_packages to the file system on the BSM machine.
  2. Open the BSM user interface.
  3. Navigate to Admin > RTSM Administration > Administration > Package Manager.
  4. Select Deploy Packages to server (from local disk).
  5. Click the Add button and select the file CMS_to_RTSM_Sync.zip through the file system browser.
  6. Click Deploy.

Enable the CMDB 9.x Integration Point

  1. Open the UCMDB user interface.
  2. Select the Data Flow Management tab.
  3. Select Integration Studio.
  4. Create a new Integration Point according to the following table:

     

     

    Name
    Recommended
    Value
    Description
    Integration
    Name
    <user defined> The name you give to the integration point.
    Adapter BSM Adapter Select the adapter type from the drop-down list.
    Is Integration
    Activated
    selected Select this check box to create an active integration point.
    Hostname/IP <user defined> The name of the BSM server.
    Port <user defined> The port through which you access UCMDB.
    Credentials <user defined>
    If UCMDB credentials appear in the Credentials column, select them.
     
    If no UCMDB credentials appear, select Generic Protocol and click the Add new connection details for selected protocol type button.
     
    Enter the following information:
    • Description. Enter UCMDB.
    • User Name. Enter the UCMDB user name. The default value is admin.
    • User Password. Enter and confirm a password.
    Push Back IDs Enabled
    Specifies whether to push back the global IDs after CIs are populated in the server.
     
    Note: Relevant for UCMDB 9.x adapters.
    Probe Name <user defined> Select the probe you configured previously from the dropdown list.
  5. Click the Add button on the right side of the window and add Job definitions as follows:

     

     

    • Name the Job Definition.
    • Select the Allow Delete check box.
    • Click the Add button in the Job definition window.
    • From the pop up window, browse to root – CMS sync, select the ActiveDirectory_sync job and click OK.
    • Select the Scheduler definition check box.
    • In the Repeat window, select Cron.
    • For the Cron expression, enter the followning string: * 0/10 * * * ? *
    • Adjust other settings as needed.
    • When finished, click OK and save the integration.
    • Repeat steps to a to i and configure the following jobs:

       

       

      • FailoverCluster_Sync
      • IIS_Sync
      • SOA_Sync
      • BusinessAndFacilities_Sync
      • ExchangeServer_Sync
      • Virtualization_Sync
      • Siebel_Sync
      • Credentials_Sync
      • Basicinfrastructure_Sync
      • J2EE_Sync
      • SAP_Sync
  6. Browse to BSM on port 21212 (for example, http://yourDPShost.domain:21212), and select the JMX Console.
  7. Log on to the JMX console.
  8. From the UCMDB section, select UCMDB:service=Multiple CMDB Instances Services.
  9. Invoke:

     

     

    • setAsNonGlobalIdGenerator for customer ID 1 and verify it succeeded.
    • getGlobalIdGeneratorScopes for customer ID 1 and verify it succeeded.
  10. Browse to your UCMDB administration user interface.
  11. Click the Data Flow Management tab.
  12. Select Integration Studio from the options.
  13. Select the integration point that you have configured.
  14. In the Job definition section, click Synchronize All to run the synchronization.

‚ÄčThe integration point should be active and the jobs appear properly.

Verify UCMDB – BSM Configuration

  1. Browse to your UCMDB server user interface.
  2. In the CI Type manager screen, locate the Node element.
  3. Right-click a Node object and select Show CIT Instances. The CIT Instances window is displayed.
  4. Right click on one of the CIs and select Properties.
  5. Locate the Global ID and write down its value.
  6. Browse to your BSM server user interface.
  7. Repeat steps 2-4 and identify the value of Global ID.
  8. Compare the IDs from steps 5 and 7 and verify that they are the same.

Afterwards, there are a number of LWSSO/Security settings that will should be configured as well.  Please refer to the guide to complete those steps

HP uCMDB – Neebula Integration

Neebula advertises an HP uCMDB integration which uses a patented automatic Service Modeling technology (ServiceWatch)… one that dramatically reduces the time it takes to build Service models in UCMDB/RTSM.

Neebula CMDB

Their webinar claims ServiceWatch can reconcile cleanly with DDMa CI's, though it is not shown in the demo.
Unfortunately, an explanation of how the automatic "top-down, entry-point" Service Modeling actually works, is also missing.
 
Beyond simple Service Modeling use cases, I cannot see how a HTTP URL entry-point for example will take me all the way back, past the network layer, to not only the clustered app servers themselves, and running software therein, and the separate and clustered DB's supporting them, but the critical DB instances themselves.  There are so many "what-ifs" along this path that I can't help but think of the great potential for misleading models! 
 
Further, if the Service Delivery team is now in charge of building Service Models – as the webinar seems to suggest, how will IT or Service Delivery ever know if an application is even right?
There is still a disconnect – no matter how revolutionary this "entry-point" modeling is, the models still need to be verified, scrubed, etc.
Which is of course the "lengthy" portion of Service Modeling in the uCMDB to begin with.
 
Regardless, I'd like to be proven wrong – Service Modeling IS the "achilles heel" of the UCMDB/BSM suite of products.
 
Take a look for yourself.  What do you think?

HP Discovery not available for Linux Probes

I guess it never came up in the field, but the Discovery Flow Probe Linux installation can only be used for integrations… not discovery.

h30499.www3.hp.com

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

Return top