This set of step-by-step exercises will walkthrough the discovery of a BPEL PM target and setting up monitoring configuration for the target.
Navigating to application servers
As the SOA Suite and BPEL Process Manager server is hosted on an application server (for example, Oracle Application Server, Oracle WebLogic Server), the first task is to visit the application server home page:
Navigate to http://<Grid_Control_server_name>:<server_port>/em.
Log in as sysman. Use the password you set during the installation.
Click on the Targets tab.
Click on the Middleware sub-tab.
Note
This is a view showing all of the monitored application servers (Oracle AS, BEA WebLogic, and so on) within the enterprise. For each target, a summary of status with details, alerts, policy violations, CPU usage, and memory usage on the host are tabulated.
Discovering a BPEL PM target
The administrator needs to inform Grid Control to explicitly discover the application server and the associated targets such as BPEL PM. Before attempting discovery, the Grid Control Agent (10.2.0.3 or higher) needs to be installed on the host with the application server software. Note that a remote agent can also be used to discover an application server. The only drawback with a remote agent is the host and operating system metrics for the application server machine will not be picked up.
As shown in the following screenshot, from the drop-down list on the right, add an Oracle Application Server target. Click on Go.
On the Add Application Server page:
Click on the flashlight icon to pick a host.
In the pop-up window, select the radio button for the host and click on Select, as shown in the following screenshot:
On the Add Application Server page, click on Continue on the right.
On the Discover Application Server: Results page, click on OK.
In a very short time, you should get a confirmation page. Click on OK.
On the Application Servers page, click on Expand All and view your application server.
Note
Notice the components of this application server. Notice the two OC4J targets, as well as the Oracle BPEL Process Manager target.
Navigating to the BPEL PM target home page
The BPEL PM target is a child target of the application server target. There are multiple ways to navigate to the home page of the BPEL PM target; the most common path is to click on the Oracle BPEL Process Manager target name hyperlink.
Note
On the Oracle BPEL Process Manager home pages, you will see the Status label, which shows the availability status of the BPEL PM server, Availability (%) (last 24 hours), Oracle Home, and Host.
Configuring a BPEL PM target
Once the BPEL PM target is discovered, the administrator needs to provide the target with basic configuration information. This enables the BPEL target in Grid Control to talk to the BPEL PM server. This communication is needed because the BPEL target collects out-of-box monitoring metric data by polling the BPEL PM server through APIs.
Under the Related Links section at the bottom, click on Monitoring Configuration.
Enter the administrator username for BPEL Process Manager as oc4jadmin.
Enter the password for the administrator as welcome1.
Enter the Initial Context Factory as com.evermind.server.rmi.RMIInitialContextFactory.