Service Operations Insight

eHealth Data Source showing hostnames in Select Resources from Data Source 

10-26-2017 02:14 PM

By default, eHealth Data Source is configured to bring eHealth information with information provided by eHealth.

In eHealth reports in CCR, servers are displayed with improper prefixes for the interpretation of reporting information.

 

For example: A given server named hostname.domain is displayed with the information hostname.domain-sh-A, hostname.domain-sh-B, hostname.domain-sh-C etc.
This is because the eHealth DataSource XML file contains the search for the name field, which looks for hosts with prefixes.
The solution was to modify the search instead of the field NAME searches for the field SYS_NAME, which is the field that displays the hostname information without prefixes.
Here is an example to modify this XML file.

 

1 - Access the CAPMAN Server and go to the <ccc-install-folder>\ApacheTomcat\webapps\DM\WEB-INF\classes\
2 - Edit the hyp_ehealth_622_physicalservers.xml file
Tip: Use NotePad ++ to edit the xml file

 

Note that in the default file, the query looks for the name field, for example: e.name

That way the DataSource will fetch the hostname with undesirable prefixes in eHealth

Note: The XML file is generic for all eHealth DataSources that are created.

 

3 - In this part of the XML it is also necessary to modify from name to sys_name throughout the document.

 

4 - There is a faster and more secure way to cascade the fields from name to sys_name.
In Notepad ++ go to Search -> Replace ...

 

5 - In the Find what field, type ".name"
In the Replace with field type ".sys_name"
Finally click the Replace All button

 

6 - In the result in blue, you should show the following message:
Replace All: 14 occurrences were replaced

 

7 - Note que no arquivo, onde havia campo name, foi alterado para sys_name

 

8 - One more time go to Search -> Replace ...

 

9 - In the Find what field type "name =" name "
In the Replace with field type: "name =" sys_name "
Then click the Replace All button

 

10 - Note that in the column tags have been changed to sys_name

 

11 - Restart the CCC Service

12 - Log in to the Data Manager interface to test the eHealth DataSource Go to Manage Data Source Select an eHealth DataSource, and then click the Edit button

13 - Click the Select Resources from Data Source button.

Note that all servers are with hostname

In CCR is this values witch will be showed

 

Best Regards,

 

Luciano Salino

Statistics
0 Favorited
0 Views
0 Files
0 Shares
0 Downloads

Tags and Keywords

Comments

10-31-2017 11:32 AM

David_Tsatsi – you ask a good question.

 

What will happen if you just make the changes to the data adapter is that the new server_names will be identified as brand new machines.  If just using OOTB capabilities:

  • There will be no linkage inside Data Manager of the old device name (with prefix) and the new device name
  • The old device will cease to have new metric samples added
  • The new device will not have any metric history prior to the Data Adapter change

 

I had written a much longer response explaining a couple of alternative approaches to addressing the problem.  HOWEVER, they all involve actions that outside of standard CA Product Support, so it might be wiser not to open that particular can of worms any further for now…

 

10-30-2017 02:06 PM

Hi David,

 

Unfortunately this is a pre-implementation solution, because on a particular customer, they complained a lot of the prefixes loaded in CAPMAN from eHealth. The test was done in homologation and applied in production.

 

Regards,

Luciano Salino

10-26-2017 05:24 PM

Great write up indeed Luciano

 

My question now is. What will happen with the existing data in an event I had already pulled in data with the undesirable prefixes. Is there a definitge solution which will help with deleting them to avoid having duplicates.

 

Regards

David Tsatsi

10-26-2017 04:17 PM

Great write-up.   Thanks for posting it.

David

Related Entries and Links

No Related Resource entered.