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

UD doscovery for Delphi Application

SOLVED
Go to Solution
Advisor

UD doscovery for Delphi Application

Hi,

 

I am a newbie to HP Universal Discovery, My customer wants to see a Topology for one of their Business Application(Delphi+). Can you please suggest what are the Steps I have to do. Do I have to discovery it first and then apply some models.

 

Step 1.

Step2 etc... 

 

Regards

Muzaffar

5 REPLIES
Trusted Contributor

Re: UD doscovery for Delphi Application

Without knowing beforehand what identifies the application, you'd be running in the dark. I'd recommend sitting down with an application specialist. I have no idea what Delphi+ is, I am assuming it's something built in-house or else a vendor supplied solution with an internal codename. You would first determine the type of processes, services, databases that the application uses. Then see if those processes and services show up in your UCMDB. Then I'd relate those CIs to a BusinessApplication CI "Delphi+". And then you'd be able to show a view of everything discovered and automatically related to the application.

 

 

Trusted Contributor

Re: UD doscovery for Delphi Application

[ Edited ]

I did a little bit of Googling and found something called Delphi+ by NewMarket Inc.

This software runs on Windows, uses a SQL Server backend and is hosted on IIS.

There's an SMTP component as well.

So. First, get the IPs to the Windows servers hosting Delphi+. Get credentials to access Windows by WMI or NTCMD.

Then add the IPs and credentials to the Data Flow Probe setup.

Run Range IPs by ICMP, run Host Connection by WMI (or Shell in case you use NTCMD), run Host Applications by WMI (or Shell). Check your CMDB if you have a Windows host CI and its related CIs. See if there's any IIS, SQL Server, SMTP processes visible. You now have enough data to present a basic topology view.

Open the Modeling Studio, create a new Pattern View and drop the Windows Node CI you discovered, see related CIs and show then in the View.

Or:

Open the Modeling Studio, create a new instance based Model of type BusinessApplication called Delphi+.

Add the Windows host you discovered and save it. You now have a BusinessApplication CI with related CI's which you can use to show the customer.

 

Advisor

Re: UD doscovery for Delphi Application

Thanks Rutger, I will work on your instructions and let you know further.

Regards
Muzaffar
Advisor

Re: UD doscovery for Delphi Application

Thanks for your instructions. I have one more question, my customer expecting to have the Model with relationships to be created automatically based on the discovered data by UD. As I have manually created a Model using the Modelling Studio. please advise.

Regards
Muzaffar

Regards
Muzaffar
Trusted Contributor

Re: UD doscovery for Delphi Application

First thing to remember is that practically all components you're using to present the customer with a report come from automatic discovery by DDM/UD. That also includes the relationships between them. What you're doing with the Modeling Studio is to make the CIs and relationships visible. So as an alternative approach you could use the Modeling Studio to create a new Pattern View, drop the Delphi components like IIS servers, databases etc into it and draw relationships between them. This creates a "filter" which is used to draw CIs from the CMDB and present them in a View or Report. It would help if you could make your customer aware about the way discovery works and how TQLs are used to present discovered items and relationships between them.

Overview of steps involved in discovery of a Delphi application and/or generating a report or View:

1. IP addresses and credentials for Windows servers are collected and input in the Data Flow Management component.

2. IP addresses are discovered. IP address CIs are created.

3. You run the discovery jobs Range IPs by ICMP, Host Connection by WMI and Host Applications by WMI. Assuming the systems run Windows.

4. Using the discovered IP addresses, Windows servers are discovered and identified, Windows CIs are created.

5. Using the newly created Windows nodes, target systems are queried for services, running processes and installed software. Windows Services, Processes, RunningSoftware and InstalledSoftware CIs are created. Relationships are created automatically between software, services, processes and Windows CIs.

6. You create a model TQL based on Windows CIs and other element, you indicate the type of relationships you want to see between them. UCMDB uses your TQL or View to draw CIs from the CMDB and gives them back to your GUI.

7. You use the Report aspect of the View to set Report parameters.

8. Using the Reports Manager you schedule the Delphi report to be sent to the customer with some frequency.

 

What I advised you with regard to creation of a Model is just one way of doing things.

Another way would be to have Delphi autmatically discovered as an application by manipulating the ApplicationsSignatures.xml file in the Adapter Management. You can there indicate services, processes and their attributes to uniquely identify your Delphi application.

 

//Add this to "OnDomLoad" event