Discovering Fusion Applications in Oracle Enterprise Manager 12c

Introduction

Oracle Enterprise Manager Cloud Control 12c offers a comprehensive and convenient way to manage Fusion Applications environments.

Enterprise Manager relies on Oracle Management Agents to monitor and manage hosts and applications. These Oracle Management Agents are not to be confused with the Oracle Enterprise Manager Fusion Middleware Control agents that are deployed as part of Fusion Applications provisioning.

In order to allow end-to-end monitoring and management for the entire Fusion Application environment, it is recommended to discover the entire stack including all additional components that are not discovered by default. Only discovering all components unleashes the full potential for managing, monitoring and diagnosing Fusion Applications. The process to completely discover FA in Oracle Enterprise Manager can be broken down in the following phases:

discoveryWorkflow

Agent Deployment

Oracle Enterprise Manager offers a variety of different methods to deploy the Oracle Management Agents. The option shown here, installs the agents on remote machines without the need to manually copy the files to the remote host. To access this deployment method, simply select the Add Targets manually option from the Add Target drop down list.

agent1

The Oracle Management Agents should be deployed on all hosts that are part of the Fusion Applications deployment. This includes Oracle HTTP Server host and Servers where Fusion Applications has been scaled out to. Simply add all hosts to the list below and select the corresponding platform.

agent2

Generally it makes sense to deploy the Oracle Management Agent to the local file system to avoid dependencies to the storage system, however if you choose to deploy on a shared location make sure that even though the base directory can be shared the instance directory has to be unique in this deployment model. This can only be achieved by iterating through the Add Host Target Wizard. Make sure to add and test the Named Credentials and give it a meaningful name.

agent3

Review all settings in this screen and click “Deploy Agent” to continue to initialize the deployment.

agent4

The Wizard will let you know, how to proceed in case of any problems. A typical issue arises when the access rights to the Oracle Inventory are not setup correctly. This will lead to the error message: SEVERE: ERROR: Update home dependency failed ERROR: Agent Deployment Failed - Review MOS Support Note 1457347.1 to further analyze the issue. Missing sudo rights for the selected named credentials – as shown below – can be fixed by logging into the node as root to the target host and run the root.sh manually.

agent5

  • Discover Databases

  • The discovery process for the databases also gets initiated from the “Add Targets Manually” screen. There are other options to add and discover databases – these are described in the discovery documentation. This example shows how to add single instance database that are used with Oracle Fusion Applications.
  • database1

Select the host that has been discovered in the previous step where the databases are running.

database2

Oracle Enterprise Manager uses the dbsnmp account in the database by default – make sure to unlock this account and set a password. Also select the listener to be added to allow seamless end-to-end monitoring. All connections should be tested before moving on to the next step. In more complex environments (e.g. clone environments), it is strongly recommended to use the group functionality to be able to distinguish between the different environments.

database3

The review step reports any errors that might have happened during the discovery and concludes the database discovery.

database4

 

 

Discover Identity Management Components

After the database discovery is concluded the Oracle Identity Management components have to be added to the Enterprise Manager. The “Guided Discovery Process” used for the database can be used for the Oracle Identity Management components as well. Simply navigate to the “Add Targets Manually” window and select the “Add Targets Using Guided Process” checkbox. Set the “Target Type” to “Oracle Fusion Middleware/Weblogic Domain” and continue.

idm1

The discovery process connects to the AdminServer of the IDMDomain and uses this information to discover the other servers like the Oracle Access Manager, Oracle Internet Directory and Oracle Identity Manager. Should you have IDM deployed across multiple Domain, e.g. a separate OIDDoamin you have to repeat this process for each domain.

idm2

The “Assign Agents” Screen allows you to relate specific targets to agents.  The settings need to be reviewed carefully as Oracle Enterprise Manager defaults most targets to the agent that has been have selected in the previous screen. This is especially important if you have a multinode or scaled out environment. Clicking “Add Targets” concludes this part. You should validate that all components have been added correctly – including all OHS Servers that might be deployed for the IDM Stack.

idm3

Discover Business Intelligence Components

Next on the list off prerequisites is to discover the entire Fusion Applications stack are the Business Intelligence (BI) components. The “Guided Discovery Process” simplifies discovery for the BI components as well. Simply repeat the process used for the Identity Management Stack above to discover the BI Components via the AdminServer of the BIDomain – this will discover all required components.

bi1

Discover Fusion Applications

Next up is the discovery of the core Fusion Applications components. In order to add the Fusion Instance navigate to the Targets – Fusion Applications page and click on “Add Fusion Instance”.

fa1

The discovery process is using the CommonDomain AdminServer to discover the other products that have been provisioned in this Fusion Applications Instance. The agent selected on this screen is used for the discovery and will be the default agent for most discovered target. If possible select he agent that is deployed on the host that runs the AdminSever of the CommonDomain to simplify the post discovery allocation changes.

fa2

It is strongly recommended to configure all Product Families at this stage – even though not all products are being used the specific environment. Selecting every family makes it less difficult to analyze issues that occur across multiple domains. Multiple families can be selected by holding down the Shift key while selecting the families.

fa3

In this third step of the “Add Fusion Instance” wizard it is important to note that by default the Administration Server Host is discovered as the logical / abstract name which can lead to discovery problems. A typical issue here is the usage of the /etc/hosts to resolve the logical names in the Fusion Applications environment. The Oracle Enterprise Manager Server might not have this information and will have issues resolving those names. If there are issues during the discovery – replace the Administration Server Host settings with the physical names of the hosts where applicable.

fa4

The next step deals with the relationship of the Oracle Management Agents and the Fusion Application Products. Per default agents are assigned to the local products. This however needs to be checked especially in scaled out environments where multiple agents can potentially manage the same components.

fa5

Review all results in the final screen and move on to the association of targets.

fa6

Associate FA – BI – IDM

In this step all discovered components are associated with each other. The association of all components is required to enable the full management capabilities of the environment. Navigate via Targets – Fusion Applications and select the relevant Fusion Instance. Open the drop down menu behind the Fusion Applications button to access the “Additional Associations” window.

associate1

From here work the way through all other relevant components that have been deployed in this Fusion Applications Environment. Oracle HTTP Server don’t have to be associated in this example given the fact that they are collocated with the AdminServer of the IDMDomain/CommonDomain. If the Oracle HTTP Server has been deployed on different server, e.g. in a DMZ they have to be discovered and associated separately.

associate2

No error messages should be displayed when creating the association. WebChat and Oracle Social Network are not used in this example.

associate3

 

Summary

Whilst the discovery process of the individual components is well guided and straight forward – it is important to discover all components that are part of the Oracle Fusion Applications deployment. In most environments this includes Business Intelligence, Identity Management and the Oracle HTTP Server. Reliable management and monitoring is only possible when all components are associated with the Fusion Applications Instance.

 

Add Your Comment