3 Prerequisites

This chapter discusses the prerequisites of installing AutoVue for Agile PLM.

Pre-requisites for Installing AutoVue for Agile PLM

Prior to installing AutoVue for Agile PLM, there are certain prerequisites that must be met. The following prerequisites are common to Windows and Linux OSes.

• It is recommended that you install the AutoVue server component with each File Manager.

• The machine that is hosting the AutoVue server must have a color depth of at least 16-bits. If the machine has a lower color depth, you may run into discrepancies in color or filling when viewing, printing or converting from AutoVue.

• Ensure that the AutoVue server has permission to write to the operating system's temporary directory. To ensure temporary files are created in protected locations on Linux, the scripts jvueserver and jvueserver_debug have been changed to set new temporary directory. This it does by setting environment variable TMPDIR (by default, TMPDIR="/tmp/autovue"), and the new temporary folder to the permissions 700 (owner can read, write and execute).

  The AutoVue server administrator is responsible for setting this environment variable for security.

  1. If setting TMPDIR="/tmp", AutoVue will create temporary files in no secure location /tmp, and log a security warning, such as "SECURITY WARNING: Incorrect or insecure temp folder (/tmp), using global temp directory".

  2. If a temporary folder is set to one owned by another user, AutoVue will prompt "AutoVue temporary folder $TMPDIR is owned by a different user", and exit.

  3. If a temporary folder on Linux is set to one without 700 permission, AutoVue will prompt "AutoVue temporary folder $TMPDIR has incorrect permissions", and exit.

• If you are using a load balancer, ensure that the load balancer is configured to enable session stickiness (also referred to as session persistence). Session stickiness is normally achieved through the use of browser cookies.

• For performance reasons, it is recommended that the applications’ streaming file cache directory is excluded from real-time virus scans. If virus scans are enabled, there is a performance impact on it and the impact is tied to the kind of operations done by the virus scan. It is also recommended that you run scheduled virus scans at a time when the server is not heavily in use.

• All server machines should obey the following conditions:

  • Have the same fonts installed.

  • If SSL is enabled, have identical certificates in their JVM repositories

  • If an AutoVue server farm is configured, then ensure that the jvueserver.rmi.host.* is set to the same entries for all the servers in the farm. If a new server is added to the farm and the entries of jvueserver.properties of the existing servers are not updated, this new server will not be allowed to connect to the farm. When this happens, a warning is logged in the server logs.

• It is recommended to install only one instance of the AutoVue server per physical machine.

The following sections describe Windows-specific and Linux-specific prerequisites.

Windows Prerequisites

• AutoVue for Agile PLM installs the AutoVue Document Converter print driver on Windows operating systems. Ensure that the print spooler service is enabled and that you have the permissions to install print drivers on the AutoVue server machine.

Linux Prerequisites

To correctly install AutoVue for Agile PLM on a Linux OS, it is recommended that you have basic knowledge of Linux and its administration. Note that you can install AutoVue for Agile PLM on Linux only in the GUI mode.

Note: To install packages on a Linux system you must have appropriate administrative privileges

• It is recommended to install AutoVue for Agile PLM using the same user account used to install Agile PLM.

  If the drawings you are accessing from AutoVue (or any of the external references) reside on a mounted drive, ensure that the drive is mounted with the noserverino parameter.

• Install the core fonts from http://corefonts.sourceforge.net/. These fonts are required for viewing files that use some specific fonts.

• Ensure that the pre-requisite libraries for Linux are installed. For the most up-to-date list of libraries, refer to the Oracle Support Document 967083.1 (Prerequisite Library Names for AutoVue Web Version on Linux) at: https://support.oracle.com/epmos/faces/DocumentDisplay?id=967083.1

• The following must be installed on the Linux machine:

  • The Xvfb, libXfont and Mesa packages. The Mesa package must be 32-bit.

  • The following 32-bit libraries must be installed on the 64-bit machine:

    • libGL.so.1 (yum install mesa-libGL.i686)libGLU.so.1 (yum install mesa-libGLU.i686)libz.so.1 (yum install zlib.i686)libbz2.so.1 (yum install bzip2-libs.i686)

    • libXt.so (yum install libXt.i686)

    • libXp.so (yum install libXp.i686)

  
  

  Note: The AutoVue server does not detect whether Xvfb or Mesa are installed.

  
  

• Make sure to run the YUM update command for a package before installing it.

  # yum update <package_name/s>
  

• Install the latest Xvfb by running the following command:

  # yum install Xvfb
  

  
  

  Note: For Linux 5.x, install Xvfb version 6.8.2 or later. Make sure you install the Xvfb with XRender and GLX extensions.

  
  

• Install the latest Mesa package (recommended version is 6.5.1 or later) by running the following command:

  # yum install mesa-libGLU
  

  
  

  Note: In the event you want to use an earlier version of Mesa, it is acceptable to use the version that is included in the repository of the supported Linux distribution.

  
  

• Install the 32-bit libsane and libXP packages, if not already installed.

• Install the WINE RPM package. To do so, install wine-av-20040914-24.i386.rpm from http://oss.oracle.com/AutoVue.

  • If you have an older version of WINE, you need to uninstall it and then install the package that is certified with your version of Oracle AutoVue.

  • Install WINE as a root user by running the following:

    #rpm -i wine-av-20040914-24.i386.rpm
    

    
    

    Note: This version of WINE is installed in the /usr/av directory.

    
    

Additional Guidelines for Security

The following prerequisites are common to Windows and Linux OSes, and is essential for security purposes.

• Shutdown all applications (including the AutoVue server) before you run the installer for the AutoVue for Agile PLM installation.

• When upgrading, if the installer prompts you to reboot the machine before or after the un-installation, you must reboot the machine in order to get a successful installation. If you fail to reboot when prompted, the application installation may be left in an unusable state.

• In a multi-AutoVue server deployment, it is recommended to install AutoVue in the exact same folder path on each server.

Default Locations

The default location of the components of AutoVue for Agile PLM is provided in the Table 3-1, "Default Location of AutoVue for Agile PLM Components".

Table 3-1 Default Location of AutoVue for Agile PLM Components

Component	Select this while installing	Default Location
Agile PLM with application server	In the Choose Install Component(s) window, select Application Server check box.	AGILE_HOME/agileDomain
File Manager	In the Choose Install Component(s) window, select File Manager check box.	AGILE_HOME/FileManager
AutoVue Server	Select the AutoVue Server component.	AGILE_HOME/AVS