Download Release Notes - Oracle Documentation

Release Notes: Oracle AutoVue 20.2.1,
Client/Server Deployment
For the most up-to-date version of this document, go to the AutoVue Documentation Web site on the Oracle
Technology Network at http://www.oracle.com/technetwork/documentation/autovue-091442.html.
Application User License
•
•
AutoVue includes a Desktop Deployment and a Client/Server deployment. For Application User licensing metric
(in the Component licensing model) or Custom Suite User licensing metric (in the Custom Applications Suite
licensing model), a single license cannot be split or shared between two users (e.g., one user using the AutoVue
Desktop Deployment and a different user using the Client/Server deployment would require two licenses).
For the purposes of the following programs: Oracle AutoVue Office, Oracle AutoVue 2D Professional, Oracle
AutoVue 3D Professional Advanced, Oracle AutoVue EDA Professional, Oracle AutoVue Electro-Mechanical
Professional, Oracle AutoVue 2D Professional for Agile and Oracle AutoVue Electro-Mechanical Professional
for Agile a user external to your company who participates in and attends an AutoVue Real-Time Collaboration
session or AutoVue web conference, but neither initiates nor hosts it, is not required to be separately licensed. All
users within your company must be licensed.
Installation
•
•
•
•
•
•
If you are upgrading from AutoVue 20.x, you do not need to run the uninstaller before you install AutoVue
20.2.1. You can just run the installer for AutoVue 20.2.1. The installer detects if AutoVue 20.0/20.1.x/20.2 is
installed on your machine. If it is installed, the installer backs up required data, uninstalls version 20.0/20.1.x/
20.2 and then installs 20.2.1 to the same location.
If installing on a Linux OS, make sure you have the correct version of WINE installed. The version of WINE
compatible with AutoVue 20.2.1 is wine-av-20040914-21.i386.rpm. You can download this version of WINE
from http://oss.oracle.com/AutoVue.
When upgrading AutoVue, if the client and server versions do not match, AutoVue now displays an error
message indicating the incompatibility. Ensure that the client jars are upgraded when you upgrade the server.
AutoVue installer can now scan for default RMI ports during interactive installation and prompt user to use
another port if the default ports are already in use.
AutoVue documentation, with the exception of the User’s Manual, are no longer included in the AutoVue
installation. Refer to Documentation Updates for more information.
For pre-requisites and complete secure installation instructions, refer to the Oracle AutoVue Installation and
Configuration Guide.
-1 -
September 2012
System Requirements
Component
Oracle-Certified Operating Systems and Software
Server
Windows
•
Windows Server 2003
- 32-bit
- 64-bit (AutoVue running in 32-bit mode)
•
Windows Server 2008
- 32-bit
- 64-bit (AutoVue running in 32-bit mode)
•
Windows Server 2008 R2
- 64-bit (AutoVue running in 32-bit mode)
Important: Windows 2008R2 has improved memory management
compared to Windows 2008 and Windows 2003. It is recommended
that you run AutoVue on Windows 2008R2 for better memory
handling and long-term stability.
(The installation requires about 400MB of free space.
Additional space will be required by AutoVue for
storing other data such as streaming files and markups.
Refer to the AutoVue Planning Guide for additional
information.)
Linux
•
Oracle Linux 5.8 (x86)
- 32-bit
- 64-bit (AutoVue running in 32-bit mode)
•
Red Hat Enterprise Linux 5.8 (x86)
- 32-bit
- 64-bit (AutoVue running in 32-bit mode)
Virtualization
•
VMWare Server version ESX 4.1
•
Oracle Virtual Machine 2.2.2
Client
Clients running the following Java Virtual Machines:
•
Java SE 6 Update 31—32-bit and 64-bit
•
Java SE 7u5—32-bit
Windows OSes (XP, Vista, and 7)—32-bit and 64-bit
•
Internet Explorer 7
•
Internet Explorer 8
•
Internet Explorer 9
•
Firefox ESR 10
•
Chrome 19
MAC OS X 10.7
•
Safari 5.0
•
Firefox ESR 10
RedHat Enterprise Linux 5
•
Firefox ESR 10
Ubuntu 10.04 LTS
•
Firefox ESR 10
Solaris 10 (Sparc)
•
Firefox 9
Note: Ensure that the JRE used for the AutoVue client supports
SWING UI.
Application Server
The VueServlet has been certified on the following
application servers:
•
•
•
•
•
WebLogic 9.x and up
Oracle Application Server 10g
Tomcat 6.x and up
WebSphere 6.1 and up
Jetty 6.0 and up
-2 -
September 2012
Integrations with AutoVue 20.2.1
The following integrations have been certified with AutoVue 20.2.1:
•
•
VueLink for UCM 20.1
VueLink for Documentum 19.3.2
General Enhancements
The functionality changes include:
•
•
•
•
•
Added support for Decimeter Unit for measurement
Enhancements to markups
• Added support for aligning the text in markups in conversion – The markup text will be aligned in the
converted output as it is aligned in the display.
• Added DPI support for markup printing
• The printout matches the workspace display. For example, Hyperlink and Note icons appear as displayed
in the workspace.
• Added support for Stamp conversion to PDF
• The background image of a Stamp now displays after conversion to PDF
• Added markup stamp support to AutoVue Office
AutoVue can work with Oracle Business Process Management (BPM) through AutoVue Web Services (for
example, users can call AutoVue printing Web Services in order to automate the printing of documents as part of
a workflow built in Oracle BPM). For more information on BPM, search for Business Process Management
documentation on the Oracle Technology Network (OTN).
Enhancement to print functionality
• Added support to share print settings amongst multiple AutoVue child windows
Enhancements to AutoVue hotspot capabilities:
• Added support for polygon regional hotspots – Allows hotspots in 2D drawings, images and PDFs to be
defined as polygons, rather than only by rectangles.
• Added support for page specific hotspots to support the case whereby the same regional hotspot (box or
polygon) appears on multiple pages.
• Enhanced text hotspot support for PDF format with more accurate string/character recognition.
Format Enhancements
MCAD Formats
•
•
•
•
•
•
•
Added support for Autodesk Inventor 2013
Added support for Unigraphics NX8
Added support for CATIA V5-6R2012
Added support for Creo Parametric 2.0
Added support for JT (Direct Model) versions 9.2 to 9.5 (i.e. 9.2, 9.3, 9.4 and 9.5)
Added bookmarks for family tables in Creo Parametric (Pro/ENGINEER) files. The xpr and xas accelerator
instance files for each entry in the family table are required for correct display.
General bug fixes for:
• Unigraphics
• Creo Parametric (Pro/ENGINEER)
• Autodesk Inventor
• CATIA 5
• DirectModel (JT)
-3 -
September 2012
• Solid Edge
AEC Formats
•
•
•
Added support for AutoCAD 2013 and AutoCAD Mechanical 2013
Added support for embedded rasters generated by the AutoCAD Raster Design for DWG files
General bug fixes for:
• AutoCAD/DXF
• Autodesk DWF 3D
• MicroStation 7
• Visio
EDA Formats
•
•
Added support for Mentor CCZ Schematics format
General bug fixes for:
• Cadence Allegro
• Mentor Expedition
Desktop/Office Formats
•
•
•
•
•
•
Improved support for image rendering, arrow display in PowerPoint XML files
Improved support for shading and gradient fill, Eschers shapes PowerPoint Binary files
Added support for OLE objects in PowerPoint file
Added support for viewing PDF/A files
Added support for check boxes in Excel
General bug fixes:
• Text
• Acrobat PDF
• Word
• Excel
• PowerPoint
• Outlook
Re-introduced File Formats
•
•
•
Altium Designer
RTF
JPEG 2000
Documentation Updates
The following documents, with the exception of the User’s Manual and JavaDocs, are no longer included in the
AutoVue installation. All of these documents can be found on the Oracle AutoVue Documentation OTN site under
“AutoVue 20.2.1” at http://www.oracle.com/technetwork/documentation/autovue-091442.html.
•
•
The following document is new in 20.2.1:
• Augmented Business Visualization Developer's Guide
The following documents have been updated in 20.2.1:
• Installation and Configuration Guide
• Viewing and Configuration Guide
-4 -
September 2012
•
•
•
•
•
•
•
•
•
AutoVue API Programmer’s Guide
User’s Manual
Acknowledgments
Supported File Formats
Release Notes
Product Variations – Feature Matrix
Testing Guide
Security Guide
Planning Guide
New INI File Settings
INI options described in following sections should be set in user INI files.
DWF3D Options
Configure options for Autodesk DWF3D files.
[Options]
Parameter
DWFLOADPMI = [0|1]
Description
Default
Controls the loading of PMI entities in DWF 3D files.
Set to 1 to enable loading of PMIs.
Set to 0 to disable loading of PMIs.
1
Hotspot INI Options
All of the following options have to be placed in the [HOTSPOTS] header of the INI file:
Parameter
Description
Default
ADVANCEGAP =[integer]
Specify the maximum number of spaces between consecutive text strings.
When there is large spacing between characters, you can increase the value
assigned to the INI option.
3
De-supported INI Options
•
•
The following INI options were removed in AutoVue:
• Removed SHOW_POINTTOPOINT_PAGE INI option
• Removed the use of TRYWITHMSXMLPARSER INI option
• Removed UIENABLEPRINTTYPESELECTION and HIGHRESOLUTION
• Removed TILED parameter for FORMAT
Removed AdminDoc option from CHOSEN_INSTALL_FEATURES Parameter for Silent Installation
Updated INI Options
The following INI options were updated in AutoVue:
•
•
The default value of MAXPLAINTEXTPAGES has changed to 100. Earlier, the default was 1000.
The default value of DISABLE3DMODEL for MicroStation 7 has changed to 1.
Refer to the Oracle AutoVue Client/Server Deployment Viewing Configuration Guide for more information regarding
these options.
-5 -
September 2012
De-supported File Formats/Versions
Oracle AutoVue has dropped support for some file formats/versions, which had very limited usage and low demand
from our customers. This will allow Oracle AutoVue to focus development efforts on formats which are most
strategic to our customers. The following file formats/versions were officially de-supported in release 20.1.1 and are
not supported in this release of AutoVue (that is, when these files are opened in AutoVue, the Unsupported File
Format/Version message appears).
De-supported File Formats
The following formats have been de-supported in 20.2.1.
MCAD Formats
•
•
I-deas
Pointcloud
AEC Formats
•
•
•
•
MicroStation 8 3D
AutoCAD Slide/AutoCAD Slide Library/AutoCAD Sheetset
CADkey
ESRI Shapefile
EDA Formats
•
•
•
•
•
•
•
•
•
•
•
PCAD
PDIF
Allegro IPF
OrCAD Layout
Cadence Specctra
Zuken Cadif
Zuken Cadstar
IFF
Barco PDF
CIF
Protel
Raster Formats
•
•
X-Windows Dump
IBM-IOCA
Archive Formats
•
•
Tar
Gzip
-6 -
September 2012
De-supported File Versions
The following format versions have been de-supported in 20.2.1.
MCAD Formats
•
•
•
•
•
•
•
CATIA 5 2D/3D prior to version V5R17
AutoDesk Inventor 2D/3D prior to version 10
Creo Parametric (Pro/ENGINEER) 2D/3D prior to version Wildfire
CoCreate Modeling/SolidDesigner prior to version 15
Solid Edge prior to version 18
SolidWorks prior to version 2006
Unigraphic prior to NX3
EDA Formats
•
•
Cadence Design Suite prior to version 15
PADS prior to version 2005
AEC Formats
•
•
•
•
AutoCAD prior to version 2000
AutoDesk DWF prior to version 5
AutoDesk DXF prior to version 2000
CoCreate Drafting/ME10 prior to version 2006/V14
MS Office Formats
•
•
•
Excel prior to version 2003
PPT prior to version 2003
Word prior to version 2003
De-supported Functionality
Oracle AutoVue will no longer support some of its functionality, which had very limited usage and low demand from
our customers. This will allow Oracle AutoVue to focus development efforts on functionalities which are more
important to our customers. Following is the list of functionalities that are de-supported in Release 20.2.1:
•
•
•
•
•
•
•
Interference Checking – The Check for interference menu item in 3D modes has been removed
Set User Coordinate System – The Set User Coordinate System menu item in 3D modes has been removed
Align Parts – The Align Parts menu item in 3D modes has been removed
Contrast Visual Effects – The contrast visual effects cannot be applied in any of the modes.
Verify Design – The Verify Design menu item has been removed in the EDA modes.
Magnify Glass – This menu item is removed for all the applicable modes.
Magnify Window – The Magnify Window menu item has been removed for all the applicable modes.
Note: The Pan and Zoom Window feature can be used to achieve the "Magnify Window", and "Magnify Glass"
functionalities.
•
•
•
•
Flip – The Flip menu item, both horizontal and vertical, from all the applicable modes
Hyperlink – The Follow Hyperlink, Hyperlink History, and Hyperlink Go Back menu items have been
removed. You can still launch a hyperlink when selecting a link from the AutoVue workspace.
All Markup Object Rotate – The functionality to select and rotate all markup entities has been removed. Markups
can only be rotated along with the base file. The capability to arbitrarily rotate individual entities still exists.
AutoVue in Offline Mode – Support for Offline mode is deprecated.
-7 -
September 2012
•
Conversion to the following formats has been removed: VRML, CALS GP4, Encapsulated Postscript, PCL, PCX
Bitmap, Run Length RLC.
Note: Please contact your Customer Support Representative in case you want any of the above de-supported
formats/file versions/functionalites to be included in the Oracle AutoVue product.
Known Issues
For information on known issues, refer to the Knowledge Base:
https://support.us.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1488647.1
-8 -
September 2012
Release Notes: Oracle AutoVue 20.2,
Client/Server Deployment
For the most up-to-date version of this document, go to the AutoVue Documentation Web site on the Oracle
Technology Network at http://www.oracle.com/technetwork/documentation/autovue-091442.html.
Application User License
•
•
AutoVue includes an AutoVue Desktop Version, a Desktop Deployment, and a Client/Server deployment. For
Application User licensing metric (in the Component licensing model) or Custom Suite User licensing metric (in
the Custom Applications Suite licensing model), a single license cannot be split or shared between two users
(e.g., one user using the AutoVue Desktop Version and a different user using the Desktop Deployment would
require two licenses).
For the purposes of the following programs: Oracle AutoVue Office, Oracle AutoVue 2D Professional, Oracle
AutoVue 3D Professional Advanced, Oracle AutoVue EDA Professional, Oracle AutoVue Electro-Mechanical
Professional, Oracle AutoVue 2D Professional for Agile and Oracle AutoVue Electro-Mechanical Professional
for Agile a user external to your company who participates in and attends an AutoVue Real-Time Collaboration
session or AutoVue web conference, but neither initiates nor hosts it, is not required to be separately licensed. All
users within your company must be licensed.
Installation
•
•
•
•
•
AutoVue 20.2 provides a secure installation by default. During the installation process, the installer lets you
configure AutoVue for Secure Socket Layer (SSL) and identity authentication.
The Oracle AutoVue installer no longer deploys AutoVue client components on a Web server in order to avoid
dependencies on external web servers. That is, the installer no longer prompts you to install with IIS/Oracle
HTTP/Apache Web servers. The installer installs the sample HTML files with the Jetty application server that
ships with AutoVue.
The following silent installation configuration parameters are obsolete since the installer does not deploy client
components with a Web server
• WEBSERVER_HOST
• WEBSERVER_DOCROOT
• WEBSERVER_PATH
If you are upgrading from AutoVue 20.x, you do not need to run the uninstaller before you install AutoVue 20.2.
You can just run the installer for AutoVue 20.2. The installer detects if AutoVue 20.0/20.1.x is installed on your
machine. If it is installed, the installer backs up required data, uninstalls version 20.0/20.1.x and then installs 20.2
to the same location.
The components available for default installation have changed. The Example Client Application is no longer
installed by default. If you wish to install the demo htmls, you should do a custom installation and select
Example Client Application.
Note: If you are upgrading from a previous release and you select default installation, the Example Client
Application will not be installed.
•
•
•
If installing on a Linux OS, make sure you have the correct version of WINE installed. The version of WINE
compatible with AutoVue 20.2 is wine-av-20040914-21.i386.rpm. You can download this version of WINE
from http://oss.oracle.com/AutoVue.
For pre-requisites and complete secure installation instructions, refer to the Oracle AutoVue Installation and
Configuration Guide.
Customers upgrading from a previous release of AutoVue to the new release must ensure that all locations
referenced by the CODEBASE parameter of the AutoVue client are updated with the 20.2 client jars (jvue.jar,
jogl.jar, gluegen-rt.jar)
-9 -
September 2012
Refer to KM Note: https://support.us.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1439152.1 for
instructions on how to verify if the client components are updated.
System Requirements
Component
Oracle-Certified Operating Systems and Software
Server
Windows
•
Windows Server 2003
- 32-bit
- 64-bit (AutoVue running in 32-bit mode)
•
Windows Server 2008
- 32-bit
- 64-bit (AutoVue running in 32-bit mode)
•
Windows Server 2008 R2
- 64-bit (AutoVue running in 32-bit mode)
Important: Windows 2008R2 has improved memory management
compared to Windows 2008 and Windows 2003. It is recommended
that you run AutoVue on Windows 2008R2 for better memory
handling and long-term stability.
(The installation requires about 400MB of free space.
Additional space will be required by AutoVue for
storing other data such as streaming files and markups.
Refer to the AutoVue Planning Guide for additional
information.)
Linux
•
Oracle Linux 5.6 (x86)
- 32-bit
- 64-bit (AutoVue running in 32-bit mode)
•
Red Hat Enterprise Linux 5.6 (x86)
- 32-bit
- 64-bit (AutoVue running in 32-bit mode)
Virtualization
•
VMWare Server version ESX 4.1
Client
Clients running the following Java Virtual Machines:
•
J2SE 6.0 update 26—32-bit and 64-bit
Windows OSes (XP, Vista, and 7)—32-bit and 64-bit
•
Internet Explorer 7
•
Internet Explorer 8
•
Internet Explorer 9
•
Firefox 8
MAC OS X 10.6
•
Safari 5.0
•
Firefox 8
RedHat Enterprise Linux 5
•
Firefox 8
Ubuntu 10.04 LTS
•
Firefox 8
Solaris 10 (Sparc)
•
Firefox 8
Note: Ensure that the JRE used for the AutoVue client supports
SWING UI.
Application Server
The VueServlet has been certified on the following
application servers:
•
•
•
•
•
WebLogic 9.x and up
Oracle Application Server 10g
Tomcat 6.x and up
WebSphere 6.1 and up
Jetty 6.0 and up
- 10 -
September 2012
Integrations with AutoVue 20.2
The following integrations have been certified with AutoVue 20.2:
•
•
VueLink for UCM 20.1
VueLink for Documentum 19.3.1 with patch 13355092
General Enhancements
•
•
•
•
•
•
•
•
Enhancements to markups
• The Stamp markup entity has been renamed to Symbol.
• The Intellistamp markup entity has been renamed to Stamp.
• Enhancements to Stamp (formerly Intellistamp):
• Stamps can now be defined to have fields that store their values locally or in the back-end system.The
original value and constraints (lists of possible values) can come from the back-end system even if the
field value is stored locally.
• Stamps can be defined to have a fixed physical size (e.g. 10cm by 10cm) to comply with industry or
corporate standards.
• Stamps with an Enhanced Metafile (EMF) background image will have a better appearance when resizing
- text and the background image will keep the same relatively size and location.
• Enhanced attribute permissions (readonce, read, write and edit).
• Ability to resize both the Stamp and the Stamp text (supported only when EMF is used as the Stamp
background).
• Ability to specify the Stamp size (fixed, default, resizable).
• Improvements to the Stamp Designer includes:
• View preview text in the designer to speed up stamp design process.
• Set a specific bounding box for each field.
• Set the alignment of text in each field.
• New designer available. To invoke the designer, run designer.bat located at <AutoVue Install Dir>\bin.
AutoVue provides the ability to do batch stamping. An API sample to demonstrate batch stamping is available at
<AutoVue Installation Directory>\Examples\BatchStamping.
• AutoVue now exits markup creation mode after you create a markup entity. In previous releases of AutoVue,
you were able to continue adding markups until you right-click the workspace.
Enhancements to AutoVue’s hotspot capabilities:
• New regional hotspots: Allow hotspots in 2D drawings and images to be defined as boxes, rather than only by
text strings to:
• Support cases where the underlying document has no textual information (Tiff or scanned document).
• Create hotspots that more closely match the area of interest - e.g. a block or other object in a drawing.
• New 3D hotspots: Allow 3D parts to become hotspots, based on metadata attributes such as 'part number' or
'asset id' to:
• Enable augmented business visualization in 3D models.
• Allow the parts and components of a 3D model to be used to trigger actions, or to be highlighted as part of
a visual dashboard.
Added Unicode support for Layers, Views, Blocks and 3D attributes.
Added support for layer printability for AutoCAD and PDF files. AutoVue does not print layers that are marked
“non-printable”. Note the following:
• Layer printability does not take effect when in Compare mode.
• Layer printability does not apply to conversion.
Added support for multi-selection of local files in the file open dialog.
Added support for specifying a page range when converting to PDF.
Improvements to logging to be able to detect files that hang the server. A new property (docserver.timeout) has
been added to let system administrators configure the time at which AutoVue should generate the hang report. If
- 11 -
September 2012
•
an operation takes more time than this period, AutoVue generates a message in the Document Server log
indicating that there could be a problem with this file.
Added support for the Dutch language (locale NL) for the AutoVue user interface.
MCAD Formats
•
•
•
•
•
•
•
•
•
•
Added support for CATIA 5R21
Added support for SolidWorks 2012
Added support for Solid Edge ST3, ST4
Added support for Creo Parametric 1.0
Added support for Creo Element\Direct Modeling 17.10, 17.20, 17.25, 17.30 and 18.00
Added support for PLM XML
Improved handling of background of AutoDesk Inventor drawings. If drawings contain a background image,
AutoVue displays it, but does not print this background image.
Added support for shaded views in Pro/ENGINEER 2D files.
Enhanced support for IGES:
• Added support for 3D layers
• Improved loading performance
General bug fixes:
• CATIA 4
• CATIA 5
• IGES
• Autodesk Inventor
• Creo Parametric (Pro/ENGINEER)
• Unigraphics
• SolidWorks
• Solid Edge
• STEP
AEC Formats
•
•
•
Added support for Creo Element/Direct Drafting 17.10 to 18.00
Enhanced support for AutoCAD DXF:
• Added support for layout pages
• Added support for OLE embedded objects
• Added support for raster embedded entities
• Added support for Viewports in layout pages
General bug fixes:
• AutoCAD (DWG & DXF)
• MicroStation
• Creo Element/Direct Drafting (ME10)
• Visio
• TIFF
- 12 -
September 2012
EDA Formats
•
•
•
•
•
•
Added support for Cadence Concept HDL 16.5
Added support for Allegro Layout 16.5
Added support for Orcad Capture 16.5
Added support for Board Station ASCII Symbol Geometry
Added support for Cadence Cell Library
General bug fixes:
• Cadence Allegro
• EDIF
• OrCAD Capture
• Mentor BoardStation
• PADS Logic
Desktop/Office Formats
•
•
•
•
•
•
Added support for Word 2010
Added support for Excel 2010
Added support for PowerPoint 2010
Added support for Outlook 2010
Enhancements to Desktop/Office formats:
• Improved handling of PDFs with large JPEG images
• Added support for PDF files embedded in Excel files
• Improvements to hyperlinks in Excel
• Added Workbook protection for binary Excel binary files
• Improvements to field display support in PowerPoint (date, time, page, number)
• Improvements to arrow head rendering in PowerPoint
• Added gradient fill support in Word XML
General bug fixes:
• Excel
• Outlook
• PowerPoint
• Word
• PDF
• TXT
Documentation
•
•
The Oracle AutoVue Security Guide (SecurityGuide.pdf) is included with the installation. It provides guidelines
on how to securely install and configure the AutoVue server and its associated components.
The following documents have been updated in 20.2:
• Installation and Configuration Guide
• Viewing and Configuration Guide
• Planning Guide
• User’s Manual
• Acknowledgments
• Supported File Formats
• Release Notes
• Product Variations – Feature Matrix
- 13 -
September 2012
New jvueserver.properties Options
The following are new options that can be set in jvueserver.properties file located in the <AutoVue Installation
folder>\bin directory. For more information on these options, refer to the Oracle AutoVue Installation Guide:
Option in jvueserver.properties
Description
docserver.timeout=N, classname
Specify the timeout in minutes after which the AutoVue server hang logs will be
generated. It is possible to implement a custom action to invoke on a hang
situation. When implemented, replace ClassName with the name of the class
implementing the custom action.
Default: 10 (minutes)
New INI File Settings
INI options described in following sections should be set in user INI files.
Acrobat Options
Configure options for Acrobat files.
[Options]
Parameter
PDFOVERPRINTPREVIE
W = [0|1]
Description
Displays content that otherwise may be obscured by overprinted fills.
Set to 1 so that overprinted fills are not displayed if they use a spot color.
Set to 0 so that overprinted content is shown as in Adobe Acrobat.
- 14 -
Default
0
September 2012
Autodesk Inventor Options
Configure options for Autodesk Inventor files.
[Options]
Parameter
Description
Default
DRAWINGPAGE = [0|1]
Set to 1 to limit the display of the drawing to the sheet borders.
Set to 0 to display the whole drawing.
0
INVENTOR_HIDE_CONS
TRUCTION_GEOMETRY
= [0|1]
Option to control the visibility of construction/non-manifold geometries for
Inventor 3D files.
Set to 0 to display non-manifold/construction geometries.
Set to 1 to hide non-manifold/construction geometries.
1
CATIA 5 Options
Configure options for CATIA 5files.
[Options]
Parameter
Description
Default
LOAD_ATTRIBUTES =
[0|1]
Control the loading of attributes when viewing CATIA 5 part or assembly
files.
Set to 1 to read attributes and attach them to their appropriate entities.
Set to 0 to disable the loading of attributes.
Note: This option may be used for performance tweaking for large assembly
files with many attributes.
1
MINIMIZETREENODES =
[0|1]
Set to 1 to minimize the number of nodes in the model tree and to increase
performance.
Set to 0 to build a model tree similar to the CATIA 5 feature tree.
Note: This option is only valid in BREP mode (LOADFACETEDDATA=0).
0
CATIA5BUILDINTERMED
IATECGMBODIES = [0|1]
This option controls the building and display of intermediate CGM bodies
Set to 1 if you wish to process and display all intermediate CGM bodies.
(You also need to set the INI option CATIA5BuildInvisibleCGMBodies to 1
if the intermediate bodies are saved as invisible. File will take longer to load
if it contains lots of intermediate bodies).
Set to 0 to disable the loading and display of intermediate CGM bodies.
Note: The option takes effect only in BREP mode
(LOADFACETEDDATA=0).
0
- 15 -
September 2012
Creo Element/Direct Drafting (ME10) Options
Configure options for Creo Element/Direct Drafting (ME10) files.
[Options]
Parameter
ME10_USEHTMLASCIIC
ODES=[0|1]
Description
Specify whether or not to use the HTML ASCII CODES table for character
mapping when accessing ME10 native fonts.
Set to 0 to use ME10’s native character mapping instead of the HTML ASCII
CODES table.
Set to 1 to use HTML ASCII CODES table for character mapping for
special characters.
Default
0
IGES Options
Configure options for IGES files.
[Options]
Parameter
Description
Default
IGESDETAILEDTREE =
[0|1]
Set to 1 to display every face (surface) as a separate node in the model tree.
Set to 0 to merge all single faces together into one body.
0
IGESHIERARCHYCOLOR
= [0|1]
Controls the color overwrite setting of IGES files.
Set to 1 so that the child entity color always overwrites the parent entity
color. For example, the color of the face, if set, always overwrites color of
the body.
1
IGESINVISIBLEPARTS =
[0|1|2]
Set to 0 so that hidden entities are not loaded.
Set to 1 to load but not display hidden entities.
Set to 2 to load and display hidden entities.
1
IGES3DLAYERS = [0|1]
Set to 0 to disable loading of layers in IGES files containing layer
information.
Set to 1 to enable loading of layers in IGES files containing layer
information.
1
IGESFACEORIENTATION
= [0|1]
Set to 0 to disable validation of face orientations in IGES 3D files
Set to 1 to enable validation of face orientations in IGES 3D files
0
IGESSHOWALL = [0|1]
Set to 0 to disable loading of subordinate entities in IGES 3D files
Set to 1 to load subordinate entities (children) in IGES 3D files
0
- 16 -
September 2012
Mentor Options
Configure options for Mentor files.
[ECAD]
Parameter
MENTOR_PCB_DESIGNT
OOL = [0|1|2]
Description
Controls which Mentor PCB Design Tool’s display to match.
Set to 0 so that AutoVue matches the display of Mentor Librarian.
Set to 1 so that AutoVue matches the display of Mentor Layout.
Set to 2 so that AutoVue matches the display of Mentor Fablink.
Default
0 for Mentor
ASCII
Geometry
Symbol file
2 for Mentor
PCB designs
Microsoft Office Options
Configure options for Microsoft Office files.
[Options]
Parameter
TRYWITHMSXMLPARSE
R = [0|1]
Description
Specify which parser to use when loading Office XML files.
Set to 1 to use the MSXML parser that is included with Windows OS.
Set to 0 to use the Xerces XML parser.
Note: This option affects the following formats: WordXML PPTXML,
ExcelXML
Default
1
Creo Parametric (Pro/ENGINEER) Options
Configure options for Creo Parametric (Pro/ENGINEER) files.
[Options]
Parameter
Description
PROEBACKGROUNDCOL
OR=<integer>
Specify the background color of shaded views in Creo Parametric (Pro/
ENGINEER) 2D drawing (when in saved display list and/or picture mode) to
the background color used in Creo Parametric at the time the drawing
(shaded view) was created.
To obtain the background color from Pro/ENGINEER, select View > Display
Settings > System Colors > Background Color.
Note: If no color is specified (PROEBACKGROUNDCOLOR=-1), the
hard-coded default Creo Parametric (Pro/ENGINEER) 2D background color
is used:
•
For versions Wildfire, Wildfire2: RGB(183, 183, 183)
•
For versions Wildfire3, Wildfire4: RGB(51, 50, 46)
•
For version Wildfire5: RGB(160, 186, 212)
•
For Creo 1.0: RGB(251, 251, 252)
- 17 -
Default
-1
September 2012
Parameter
PROE2DVIEWDEFAULTS
TYLE = [HIDDEN |
WIREFRAME | SHADING |
NO HIDDEN]
Description
Specify a default style to display 3D projected views. This option controls
the amount of detail in projected views. Showing less detail in views might
improve the performance:
•
HIDDEN
•
WIREFRAME
•
SHADING
•
NO HIDDEN
Default
NO HIDDEN
This option will work in the following conditions:
•
When the view's display style follows the global style (that is, Pro/
Engineer environment variable Display Style is set to Follow
Environment)
•
Loading drawing files in picture mode is turned off
(PROE2DLOADPICTURE=0)
•
Loading drawing files from display list is turned off
(PROE2DLOADSAVEDDISPLAYLIST=0)
Raster Options
Configure options for Raster files.
[Options]
Parameter
APPLYRASTERTRANSPA
RENCY=[0|1]
Description
Set to 0 to ignore alpha-channel and display the whole bitmap opaque.
Set to 1 to use the alpha-channel stored in the file to apply transparency.
Default
1
Text Options
Configure options for Text files.
[Options]
Parameter
DEFAULTDOCMARGINS=
[leftMargin, rightMargin,
topMargin, bottomMargin]
Description
Specify page margins in inches for plain Text files.
If this option is not set, a default of 1 inch for each margin is set.
Sample Syntax:
DEFAULTDOCMARGINS=1.2, 1, 0.8, 0.8
- 18 -
Default
1, 1, 1, 1
September 2012
TIFF Options
Configure options for TIFF files.
[Options]
Parameter
Description
TIFF_LOADPREVIEWS =
[0|1]
Specifies if the TIFF images with reduced resolution (that is, preview pages)
are displayed.
Set to 1 to display all pages including the preview pages.
Set to 0 so that the preview pages are not displayed.
Default
0
De-supported in Release 20.2
•
•
•
The INI option SENDPAGEASIMAGE has been de-supported since it is no longer needed.
The integrations backward compatibility option dms.vuelink.version=19.3 has been de-supported.
INI option FolderPermissions has been de-supported for security reasons.
Known Issues
For more information on known issues, refer to the Knowledge Base:
https://support.us.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1401724.1
•
•
•
•
Copy/Paste feature is not supported for Stamp markup entity.
Stamping does not work in 3D files.
There is a known issue with 64-bit JREs when loading 3D files. In some situations (for instance, using Remote
Desktop to access AutoVue), 3D files will not display. This is a known issue with JOGL 1.1.1. See JOGL bug:
https://jogamp.org/bugzilla/show_bug.cgi?id=427: https://jogamp.org/bugzilla/show_bug.cgi?id=427
There are some known issues with the Universal File Open dialog:
• If loading the client on Windows 7, there maybe situations where the icons do not display. Refer to SUN bug:
http://bugs.sun.com/view_bug.do?bug_id=6840086.
• If loading the client on a MAC OS, the universal file open dialog will not display correctly. Refer to SUN bug:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7077418.
A workaround is to use the native file open dialog by setting INI option
ENABLEUNIVERSALFILECHOOSER to 0.
• If loading the client on a Linux client that uses GNOME, the Universal File Open dialog may not show the
DMS Browse and Search Buttons. A workaround is to use the KDE desktop environment. Refer to SUN bug:
http://bugs.sun.com/view_bug.do?bug_id=6840086.
- 19 -
September 2012
Copyright © 1999, 2012, Oracle and/or its affiliates. All rights reserved.
Portions of this software Copyright 1996-2007 Glyph & Cog, LLC.
Portions of this software Copyright Unisearch Ltd, Australia.
Portions of this software are owned by Siemens PLM © 1986-2012. All rights reserved.
This software uses ACIS® software by Spatial Technology Inc. ACIS® Copyright © 1994-2008 Spatial Technology Inc. All rights
reserved.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective
owners.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and
are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may
not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in
any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for
interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors,
please report them to us in writing.
If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S.
Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS
Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are
"commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and
agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject
to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of
the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December
2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
This software is developed for general use in a variety of information management applications. It is not developed or intended for
use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this
software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy and other
measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused
by use of this software in dangerous applications.
This software and documentation may provide access to or information on content, products and services from third parties. Oracle
Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third party
content, products and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred
due to your access to or use of third party content, products or services.
- 20 -
September 2012