Oracle AutoVue
Meridian Enterprise supports AutoVue for source document viewing. A complete list of the supported file formats, user documentation, and additional technical documentation for AutoVue products can be found online at the Oracle web site. For the input and output formats supported by Accruent Publisher, see AutoVue Rendering Module Supported Formats.
AutoVue 2D and 3D viewing requires additional cost licenses and software that are available from Oracle. A list of the additional file formats supported by AutoVue 3D can be found at the link above.
-
When AutoVue is installed as a desktop deployment, the version of the Java Runtime Environment that is included with AutoVue is used by the viewer regardless of any other versions of Java that are installed.
When AutoVue is installed as a client/server deployment, the client computers require a Java Virtual Machine version that is listed in the Oracle AutoVue Client-Server Deployment Installation and Configuration Guide for the version of AutoVue that is installed (also listed in the following table).
- Each version of the AutoVue software supports specific Java versions. If the computer on which you want to install AutoVue must use a Java version that is unsupported by AutoVue in order to support another application, you can configure separate Java versions on the same computer for each application as described in Deployment Rule Set.
- Legacy Accruent viewer redlines and AutoVue redlines are incompatible and cannot be used interchangeably for the same file formats. If Accruent viewer redlines exist for AutoCAD or raster image files, they will be automatically converted to AutoVue redlines and shown in AutoVue. Editing and saving the redlines stores them permanently in the AutoVue format.
- The AutoVue desktop versions do not run in the Accruent 64-bit client applications. The AutoVue Client/Server viewer can be deployed in such cases.
- The Accruent Connector that is installed for use by AutoVue client/server deployments runs on the Java application server Jetty that is installed with AutoVue by default. In high load environments, we recommend running it on the Apache Tomcat Java server instead. Instructions on deployment can be found in the Meridian knowledge base.
- For information about deploying AutoVue on Apache Tomcat, see the Meridian Knowledge Base article How to deploy AutoVue on Apache Tomcat.
The versions of Oracle AutoVue that are supported by the Accruent products that use it are listed in the following table.
| Product | AutoVue 20.2.3 |
AutoVue 21.0 |
AutoVue 21.0.1 |
AutoVue 21.0.2 |
|---|---|---|---|---|
|
Meridian Enterprise/Meridian Explorer |
||||
| 2020 |
|
|
|
5
|
| 2019, 2019 R2 |
|
|
|
5
|
| 2018, 2018 R2 |
|
|
|
5
|
| 2017, 2017 SP1 |
|
|
|
|
|
Java Virtual Machine |
||||
| Java Platform Standard Edition3 |
8 and higher 7 update 45 and higher |
8 update 11 and higher 7 update 45 and higher |
8 update 11 and higher 7 update 45 and higher |
8 update 11 and higher 7 update 45 and higher |
-
Beginning with release 2016, two rendering modules are provided that are both based on AutoVue software. The AutoVue rendering module uses the AutoVue Desktop version 20.0.4 that supports the most rendering options but older file formats and has been discontinued by Oracle. The AutoVue Desktop Deployment rendering module uses the AutoVue client/server edition that is installed as a desktop deployment, supports newer file formats, and is fully supported by Oracle but supports fewer rendering options. A complete list of the supported formats can be found on the Oracle web site.
-
Industry Foundation Classes (IFC) files generated by Autodesk Revit that contain encoded comments are not supported.
-
Some updates might register the wrong path to the Java runtime library during installation and require manual correction as described in:
JRE 1.7.0 Update 1 incorrect RuntimeLib registry entry
amd64 prunsrv.exe pointed to wrong default jvm.dll
Version 8 update 25 can produce the error Can not establish connection to BlueCielo WebService when viewing documents if the Enable dynamic content compression option is enabled for the BCWebService application in IIS Manager. To prevent this error, disable the option or install a different version of the Java virtual machine.
Version 8 is also incompatible with the Print and Print Preview commands in AutoVue unless the NATIVEJAVAPRINTING setting is set to 1 in the PRINTOPTIONS section of the file AVS\bin\allusers.ini and the AutoVue Server is restarted.
-
Install all applicable AutoVue rollup patches (RUPs) to prevent errors and performance issues. Not all patches have been tested with Meridian, particularly those that were released after a supported Meridian version was released.
-
This version of AutoVue Client/Server is not supported. Only AutoVue Desktop is supported.
