Deploy Custom User Defined Collections Across Multiple FMS Installations (4309510)

How can a User Defined Collection be deployed across multiple FMS installations?

User Defined Collection (UDC):

• Definition of UDC are stored in the ASP
• The primary ASPs are controlling the credentials that will be used for running the UDC.
• The Secondary ASP is a table with all the UDCs in it. each collection is a row in that table.
• UDC data is being stored in a topology type which is defined according to the result set of the collection.

Below are the steps for copying UDC definition from one agent to a different FMS:

1. Initial definition

• Define UDC for 1 agent via the Agent's "Administration --> User-Defined Collection"
  

2. Export the settings of the agent that the UDC was defined on

• Export the ASP of that agent, use the fglcmd -cmd util:configexport command to export the config with the definition of the ASP.
• From the export, take the relevant ASP definition and use it to locate the name of the topology type that is being used to save the data of the UDC.
• See the attached "ASPFromConfigExport.xml" file to see how the ASP definition looks in the export file.
• The content of the xml file is presented in the ASP definition
  
• Look for the tag "valuelist" and see the ASP definition for the tag "row"
• The name of the topology is under the value with the name "custColName" - in this example it is "DBO_Cust_test" for the first row and "DBO_Cust_test_2" for the second row.
  
• Export the topology type associated with the UDC, KB 332432 describes how to export topology types. It would look similar to the following and be based on the topology path as described in KB 114172
  

3. Import the settings to the target FMS

• Load the topology type definition to the target FMS as described in KB 332435
• Create a config file just for the relevant UDC definition
• Import the config file to the target FMS (using the fglcmd -cmd util:configimport command)