Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > Database Performance Analyzer (DPA) > Changes to database clients discovery for DPA in Orion

Changes to database clients discovery for DPA in Orion

Created by Anthony.Rinaldi_ret, last modified by Anthony.Rinaldi_ret on Aug 23, 2016

Views: 12 Votes: 0 Revisions: 2

Updated August 23, 2016

Overview

This article describes how the database clients discovery has changed in DPA in Orion 10.2 and later.

Environment

  • DPA 10.2 and later
  • SAM 6.3 and later
  • Orion Platform 2016.2 and later

Detail

Original functionality

In earlier versions of DPA in Orion, the database clients discovery was a part of the Integration Wizard. This wizard automatically ran after you integrated your DPA server with the Orion Platform. There you could review and confirm all of the detected relationships.

The detected relationships between databases and clients are just database client candidates, however. DPA in Orion cannot detect whether SAM applications are database clients of a DPA server.

The DPA server provides a list of computer addresses identified (by the database engine) as database clients to the Orion Platform. DPA in Orion uses this list to collect all applications assigned to nodes, which matches the addresses of database clients. All of these application are then marked as database clients.

Changes to DPA in Orion 10.2

Integration Wizard removed

The integration process in DPA 10.2 is simpler. There is no Integration Wizard, because relationships are discovered and saved automatically without user confirmation. This includes when you add or remove an application or database instance.

You can still create relationships manually by clicking Manage Relationships in DPA Settings.

Database Instances in the AppStack

DPA in Orion 10.2 introduces a new category called Database Instances in the SAM Application Stack (or AppStack). You can see relationships between Orion nodes and applications and DPA database instances. Some of these relationships are the database clients.

Because DPA in Orion can only discover database client candidates, many of the applications (database clients) in AppStack should not be highlighted. This is because there are no database clients, which could make the AppStack difficult to interpret.

For this reason, the database client discovery is not performed when you integrate your DPA server with the Orion Platform. You must create database clients manually.

To view the database client candidates:

  1. Click Settings > All Settings.
  2. Under Product Specific Settings, click Database Performance Analyzer.
  3. Click Manage Relationships.
  4. Click the Client Applications tab.
  5. Click Find New Relationship, and click OK.

The discovered database client candidates are collected using the original discovery functionality. You can decide which of them are correct database clients.

Upgrade from DPA in Orion 10.0.1 or later

Database clients are migrated when you upgrade from an earlier version of DPA in Orion. Those database clients are just candidates, and you may want to remove them. You can delete relationships on the Manage Client Applications Relationships view accessed in the steps above.

Database clients are migrated as Orion dependencies. To view and edit dependencies:

  1. Click Settings > All Settings.
  2. Under Node & Group Management, click Manage Dependencies.
Last modified
09:24, 23 Aug 2016

Tags

Classifications

Public