Installation and Configuration Guide
Contents
1. AutoVue 22 Debugging AutoVue Logging for AutoVue AutoVue uses the log4j package to generate debug information The configuration file log4j xml located in the AutoVue Install Root gt bin directory makes it possible to display debugging information for AutoVue Log files are created in the AutoVue Install Directory gt bin logs folder by default In situations where trouble shooting information is necessary an Oracle Global Customer Support representative will ask you to update the log4j xml and enable logging for AutoVue Note By default logging is enabled at the WARN level Any warning messages generated while you use AutoVue are written to the log4j output file For additional information regarding log4j go to Apache s log4j documentation The following section describes the classes for which you can enable debugging information Logger Information The following descriptions explain what kind of logger information will be seen for each class specified Class Description com cimmetry jvueserver con Displays reports on loading errors of AutoVue s configuration figuration com cimmetry jvueserver eve Displays information concerning posting and handling of different AutoVue nt events opened and closed sessions opened and closed documents and so on com cimmetry jvueserver cac Displays information concerning the AutoVue cache Reports messages and he errors related to loading the cache locking saving deleti2. The Oracle AutoVue Installation and Configuration Manual is directed at any user of Oracle AutoVue Desktop Deployment Documentation Accessibility Our goal is to make Oracle products services and supporting documentation accessible to all users including users that are disabled To that end our documentation includes features that make information available to users of assistive technology Accessibility standards will continue to evolve over time and Oracle is actively engaged with other market leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers For more information visit the Oracle Accessibility Program Web site at http www oracle com accessibility Accessibility of Code Examples in Documentation Screen readers may not always correctly read the code examples in this document The conventions for writing code require that closing braces should appear on an otherwise empty line however some screen readers may not always read a line of text that consists solely of a bracket or brace Accessibility of Links to External Web Sites in Documentation This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites TTY Access to Oracle Support Services Oracle provides dedicated Text Telephone TTY acces
3. Hd ceni bo aee eeu Longa 22 CUSTOMIZING EHE GUL reti eer SED testeo SEIN TBI SPROEIRENO A OR NEUEM UMS ON EE 24 Choosing the GUI Fil 5 5 eniro eerte eu eo eroe n eto re e eco r ree eror eee enero sono cr so eU E Vo ees Dw esa SAAS SARER 24 Modifying the GUI B IT possis 24 Structure and Syntax of GUI Files eese eere en rennen nene rennen enne 24 GUT C nfig ration Syntax rere e e que Peta e Ee e rece rH eA Ue vei rpg eua 25 APPENDIX A SAMPLES AND API EXAMPLES INCLUDED WITH AUTOVUE 30 API Examples seinna NA 30 Sami Ple I E E E E E E E E EE 30 Adding Custom Tools Menu to AutoVue ssoesssooessoosesssoosssooesssoseesoosesoossesoocsssoosesocesssoosssoosessossesoosse 30 EREDBACR E REA oaa ater re CERE a rain eI E Cis Pie Ee Eo EREDVU M AERE 32 General UNGUITIES er 32 Sales INGUILICS sssscsscsecsssstessvsctvevessecnsessansvesecdetessetssnscebueesssssenssssuseuscosesDeavsbensconteoustedesbesescesssCesensesSiacsoue 32 GCUStOMER SUpport PEE 32 AutoVue 4 Preface The Oracle AutoVue Installation and Configuration Manual describes how to install and configure Oracle AutoVue Desktop 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 Audience
4. bar configuration MENUBAR BEGIN popup menu configuration END toolbar configuration TOOLBAR NORTH WEST EAST BEGIN button control END Status bar configuration STATUSBAR SOUTH BEGIN button control pane control END RMB popup menu configuration RMB BEGIN popup menu configuration menu item control END popup menu configuration POPUP IDS FILE EDIT VIEW OPTIONS HELP MANIPULATE TOOLS ANALYSIS MODIFY COLLABORATION BEGIN popup menu configuration menu item control SEPARATOR END button control BUTTON action control menu item control MENUITEM action control pane control PANE action control action control control name control key list permissions control name For list of available control names refer to Control Names control key list For the control key list for different controls refer to Control Names AutoVue 26 GUI Configuration Blocks permissions All action names need PERM READ These are the exceptions to this rule VueActionFilePrint needs PERM READ PERM HEADERS PERM WATERMARK VueActionOptionsBars needs PERM NONE VueActionHelp needs PERM NONE Example To define a very basic user interface that only allows users through menu items to open or print a file and get the file information without changing watermark headers footers BEGIN UI VIEW MENUBAR BEGIN POPUP IDS FILE BEGIN MENUITEM VueActi
5. common AutoVue features Note that this set does not install the sample drawing Standard files or API examples AutoVue 11 Installation Set Description Rm You can select the features to install Select this installation set to install the sample drawing files Custom and API examples If you selected the Custom install set continue to step 7 otherwise proceed to step 8 9 Select which of the following features to install and then click Next Option Description Program Files Administration Documentation User Documentation Sample Files API Examples Installs Oracle AutoVue The option is selected by default Installs Oracle AutoVue system administration documentation The option is selected by default Installs AutoVue end user documentation The option is selected by default Installs drawing sample files Installs examples of how Oracle AutoVue features can be added to third party applications using APIs 10 Select one of the following locations to create shortcuts and then click Next Options Description In a new Program Group In an existing Program Group In the Start Menu On the Desktop In the Quick Launch Bar Other Don t create icons Creates a shortcut in the Program group of the Start menu For example Oracle AutoVue This is the default option Adds a shortcut to an existing Program group For example Accessories Adds a shortcut in the Start menu Adds a
6. wish to have a customized GUI for AutoVue you must create a custom GUI file and specify this custom file using the param GUIFILE command line parameter GUI files are placed at the location specified by autovue users directory By default the location is AutoVue Installation Directory bin WProfiles Modifying the GUI File The GUI definition file describes which controls are added to which context such as MenuBar ToolBar and so on If you are customizing your GUI file for the first time it is recommended that you make a backup of the default gui file and modify the controls in this file to meet your needs The deafult gui is located in the lt AutoVue Installation Directory gt bin folder If you have a previous version of AutoVue and you used a customized GUI in this previous version we recommend that you use the diff utility to perform a comparison between the previous version s default gui and your customized GUI The delta between the two GUI files should be manually applied to the current version GUI Note If you use the previous version s customized GUI with the new version of AutoVue you might run into situations where some or all of the GUI elements fail to load Structure and Syntax of GUI Files AutoVue supports five modes View Compare Markup Collaboration and Print Preview A GUI file defines the graphical interface for each mode Menu bars toolbars status bar and Right Mouse Button RMB menus are defined in th
7. 0 180 270 VueAction VCM Apply contrast ViewContrast VueAction VCM Apply anti alias ViewAntiAlias VueAction VCM Apply invert ViewInvert VueAction VCM Go to next page previouse page or select page X ViewPage number VueAction VC Select view point View ViewPoint VueAction VCM Select Xrefs X ViewXrefs VueAction VCM Select layers X ViewLayers VueAction VCM Select blocks X ViewBlocks VueAction VCM Select views X ViewViews VueAction VCM Get entity s drawing information ViewDrawing Info AutoVue 28 Control UI Control Functionalit Contexts Name Modes y Key List VueAction VCM Measure distance cumulative distance area or ViewMeasure calibrate VueAction VCM Show special view modes Pan and Zoom X ViewSpecialVi Window ewModes MagnifyWindow MagnifyGlass VueAction VCM Get drawing information for one entity some ToolsDrawing entities or a block Info VueAction VCM Hide or show toolbars or status bar OptionsBars VueAction VCM Get entity s drawing information ViewDrawing Info VueAction VM Create a Mobile Pack CreateMobile Pack VueAction VM Send Mobile pack with your default e mail client ReplyMobile Pack VueAction VM Synchronize changes to Mobile Pack to backend SyncMobile system Pack VueAction VM Show renditions in the Mobile Pack ShowRendition Note The letters in the UI Modes column indicate V View C Compare M Markup The columns indicate Control Name Column sh
8. 0 MB of disk space for installation 6 GB of free disk space e 4 GB needed for storing cached files e Remainder needed by AutoVue to store temporary files at the 7TEMP path If streaming file generation is enabled you must ensure that the disk space specified by autovue cache size is available to AutoVue Refer to section Configuring AutoVue for more information on streaming files AutoVue 10 AutoVue Installation Planning AutoVue by default installs at C Oracle AutoVue Desktop Deployment AutoVue must have write permissions to the installation path in order to start up successfully since it stores markup symbols markups profiles and cache data in sub folders at the installation path On Windows 7 and Windows VISTA Operating Systems that have User Access Control UAC enabled ensure that AutoVue is installed in a directory where the user has write permissions If UAC is enabled on the system the installer notifies you that UAC is enabled and reminds you to install into a location where the user has write permissions Pre requisites e The installer for AutoVue also installs the AutoVue Document Converter print driver Ensure that the print spooler service is enabled and that you have permissions to install print drivers on the machine where you will install Auto Vue e The machine that is running AutoVue must have a color depth of at least 16 bits If the machine has a lower color depth you may run into discrepancies in
9. EE Fe bp OE PER aS 9 AUTOVUE INSTALLATION soes ees eec re nS ENS serros eens Y Ye NS EN ESE EE RYE MEET SENS EEE e UE 10 Plannin anans a 10 PYG P QUISICES RE 10 Hotell 10 Startins Aut ATTE 11 File Crucial 12 COMMAND LINE OPTIONS FOR AUTOYV UE ee esee ee eee ee eo eee to seen ease tees eene seen aae 13 CONFIGURING AU TOV UE 5 efe ee PR RENE QERISER YEDE TEE PE NEFRN USE QE eR Dae XE NR Ee ERR ER EPA ETHER MEE 14 Changing the Locale of Auto Vue eee eee cete eee eren ee eene sese tne sette tbe se etta so eet eo ese toes e eo se s ete eae sese eaa 16 COMMAND LINE PARAMETERS ee eee eee eee eo oe ee eo se ee eo Pete eo Pete ao Pese ao Pese en P ets eee tO see en nee 18 Setting the PARAM Flag e sssi sse 18 CONFIGURING MEMORY SETTINGS eesssesssesssecssocssocesoocesocessccssocesocesoocsssecssocesocesoosessesssse 20 CONMPSUTING Ip PLI 20 NON INTERACTIVE INSTALLATIONS ee ee ee ee eese ense seen sese ea sete ao setae setate setae s ea aa 21 InrlPnImi e 1 21 LOTEEN ACE t A E 21 DEBUGGING AUTOY UE eerko orna errata va nain VE v a n serit eu Y sna Y srei iras ia dS Vu en eh ene aaas 22 Logging for VITIO Ea 22 Logger Information ere eri eH ep on egt E optio rd loce devi
10. For information on enabling logging refer to section Logging for AutoVue File Associations You can associate AutoVue with certain file types so that when you double click on a file of this type it opens in Auto Vue Below are the ways to associate file types with Auto Vue 1 From Windows explorer When you double click on a file that is not associated with another application you will be prompted with the Open With dialog where you can specify the application with which to open the file Select Auto Vue Desktop Deployment from the list of programs and then select Always use the selected program to open this kind of file If a file type is associated with an application right click on the file and select Open With and then select AutoVue Desktop Deployment from the list of programs Select the Always use the selected program to open this kind of file checkbox 2 Programmatically You can create a batch file to associate file types with AutoVue Create a batch file with following content assoc ext AVFile ftype AVFile dpOautovue exe 21 Replace ext with the file extension that you want to associate with AutoVue Repeat this line for all extensions that you want to associate with AutoVue For example assoc dwg AVFile assoc dgn AVFile assoc pdf AVFile ftype AVFile dpOautovue exe 21 Run this batch file to associate the specified file extensions with AutoVue AutoVue 13 Command Line Options for A
11. LE tools gui param EXTRABUNDLES CustomResources When you startup AutoVue you should see new Tools menu items corresponding to your definition in CustomActionTools java AutoVue 32 Feedback If you have any questions or require support for AutoVue please contact your system administrator Some customization and maintenance must be done on the server and cannot be implemented on the client machine If the administrator is unable to resolve the issue please contact Oracle Corp If at any time you have questions or concerns regarding AutoVue call or e mail us General Inquiries Telephone 1 514 905 8400 or 1 800 363 5805 E mail autovuesales ww oracle com Web Site http www oracle com us products applications autovue index html Sales Inquiries Telephone 1 514 905 8400 or 1 800 363 5805 E mail autovuesales ww oracle com Customer Support Web Site http www oracle com support index html
12. Previous FullRes FitBoth PERM READ texts Column provides the contexts to which you can add the control to mple You can have the entry in a popup menu of the menu bar but not in an RMB configuration If you have such an entry it will be ignored M ENUITEM VueActionFileOpen PERM READ AutoVue 30 Appendix A Samples and API Examples Included with AutoVue During the installation process if you select Custom installation Auto Vue provides you options to install samples and API examples This chapter provides an overview of the samples and API that are installed with AutoVue API Examples The following API Examples are installed at AutoVue Install Root gt examples if you do a Custom installation and choose to install API examples e VBSample This is the Desktop Deployment ActiveX example This example is located in folder AutoVue Install Root gt examples VBExample e CustomActionTools This example demonstrates how you can add custom Tools menu actions to AutoVue For more information see section Adding Custom Tools Menu to AutoVue e VueActionSample This provides an example of how to implement hotspots using the VueAction For more information on VueAction refer to the AutoVue API Programmer s Guide and to the VueBean JavaDocs To use this sample Hotspots txt contains some hotspot definitions You can use these definitions to test this sample or
13. anyone licensing it on behalf of the U S Govern ment 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 com mercial 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 Gov ernment 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 soft ware in dangerous applications then you shall be responsible to take all appropriate fail safe backup redundancy and other mea sures 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 pro
14. ation directory gt bin log4j xml Refer to section Debugging AutoVue for more information AutoVue 21 Non Interactive Installations Installation To install AutoVue in non interactive mode you need to specify a configuration file that contains the required installation parameters To do so you must generate the configuration file manually following this syntax Specify Installation Directory jh tds ics ih us a ta tal Gas E is SS E QU ae is RC ai ha ds a Cai en xi USER_INSTALL_DIR C Oracle AutoVue Select Shortcut Folder Saas SS ae USER_SHORTCUTS C Documents and Settings Administrator Start Menu Programs Oracle AutoVue Following are the installation parameters that you can specify in the configuration file Default Parameter Description Value USER INSTALL DIR ile path Specify the path where you want to install AutoVue USER SHORTCUTS file path Specify the shortcut path Note This parameter is only for Windows OS installations After you specify the parameters for the configuration file you can run the installation in non interactive mode Enter the following command lines InstallDesktopDeployment ex i silent f full path to configuration file Uninstallation If AutoVue is installed in non interactive mode the uninstallation is automatically in non interactive mode Simply invoke the uninstaller for AutoVue lt AutoVue Installation Folder gt uninstall uninstall exe
15. color or filling when viewing printing or converting from AutoVue e AutoVue stores temporary files at the user s TEMP directory These files are generated by AutoVue while processing files and are generally removed once the processing is complete Ensure that the user running AutoVue has a temporary directory defined and is able to write to the temporary directory Installing AutoVue Note If you want to install AutoVue in non interactive mode refer to Non Interactive Installations To install AutoVue do the following 1 Download the Oracle AutoVue Media Pack and extract its contents 2 Close all applications before you start the installation for AutoVue 3 Run the AutoVue installer executable InstallDesktopDeployment exe that is located in folder DesktopDeployment 4 Select a language from the installation dialog and then click OK 5 Click Next to begin installation 6 Ifthe installer detects version 20 0 installed on the machine it prompts if you want to upgrade your installation If you choose to not upgrade the installer will exit You must backup required data manually uninstall 20 0 and then re run the installer If you choose to upgrade the installation will continue It will install to the same location as 20 0 7 Specify the installation directory and then click Next Example c Oracle AutoVue Desktop Deployment 8 Select an installation set and then click Next Installation Set Description Installs the most
16. ducts 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 February 28 2011 AutoVue 3 PREVA O mI M 4 ENXLIII Um 4 Documentation edid c M Eae 4 Accessibility of Code Examples in Documentation sese 4 Accessibility of Links to External Web Sites in Documentation sese 4 TTY Access to Oracle Support Services sese enne 4 Related DOCUMENS mee Dl 4 Conventions ieeesteeseeb eo oeo ses ves Y RUP IPTE Ever e Se PNE E npe ance ue Te Lope e over eeU se ede sag Po eV e e eie RE eV EUG 5 INTRODUCGCEDUION oascesertepivs eu NU HEP EeLetpaY FREI UNSERE seen edausies tot e vao uium tdem eive ter piden diedes 6 UPGRADING AU BOW UIE itis ibn ERE P SERPRUR AE Ee ES Ne istos tu oae t cu eee e a RR beise 7 MA rk ps nee eei e tm titio diete cete ne a ee oet ee essed E 7 SYSTEM REOUIREMNENTS 25 eR ORUM FE ORSE PRENNE S SENI Kato UE ION RR HAIR D It E NRI Rute 9 Hardware Requirenients c eeLee cierre eere e nee tope ree epe rre ep erase opo area op rre eto resa ep Er sepe
17. ed at the old location will not be detected by AutoVue You will need to import the markups manually and save the markups so that they are saved at the new location Specifies the directory where AutoVue stores all symbol libraries and symbol files 0 No default value markups are stored at lt Base file location gt avred lt AutoVue Installation Directory gt bin Symbols Streaming File Options AutoVue 16 autovue metacache enable Specifies whether to generate streaming files FALSE TRUEIFALSE When set to TRUE streaming files are stored in the location specified by the autovue cache directory parameter autovue metacache pdf ena Set to TRUE to enable generation of streaming files for PDF FALSE ble TRUEIFALSE documents Note Option autovue metache enable must be set to TRUE for this option to take effect Note The following options take effect set if autovue metcache enable TRUE autovue cache directory file path autovue cache size int autovue cache maxnumfile s integer autovue cache maxlifetime integer autovue rmi port port value docserver cmdline Specifies in which directory the cached files should be saved A central cache information file named cache map is stored in the same directory The user must have write permissions to the folder Specifies in Megabytes the maximum size of the file cache If not specified or if value specified is less than 50 MB the defau
18. em locale and AutoVue locale are different you might notice that some dialogs or buttons in AutoVue use the locale from the OS AutoVue 17 This is because AutoVue relies on the OS for UI items such as Open Close OK Cancel You can set the Java parameter user locale locale to ensure that these items also appear in the right locale This option must be set in the autovue cmdline property in autovue properties You can also set the Java parameter user country country for country specific localization AutoVue 18 Command Line Parameters You can configure AutoVue by modifying certain settings in autovue cmdline property in autovue properties Setting the PARAM Flag You can specify command line parameters to AutoVue by setting the Paran flag in the autovue cmdline property in autovue properties Syntax PARAM lt name gt lt value gt Follow are a list of parameters than can be configured Name Type Value FILENAME Note When specifying a local file ensure that the filepath is preceded by an upload protocol For example upload c samples 2d acad dwg http host file Specify a HTTP URL for file open ftp host file Specify a FTP URL for file open Or ftp lt user gt lt password gt lt ftpserver gt file EXTRABUNDLES name of the bundle file If you are adding custom actions to AutoVue you can specify the name of the custom resources file using this parameter Names of the custom reso
19. g low on Java Virtual Memory JVM you must set the maximum memory to a higher value It is recommended that you increase the maximum memory for the Java component to 512MB AutoVue Desktop Deployment has both Java and native components The Xmx flag only controls the memory available to the Java components It is recommended that you do not set the memory for the Java component to a very large value as it results in less memory for the native components The native components use the remaining memory on the machine after the specified Java memory used by the Desktop Deployment You can tell the JVM how to allocate deallocate heap memory with the XX MinHeapFreeRatio and XXMaxHeapFreeRatio options By setting these options to a reasonably small value for example XX MinHeapFreeRatio 10 and XXMaxHeapFreeRatio 10 the memory allocated is reduced and the unused memory may be utilized elsewhere Ultimately it is up to the garbage collection settings of the JVM whether or not to use these options As a result these options are not critical and removing them does not cause the Desktop Deployment to stop working the Desktop Deployment may just use more memory For more information on these options refer to the documentation at http java sun com docs hotspot gc1 4 2 Configuring log4j The log4j configuration file to use is specified by the Dlog44 configuration parameter in autovue cmdline By default this the file is lt Auto Vue Install
20. hen heavyweight is on Auto Vue uses hardware acceleration to render 3D Default is AUTO and AutoVue uses heavyweight rendering on all clients except MAC clients LOCALE DEIENIFRIJAIKOITWIZH The Locale to be used in the user interface specified as an ISO639 two letter code Using this parameter you can force the applet GUI to be displayed in one of the supported languages If not set the Locale is determined using the client system properties Syntax PARAM LOCALE FR See section Changing the Locale of AutoVue for additional configuration that maybe necessary for forcing AutoVue user interface to a specific LOCALE NEWWINDOW TRUEIFALSE Specifies whether to launch a new window when running an additional instance of AutoVue If set to TRUE a new window is launched without replacing the existing AutoVue window when there is already an instance of AutoVue running If set to FALSE a new window is not launched when there is already an instance of AutoVue running Note If you set NEWWINDOW to FALSE and you specify 2 or more files to open in the command line for AutoVue AutoVue will open these files in separate windows AutoVue 20 Configuring Memory Settings The maximum memory available to the Java component of the Desktop Deployment is determined by the Xmx flag in the autovue cmdline property By default this is set to 256MB If you encounter a situation where Auto Vue indicates that it is runnin
21. ile allusers ini every time a user accesses AutoVue This is done by setting required options in allusers ini or the files specified by autovue users allusersini This file should be at lt AutoVue Installation Direcotry gt bin Profiles directory If a file requires resources from the Internet AutoVue must connect to the Internet to retrieve the required resources If the machine that AutoVue is installed on uses a proxy server to connect to the Internet you must set the proxy setting to allow the request to go through For example autovue http proxyhostemy proxyserver com 80 autovue ftp proxyhost my proxyserver com 80 AutoVue autovue classpath autovue jre autovue jre path autovue cmdline autovue splash full path of PNG JPEG autovue help file anguag e file path Specifies the classpath needed for AutoVue to startup successfully We recommend that you do not change this parameter Specifies the path to the java executable used by AutoVue We recommend that you do not change this value Specifies the path to the JRE used by AutoVue We recommend that you do not change this value Specifies the command line parameters for AutoVue You can modify memory settings for AutoVue modify the log4j configuration and specify additional commands here using the Param flag Do not modify other values Refer to section Command Line Parameters for more information Specify the splash screen to display while A
22. installation and Configuration Guide Oracle AutoVue 20 1 Desktop Deployment ORACLE February 28 2011 Copyright 1999 2011 Oracle and or its affiliates All rights reserved Portions of this software Copyright 1996 2007 Glyph amp Cog LLC Portions of this software Copyright Unisearch Ltd Australia Portions of this software are owned by Siemens PLM 1986 2008 All rights reserved This software uses ACIS software by Spatial Technology Inc ACIS Copyright 1994 1999 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
23. is file For some of these objects location north south west east may be specified Toolbars are located in north west or east The status bar is always located at the bottom of the component south Note Popup menus may be added to menu bars Menu items popup menus or separators may be added to popup menus Toolbars only accept buttons Buttons or panes may be defined for the status bar The RMB popup is processed as any other popup menu The following table lists each GUI file for each mode 2D EDA 3D View VIEW ECADVIEW SMVIEW Markup MARKUP ECADMARKUP MARKUPS3D Collaboration COLLABORATION ECADCOLLABORAT COLLABORATION3 ION D Compare COMPARE COMPARE COMPARE 3D Print Preview PRINTPREVIEW PRINTPREVIEW PRINTPREVIEW AutoVue 25 GUI Configuration Syntax The most generic definition of a GUI file can be described through the symbols below Words with CAPITAL LETTERS should be entered literally e The character is used as or for example a b means a or b e The character means zero or more occurrences of e A GUI file can contain one or more GUI configuration blocks as shown in the following table GUI Configuration Blocks GUI configuration BEGIN UI VIEW UI mode configuration END BEGIN UI COMPARE MARKUP UI mode configuration END UI mode configuration menu bar configuration toolbar configuration status bar configuration RMB popup menu configuration menu
24. lt value of 4GB is used Specifies the maximum number of files allowed in the cache directory Specifies the maximum number of days a file is kept in the AutoVue cache directory By default RMI port is not used If you enable streaming file generation autovue metacache enable true AutoVue uses the RMI port specified by this parameter You may need to change this parameter in situations where another application uses the same port or if company policy restricts the range of ports you can use Specifies the command line parameters for AutoVue s streaming file generator We recommend that you do not change these files other than log4j configuration Changing the Locale of AutoVue AutoVue supports the following languages for the user interface English EN French FR German DE Japanese JA Traditional Chinese TW Simplified Chinese ZH Korean KO AutoVue installation folder gt bin Cache 4096 64000 30 days 1299 On startup Auto Vue detects if the language of the OS is one of its supported locales and automatically switches the user interface to the locale of the operating system When the OS language is not supported by AutoVue the AutoVue user interface defaults to English It is possible to force the AutoVue user interface to a supported language by specifying the LOCALE parameter See section Command Line Parameters for the structure and syntax In cases where the operating syst
25. ng cached files as well as searching for archive and XRef files log4j category com cimmetry Displays information concerning downloading files from the network connection com cimmetry jvueserver doc Displays document related information open information properties and so ument on com cimmetry jvueserver doc Displays messages and error reporting for document related native code ument native execution com cimmetry jvueserver str Displays information concerning generation and usage of streaming files eamingfile com cimmetry frontend Displays all messages and errors reported from the AutoVue client You can specify what kind of information to output by setting the classes to one of the following information levels Information Level Description INFO Displays informative messages such as session information document open requests WARN Displays warning messages This is the default value ERROR Displays errors or exceptions AutoVue 23 Information Level Description OFF Turn logging off AutoVue 24 Customizing the GUI Choosing the GUI File AutoVue provides you the option of customizing your graphical user interface GUI By default the GUI specification is not set and AutoVue uses an internal GUI file for the menus and toolbars The GUI file that AutoVue generates is the same as the default gui file located in the lt AutoVue Installation Folder gt bin directory If you
26. nts Indicates an either or type of choice Indicates that information may be repeated AutoVue 6 Introduction AutoVue is Oracle s suite of Enterprise Visualization solutions which are designed to view digitally annotate and collaborate on any digital information from any system AutoVue delivers visualization capabilities for hundreds of document types including business documents such as Office and Graphics as well as technical document types such as 2 D 3 D Computer Aided Design CAD and Electronic Design Automation EDA AutoVue Desktop Deployment is a solution for users that want to run AutoVue locally as a personal productivity tool on their individual desktops For current users of AutoVue Desktop Version that plan to move to AutoVue Desktop Deployment a migration guide is available to plan and assist with the migration Contact your Oracle Customer Support representative to obtain a copy of the migration guide This document provides instructions for installing and configuring AutoVue Desktop Deployment In the remainder of this document AutoVue Desktop Deployment will be referred to as Auto Vue AutoVue 7 Upgrading AutoVue If you are upgrading AutoVue from version 20 all of your configuration files are automatically migrated The installer will notify that you have version 20 installed If you proceed with the installation the installer will backup required settings uninstall version 20 install version 20 1 and res
27. onFileOpen PERM READ MENUITEM VueActionFileProperties PERM READ MENUITEM VueActionFilePrint PERM READ END END END Control Names The following table lists available Control Names and their functionality Control Functionalit centro Contexts Name Modes y Key List a S g geile eo aq amp Salk VueAction VC When INI option EnableUniversalFileChooser is X FileOpen set to 0 invokes open URL dialog When option is set to 1 the universal file chooser dialog that supports URLs local files server protocol and DMS files appears Default for EnableUniversalFileChooser is 1 VueAction VC Open files using UNC names X FileOpenUNC VueAction V Switch to Markup mode X X XX FileMarkup VueAction V Switch to compare mode X FileCompare VueAction V Select and modify overlays X FileOverlays AutoVue 27 Control Ur Control Functionalit Contexts Name Modes y Key List VueAction VCM Show file properties x FileProperties M status bar only VueAction VCM Modify print options and print a file X FilePrint VueAction V List most recently used documents FileMRU VueAction VM Do search or repeat search X EditSearch VueAction VCM Apply zoom In X X ViewZoom Out Previous FullRes FitBoth VueAction VCM Apply flip Vertical X ViewFlip Horizontal Both VueAction VCM Apply rotation 0 X ViewRotate 9
28. ows the list of available control names UI modes Column specify in which modes can be used that control safely Example VueActionFileOpen can be added to View and Compare Modes except for Markup mode Functionality Column specifies which functionalities are provided when this control is added to a context Example Adding VueActionFileMarkup to any context enables you to switch to Markup mode Control key list Column provides the optional functionalities that can be added to a context e If for acontrol name there is no entry in this list this means that by default all the controls providing the functionality listed in the functionality column are provided For example for VueActionFileOverlays there is no entry in the control key list and adding it to a popup menu will provide both select and modify functionalities for overlays The entry will look like this AutoVu Con Exa e 29 MENUITEM VueActionFileOverlays PERM READ If there is a list of strings separated by you can specify which functionalities you want added If you don t specify any of them by default all functionalities will be added For example the following entry adds two buttons to the toolbar one for Zoom In and one for Zoom Out BUTTON VueActionViewZoom In Out PERM READ Whereas the following entry BUTTON VueActionViewZoom PERM READ is interpreted as BUTTON VueActionViewZoom In Out
29. s to Oracle Support Services within the United States of America 24 hours a day 7 days a week For TTY support call 800 446 2398 Outside the United States call 1 407 458 2479 Related Documents For more information see the following documents in the Oracle AutoVue documentation library e User s Manual e AutoVue Viewing Configuration Guide Release Notes e Acknowledgments e Supported Formats List Product Variations Feature Matrix AutoVue Conventions The following text conventions are used in this document Convention Meaning boldface Boldface type indicates graphical user interface elements associated with an action or terms defined in the text italic Italic type indicates book titles emphasis or placeholder variables for which you supply particular values monospace Monospace type indicates commands within a paragraph URLs code in examples root directory sub directory lt angular brackets gt curly braces square brackets text that appears on the screen or text that you enter In Windows and Linux OSes directory hierarchy is written with backward slashes and forward slashes respectively In this document unless mentioned otherwise directory hierarchy for Windows and Linux OSes are written with the backward slash Indicates required entries but are not to be included in the entered information Indicates mandatory information Indicates optional syntactical eleme
30. shortcut on the Desktop Adds a shortcut to the Quick Launch bar Adds a shortcut to the specified location Shortcuts are not created To create icons for all users of AutoVue select Create Icons for All Users 11 Review the pre installation summary and then click Install 12 Click Done to quit the installer AutoVue is installed in the specified directory Start AutoVue to verify that your installation went through successfully Refer to section Starting AutoVue for more information Note If there are any warnings or errors refer to the installation log file install 1og located in the lt AutoVue Installation Folder directory Starting AutoVue To verify your AutoVue installation start up AutoVue by doing one of the following e From the program shortcuts select Oracle AutoVue Desktop Deployment and then Start AutoVue AutoVue 12 or e Run autovue exe located in the lt AutoVue Installation Directory gt bin directory Auto Vue loads and the AutoVue icon amp appears in the system tray Note On machines that have firewall enabled a pop up appears asking if you want to block or unblock the program AutoVue will work fine no matter what option you choose If you close the AutoVue window it continues to run in the background To close AutoVue completely right click the AutoVue icon S in the system tray and select Close Note If AutoVue does not load enable logging and contact Oracle Customer Support
31. table lists the parameters that can be configured Property Description Default Main Options autovue inifile file name Specify the INI file where AutoVue stores information on the file VueCore ini formats supported by AutoVue We recommend that you do not change this option value Note AutoVue also saves certain memory management settings in this file We recommend that you do not modify these options or the file VueCore ini User Profiles Options autovue users directory file path autovue users defaultini file name autovue users allusersini file name Proxy Options autovue http proxyhost autovue ftp proxyhost Startup Options lt AutoVue installation directory gt bin Profiles Contains the directory in which user information is stored initialization files and GUI files The user must have write permissions to the folder AutoVue creates an username ini file for every user that accesses AutoVue This file is stored at the location specified by the autovue users directory parameter AutoVue provides a way to force certain INI settings to the user default ini INI the first time the user accesses AutoVue This is done by setting the required options in the default ini file or in the file specified by autovue users defaultini parameter This file should be located at AutoVue Installation Directory bin directory AutoVue provides a way to force INI settings to the user prof
32. the base file to locate markups Markups are saved with the name basefile name extension specified by user When upgrading from version 20 0 markups located at lt AutoVue installation directory gt bin Markups are backed up and migrated to version 20 1 Auto Vue 20 1 detects these migrated markups When you open these markups and resave them markups are saved with the version 20 1 behaviour i e they are saved either into the avred folder or at the location specified by autovue markups local directory AutoVue AutoVue 9 System Requirements Oracle AutoVue Desktop Deployment is certified on the following platforms Windows XP 32 bit Windows Vista 32 bit and 64 bit AutoVue running in 32 bit mode Windows 7 32 bit and 64 bit AutoVue running in 32 bit mode Hardware Requirements The recommended requirements for a machine running AutoVue Desktop Deployment is as follows 2 GB of RAM Note AutoVue is a 32 bit application Generally 32 bit processes are limited to 2 GB of RAM However the AutoVue Desktop Deployment executable is large address aware This means that if AutoVue is running on a 64 bit OS that has 4 GB of RAM AutoVue can use up to 4 GB of RAM If AutoVue is running on a 32 bit machine that is booted up with the 3 GB switch and the machine has 3 GB of RAM AutoVue can use up to 3 GB of RAM 2 GHz dual core CPU Display driver that supports OpenGL and has dedicated memory required for 3D support 40
33. tore backed up settings Below is a list of configuration settings that are migrated e User INI file default ini and allusers ini files e Configuration settings from VueCore ini and autovue properties are migrated into autovue properties Note In version 20 1 parameters from VueCore ini have been moved to autovue properties file located in the AutoVue Installation folder gt bin directory For more information on these migrated options refer to the Release Notes e Customized GUI files located in the AutoVue Installation Directory gt bin Profiles directory e Global user settings from the allusers ini file and default user settings from the default ini file located in the AutoVue Installation Directory bin directory e Custom logging settings from the log4j xml file located in the AutoVue Installation Directory gt bin directory e Custom markup symbol libraries located in the lt AutoVue Installation Directory gt bin Symbols directory e Markup files located in the lt AutoVue Installation Directory gt bin Markups directory Markups The location where markups are saved has changed in version 20 1 In 20 1 by default markups are stored in an avred folder at the location of the base file Alternatively option autovue markups local directory can be set to a folder where all markups created by the user will be stored AutoVue no longer relies on markups map to map markup files to base files Auto Vue relies on the name of
34. urce files are expected to follow filename_XX properties where XX is a two character representation of a language When specifying the custom resources using this parameter do not specify the language and the extension For example lt PARAM NAME EXTRABUNDLES VALUE CustomActions gt FORMAT AUTO TILED METAFILE Set the rendering format TILED uses a tiled raster representation of documents to display file AUTO uses adapted representations depending on the type of file viewed When set to METAFILE data is streamed to the client as a compressed metafile CMF Display lists are sent to the client and the client interprets and renders these display lists Generally Office documents are rendered in TILED mode while 2D and Raster documents are rendered in METAFILE mode Default AUTO AutoVue 19 Name Type Value GUIFILE String The Graphical User Interface GUI definition file used GUI files are stored in subdirectories of the root directory specified in the autovue users directory parameter of the autovue properties file The specification can also specify a local file using the file convention Default for the autovue users directory parameter is bin dir Profiles Refer to appendix Customizing the GUI for more information HEAVYWEIGHT TRUEIFALSEIAUTO Specify if you would like to use JOGL s heavyweight or lightweight widget to render 3D Models W
35. ustomActionTools CustomActionTools java and edit the following lines private static final String resources TOOL1 TOOL2 10 AutoVue 31 private static final String subActions tooll1 tool2 private static final String batchfiles batchl bat batch2 bat where resources is the list of strings that will show up in the Tools menu The first string should correspond to the first batch file the second string to the second batch file and so on subActions is a list of strings that is used to associate a particular Tool menu item to a batch file batchfiles is the list of batch files Compile the Java code Copy the generated CustomActionTools class to AutoVue Installation Directory bin Make a copy lt AutoVue Installation Directory binMVefault gui to a file called tools gui Copy this GUI file to AutoVue Installation Directory bin Profiles Edit tools gui and add the new CustomActionTools to an existing or new menu MENUITEM CustomActionTools PERM READ If you are referencing new resources you will need to update file CustomResources_en properties with the new resources You can translate the custom resources The translations should be named CustomResources_xx properties where xx represents the two letter language code Copy the resource files to lt AutoVue Installation Directory gt bin Add the following to the autovue cmdline property in autovue properties param GUIFI
36. utoVue AutoVue supports the following command line options You can specify an alternative configuration file for AutoVue by specifying the config parameter Syntax autovue exe config fullpath to config file For example autovue exe config C users avuser appdata autovue autovue properties You can specify a filename to load when starting AutoVue by specifying the full path to the file on the command line For example autovue exe C samples 2D AutoCAD dwg Note You can specify multiple files as command line options AutoVue opens the specified files in new child windows Note By default the file opens in a new window To change this behavior you must set NEWWINDOW parameter to FALSE in autovue properties Refer to section Configuring AutoVue for more information For example autovue exe C samples 2D AutoCAD dwg C samples 3D Solidworks sldprt AutoVue 14 Configuring AutoVue You can configure AutoVue by modifying autovue properties located in the lt AutoVue Installation Directory bin directory Configuration parameters include configuring the maximum memory available to AutoVue location of markups cache and profiles GUI file to use on startup new window behavior and so on Changes to autovue properties will take effect when AutoVue is restarted Refer to the following table for the list of configuration parameters For Example c Program Files Oracle AutoVue Desktop Deployment bin The following
37. utoVue starts up If the full path of the PNG or JPEG is not specified the splash screen does not display Entry specifies the file path to the English en French fr German de Japanese ja Help file 15 lt AutoVue installation directory gt jre bin java exe lt AutoVue installation directory gt jre lt AutoVue installation directory gt html help lt an guage gt AutoVueOnlineH elp html For example lt AutoVue installation directory gt html help en A uto VueOnlineHelp html Markup Options autovue markup nativegui t ype 01112131417 autovue markups local dire ctory file path autovue markups symbols directory file path Add Author Date and Markup Info columns to the Markup Files dialog box 0 Name column displays 1 Enable Author 2 Enable Date 4 Enable Markup Info Note These are ORed flags For example Enter 7 to enable all three columns In version 20 1 markup files are saved with the name lt base file name gt lt end user specified extension gt By default AutoVue Desktop Deployment saves markups in the avred directory at the base file location If the user does not have permission to write into the base file location they can export the markup into an alternate directory Alternatively user can set this property autovue markups local directory to a location where all markup files should be stored Note If you change the markup save location markups previously sav
38. you can create your own definitions PartCatalogueAction java and PartListAction java demonstrate how to write custom actions A custom gui file is the customized gui for the custom actions Copy this file to AutoVue Installation Directory gt bin Profiles Update the Java code as needed and compile the code Bundle all the class files into VueActionSample jar Add this VueActionSample jar to AutoVue s classpath autovue classpath in autovue properties Add following to the AutoVue commandline autovue cmdline in autovue properties param GUIFILE custom gui param EXTRABUNDLES PartCatalogueAction Sample Files When you choose to install sample files during the AutoVue installation process the following samples are installed Sample 2D 3D EDA Office and Graphics file are installed at AutoVue Install Root gt html samples Adding Custom Tools Menu to AutoVue You can add custom Tools menu items to AutoVue so that batch files can be triggered from the menu items AutoVue provides some example code that demonstrates how to build custom Tools meny items The example code is installed when you do a Custom installation of AutoVue and select the API Examples checkbox during installation The steps for adding custom Tools menu are below Note that this requires familiarity with programming in Java 1 Copy your batch files to lt AutoVue Installation Directory bin 2 Edit lt AutoVue Installation Directory gt examples C
Download Pdf Manuals
Related Search