Database Reference
In-Depth Information
SYSMAN_APM
,
SYSMAN_MDS
, and
SYSMAN_OPSS
are metadata schemas for Fusion Middleware
components.
•
SYSMAN_BIP
is used for Business Intelligence (BI) Publisher integration.
•
SYSMAN_RO
is a general-purpose, read-only user.
•
Not much detail is provided in the Oracle documentation on these accounts. Suffice it to say, though, that these
are all special accounts that you should not drop. Nor should you change their passwords.
Repository Views
Information about administrators, targets, metrics, blackouts, and jobs is all kept in the Oracle Management
Repository in a group of repository views. Although the information in these views is obviously used by the Cloud
Control console to display that information to you, it can also be used in other ways, primarily by a programmer
building extensibility on top of the Enterprise Manager product. As a plug-in developer, for example, you may want to
extend Enterprise Manager to manage your own, custom-developed targets, or indeed expand on the target types that
Oracle provides out of the box. You may also want to write your own scripts to query historical data from these views,
or build your own custom reports to run from SQL Developer or other products. Clearly, a chapter on the Enterprise
Manager architecture is not the place to drill into gory details on how to do all these things, but it is worthwhile to
understand what these repository views are and how to find more information about them.
The repository views are documented as part of the
Enterprise Manager Cloud Control Extensibility Programmer's
Reference
(you can access this from the EM12c documentation located at
http://docs.oracle.com/cd/E24628_01/
index.htm
)
. Chapter 18 of that online reference details the use of those views, along with a complete listing of the
views displaying the column names for each view.
Communication Flow
When you first start using a product such as Enterprise Manager Cloud Control 12c, one of the areas of greatest
confusion is just how communications flow between the various parts of the product. Essentially, you need to
understand three areas: the protocols involved, the ports that are being used, and whether firewalls are being used.
Protocols
Three main protocols are used to communicate between the components in an EM12c installation:
Hypertext Transfer Protocol (HTTP) or Hypertext Transfer Protocol/Secure (HTTP/S)
: These
are the underlying protocols used by the World Wide Web. They define how messages are
transmitted and formatted, as well as the actions that browsers and web servers take in
response to different commands. HTTP and HTTP/S are used to communicate between the
OMA, OMS, and OMR. For security reasons, Oracle typically recommends using HTTP/S
rather than HTTP.
Java Database Connectivity (JDBC)
: This Java standard is used by the OMS to communicate
with the repository, as well as to communicate with any database targets.
Internet Control Message Protocol (ICMP)
: This protocol is used by the OMS to
communicate with a host, to check the status of the host. Essentially, a ping command is
used to check its status.
