Absent Member.. venkatramireddy Absent Member..
Absent Member..
782 views

WHY HP SM needs to talk to HP uCMDB directly ?Could you please help?

 
0 Likes
4 Replies
Acclaimed Contributor.. Jacob Heubner Acclaimed Contributor..
Acclaimed Contributor..

Re: WHY HP SM needs to talk to HP uCMDB directly ?Could you please help?

I'm sorry; I don't understand your question.  Can you elaborate on the issue you're experiencing?

 

0 Likes
Micro Focus Expert
Micro Focus Expert

Re: WHY HP SM needs to talk to HP uCMDB directly ?Could you please help?

Hi Reddy, SM does not need to talk to UCMDB. It's optional. If you have setup UCMDB, these are the enhanced functionalities that can be obtained from the integration. Check the SM/UCMDB integration guide. Here's the cut paste from the intro. Purpose of the integration An integration between HP Universal CMDB (UCMDB) and HP Service Manager enables you to share information about the actual state of a configuration item (CI) between your UCMDB system and a Service Manager system. CIs commonly include IT services, hardware and software. Any organization that wants to implement the best practices Configuration Management and Change Management ITIL processes can use this integration to verify that CIs actually have the attribute values the organization has agreed to support. You can use this integration to automate the creation of Service Manager change or incident records to update or rollback CIs that have unexpected attribute values. Service Manager allows you to programmatically define what actions you want to take whenever a CI’s actual state does not match the expected state as defined in the CI record. The integration offers several different ways for users to view CI actual state information: • By default, the integration automatically updates the managed fields of Service Manager CI records as part of the regular UCMDB synchronization schedule. You can choose the option to configure the integration to automatically create change or incident records instead. • A Service Manager user can view the current actual state of a CI by looking at the Actual State section in the CI record. When you open the Actual State section, Service Manager makes a web services request to UCMDB and displays all CI attributes the request returns. Service Manager only makes the web service call when you open this section. • A Service Manager user can use the View in UCMDB option to log in to the UCMDB system and view the current CI attributes from UCMDB. The Service Manager user must have a valid UCMDB user name and password to log in to the UCMDB system. Supported use cases This section describes use cases that are supported by the UCMDB-SM integration. The supported use cases provide the core business processes that are enabled by the UCMDB-SM integration. There are four main business use cases supported by the UCMDB-SM integration. They are as follows: • Planned Change: A change created in SM through the formal SM change process. • Unplanned Change: A change or incident that occurred in SM and does not conform to the formal SM change process. • Retrieving SM Ticket Information: The ability to view SM ticket information in UCMDB. • Actual State: The ability to view the UCMDB CI information in SM. All of the use cases provide important functionalities that enable the user to perform ITIL(IT Infrastructure Library) processes. The ITIL processes refer to a set of best practices that define and outline how organizations should manage their IT. Enabling ITIL processes By activating CI push from UCMDB to SM the user facilitates ITIL processes such as Incident, Problem and Change Management in SM. SM utilizes the data pushed from UCMDB in the following modules: • Incident Management: the Service Desk operator (SD Agent) selects the “Service” and the “Affected CI” for the specific Incident record. • Problem Management: the SD agent selects the “Service” and the “Primary CI” for the specific Problem record. • Change Management: the SD agent selects the “Service” and the “Affected CI(s)” for the specific Change record. In each of the previously mentioned ITIL processes, SM utilizes CI information for Service, Affected CIs and Primary CIs that all originate in UCMDB. Managing planned changes The purpose of the “Planned Change” use case is to provide IT organizations a formal process by which changes to the IT infrastructure are introduced after thorough review and analysis. This is performed according to the “Change Management” process defined in ITIL v3. A “Planned Change” is initiated by the SM user via the formal “Change Management” process module in SM. This is followed by the actual change implementation. The actual changes are discovered by a discovery tool such as HP DDMA, and then updated in UCMDB and the relevant modifications are pushed to SM. Once the user has validated the change, the user closes the relevant planned change in SM. Managing unplanned changes The purpose of the “Unplanned Change” use case is to provide IT organizations a formal process by which all changes that occur to the IT infrastructure are both logged and conventionalized through the organizations formal approval process. An “Unplanned Change” is a change that is recognized by a Discovery tool such as DDMA. The change is first updated and visible in UCMDB and then the data is pushed to SM. SM recognizes the change and as a result an “Incident” or “Change” record is generated. These Changes are seen also in the SM “Pending Changes” section in the Configuration Item form, once approved they are moved to the SM “Historic Changes” section. Retrieving Service Manager ticket information Retrieving SM ticket information from within UCMDB provides all HP Software applications users with access to this information by using UCMDB's federation capabilities and supporting APIs. These applications include Business Service Management (BSM), Asset Manager (AM), Operations Orchestration (OO), etc. SM ticket data is accessed from within UCMDB using UCMDB federation capabilities. SM ticket data includes Incident, Problem and Change records as well as a key set of their attributes. UCMDB enables users to create reports/views that combine the federated ticket data from SM with CI information from UCMDB. Retrieving actual state of UCMDB CIs The purpose of “Actual State” is to enable SM users insight into CIs’ current state as detected by “Discovery Tools” and populated in UCMDB. This state provides up-to-date information that may vary from the information displayed in SM both in content and in scope. The “Actual State” of the CI is displayed in SM in order to enable the user to validate the current state of the CI that resides in UCMDB or in another data repository. SM users retrieve the Actual State of CIs from UCMDB or additional data sources by viewing the CI's Actual State section in the SM Configuration Item form. Accessing UCMDB CIs from Service Manager SM users can open the UCMDB User Interface in the context of a specific CI, by clicking the View in UCMDB button in the SM CI record. When the user clicks the View in UCMDB button, a UCMDB login screen displays; After the user enters a UCMDB username and password, UCMDB displays a topological view of the specific CI together with all related CIs that are linked to it. You can configure Lightweight Single Sign-On (LW-SSO) for the integration, so that Service Manager web client users can bypass the UCMDB login screen after clicking the View in UCMDB button. For more information, see Lightweight Single Sign-On (LW-SSO) configuration on page 79. If the UCMDB Browser URL is specified in the SM System Information Record, this button is replaced by the View in UCMDB Browser button. When you click the View in UCMDB Browser button, a UCMDB Browser login screen displays; After you enter a UCMDB Browser username and password, the CI is displayed in the UCMDB Browser UI. Core features This section explains the rudimentary concepts behind the Federation, Push, and Population features as they pertain to the integration. Push UCMDB can automatically discover most types of CIs available in Service Manager. This integration enables you to push these types of CIs from UCMDB to Service Manager. Figure 1 shows how data is pushed from UCMDB to Service Manager (SM). The data is physically pushed (copied) from UCMDB to SM. Once the data is physically located in SM, the data is utilized by the SM user that consumes this information in various SM processes.
0 Likes
Absent Member.. venkatramireddy Absent Member..
Absent Member..

Re: WHY HP SM needs to talk to HP uCMDB directly ?Could you please help?

Thank you so much ..could you please share the SM/UCMDB integration guide link/url to me.

0 Likes
Super Contributor.. stsav Super Contributor..
Super Contributor..

Re: WHY HP SM needs to talk to HP uCMDB directly ?Could you please help?

There are benefits to the integration, but it is optional.

Universal CMDB Integration Guides for version 9.3x and more recent can be accessed here: https://softwaresupport.hpe.com/km/KM01294561

 

_________________________________________
Service Management Automation Expert at Micro Focus
If you find this post useful/helpful click the Kudos thumb on this post!
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.