UCMDB and UD Practitioners Forum (Previously CMS)
Showing results for 
Search instead for 
Do you mean 

HP UCMDB Queries

Occasional Contributor

HP UCMDB Queries

Hi All,

 

I would be happy if any HP UCMDB certified, answers the below queries, as this data required urgently.

 

1. What is the Licensing model of uCMDB(with DDMA/Without DDMA/per user/Per CI etc)?

2. What are the typical timelines and #resources required for an end to end uCMDB implementation(for about 20,000 CIs)?

3. How does importing CI data from excel to uCMDB work?

7 REPLIES
Visitor

Re: HP UCMDB Queries

 

1. What is the Licensing model of uCMDB(with DDMA/Without DDMA/per user/Per CI etc)?

I'm not sure what the licensing model without DDMA but with it I believe it's on the number of nodes you plan to discover

.

2. What are the typical timelines and #resources required for an end to end uCMDB implementation(for about 20,000 CIs)?

It really depends on what problem your implementation is trying to solve. Also 20,000 CIs in the ucmdb is not very many at all. Most larger implementations get into the millions very quickly. 

 

3. How does importing CI data from excel to uCMDB work?

There are out of the box discovery jobs that are there to read excel files and import them into the ucmdb. There is a bit of mapping that needs to take place for this to work but it's a fairly easy thing to get working.

Valued Contributor

Re: HP UCMDB Queries

HI,

 

The Licensing Model in UCMDB is basically of three types:

1.Basic License - which doesnt cover the Discovery and with standard integrations of HP Products

2.Integration License - This Involves all the Integrations but not Discovery

3.Advanced License - It has the capability to do Discovery as well the Standard Integrations.

The License count is directionaly proportional to the Number of OS Instances you discover using DDMA.

 

With respect to the Timelines the following are the factors you need to consider:

1.The Availability of the Vairous teams(Wintel.UNIX,Network) at the customer end to make sure the pre-requisites are configured

2.The Quality of the data in Manual CMDB maintained at the customer End for the quick validation after the Discovery

3.The Type of Datacenter :static or Dynamic.

These are the siginificant factors you need to consider. Apart from these there are several other minor factors which can be overcome easily

 

 

Frequent Visitor

Re: HP UCMDB Queries

Is it possible to import ci and relation in rtsm like ucmdb??? Can you help me with the steps like how to import in ucmdb from excel???
Trusted Contributor

Re: HP UCMDB Queries

Please read the section "Import from Excel Workbook Discovery" from "HP UCMDB Discovery and Integration Content Guide".

Regards
Puneet

If you find this reply helpful, Click the KUDOS button on the bottom to say 'Thanks'
Occasional Contributor

Re: HP UCMDB Queries

I recently did a import using excel

Please follow the steps

 

Please read

Import from Excel Workbook Discovery from UCMDB10.00_DiscoveryIntegration guide

Frequent Visitor

Re: HP UCMDB Queries

Thanks Experts..

 

Just to know incase we are not using ucmdb and only BSM  is it possible to import ci and relations in RTSM(BSM) from external excel.

 

Is there any guide for that or i can follow the same steps....

Occasional Advisor

Re: HP UCMDB Queries

Can anyone help me with this error, this is being shown when I am trying to create an Integration Point between SM and UCMDB.

 

com.hp.ucmdb.discovery.probe.request.ProbeSideProcessorException: [ErrorCode [-2147483648]
undefined error code]
null

--- Start of probe-side exception ---
java.lang.NullPointerException
at
com.hp.ucmdb.discovery.common.utils.PatternSimpleXMLParser.getAdapterInfoElement(PatternSimpleXMLParser.java:103)
at
com.hp.ucmdb.discovery.common.utils.AdapterConfigCreatorUtil.getAdapterConfigFromPatternXML(AdapterConfigCreatorUtil.java:52)
at
com.hp.ucmdb.discovery.probe.agents.probemgr.adapters.DataAccessAdaptersFacade.getAdapterConfigDef(DataAccessAdaptersFacade.java:203)
at
com.hp.ucmdb.discovery.probe.agents.probemgr.adapters.DataAccessAdaptersFacade.convertDestinationConfigDefToDestinationConfig(DataAccessAdaptersFacade.java:337)
at
com.hp.ucmdb.discovery.probe.processor.FederationNoneLifeCycleProbeProcessor.process(FederationNoneLifeCycleProbeProcessor.java:44)
at
com.hp.ucmdb.discovery.probe.processor.FederationNoneLifeCycleProbeProcessor.process(FederationNoneLifeCycleProbeProcessor.java:27)
at
com.hp.ucmdb.discovery.probe.agents.probemgr.adhoctasks.AdHocProbeRequestOperation.performAction(AdHocProbeRequestOperation.java:59)
at
com.hp.ucmdb.discovery.probe.agents.probemgr.taskdispatcher.AdHocTaskDispatcher.dispatchTask(AdHocTaskDispatcher.java:73)
at sun.reflect.GeneratedMethodAccessor53.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:111)
at
com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:45)
at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:235)
at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138)
at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:250)
at javax.management.StandardMBean.invoke(StandardMBean.java:405)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:791)
at
javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:305)
at
org.springframework.jmx.access.MBeanClientInterceptor.doInvoke(MBeanClientInterceptor.java:405)
at
org.springframework.jmx.access.MBeanClientInterceptor.invoke(MBeanClientInterceptor.java:353)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)
at $Proxy47.dispatchTask(Unknown Source)
at
com.hp.ucmdb.discovery.probe.agents.probegw.managementtasks.adhoctasks.AdhocThread.run(AdhocThread.java:54)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:599)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:534)
at java.lang.Thread.run(Thread.java:722)
--- End of probe-side exception ---

//Add this to "OnDomLoad" event