Load relationships between hosts and host group
Description | Imports host-to-host-group relationships from a comma-delimited file. You can choose to audit the host movement, which records the details when a host is removed, added, or moved. See Sample Audit File (output from load_package.loadGroupMemberFile). |
Usage | execute load_package.loadGroupMemberFile('<file_name>',
'<recycle_group>', <remove_old_entries>,'<audit_pathname>',
'<audit_output_file>', <do_log>);
Where: file_name is the fully qualified path to the csv file. For example: /opt/aptare/database/hosts.csv recycle_group is the full path to the group into which deleted hosts will be moved (i.e., the 'recycle bin'). remove_old_entries enables you to remove relationships in the Reporting Database that are not in the file. If set to 1 and where there are hosts with a previous relationship to a host group and where that relationship is no longer represented within the file, the utility moves those hosts to the recycle group. If set to 0, the utility does not remove those hosts. audit_pathnameis the full path to the audit file, not including the filename. audit_output_fileis the name of the audit file where the audit results will be stored. do_logenables you to turn on the auditing function so that all host movements are logged in the audit_output_file. Enter a numeric: 0 or 1, where 0 = No, 1 = Yes. Example command: execute load_package.loadgroupmemberfile ('/opt/aptare/database/movehosts.csv','/Global1/Recycle',1,'/opt/aptare/database','movehosts.out',1); |
Load File Specification | The specification for the comma-delimited file is as follows: path_to_host_group, internal_name1, internal_name2, internal_name3, etc. Where path_to_host_group is the fully qualified path to the host group into which the hosts should be added, and internal_name1 is the internal name of a host within the existing host group hierarchy. Example: /APTARE/Test, testhost01, testhost02 /APTARE/Infrastructure, testhost02, testhost03 Detailed specification for each field follows: internal_name CHAR(64) NOT NULL |
Data Constraints | The first field, path_to_host_group, must be the full path to an existing host group. If any host groups in the path_to_host_group field value do not exist, the utility creates them. Field values cannot contain embedded commas. The csv file must exist and be readable. The recycle group folder must exist. Each row must have at least one host specified, otherwise the row will not be processed. |
Logic Conditions | If you list hosts after the path_to_host_group field and those hosts are located in the existing host group hierarchy, the utility adds those host groups to the specified host group. If a host with the specified internal name does not exist in the hierarchy, the relationship will not be added. The host must already be configured in the reporting database. If any host groups in the path_to_host_group field value do not exist, the utility creates them. If the removeOldEntries parameter is set to 1, the utility assumes that this file will contain all the required relationships. In other words, for all the host groups that you specify in the file, only those hosts will be in that group after you run this utility. If the host group previously contained other host(s) that are now no longer listed in the file, the utility removes those host(s) from the host group and moves them to the recycle folder. The utility does not delete host groups from the Reporting Database; it only removes members of a host group. If a host group in the Reporting Database is not listed in the file, the utility does not take any processing action against that host group. Host groups with many hosts can be split into multiple lines for ease of file maintenance--for example, the host group and some of the hosts appear on the first line, then the same host group and other hosts appear on subsequent lines. |
Logging | The utility logs all additions, updates, warnings, and errors to the scon.log file, which is located under /tmp by default on Linux systems and C:\opt\oracle\logs on Windows systems. Logging strings are typically in the following format: Date -> Time -> Level -> load_package:sub_routine -> Action Where: Level is DBG, INFO,WARN, or ERR. sub_routine is the sub routine that is being executed (e.g. loadServerLine). Action is the action that was being reported on. Example: 14-MAY 19:00:06 ERR load_package:loadServerGroupMembers: Host group /APTARE/Business Views/Regional Offices/ Connecticut does not exist on line 6 of the data load file |