Archive for the ‘Business Service Management’ Category

Integrating SiteScope 11.30 Events with BSM 9.25

  1. Install SiteScope 11.30
  2. Extract "Software_HP_Operations_Agent_v11.14_Windows_ISO_TC097-15046" iso locally on sis server
  3. CD to that extracted dir (run as admin)
  4. Run "cscript oainstall.vbs -i -a" and click ok to any prompts, etc.
  5. Select Start > All Programs > HP SiteScope > Configuration Tool (run as admin)
  6. In the "Configure HP Operations Agent installed separately" option select "Configure HP Operations Agent" to complete the installation of the HP Operations agent.
  7. Restart SiteScope server.
  8. In SIS UI, select Preferences > Integration Preferences:

    • Click the "New Integration" button and select "HP Operations Manager Integration".
    • Configure the OM/BSM path (in distributed environment, point to gateway server)
    • Click "Connect" to connect the agent to the BSM server. This sends a connection request from the agent to the specified server.
    • Leave this window open
  9. Accept the agent connection request on the BSM Gateway/Web Processing server

    • In BSM 9.20 or later UI, go to Admin > Operations Manager > Certificate Request, locate and grant your certificate request.
  10. Install the log policies on the SiteScope server

    • After the certificate request has been granted on the BSM server, back in SIS UI, click "Install Policies" in the HP Operations Manager Integrations Main Settings panel of the HP Operations Manager Integration dialog box. This installs and signs the preconfigured log file policy file on the HP Operations agent.
    • Leave this window open
  11. Check connection status and send test message from the SiteScope server – optional

    • In the HP Operations Manager Integration dialog box, expand the HP Operations Manager Integrations Main Settings panel, and click "Analyze".
    • To check that the agent is connected to the BSM server, type a message in the Test message text box, and click "Send Test Message".
    • If the test is successful, the text message is displayed in the Operations Management Event Browser in BSM. This message is generated by a basic opcmsg policy command (i.e. opcmsg a=a msg_grp=test o=o msg_t=test).
  12. Enable SiteScope to send events to HPOM or Operations Management

    • In the HP Operations Manager Integration dialog box, expand the HP Operations Manager Integrations Main Settings panel, and in the Configuration Settings area select "Enable sending events".
    • Leave all other options at default
    • Save and close the window – done.
  13. Note: LWSSO will automatically be configured between BSM and SIS.
 
Reference: SIS_1130_OM_Integration_Guide.pdf (pages 21 – 32)

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

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" ;

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.

Debugging .hprof files using the Memory Analyzer Tool

If a SiteScope GUI becomes completely blank, or is otherwise unavailable, one of the culprits may be a lack of available disk space – on account of SiteScope creating a number of large JVM debugging files (.hprof files).  Over 35GB’s worth is not out of the question, and this can clearly tank an application as a result.  Essentially, these files are memory dumps that indicate a problem with the application configuration.

To open and parse these files, use the Eclipse Memory Analyzer Tool (MAT).
Download the zip file and extract its contents into the same SiteScope directory where javaw.exe lives:  C:\SiteScope\java\bin

From here on you are on your own, but the basic gist of it goes like this:

  • Open the MAT .exe file, which is located in the same directory you extracted the zip into.
  • Import/Open the SiteScope .hprof files, which are located in SiteScope bin folder: C:\SiteScope\bin
  • …And run all of the canned analysis reports against the .hprof files as you wish

Unless you are a Java Developer, the memory analyzer will not be terribly useful to you.
However, MAT will automatically zip up every Report you generate – which is a perfect format to forward to HP Support, along with the raw .hprof files themselves.  The zipped Reports should end up in the SiteScope\Bin directory after being created.

As a final note, the MAT *should* work against any other HP BTO product that produces .hprof files, such as BSM, however I have not tested this and would only do so after performing a full file system/db backup.

Enjoy!

Return top