'Lightweight' replication and centralized reporting using 'Summary Generator' item class.
search cancel

'Lightweight' replication and centralized reporting using 'Summary Generator' item class.


Article ID: 164845


Updated On:


IT Management Suite


There are situations when it is needed to replicate a very specific set of data from one Notification Server to another. For example, you need to replicate data that is being generated by a custom query configured to run on a custom schedule.  What is the 'easiest' way?


No errors.


ITMS 7.0.x / 7.5.x / 7.6.x / 8.0.x.


Working as designed. 


"Summary Generator" items were introduced in Notification Server 7.0 (NS). 

If you run the following query against Symantec_CMDB, few Summary Generator items will be returned, depending on a number of IT Management Suite (ITMS) solutions you have installed. 

select * from vItem where ClassGuid ='38594257-051E-4162-8513-65F269AE9918'

 Let's review the structure of "2A4E0117-2757-48D2-911A-A4CF5F2C96AB / Hardware Summary Generator" item for example. What are the most import fields?

1. Export the item using ExportImport utility, "C:\Program Files\Altiris\Notification Server\Bin\Tools\ImportExportUtil.exe" /export {2A4E0117-2757-48D2-911A-A4CF5F2C96AB} c:/

2. Open it with Notepad++, for example. 

<name> item name.
item guid - item guid.
 <sharedSchedule> and <enabled> - used to configure a schedule when the generator item will execute the pre-configured stored procedure.
 <storedProcedure> - a pre-configured set of SQL statements that will be executed by the generator. Format -  <name>sp_Name</name>.
 <dataClass><name> and  <dataClass guid> - a pre-configured custom data class (http://www.symantec.com/docs/HOWTO83473).
<purgeExistingRecordsOnUpdate> - a setting that allows to control obsolete data purge. 


a. Create a custom stored procedure on all Notification Servers (i.e. create it in the corresponding Symantec_CMDBs) that will be used to replicate data from (https://msdn.microsoft.com/en-us/library/ms345415(v=sql.110).aspx). You can use one of the existing procedures as a pattern. Verify the duration it take to complete the stored procedure. Try not to overload SQL Server(s) with 'heavy' queries. 

b. Create a custom data class on all Notification Servers that will be used to replicate data from and to (http://www.symantec.com/docs/HOWTO83473). 

c. Export a Summary Generator class item (for example, 2A4E0117-2757-48D2-911A-A4CF5F2C96AB) -> modify it (modify the fields listed above) -> give it a unique GUID!!! ->  import it back to the NS Console. Verify it works by manually triggering the schedule item from Windows Task Scheduler.

d. Configure a standalone replication rule to replicate NS resource only (there is not need to replicate more resources) + the custom data class (for example, http://www.symantec.com/docs/HOWTO62641). 

e. Create a custom report that will pull data from the replicated data class (for example, http://www.symantec.com/docs/HOWTO119431). 

Using this approach, you replicate 'text data' only, i.e. 'lightweight' replication. Resource keys will not be replicated. 

If you need to delete the item(s):

- Change the attribute to 'Normal' = 0  it Item table manually;

- Detete the item using ItemToDelete table http://www.symantec.com/docs/HOWTO95559 -> run NS.Quarter-Hour in Windows Task Scheduler.