Installing the OEM adapter

IT Asset Management (Cloud)

The OEM adapter is normally installed on an inventory beacon that has high-speed network access to the Oracle server to which the adapter must connect. It is possible to install multiple instances of the OEM adapter on the same computer, each configured to access a different OEM repository. Each instance of the OEM adapter can access exactly one OEM repository.

To install the OEM adapter:

1. From the unzipped Adapter Tools archive, navigate into the Oracle Enterprise Manager Adapter folder.
   For details about downloading the archive, see Download Adapter Tools Archive.
2. In Windows Explorer, execute the OEMAdapter.exe installer from that folder.
   If this is the first installation of the OEM adapter on this computer, the welcome page appears, and you can click Next. If another instance of the OEM adapter is already installed on this computer, the following screen appears.
   
   
3. If this page appears, choose either of the following:
   1. For an additional installation, click Install a new instance, and click Next. Follow the remaining instructions below.
   2. To change one of the instances previously installed, select the instance from the list on this page, click Maintain or upgrade an existing instance, and click Next.
   The Customer Information page appears.
   
   
4. Identify the license owner, and the enterprise name, in the User Name and Organization fields respectively.
5. Provide credentials for the Windows scheduled task that triggers operation of the OEM adapter.
   Tip: This account need not be the same as the one to access the OEM repository (identified in a later page).

   Leave the fields blank to run the scheduled task as the local SYSTEM account on this computer.

   Note: To change timing or frequency of the scheduled task, use the Microsoft Windows facilities as usual. They are not configurable through the installer.
6. Click Next >.
   The Destination Folder page appears.
   
   
7. Optionally, click Change... to modify the supplied installation location.
   Note: If you are installing multiple instances of the OEM adapter on this computer, you must modify the path so that each is installed in a separate folder. The InstallShield wizard offers the default folder 0 for the first instance. Increment this value to give a unique folder for each instance.

   Important: By default the OEM adapter saves the .ora file in the directory where it is executing (that is, the one you specify here). This is useful as a holding bay where the files may be manually inspected for initial testing/verification; but no automated processing of the .ora files occurs from this location. For automated operation after initial testing, you must reconfigure the file path and name as described in Configure Data Staging.
8. When satisfied with the location, click Next >.
   The Database Connection Information page appears.
   
   
9. If necessary, confer with your Oracle DBA to complete details about the Oracle Database from which this instance of the OEM adapter collects inventory:
   1. In the Host field, identify the server where Oracle Enterprise Manager is installed.
   2. The Port is used by the OEM adapter to access Oracle Enterprise Manager.
   3. Service Name identifies the Oracle service (for this database instance) that was defined when Oracle was installed.
   4. UserID is the account name (with its related Password) accepted by Oracle Enterprise Manager for login by the OEM adapter.
      Suggestion: FNMS-OEMadapter.
   When satisfied, click Next >, and the Email Configuration page appears.
   
   
10. To receive email alerts when the OEM adapter encounters any errors:
    1. Enter your email address as the To Mail value.
    2. In From Mail, enter the email address from which the error alerts should come.
    3. In the SMTP field, enter the fully qualified domain name (or IP address) of the email server.
       Tip: Ensure that the To Mail and From Mail addresses are both recognized by this email server.
    4. Click Next >.
    The Ready to Install the Program page appears.
11. When satisfied, click Install.

The installer writes the OEM adapter executable (OEMAdapter.exe) into your chosen folder, and records your other settings in a configuration file (OEMAdapter.exe.config) saved in the same folder. It also creates a scheduled task to run the OEM adapter. To allow for multiple instances of the OEM adapter on the same computer, the scheduled tasks are named based on the numbering of the installed instances. The default scheduled task for the initial installation on a computer looks like this:

You may update the scheduled task(s) as usual through the Microsoft interface.

Before using the OEM adapter in production, you must also do all of the following:

• Confirm that the account used to access Oracle Enterprise Manager (suggested name FNMS-OEMadapter) has adequate permissions to read from the OEM repository (see Grant Permissions to Account)
• Modify the location where the .ora file is saved for production use (see Configure Data Staging)
• Ensure that the appropriate subnets containing target Oracle servers are identified and assigned to the inventory beacon where the TSNNames.ora file is saved (see Assign Beacon to Subnet)
• Configure the collection of Oracle inventory in the web interface for IT Asset Management (see Configure Collection of Oracle Inventory)
• Set up accounts on each Oracle server with adequate permissions to gather inventory, with target machines being based on the contents of the .ora file created by the OEM adapter (see Inventory-Gathering Accounts on Oracle Servers)
• Register the same account(s) in the Password Manager for each relevant inventory beacon (see Save Inventory Account in Password Manager).