Hi.

I'm hoping that someone can help me with trying to configure the Microsoft MP for JEE Application Servers to monitor WebLogic.  I downloaded it from here:

http://www.microsoft.com/en-us/download/details.aspx?id=44576

We have WebLogic version 12.1.3.0 running on Server 2012 R2 and are running SCOM 2012 R2.

I have imported the MPs:

 Microsoft.JEE.Library.mpb
 Microsoft.JEE.Templates.Library.mpb

Microsoft.JEE.WebLogic.12cR1.mp

but none of our JEE application server instances are being discovered automatically.

I have read the readme file and performed the following steps from it:

3. JEE application server instances on Windows are not automatically discovered without enabling agent as a proxy.
You will need to enable Operations Manager agent as a proxy in order for JEE application servers to be discovered on Windows computers.
To enable an agent as a proxy:
  a. Open the Administration workspace in the Operations Console.
  b. In the (left-side) navigation pane under Agent Managed under Device Management, select the computer that has the JEE application servers running, and click Properties.
  c. In the Security tab of the dialog box, check "Allow this agent to act as a proxy and discover managed objects on other computers" 

After that didn't work, i tried the manual discovery method from the readme file:

The System Center 2012 Operations Manager monitoring packs includes PowerShell scripts for manually discovering JEE application servers where such application servers cannot be automatically discovered.  For example, if you are running Tomcat as a Windows Service, or if you have JEE application servers running on machines not managed by Operations Manager.  The following steps describe how to manually discover a JEE application server. 
  a. Deploy BeanSpy to your JEE application server as described above.  
  b. If your application server requires authentication, create a Run As account to be associated with "JEE Monitoring Account" Run As profile for monitoring.  Create another Run As account to be associated with "JEE Invoke Account" Run As profile for invoking methods on MBeans.
  c. Obtain PowerShell scripts using one of the following methods:
        1) If you have at least one JEE application server automatically discovered by Operations Manager, go to Operations Console, select an automatically discovered JEE application server instance, and run the task "Copy BeanSpy and Universal discovery files" in the Tasks pane. This will copy the BeanSpy files to the %WINDIR%\temp folder.
        2) Search the Operations Manager installation folder for BeanSpy*. For example, if Operations Manager is installed under "C:\Program Files\System Center 2012\Operations Manager", BeanSpy files are located in one of the folders under C:\Program Files\System Center 2012\Operations Manager\Server\Health Service State\Resources\ as of this writing.
There should be three PowerShell script files:
    JEEAppServerLibrary.ps1
    NewJEEAppServer.ps1
    RemoveJEEAppServer.ps1  
  d. Run PowerShell scripts to add or remove application servers. 
        1) You can add or remove application servers one by one. However, if you have multiple application servers, you can create a configuration file. Each line of this file should contain a URL where your JEE application server is listening on for http or https requests. For example:
               https://linux.contoso.com:8080
               http://myredhat:8180
               http://10.0.0.1   
        2) To add JEE application servers for monitoring, run NewJEEAppServer.ps1.  Run this script with -help for details of command line options. You can pipe the configuration file you created to this script, or specify a single URL on the command line.
        3) To remove JEE application servers currently being monitored, run RemoveJEEAppServer.ps1.  Run this script with -help for details of command line options. You can pipe the configuration file you created to this script, or specify a single URL on the command line.
The discovered application servers will first appear under "Universal application servers" folder in the "Configured application servers" view. Verify that the application server type and version are populated correctly.  After multi-stage discovery (ranging from a few minutes to four hours by default), the discovered application server should appear under the application server folder specific to its type, in the deep monitored application server view, with detailed application server information populated.

This was partially successful.

We tried this on one server and it showed up under Universal Application Servers as per the instructions.  However, after waiting for a few days, it has not appeared under the WebLogic application server folder.  It's still in the Universal Application servers folder.

At this point, I'm not sure what else i can do.  

Can anyone help?

• Edited by DT_2100 Wednesday, July 22, 2015 1:48 PM