SYSCO_MW_EM12c_Rollout.pdf

sysco.no

Enterprise Manager 12c Rollout

sysco.no

Overview

• Architecture / Planning

• Installation

• Users/Credentials/MOS

• Licensing

• Extensibility

• Patching

• Groups

• Monitoring Templates

• Incidents/Notifications

• Discovery

• Competence

sysco.no

What do you want from EM12c?

• What will be the role of EM?

• What other tools will you use?

• Do you need integration?

Architecture / Planning

sysco.no

Phases

Planning/Architecture Licensing

Installation Patching Integration Backup / Recovery

MOS Connection/Credentials

Authentication

Group Setup Target discorery Monitoring Templates Incidents/Notifications

Daily use of EM Upgrading

Architecture / Planning

sysco.no

Do you need licences from the start?

• No, you do not

• You need licence(s) when

– You need HA options

– You need management pack options

Architecture / Planning

sysco.no

Check – Do you need a separate test and production environment?

• Pros

– Only possible solution when there are separate network zones

– Can test patches in test environment

• Cons

– Higher cost for maintenance and hardware

– Cannot verifiy every patch first, but do you need it?

Architecture / Planning

sysco.no

Check – Where is your service desk?

• Will all be handeled in EM ?

• Do you have external systems for this?

– Nagios

– HP

– Remedy

• This is handeled by Connectors or custom

Architecture / Planning

sysco.no

Check – Is there any ITIL requirements?

• EM fits the ITIL vocubulary well

• There is good support for compliance rules / framework

Architecture / Planning

sysco.no

Check – Will you use an LDAP service?

• You can have a user base in EM, but we recommend only for a small

set of users

• If you have LDAP in place, we recommend using it

• This will need some setup on the LDAP service

• Use personal users – not SYSMAN

Architecture / Planning

sysco.no

Check – Do you have any OS requirements?

• We recommend Oracle Enterprise Linux

• But others work too

Architecture / Planning

sysco.no

Check – Can you run this virtual?

• Recommended is dedicated physical environment

– For redundancy: ODA X4-2

• For virtual environment we recommend OVM

– Not on same virtual environment as the rest (separate OVM Manager)

• Licencing is not an issue, so use a fast server – recommendation is 32GB RAM,

minimum 16GB RAM

• Check that your disk is not slow

• Our recommendation is the simplest choice: Run DB and EM on same node

Architecture / Planning

sysco.no

Check – Do you need HA?

• HA will require HA on database, and you will have to licence the database

• HA will require a more complex installation procedure

• For clustered install, Oracle Database Appliance is an option

• If you are not sure, plan for HA or growth

– for example configure a virtual host name

– use the middle size option instead of small

Architecture / Planning

sysco.no

Installation, patching & deployment options

• Is handeled in separate presentations

Installation

sysco.no

Browsers

• Chrome is the fastest

• Firefox comes as second

• IE is very slow on older versions

• Have seen login-problems on different browsers

• You need to handle Certificate that comes with EM, it gives

certificate problem

sysco.no

Licencing

• Enable Annotations

• Enable/disable appropriate packs

sysco.no

Credentials

• Each target type has a set of credentials (name/password)

– Ex Agent: Normal Host Credentials, Privileged Host Credentials

• Default Preferred Credentials

– Target Preferred Credentials

• Named credentials (use them)

– Can be given access to for others

sysco.no

Credentials

sysco.no

Credentials

sysco.no

Competence

• Try out EM!

• Install on a test server or use Virtual Box Image

• Trainings or tailored Workshops

• Or work together with those who know the products

sysco.no

Common Challenges

• Do not get relevant notifications

– Must activate relevant rules

• Do get too many notifications

– Stop those not relevant

• Target monitoring / Notifications

Up and running

sysco.no

Q&A

• Email: [email protected]

• Twitter: jphjulstad