SYSCO_MW_EM12c_SetupConfig.pdf

sysco.no

Enterprise Manager 12c - Setup

EM 12c Deep dive

sysco.no

Overview

• Target Groups

• Problem management

• Monitoring templates

• Notifications

sysco.no

Groups

• Groups are an efficient way to logically organize, manage,

and monitor the targets in your global environments.

• Each group has its own group home page

– Shows the most important information for the group and

enables you to drill down for more information.

– Shows the overall status of the group and other information

such as current availability, incidents, and patch

recommendations for members of the group.

sysco.no

Groups

• Groups enable you to collectively monitor and administer

many targets as a single logical unit

• A group can include targets of different types

• You can nest static groups inside each other

• If a system target is added to a group, it automatically

pulls in its member targets

• Privilege propagating groups enable administrators to

propagate privileges to members of a group

sysco.no

Groups – 3 types

• Static groups

– Works well for small deployments

• Dynamic groups

– Useful for larger deployments where change is frequent

– When the membership criteria is defined once, Enterprise Manager will automatically add targets.

• Administration groups

– A special kind of dynamic group

– Can be used to attach monitoring templates and compliance standards

sysco.no

Dynamic Groups

• The following requirements apply to dynamic groups:

– Dynamic groups cannot contain static groups, other dynamic groups, or administration groups.

– Administration groups cannot contain dynamic groups, however, a static group can contain dynamic groups as a member.

– OR-based criteria is not supported. All criteria selected on the criteria page are AND-based.

– Supported properties are limited to global properties plus other attributes specifically supported for administration groups such as Version, Platform, Target Name and Type, and so on. Specifically user-defined properties and other instance properties, plus config data elements are not supported as criteria.

sysco.no

Administration Groups

• Automating the application of management settings such

as monitoring settings or compliance standards

sysco.no

Administration Groups

• You can only have one administration group hierarchy

in your Enterprise Manager deployment

– Group member targets can only directly belong to one

administration group

– Prevents monitoring conflicts from occurring

• Start with the highest (root) level consisting of all targets

that have been added to Enterprise Manager

• On the next level of the hierarchy, you organize the

targets into groups

sysco.no

Administration Groups

• Target properties that can be used in the creation of administration groups are:

– Lifecycle Status

– Location

– Line of Business

– Department

– Cost Center

– Contact

– Platform (*)

– Operating System (*)

– Target Version (*)

– Customer Support Identifier (*)

– Target Type (*) Cannot be changed fromconsole

sysco.no

Lifecycle status

• Lifecycle Status can be any of the following: – Mission Critical

– Production

– Staging

– Test

– Development

• You can change display name, but not add/change types

• Lifecycle Status is used by EM when it is under heavy load in prioritizing incoming alerts and data.

• Mission Critical and Production targets are given the highest priority so that alerts always get loaded.

• Targets of Development or Test status may be asked to "back off" until the load returns to a manageable level.

• If the target property is not specified, Enterprise Manager assumes that the target is in the staging status

sysco.no

Target properties

• How can you set target properties ?

– During discovery

– Editing from console later

– Using CLI

sysco.no

User Defined Properties

• You can add custom properties

• These are not yet first class citizens

– You cannot use custom target properties in dynamic or

administration group selection criteria

• You can use them for reporting and notifications

– And that may be a good enough reason to add them

sysco.no

User Defined Properties

sysco.no

Target properties - naming

• Use consistent naming

– Location

– Line of Business

– Department

– Cost Center

– Contact

• Cannot define “valid values” for each field

• You can use database to verify naming

– For instance MGMT$TARGET_PROPERTIES

sysco.no

Target properties – bulk update

• Not well supported in Console

• You can use EMCLI for scripting (12.1.0.3)

– Need to install emcliadvancedkit.jar

• Can create scripts that

– Performs API calls to get relevant targets,

or use SQL query to database

– Performs target property update using emcli

sysco.no

Sample SQL

sysco.no

Sample emcli set target property

sysco.no

Problem management

• Problem management involves the functionality that helps track the underlying root causes of incidents

• Event– A significant occurrence of interest on a target that has been detected by

Enterprise Manager.

– Goal: Ensure that your environment is monitored.

• Incident– A set of significant events or combination of related events that pertain to the same

issue.

– Goal: Ensure that service disruptions are either avoided or resolved quickly.

• Problems– The underlying root cause of incidents. Currently, this represents critical errors in

Oracle software that represents the underlying root cause of diagnostic incidents.

– Goal: Ensure underlying root causes of issues are resolved to avoid future occurrence of issues.

sysco.no

Event/Incident/Problem Flow

sysco.no

Icon Severity Description

Fatal Corresponding service is no longer available.

Critical Immediate action is required in a particular area.

Warning Attention is required in a particular area, but the area is still functional.

Advisory While the particular area does not require immediate attention, caution is recommended regarding the area's current state.

Clear Conditions that raised the event have been resolved.

Informational A specific condition has just occurred but does not require any remedial action. Events with an informational severity: do not appear in the incident management UI, cannot create incidents, are not stored within Enterprise Manager.

sysco.no

Incidents

• All incident management/tracking operations are carried out from Incident Manager.

• Creation of incidents for events, assignment of incidents to administrators, setting priority, sending notifications and other actions can be automated using (incident) rules.

• Incident status

– New

– Work in Progress

– Closed

– Resolved

sysco.no

Incident

sysco.no

Rule Sets

• Incident rules and rule sets automate actions related to events,

incidents and problems

• Rules: A rule instructs Enterprise Manager

to take specific actions when incidents, events,

or problems occur, such as performing

notifications

• Rule Set: An incident rule set is a collection

of rules that apply to a common set of objects

• Rule Set Types: Enterprise or Private

sysco.no

Rule Actions

• Rule Application – events, incidents, problems ?

• Rule Criteria – Different criterias available

Rule Action Event Incident Problem

E-mail Yes Yes Yes

Page Yes Yes Yes

Advanced Notifications

Send SNMP Trap Yes No No

Run OS Command Yes Yes Yes

Run PL/SQL Procedure Yes Yes Yes

Create an Incident Yes No No

Workflow Attributes Yes Yes Yes

Create a Helpdesk Ticket Yes Yes No

sysco.no

Rule Set

sysco.no

Notifications

• Setting up email server (SMTP)

• Setting up your e-mail involves three steps:– Step 1: Define an e-mail addresses.

– Step 2: Set up a Notification Schedule.

– Step 3: Subscribe to incident rules in order to receive e-mails.

• Enterprise Manager does not directly support message services such as paging or SMS, but instead relies on external gateways

– Email(Long), Email(Short), Page(Short)

• Notification schedule

• E-mail Customization

• Custom notification methodsusing OS and PL/SQL scripts and SNMP traps

• Repeat Notifications

sysco.no

Monitoring Templates

• Monitoring templates let you standardize monitoring settings across your enterprise by allowing you to specify the monitoring settings once and apply them to your monitored targets.

• A monitoring template defines all Enterprise Manager parameters you would normally set to monitor a target, such as:

– Target type to which the template applies.

– Metrics (including metric extensions), thresholds, metric collection schedules, and corrective actions.

• In addition to templates that you create, there are also Oracle-supplied templates.– Create copies, not change the originals

• A template collection is an assemblage of monitoring/management settings to be applied to targets in the administration group

• Multiple monitoring templates can be added to a template collection

sysco.no

Compliance

• The EM 12c Cloud Control Compliance Management framework provides the

ability to evaluate the compliance of targets as compared to industry-wide and

business defined best practices and standards related to config, storage and

security. Can be attached to Administration Groups.

• EM 12c comes bundled with a number of in-built Compliance Standards

• The Compliance Library contains the Compliance Frameworks which are

comprised of Compliance Standards which in turn a collection of one or more

Compliance Standard Rules

sysco.no

Q&A

• Email: jonpetter.hjulstad@sysco.no

• Twitter: jphjulstad