This package uses SSH to log into the Netscaler device. It starts by discovering the existence of Netscaler, and then follows the Spiral Discovery process to find version details, IPs, interfaces, hardware details. Load Balancing is mapped from virtual servers to dedicated servers via Services and Service Groups. VPN is mapped from virtual servers to dedicated URLs or servers via Policies and Actions.

Citrix XenApp

Discovers the existence of database instances via Shell. This enables dynamic instance/port discovery so customers do not have to specify instance or port for SQL connections. Currently supports MSSQL and DB2 LUW types.

Excel Export and Import Engine

Update Credentials

HP Integrated Lights-Out (iLO)

This package uses SSH to discover AppDirectors. It starts by discovering the existence of an AppDirector device, and follows the Spiral Discovery process to trigger again and gather Load Balancing information. Load Balancing is mapped via policies through Virtual IPs, farms, and the dedicated servers.

SSL Certificates

Without additional products, there isn't an OOTB solution that enables discovery of dynamic dependencies. And without dynamic dependencies you are limited in what you can provide higher level business initiatives (e.g. automated application mapping, data center migrations, security vulnerability efforts, etc). The purpose of Rapid Iteration is to enable a framework for lightweight queries to run frequently, and we do so from within the UCMDB.

This package uses SSH to login to an Onboard Administrator card on the BladeSystem. It starts by discovering the existence of the enclosure, then follows the Spiral Discovery process to find platform, type, firmware details, IPs, interfaces, server blades, and interconnects (e.g. Ethernet or Fibre cards). 

Citrix Provisioning Services

Database Connection

Web Components

Radware AppDirector

This package is responsible for taking a desired data set (query) from the UCMDB and pushing it into a remote MySQL database table.  There are several functional differences that make this more appealing than using an OOTB mechanism:

  • Caches the data set pushed in each invocation, for the purpose of historical retention thereby enabling admins to go back and see what objects were pushed when. That context is recorded in probe-side files (logs) that are rolled on each run, and customers can specify the file retention count.
  • The results can optionally be emailed on each invocation, if results are processed.
  • Customers can enable this functionality as either a Discovery Job or an Integration Point, whatever fits their specific UCMDB licensing.
  • The functionality supports both Full and Delta syncs. Delta syncs are NOT determined by the existence of cache data on the probe, which means “clearProbeData.bat” doesn’t cause a problem with the next invocation.
  • The time range for the Delta sync is determined by the last successful runtime of the job. The timestamp comparisons are not based on “last_modified_time” on CIs; that’s too generic.The timestamp comparisons are based on changes to only the specific attributes being pushed in that integration. For example, let’s say you only push “name” and “version” attributes for specific Running Software CIs. And let’s also say something (an Enrichment, Discovery job, Integration job, or user) happens to update the “data_note” and “description” fields on one or more of your Running Software Cis. Since those updates are not on the attributes pushed in the integration (“name” and “version”), they will not get pushed to the destination. This is a very important distinction that is understood when the target database table is actionable… e.g. each new or updated Running Software CI causes the provisioning of new monitors.
  • Level of Effort (LOE) for creating a new job to push a different UCMDB result set to a different table or a different database, is very small and in some cases (depending on the DB type) requires zero code changes. Just create a new discovery job or integration point, select the same adapter, and define a different set of parameters (e.g. query definition, target database, table, column names).
  • Each job you create (Discovery or Integration based) will create a unique tracking CI related to itself.This is extremely useful when needing to assess the health of active integrations, monitor job failures, dashboard system health, etc.It tracks attributes like Last Execution Date, Last Success Date, Failed Consecutive Executions, and Probe Name.

The purpose of this package was to create a new Change Report mechanism, allowing users to define which CIs/attributes should be tracked across which queries.  And allow jobs to uniquely report on different sets, customized per consumer.

CSV Import Engine

Reporting Missing Attributes

This package provides enhanced methods to discover processes, network, software, and routing on servers.  The code enables additional context, enhanced performance, and better control.  It also has a utility to track the status of endpoints and identify credential issues, decommissioned servers, and other anomalies.

​This package uses CiscoWorks RME to track firewall rule changes. It uses PowerShell or native WMI to first identify the existence of RME servers; then via PowerShell and Spiral Discovery, it provides coverage for firewall rule changes.

After running this package you know which nodes are firewalls, which is a normal gap in standard discovery since firewalls are rarely exposed. You also have dates: a timestamp when the initial firewall backup was done (usually indicating the standup date) and then a timestamp when the latest change occurred. Combining this package with other discovery jobs can provide impact at the Application and Service levels for Networking.

Dell Hardware

Citrix Netscaler

Database Detection

This package attempts connections to database instances (context) discovered by our Database Existence package. It only pulls user and password from the protocol entries; specifically avoiding manually entered data like SID/DBNAME or TCP port... required by the out-of-the-box functionality.

Microsoft Fail-Over Cluster

Database Usage

This package provides provides a robust solution for automated creation of XLS Workbooks with defined tabs representing the output of different queries, and then allows the re-importing of the workbook after user modification.

This package provides a quick start for creating credentials from an external data source.  It connects to the UCMDB and pulls back credential entries of requested types, does type transformations, and is stubbed to be used for updates from an external data store.  The idea is that a customer can use a scheduled UCMDB job to auto-update stored UCMDB credentials from a security tool of choice.

Licensing and Support

F5 BigIP

Application Components is a very flexible package that discovers dynamic software components.   It employs non-specific, general discovery techniques to provide coverage for the technologies that lack a specific discovery package, and then maps them across the customer's infrastructure.

This type of discovery is important when dealing with shared IT services (web, app, database), where a single server TCP endpoint or process can be leveraged by multiple clients. It is also instrumental in identifying custom applications ("app dev") or enterprise applications outside current DDM coverage.

Rapid Iteration

With more than 12 years of experience in UCMDB package development, Leverage Discovery provides top notch packages to its customers. Some package abstracts are listed below.  Please note, we've developed more than 100 packages for our customers to date, and so this is not a comprehensive list of our package inventory.  Some packages are customer specific and some are only available with a bundled solution or consulting engagement.  If you have a question about something not listed below, just ask.

Application Components

This package uses Shell connection to discover Cisco CSS devices. It starts by discovering the existence of Cisco CSS and then follows the Spiral Discovery process to find additional data. Aside from basic details like version, IPs, interfaces, and hardware, this package maps through the Load Balancing flows. Load Balancing is mapped from source to destination, through virtual servers, rules, services, SSL lists and redirects.

This package discovers Microsoft IIS via PowerShell.  The OOTB IIS discovery uses xCMD (a less secure, 3rd party shell) to run an IIS command line utility that's been around for years. Given the transition in Microsoft to using PowerShell, we decided to use PowerShell as the method of discovery.

The package starts by discovering the existence of IIS Servers. It then follows the Spiral Discovery process to find IIS components: Application Pools, Web Sites, Virtual Directories, Bindings, URLs, FTP Sites, etc. It follows the same class model as HP's discovery.

Microsoft IIS

This package provides similar coverage to the HP and IBM packages created previously. It uses multiple protocols (HTTPS/SNMP/SSH) to discover Dell Remote Access Cards (DRACs) installed or embedded in stand-alone servers, blades in enclosures, and enclosures themselves (where the DRAC is the CMC).

It starts by discovering the existence of the DRACs, then follows the Spiral Discovery process to find DRAC type/versions, machine hardware context, and chassis information. The final job communicates with the authorized Dell web service to gather corresponding Asset and Warranty data. Basically soup-to-nuts hardware discovery for Dell, across several protocols - depending on the way your company configured the DRAC devices at deployment.

Excel Import

This package discovers the topology of XenApp and maps applications across that topology. Using WMI, first it discovers the existence of a server hosting XenApp and then follows the Spiral Discovery process to find Servers, Zones, the Farm, configured Folders and Apps, and maps Applications deployed onto Servers.

Microsoft Active Directory

Reporting Perspectives

This package discovers Microsoft Cluster with PowerShell. Given the transition in Microsoft to using PowerShell, we used PowerShell cmdlets as the method of discovery. It leverages WMI instead of the Cluster cmdlet because the cluster cmdlet will only work on the latest version of MS Cluster, whereas the Get-WmiObject method works on older versions.

This package discovers HP Integrated Lights Out via webservice and SSH. With the web service, the discovery finds all iLO instances. When SSH is enabled for iLO, this package not only pulls hardware details about the Management card, but also details of the OS installed on the managed server platform.

This package uses OpenSSL over HTTPS to capture handshakes and gather information from SSL Certificates - without needing certs/keys. It pulls back Name, Issuer, Location, Organization, Serial number, and Expiration Date by default, with access to additional attributes.

Similar to Application Components, this package is intended for web-enabled endpoints. It uses non-intrusive methods to discover and profile the endpoints technologies, and allows you to use pattern recognition with TQLs after gathering data, to group and profile. So even if you don't have access to login to the endpoint, you can make a determination on what it is (WAP, iLO, LB, website, etc).


Reporting Changes

Reporting Jython

This package takes a set of report definitions and creates a bulk set of CSV reports. Initially created to generate a set of 10 reports for 300 different apps (3000 reports at the click of a button). Main points:

  • ​User parameter defines whether or not the previous report layer results will be included or excluded in the next layer of reports, similar to how perspectives work with perspective based views.
  • User parameter defines the high level CIT to use as an anchor for the reporting.
  • Reporting (per tenant or for the whole UCMDB) parameterizes and filters the result set, per instance of that CIT (e.g. business applications).
  • The engine loops through all provided definitions and creates similar reports for each high level CI. 

Cisco Firewall Rules

DNS Discovery

This package provides relationship reporting and more granular control over reporting capabilities. It also provides workarounds for issues in recent releases that require Display Labels on each CI. That can make reports quite a bit more bulky than expected, especially with multiple child CIs.  It is the prerequisite package used by other reporting packages.

This package uses PowerShell to discover and map out the Provisioning Services infrastructure. After identifying a Provisioning Server, it gathers the Farm, Sites, Collections, Devices, Stores, vDisks, and database and licensing servers.

If you are using our Citrix XenApp discovery, this package can additionally relate provisioned devices to the running OS images.

Database Push Framework

Reads in an Excel workbook, and creates/updates/deletes CIs and links, based on a user-provided definition for how to handle the records. This is similar to our custom Import CSV package, but this works off Workbooks with multiple sheets, instead of individual CSVs.

HP BladeSystem

This package discovers Active Directory via PowerShell. The first job replaces the OOB job by LDAP and discovers everything expected OOTB except site links, which were unnecessary for ITIL disciplines. The second job extends the original discovery, by getting OUs of servers in the uCMDB discovery domain scope and relating them to Group Policies. This allows customers to see impact of GPO changes.

Note: this package does NOT require access on the AD servers, which was a big win for security teams.

Host Discovery

This package uses SSH to log into the TMSH shell on F5. It starts by discovering the existence of F5 devices, then follows the Spiral Discovery process to find version details, IPs, interfaces, VLANs, trunks, hardware details, pools, members, virtual servers, and iRules. It parses content to map traffic through virtual servers to the member context. You do not get this mapping OOTB.

Leverage Discovery software packages are licensed in a very open manner (install wherever, modify/upgrade as desired), and are restricted by who has access to them.

Our software packages are supported according to support matrix sections of corresponding package documentation. Those versions are covered in the Software License Agreement. Customers can validate package functionality by testing the add-on software in a Proof Of Concept ("POC" or Trial) over a limited timeframe within their environment. That testing is covered under a Software Trial License Agreement. In this manner, customers can determine if a software package meets their needs - prior to purchase.

When customers want ongoing support for Leverage Discovery software packages (patches and version upgrades), they purchase a Software Support Agreement to pick up where the Software License Agreement ends. This allows customers to reduce the required level of in-house expertise, as upgrades for those packages are managed by Leverage Discovery.

Since the Leverage Discovery software packages are add-on packages to a larger HP software suite, upgrades may either be a result of upgrading the parent product (HP DDM, HP UCMDB) or a result of upgrading the target technology.

We work direct with customers and through resellers. Please contact us to start a Proof of Concept or determine if we have current support for technologies not listed above.

This package provides a more robust import mechanism:

  • a single CSV line can contain multiple CIs
  • enables the creation of relationships in addition to creating CIs and updating attributes
  • allows CI creation/deletion from what is in the UCMDB verses what is in the CSV
  • enables custom reconciliation, by allowing customers to define which attributes to use for identification in each CSV, instead of using the generic global engine

This package uses our Reporting Jython and Reporting Perspectives packages to to loop through and generate multiple reports per model. It does this for all models owned by a tenant, and then continues to do this for all tenants in the UCMDB.  The additional logic of this package allows calculations for determining the number of missing attributes and percentage complete for each of those areas.  The resulting reports list not just percentages, but detailed reports complete with attributes of each CI that is missing.

Cisco CSS

Shared Database environments remain a stumbling block with out-of-the-box discovery. The product provides client connections to database servers, but the following gaps exist with current techniques:

  • Mapping client connections to the specific database/instance
  • Qualifying the client connections to understand the actual application using the database

Currently supports MSSQL, DB2 LUW, Oracle, and Sybase.

This package discovers DNS via JNDI, WMI, and Shell. It finds name servers and follows spiral discovery to find DNS zone. When using WMI, customers can see DNS Forwarders and DNS Records for all IPs in the uCMDB - without needing zone transfer security setup for Probes (when using WMI instead of Shell).