Other Setup Activities

FlexNet Manager Suite 2022 R2 (On-Premises)

The OEM adapter is relatively straight-forward, and, as triggered by the Windows scheduled task set up during installation, regularly collects data from Oracle Enterprise Manager and saves the data as a TNSNames.ora file in a special location on the inventory beacon.

However, by itself, when the goal is to gather inventory from Oracle Database servers, the TNSNames.ora file is just the first step. Many other 'cogs in the machine' need to do their part for the .ora file to be beneficial:
  • You need a defined set of sites and subnets, most easily obtained by Active Directory import through an inventory beacon.
  • The subnet(s) containing your Oracle servers of interest must be assigned to the inventory beacon that collects the TNSNames.ora file, and which subsequently collects the Oracle inventory (see Assign Beacon to Subnet).
  • An inventory rule must be defined that associates the target subnet with an action including inventory collection using the TNSNames.ora file, and schedules its execution (see Configure Collection of Oracle Inventory).
  • Quite separately from the account that queries the OEM repository to create the TNSNames.ora file, one or more separate accounts must be defined that connect to the Oracle Database servers and collect the inventory data. There are two parts to configuring these accounts:

Strictly speaking, none of these are part of the OEM adapter; but all are integral to the process of Oracle introspection, and therefore are at least summarized in the following sections.

FlexNet Manager Suite (On-Premises)

2022 R2