Organizing Jobs in EM13c, centralize or leave it to the team…

Using the EM Job System, especially for ‘house keeping’ jobs makes sense to many of the EM using organizations.


  • Team members should be able to schedule jobs
  • Team members should be able to create library jobs
  • Team members should be able to see, stop, resume jobs that were scheduled by other members in the team

We will discuss two possible approaches:

  • Centralized
  • Leave it to the team


I have seen organizations that prefer to work with a central EM account to locate Jobs (as well as for deployment procedures and reports). For this a ‘Non personal account’ is created, that is used to created, maintain and schedule library jobs.

A clear disadvantage of this approach would be that it is unknown which user actually modified or scheduled a specific job.  Something, your security officer will have a strong opinion about…

A clear advantage of this approach would be that all job definitions are to be found in one and the same account, which makes maintenance of library jobs easy. Job logs will be found at the same location and anyone having access to the central account can start, stop and resume jobs running in the account.

In order to get more team involvement, you could decide on creating a central account per team. So the Sales team would have a different account as the Human Resource team.

Leave it to the team

As working in Agile/Scrum teams is a standard way of working for many organizations, another approach could be: allow individual team members to create, maintain and schedule library jobs using their personal EM account.

This approach will make your security officer much happier as now it is clear who did exactly what.

Some disadvantages of this approach include:

  • The necessity of working with private roles
  • Jobs are scattered over multiple owners (team members)
  • You need to think of who is going to be the next logical owner whenever a team member leaves the team or even the organization. When removing this member as an EM user, EM will for another EM user to become the owner of the EM objects that are owned by the EM user you are trying to delete.

Advantages of using this approach include:

  • The team is responsible for creation, maintenance and scheduling itself and because of this fully self serviced
  • It is clear who did what and when

Using private roles

In order to allow other team members to view the logs and schedule and maintain the jobs, job privileges need to be granted. As the granting must be per administrator this could be a tedious job. For this using private roles could be a solution.

The private role should be created by a Super administrator or an administrator with the ‘Create role’ privilege.

This private role then should be granted to all team members once (and whenever a new member joins the team). Granting job privileges is than limited to the private role, in order to implement requirements as described above.

New Features – EM12c – Modify Administration Groups

One very powerful feature in EM12c I think is Administration Groups. It allows you to do a setup of monitoring settings that is continuously up to date.

Monitoring Templates as part of a Template Collections are instantly applied as soon as a Target become member of a Administration Group within its hierarchy.

One issue you could have with the setup of an Application Group Hierarchy is that, after creating it you could not change it anymore and had to delete it before being able to make corrections or extend.

Starting EM12c we can now modify an Administration Group Hierarchy after is has been created, which I think is a very welcome enhancement!

Screen Shot 2013-07-11 at 3.27.43 PM

In the example one level (Location) is added to an existing Hierarchy. The message in the page indicates that the change need to be save to the repository by pressing [Update]

After pressing the [Update] button a message shows up, telling you a job has been started to reorganise the Administration Group Hierarchy and you need to wait for it to finish.

Screen Shot 2013-07-11 at 3.28.39 PM

After the job has finished and you redisplay the page, the modification is completed.

Screen Shot 2013-07-11 at 3.29.10 PM

Start thinking of EMaaS

As Oracle Enterprise Manager supports the complete lifecycle of automated systems (Development, Test, Production), it might be interesting to think of enclosing EM for the complete IT Department and therefor start thinking of providing EM as a Service (EMaaS).

You might be interested in reading: Start thinking EMaaS


Auto Discovery of Targets in EM12c

Using Enterprise Manager 11 and earlier, you needed to install an Agent any time a new Server was introduced in your datacentre.

Then after you would have created a new Database or any other Target Type, you would need to perform a discovery using the Agent that was monitoring the specific server.

Starting with Enterprise Manager 12c your Targets can get discovered automatically even if no Agent has been installed yet.

Auto Discovery in EM12c