Try something like this:
Create a component template containing this config file. Discovery the component on the appropriate servers. take a snapshot of these components.
In reports create a report w/ the server name, and the config file, and however many columns of the config file you need.
the other reports can be some version of that - you can put filters or do sums to get the data of 'how many is x installed on..'
Thanx for the info. That seems to work but it seems when snapshotting component templates you can see the values, but they are each printed on another line.
an example below
Name value BLP-PT3-DummyA0-1.0.0-2009/12/22 15:14:00 1.0.0 BLP-PT3-DummyA0-1.0.0-2009/12/22 15:14:00 2009/12/22 15:14:00 BLP-PT3-DummyA0-1.0.0-2009/12/22 15:14:00 BLP-PT3-DummyA0 BLP-PT3-DummyA0-1.0.0-2009/12/22 15:14:07 1.0.0 BLP-PT3-DummyA0-1.0.0-2009/12/22 15:14:07 2009/12/22 15:14:07 BLP-PT3-DummyA0-1.0.0-2009/12/22 15:14:07 BLP-PT3-DummyA0 BLP-PT3-DummyA0-1.0.2-2009/12/29 11:44:57 1.0.2 BLP-PT3-DummyA0-1.0.2-2009/12/29 11:44:57 2009/12/29 11:44:57 BLP-PT3-DummyA0-1.0.2-2009/12/29 11:44:57 BLP-PT3-DummyA0
Do you have any idea how to solve this? Or did I manage to do something wrong?
I swithed to extended objects which makes reporting a lot easier.
I've made simple extended objects that do nothing more than "cat /path/to/file" and put a grammar on that. Then i've made a snapshot job that snapshots this extended object against all servers.
Within BSARA i've created a report combining server info and Extended object data filtering on my extended object.
The result looks somewhat like this:
Extended Object Name Server Name Responsible Team OS Release OS Version OS Name Path Package Version Timestamp Software Signatures Inventory s4010310.servers.foo.bar DEV_CTW_MIDTIER 5.10 10 Solaris Software Signatures Inventory/SWY1501TEST-1.0.0-2010/01/15 12:53:41 SWY1501TEST 1.0.0 2010/01/15 12:53:41 Software Signatures Inventory/SWY1501TEST-1.0.1-2010/01/15 12:53:56 SWY1501TEST 1.0.1 2010/01/15 12:53:56 Software Signatures Inventory/SWY1501TEST-1.0.2-2010/01/15 12:53:59 SWY1501TEST 1.0.2 2010/01/15 12:53:59 Software Signatures Inventory/SWY1501TEST-1.0.3-2010/01/15 12:54:02 SWY1501TEST 1.0.3 2010/01/15 12:54:02 Software Signatures Inventory/SWY1501TEST-1.0.4-2010/01/15 12:54:06 SWY1501TEST 1.0.4 2010/01/15 12:54:06 Software Signatures Inventory/SWY1501TEST2-1.0.0-2010/01/15 12:53:50 SWY1501TEST2 1.0.0 2010/01/15 12:53:50 sc000305.servers.foo.bar DEV_CTW_MIDTIER 5.2 2003 Windows Software Signatures Inventory/BLP-PT3-DummyA0-1.0.0-2009/12/22 15:14:00 BLP-PT3-DummyA0 1.0.0 2009/12/22 15:14:00 Software Signatures Inventory/BLP-PT3-DummyA0-1.0.0-2009/12/22 15:14:07 BLP-PT3-DummyA0 1.0.0 2009/12/22 15:14:07 Software Signatures Inventory/BLP-PT3-DummyA0-1.0.2-2010/01/06 17:27:19 BLP-PT3-DummyA0 1.0.2 2010/01/06 17:27:19 Software Signatures Inventory/BLP-PT3-DummyA1-10.0.0-2010/01/20 08:12:13 BLP-PT3-DummyA1 10.0.0 2010/01/20 08:12:13 Software Signatures Inventory/BLP-PT3-DummyA1-11.0.0-2010/01/20 08:15:15 BLP-PT3-DummyA1 11.0.0 2010/01/20 08:15:15 Software Signatures Inventory/BLP-PT3-DummyA2-1.0.0-2010/01/07 08:12:20 BLP-PT3-DummyA2 1.0.0 2010/01/07 08:12:20 Software Signatures Inventory/BLP-PT3-DummyA3-1.0.0-2009/12/21 11:24:35 BLP-PT3-DummyA3 1.0.0 2009/12/21 11:24:35
good, because I couldn't get anything useful out of the 'config file' either... the EO was my next suggestion.
if you want to, open a ticket about not being able to do this w/ the config file section...
I'm not sure if this is a real bug / missing feature.
In general, config files are designed to contain "parameter=value" for which the reporting works. Even if you have multiple values you can report on them.
So I think it's just something you have to keep in mind:
single and multiple values = Config files
data in multiple columns = Extended objects