Middleware mgmt: How to generate URL availability report for web applications?

1. Goto Targets->System, Add System, Provide System Name say ad4j,
2. Add Components to system. In my case, I added two weblogic Servers as Target components.
wls1 -> that has webapp1 URL
wls2 -> that has webapp2 URL
3. Goto Target->Services,
Add Generic Service ,
Provide Service Name e.g. ad4j_service
Select System i.e. ad4j Define Key components of system (Select needed web applications, in my case it's ad4j_http_test and petstore_http_test)
Define availability based on Service Tests
Select Test Type -> Http Ping->Give url_test_name and specify complete webapp1_url
Create Beacon->select agent which will be executing the http url test->Create beacon for that
Click on 'Verify Service Test', then move to next step
Select Performance Metrics (I went for default values for now)->next->..
Click on Finish
4. Till now we have defined the  system and Service based one web application url. Let's add another webapp_url.
Again goto Targets->Service
Select service web_app_service and click on 'Configure' button
Goto 'Monitoring Configuration'->Select Service Tests and Beacons
Add another 'HTTP ping' test -> Provide test name and url->Verify Service test and click on 'ok'
Enable newly added test
When check box appears under 'Key Service Test', select all tests and click on 'Change Key tests' button below this table
click ok
5.Goto 'Monitoring Configuration'->Availability Definition
Select 'At least one key service test is successful'. Click OK.
Select Yes when asked for confirmation.
6. You can get the URL availability report under Targets->Services
Click availability status icon for selected service.
It will give detailed report for entire service.

Given is example of URL availability if anyone of the URL is available and user wants to show status of web app as Up.

If one wants all URLs to be up and then show status as up, one needs to modify the availability Definition for Service and select service test rule as 'All key service tests are successful'.

How to add SOA Server (any FMW) Target in EMGC 11g?

Steps for discovering SOA (any FMW) target:

1.      Log into Enterprise Manager Grid Control.

2.      Goto Targets -> Middleware tab.

3.      Select Oracle Fusion Middleware/WebLogic Domain from the Add menu on top right drop down of page, then click Go.

4.      Enter the hostname of the WLS Admin Server of SOA domain for the domain in the Admin Server Host field. e.g. host1.abc.com

5.      Enter the WebLogic Admin Server port. Default value is 7001.

6.      Enter the WebLogic Admin Server username and password.

7.      Select or specify the hostname and port of the EM Agent that will monitor the domain. For EMGC 11g,  11.1 EM Agent is needed.

8.      Specify a Unique Domain Identifier. This value is used as a prefix to ensure farm names are unique in environments with the same domain name. By default, the name "Farm", followed by a two-digit number, such as, "Farm01" appears.

9.      Optionally provide the Java Management Extensions (JMX) Service URL that will be used to establish a JMX connection to the WebLogic Admin Server. For example:

service:jmx:t3://host1.abc.com:5555/jndi/weblogic.management.mbeanservers.domainruntime

        If no value is provided, EM will use the Service URL based on the host port and protocol.

10.    Click Continue. EM will discover all FMW targets within given domain.

11.    Click Close in the Finding Targets page to automatically assign EM Agents to the discovered targets.

       The Assign Agents page lists all the discovered FMW targets and the EM Agent assigned to each of them. Agents are automatically assigned as per following rule:

          *    If a local EM Agent is found on the domain host, that EM Agent will be assigned.

          *    If a local EM Agent cannot be found, the EM Agent specified in the Targets page will be assigned.

       Note: that one can also manually assign EMAgents to specific targets, if desired.

14.    Click Add Targets to assign Management Agents as listed in the Assign Agents page.

       The Saving Target to Agent processing page appears, indicating how many total targets have been added and successfully saved. It will also indicate the numbers of targets that were unsuccessfully added.

15.    Click Close when finished. The Results page displays the discovered targets and EM Agent assignments.

16.    Click OK when finished. There might be some delay before discovered FMW targets are visible and monitored.  

Note: Pl. ensure that all the EM agents used for monitoring the targets must be up and running.

Oracle Enterprise Manager 11g Grid Control Middleware Management Packs

Oracle Enterprise Manager 11g Grid Control comes with various management packs to manage different Middleware components and their performance. It includes:

a. Oracle WebLogic Server Management Pack [http://www.oracle.com/technetwork/oem/grid-control/overview/ds-wls-mgmt-132529.pdf]
This pack helps in
– spanning application performance management,
- Configuration management,
- Service level management and
- Operations automation
– improves performance and availability of Java applications and web services, improves service by avoiding downtime, and reduces cost by automating manual and error-prone operations.

b. Oracle SOA Management Pack [http://www.oracle.com/technetwork/oem/grid-control/overview/ds-soa-mgmt-pack-1-128301.pdf]
i) Oracle BPEL Process Manager
ii) Oracle Service Bus
iii) Oracle SOA Suite 11g
SOA Management Pack helps in
-Tracking and monitoring end-to-end business transactions across tiers
-Monitor the performance of SOA implementation technologies such as the Oracle SOA Suite and Oracle Service Bus
-Integrated web service testing and synthetic transaction monitoring
-Integrated authoring, attachment, and monitoring of security policies
-Collection and analysis of SOA configuration information

c. WebCenter Suite Management Pack [http://www.oracle.com/technetwork/oem/grid-control/overview/ds-camm-owebcentersuite-134498.pdf]
This pack helps in
-Monitoring WebCenter and WebLogic Portal applications via dashboards and drill-downs to root cause analysis
-Correlating WebCenter Services with underlying ADF Task Flows as well as underlying components
-Low overhead for 24/7 production monitoring
-No coding (or source code) needed
-Easy-to-read map of the WebCenter and WebLogic Portal application model-driven relationship views
-Automatic APM configuration determines what to monitor
-Auto-correlation ties every metric to high-end portal, transaction, and business functions
-Dynamic, auto-customized service-level dashboard allows any IT staff to manage performance

d. FMW Performance Management [http://www.oracle.com/technetwork/oem/grid-control/ds-as-dp-130384.pdf]
i) JVM diagnostics (AD4J)
ii)Application Dependency and Performance (OCAMM)
iii) Request Monitoring

e. Oracle Identity Management Pack [http://download.oracle.com/technology/products/oem/identity_management_pack_gc11.pdf]
i) Oracle Access Manager (OAM)
ii) Oracle Identity Federation Server (OIF)
iii)Oracle Identity Manager (OIM)
iv) Oracle Internet Directory (OID)
v) Oracle Virtual Directory (OVD)
vi) Directory Integration Platform Server
This pack has following features:
- Single-Step Discovery for both Oracle Identity Management 10g and Oracle Identity Management 11g components - Performance Monitoring: Proactively monitor your Oracle Identity Management environment from both systems & end-user perspectives.
- Configuration Management
- Service Level Management

f. Oracle Coherence Management Pack [http://www.oracle.com/technetwork/middleware/coherence/ds-coherence-mgmt-1-130356.pdf]
This pack has following features:
-Complete cluster visibility
-Monitor cache performance, stability and load distribution on nodes
-Provision new cluster or nodes
-Start/stop nodes or entire cluster
-Support for event tracking, notifications, charts and historical metric trends
-Monitors the entire Coherence infrastructure including monitoring WebLogic Server, Coherence Cluster, and the database as a single system
-Real time propagation of configuration changes to a node, a cache, or an entire cluster
-Monitor caches used by WebLogic applications