Smarter, Painless and Predictable Upgrades with Enterprise Manager 13c Release 5

Why upgrade to Enterprise Manager 13.5?  

The Enterprise Manager 13.5 release provides many new features in the areas of Hybrid Cloud Management, Ops Automation and Extensibility. Along with these main pillars, Enterprise Manager 13.5 is shipped with WebLogic 12.2.1.4 stack, JDK 8 update 261. The repository database version certified with Enterprise Manager 13.5 is 19c in line with Oracle’s Oracle Database support policy.

Oracle has rebranded BI Publisher as Oracle Analytics Server so BI Publisher is no longer installed or configured beginning with Enterprise Manager 13.5. Starting with 13.5, a standalone rebranded, Oracle Analytics Server (OAS) will support out-of-the-box and custom reports from legacy BI Publisher. It makes Enterprise Manager lightweight and enables you to use all the rich features of OAS with the Restricted Use License for Enterprise Manager Repository views. We provide guided support to configure your Enterprise Manager installation with OAS and migrate your custom reports from BI Publisher to OAS.

Read the complete article by Martin Pena (SENIOR DIRECTOR PRODUCT MANAGEMENT)

Integrating BI Publisher with Enterprise Manager

As part of Enterprise Manager 12c a complete set of default Reports deployed in BI Publisher is available after integrating BI Publisher with Enterprise Manager.

The paper describes the installation and integration of BI Publisher 11.1.1.6.0 with Enterprise Manager 12.1.0.2 and it is really as easy as 1,2,3…

In this paper I assume that you did a fresh install of EM 12.1.0.2, however if your EM environment is based on an upgrade from 12.1.0.1 to 12.1.0.2 please take notice of the documentation Post-Upgrade Steps to take after upgrading to BI Publisher to 11.1.1.6.0

Integrating BI Publisher with Enterprise Manager

During the installation of OEM GC 11.1 on AIX, there was no auto discovery of the Middleware Components

While doing the installation of OEM GC 11.1 on AIX 6.1, I noticed that there was no automatic discovery of the Middleware targets.

This is due to bug 9969664.

The solution provided in MOS Note:

Error when discovering and monitoring secured weblogic domains on AIX platforms (using t3s/iiops protocols) in EMGC11.1 (Doc ID 1208874.1)

did the trick for me and discovered the 8 additional Middleware targets.