Monitoring the Hosting Platform - Expert Consolidation in Oracle Database 12c - page 292

The Initial Configuration Steps
The first user account you have available after a fresh installation as just shown is the SYSMAN user. After the OEM
welcome screen has loaded, connect as SYSMAN using the password you defined at installation time. You will be
asked for a default home screen, a choice that does not require a lot of consideration at this point. The enterprise
summary screen seems a good candidate for the default screen, but you can always change your home screen.
Figure 8-2 earlier in this chapter showed the summary screen.
Enterprise Manager 12c has a central configuration menu to be used, named “Setup”. It can be found near the
top-right corner of the screen and will be used extensively throughout the next sections. The example assumes a
connection of the OMS to the Internet—either direct or via proxy—which Oracle refers to as the “online” mode. The
alternative is named an offline connection and is not covered in this chapter.

Configure My Oracle Support
Enterprise Manager relies heavily on My Oracle Support. Although each user you create in Enterprise Manager can
store his own credentials for My Oracle Support access, it might be a good idea to start configuring MOS for the
generic SYSMAN account to see if the access works. In order to do so, navigate to Setup ➤ My Oracle Support ➤ Set
Credentials. Enter a user name and password for My Oracle Support and click on the “Apply” button. At this stage
nothing will happen, since you have not yet configured Enterprise Manager's connection mode. Proceed to configure
the connection mode next.

Configure the Connection Mode
Enterprise Manager can be configured to connect directly or indirectly to the Internet. Oracle calls the two modes
of operation online and offline. Offline mode has to be chosen if the OMS is securely placed behind firewalls and no
proxy is available to connect to the Internet. It is by far the safest operation, but certain features in OEM will not be
as easily available. To keep this chapter within a reasonable page count, the example Management Service will be
configured so that it can access Oracle's support website via a proxy.
Connection settings are available via Setup ➤ Proxy Settings. The screen you are shown has three tabs: “My
Oracle Support and Proxy Connection”, “Online and Offline Settings”, and “Linux Patching Setup”. The default
connection mode for Enterprise Manager is “online”. You can check the current setting in the tab named “Online and
Offline Settings”. Please ensure that your system is “online” if you would like to follow the example.
Next please revert back to the “My Oracle Support and Proxy Connection” tab of the Proxy Configuration screen.
Take a moment to look at it. You will see that it contains the following sections:

• My Oracle Support

• My Oracle Support Connection Setting

• Agent Connection Setting

You should begin by configuring the proxy under “My Oracle Support Connection Setting”. Select the radio
button “Manual Proxy Configuration” and enter the proxy information. Depending on how your proxy is configured
you may need to enter the realm, and provide authorization and authentication information. If you like you could
also tweak the connection settings, the defaults for connection timeouts and retries are usually just fine. Now click on
“Apply” to save your changes.
The next item to consider is the Agent Connection setting. Most users choose “No proxy” here if the OMS can
directly communicate with the agents. If you made a change, click on “Apply” again.
The URL for My Oracle Support does not normally need to be changed. You can use the “Test” button right next
to the “Patch Search URL” to test connectivity with My Oracle Support. If that test fails you most likely did not enter
your credentials as described in the previous section. You should also test the agent connectivity right at the bottom of
the page. The “Test” button is to the right of the “Test URL” input field.