Precise 10.1 is a complete Precise version, which includes and provides enhancements and fixes for Precise version 10.0. This topic describes the new features introduced, the technologies supported and no longer supported, and the issues resolved by this version.
Install Precise 10.1 in the following ways, depending on the currently installed Precise version:
Precise 10.1 supports monitoring on the following technologies and components:
Precise 10.1 extends the new user interface based on modern UI technologies to includes the Precise Report Manager.
This feature allows you to run the Precise Report Manager on modern web browsers, such as Google Chrome and Mozilla Firefox, and extends support for Microsoft Edge and Internet Explorer.
Before launching the new user interface, clear your web browser cache including all saved cookies. |
You can launch the new interface on most browsers using the following URL:
http://<host>:<port>/precise
For example, http://precisefp:20790/precise
For Internet Explorer, using the following URL:
http://<host>:<port>
For more information about this new feature, see Precise Report Manager New User Interface Notes.
The underlying Java Runtime Environment (JRE) Shipped with Precise is changed to an OpenJDK distribution. This replaces the previously-used Oracle JDK.
As a result, none of the internal Precise java processes (focal points etc.) use an Oracle JRE any more.
Precise 10.1 includes support for monitoring of Sybase instances when using a TLS 1.2-enabled PMDB.
The new UI includes a Settings menu on the Applications side.
Precise 10.1 no longer supports monitoring the following technologies:
You must restart the Precise Focal Point after an upgrade if you are using remote instances. You also must start the SQL agents after the Focal Point restart.
When an Oracle monitoring instance is created immediately after framework installation, errors can occur in Oracle warehouse processes located under Adminpoint > Warehouse Processes. In such cases, restart the Oracle Focal Point and PMDB focal point to resolve the problems.
After a fresh install or upgrade, you must restart the Precise GUI service before using the Custom Portal.
There is an issue with injdn.dll and injdn_x64.dll on Windows Server 2008 R2 with .NET monitoring. When a .NET instance is installed on Windows Server 2008 R2, a “Bad Image” error occurs. You can resolve this problem by installing the following Windows Security Update on the machine: https://technet.microsoft.com/en-us/library/security/3033929.aspx
Some of the binaries from the Precise 10.0 installer appear as a threat under AVG antivirus. This is a false positive with AVG and does not cause any problems. You may want to whitelist when using AVG as antivirus.
The first time you access the Precise custom portal (ASD) after a fresh Precise install or upgrade, it may fail to load. As a workaround, a one-time restart of the Precise GUI tomcat is required.
Use the following steps as a work around:
Stop the Precise FW services
On UNIX machines
./<precise_dir>/psin_stop_i3.sh
On Windows machines
.\<precise_dir>\infra\bin\psin_infra -multi-service stop
Start the Precise FW services
On UNIX machines
./<precise_dir>/psin_start_i3.sh
On Windows machines
.\<precise_dir>\infra\bin\psin_infra -multi-service start
Clear the browser cache.
Access the custom portal using url http://<hostname>:<port>/asd.
If the issue still persists please contact Precise Support. |
|