Application discovery definitions that control the Business Process Views generation process
| Column Name | Column Datatype | Column Null Option | Column Comment |
| adm_add_uuid | byte varying(16) | not null | Unique Id for the Application Discovery Definition |
| definition_version | integer | not null | This version number is incremented whenever this Application Discovery Definition is changed. This includes any changes made automatically because of the autoreflectmods flag. |
| discovery_definition_name | varchar(64) | with null | The name of this Application Discovery Definition. This will be the name utilized when generating the Business Process Views in Unicenter NSM. |
| apm_application_name | varchar(64) | with null | Name of the application as known in APM. It is possible for this value to be NULL if the Business Process Views was imported. |
| description | varchar(255) | with null | Description of the application being discovered |
| creation_date | date | with null | Creation date of the first version |
| modified_date | date | with null | Modification date for the latest version |
| latest_bpv_version | integer | with null | The version number of the latest created Business Process Views. Zero means no prior version created. The version number here will be identical to the column bpvversion in the e2e_adm_add_component and e2e_adm_add_link tables. |
| last_discovery_time | date | with null | Last time the discovery was run on this application discovery definition (whether or not any changes were made). |
| last_analysis_time | date | with null | Time of the analysis data from which the discovery was based upon. This value is the maximum value of any transaction that retrieved from the modifiedtime column of the e2e_adm_rawtransaction table at the time of discovery. |
| bpv_uuid | byte varying(16) | with null | The uuid of the Business Process Views generated in Unicenter NSM. |
| source | varchar(10) | with null | The source of this application discovery defintion. The possible values are created, generated, or imported. Meanings are respectively, created by user, generated because application was discovered by APM, or imported by the user. |
| bpv_folder_name | varchar(128) | with null | The name of the BPV folder into which the Business Process Views will be created. |
| discovered | integer1 | with null | True if this version was discovered. Any definition updates will require a new version of the definition to be created if this is true. New versions always have this set false. |
| loaded_to_core | date | with null | Indicates whether the last discovery was successsfully loaded to core. Normally this will always get set to true if the bpv was generated but this allows for the possibility to do a discovery when not attached to unicenter. This capability will probably not be implemented in the first release. |
| discovery_status | varchar(20) | with null | The status of the discovery controlled by this definition. CREATED = The definition was created but no discovery was run. DISCOVERED = A discovery was run successfully. IMPORTED = The definition was just created by an import. NSM_DOWN = Discovery aborted because NSM was not available. |
| activity | char(16) | with null | The current activity of the Application Discovery definition. DISCOVERING=Being discovered at this time and cannot be modified by the administrator SUSPENDED=Has been suspended from doing discovery <empty string>=No activity at the current time. |
| imported_bpv | integer1 | with null | Was this definition the result of a import of an existing Business Process Views |
| imported_nsm_uuid | byte varying(16) | with null | The uuid of the Business Process Views that was imported |
| all_activity | integer1 | with null | Monitor all transaction activity of the application |
| auto_reflect_mods | integer1 | with null | Automatically reflect modifications to the Business Process Views as Tailoring Rules. If true then during Business Process Views generation the Comparitor will create rows in the table e2e_adm_add_bpvmods that reflect any changes made in Unicenter NSM to the previously generated Business Process Views. |
| bpv_delete_action | char(10) | with null | The action to take on the deletion of the BPV from the
repository - suspend, delete, or rediscover.
It may be set to rediscover, suspend or delete. If set to rediscover then if the Business Process Views was found to be deleted manually from core by the Comparator then the BPV will just be regenerated based on the current discovery info. If the value is set to suspend then the discovery status set to suspend no generation will take place. If the value is set to DELETE then a new version of the Application Discovery Definition will be created with the discovery status set to DELETED and no generation will take place. |
| excluded_ports | varchar(128) | with null | Commas separated list of ports that should not be followed during the analysis of the observations. |
| max_depth | integer | with null | Maximum depth during analysis and discovery. The maximum depth is relative to the clients during analysis and discovery. The client is considered to be at level zero and each link followed from component to component adds on level to the depth. For instance, all initial servers are a level one. |
| include_infrastructure | integer1 | with null | This is a quick flag to indicate whether to include infrastructure components. The default is false. If set 'false' it indicates not to include any infrastruction object during discovery correlation phase unless there is a specific overriding correlation rule to include an infrastructure component. If set true then infrastructure objects will be included if they fit the criteria of any of the correlation rules. |
| include_clients | integer1 | with null | This is a quick flag to indicate whether to include client components. The default is false. If set 'false' it indicates not to include any client object during discovery correlation phase unless there is a specific overriding correlation rule to include a client component. If set true then client objects will be included if they fit the criteria of any of the correlation rules. |
| backtracking | integer1 | with null | Flag indicating whether backtracking of links should be done during the analysis of the observations. |
| discover_on_new | integer1 | with null | If true will trigger a discovery when a new component is found |
| discover_without_nsm | integer1 | with null | Flag to continue discovery even if NSM cannot be contacted. |
Product Name: Unicenter Application Performance Management
Table Type: Table