Application Management Pack for Oracle EBS – Part 2 (Discovery)


In the previous article we have seen various benefits of using Applications Management Pack for EBS. In this post, we will see how to discover Oracle EBS Instance in EM Cloud Control.


Add the necessary Targets:

Before we add the EBS target, we need to ensure that the EBS Database, Application Hosts are already having agents running. If not, add all the EBS hosts first. Then add the EBS Database target. Find the related articles below for these tasks:

Deploy AMP Plugin in OMS and Agent:

Once the target hosts are added, we need to first deploy the EBS plugin. EBS plug-in unfortunately isn’t available by default in EMCC so we need to download, upload and deploy it manually. Please follow this article for it:


We are currently using EBS AMP Plugin The main document you need follow is:
Getting Started with Oracle Application Management Pack (AMP) for Oracle E-Business Suite, Release (Doc ID 2045552.1). There are important patches to be applied on EBS, OMS and Agent.

For EBS, I applied the latest CPU i.e. Apr 2019, 29524595.
For OMS, ensure you have applied the below patches:
For Agent (EBS Target Agent):
If you don’t apply all the patches above, you will be facing issues for sure and I cannot assure you your EBS discovery will succeed without these


Now that we have all the prerequisites done, we can now discover the EBS target. Firstly run prevalidate option in Targets –> Oracle E-Business Suite –> Administer –> Discover. During this prevalidate, we need to provide 3 credentials as showing in the screenshots below:

  • Monitoring – APPS (DB) user
  • WebLogic – EBS WebLogic
  • OS credentials

Run the prevalidate option to ensure that all the credentials and the prerequisites are validated. Once the prevalidation is done, move on to the discovery.

Discovery is very straight forward. Simply click on discover option and continue with the prompts. Since we have already prevalidated this EBS instance, we have all the credentials saved, so click next and continue.

Now that the discovery is complete, we can see that the EBS Instance target has been successfully added. Now you see that EBS status is showing as down in my case only because I haven’t configured any Workflow mailer and since that component is showing as down, the whole EBS instance target is showing as down which is nothing to bother about and can be fixed.

So to fix it, simply go to Discovery Wizard and Select No for all workflow components to ensure they are not added as targets to be monitored. After this, run Discover one more time and this time it will show EBS target running fine since workflow components have been ignored.


  1. Can you please guide how to configure EBS with SSO in OEM. When I set credentials in OEM it redirects to SSO page and test fails.


Please enter your comment!
Please enter your name here