Install and monitor Weblogic in HP-Mercury sitescope

1. Introduction to mercury sitescope
Mercury sitescope is a non-agent monitoring solution that ensures the availability and performance of distributed IT infrastructure, such as servers, operating systems, network devices, network services, applications, and application components. This active, Web-based infrastructure Monitoring solution is very concise and fully customized based on the customer's needs. You do not need to add additional agents to your online system. Sitescope also acts as a basic monitor for other mercury products (such as mercury Bac, MMS, LoadRunner.
Sitescope provides 24 × 7 monitoring services for the launch system, helps maintenance engineers identify problems in a timely manner, and ensures the normal operation of all components in the system architecture. In addition to significantly increasing the detection cycle, sitescope also reduces the cost of maintenance personnel.
Sitescope can monitor Unix server resources, Windows Server resources, WebLogic application server, IIS application server, Oracle database, sqlserver database, F5, URL address, ping, memory, CPU, disk space, and service and so on; the monitor detects the target at a specified frequency. Once an exception is detected, it sends an alert to the Administrator in a timely manner. Alarms can be sent through sound reminders, emails, and text messages. In addition, sitescope can also generate a summary report of monitoring activities, which reads historical information from the log file, summarizes and filters information, and generates a report in the chart format.

Sitescope can reduce the total cost in the following ways:
1. collect detailed performance data of basic components
2. Eliminate additional memory and CPU resources from running agents in the Product System
3. Centralized Maintenance on one server to reduce the total maintenance time and cost

4. Eliminate any need to interrupt the product system by upgrading the agent
5. Eliminate the time wasted for tuning monitoring agents and other agents that coexist
6. Reduce the installation time required to observe product services or wait for software programs to be distributed and run.
7. Avoid system shutdown or loss of transactions due to unreliable agents
Sitescope features:
Mercury sitescope is a software that provides Failover (Failover) capabilities without the need to monitor basic components on the product system. It supports simultaneous monitoring of a large number of systems and Secure SSH connections, integration with other mercury application management solutions.

2. Install sitescope
Double-hitting installer hpsitescope_v9.5_win.exe, the following interface is displayed:

Click "Next" to continue.

Select "I accept the terms of the license agreement (a)" and click "Next ".

Select the Directory Name of the installer. The default value is c: \ sitescope. Click "Next ".

Select the installation type, select "HP sitescope for LoadRunner", and click "Next ".

In the HP sitescope environment configuration, the default port number is 8080. Enter the Administrator's email address and click "Next ".

Enter the sitescope license number and click "Next ".

For some installation information, click "Next ".

Wait ......

Click "Next" to complete the installation. The "Open sitescope 9.50" page is displayed in the browser, as shown in:

The installation of sitescope is complete.

3. Use sitescope to monitor resources
Enter the following information in the browser:
Http: // localhost: 8080/sitescope/servlet/Main. the localhost can be changed based on the server IP address. The display page is as follows:

Click health. The following page is displayed:

Click Create Monitor, for example:

Select "WebLogic application server" and click this option. The page is displayed:

Enter the relevant information, server: the address of the server you want to monitor; the port number used by Weblogic, default 7001; WebLogic JAR file: you need to copy WebLogic from the Weblogic installation directory of the monitored server (for example, c: \ Bea \ weblogic81 \ Server \ Lib. jar to the sitescope server and create a separate directory (for example, c: \ WebLogic) to store weblogic. jar.

Note: Do not store weblogic. jar in the \ sitescope \ Java \ Lib \ ext directory of the sitescope server. If the weblogic. jar is stored in the \ sitescope \ Java \ Lib \ ext directory, the running of the sitescope fails.
Click "Get counter". It takes about 3 minutes. The following page appears:

Select the counter to be monitored and click "OK ".

Click "OK" to bring up the following interface:

You can see the newly created WebLogic monitor.
4. Use LoadRunner to monitor sitescope Resources
Open Controller and select the sitescope resource in available graphs:

Click "add" to enter the address of the sitescope server.

Enter the user name and password of the server, and click OK.

Select a counter and click OK ".

Click OK.