To capture resource monitoring
data from Oracle WebLogic Server, you must configure the data source.
To capture resource monitoring data from Oracle WebLogic Server, you must specify the path
to the client files:
- wljmxclient.jar
- wljmsclient.jar
- wlclient.jar
These Oracle WebLogic client files are provided with Oracle WebLogic, not with Test Performance, so you must copy the client files from
the server to a folder on the workbench computer. In Test Performance, click and specify the path to the folder containing the client files. The versions of
the client files must match the version of Oracle WebLogic Server running on the server under
test. By default, for Oracle WebLogic Server 10g Release 3 (10.3), the client files are installed
in the c:\bea\wlserver_10.3\server\lib\ folder.
The resource monitoring for Oracle WebLogic server works
with the Internet Inter-ORB Protocol (IIOP). If you use JMX protocol
in Oracle WebLogic Server, you can use the JVM monitoring option.
- In the Schedule editor, select the Resource
Monitoring category, and click Add.
- On the Location page, for a new resource
monitoring location, specify the connection and authentication information
for the computer that runs the Administration Server instance of Oracle
WebLogic Server for the domain. If you need to change the port that
is used to communicate with the Administration Server for the domain,
change the information in Connection. Typically,
your WebLogic system administrator specifies this information.
An Oracle WebLogic domain consists of one or more Oracle WebLogic
Server instances. One server is the Administration Server. If you
want to collect resource monitoring from an Oracle WebLogic domain
that consisting of multiple servers, the specified host must be the
Administration Server. The Administration Server is also known as
the domain controller.
- If administrative security is enabled on the Administration
Server, select Administrative security enabled.
- Type the user ID and password for Oracle WebLogic Server
in Authentication.
- Select Save Password to save
your password locally. If you do not save your password, you might
be prompted for it (depending on the host system configuration) when
you edit the configured location or when you run test schedules that
use the location.
- On the Resource page, select the type
of data to capture. The tree view shows the application servers that
the Administration Server manages and their counter groups and counters.
Be selective; monitoring all possible resource data requires substantial
amounts of memory. Clear the Show only selected counters check
box to see all available counters. Hold your mouse pointer over a
counter to see details about what that counter measures.
- Configure the options on the Options page.
- In Polling Interval specify in
seconds the interval for collecting resource data. For example, if
you accept the default of 5 seconds, counter information is collected
at 5-second intervals from the specified host during the schedule
run.
-
In Timeout Interval, type a time value in seconds. If the resource
monitoring host does not respond within this amount of time during a schedule run, an error
is logged.
-
Click the Cloud Options tab, and then select the Location
In Public Cloud checkbox to collect the resource monitoring data for the system
under test that is in the public cloud.
-
Click Next.
-
Enter a name for the location in the Name field, and then click
Finish.