1 Installing and Upgrading AutoVue for Agile

AutoVue for Agile PLM Installer updates the Agile PLM Application Server and File Manager components for Agile PLM version 9.3.2.x, 9.3.1.x and 9.3.0.x on all platforms. It also installs the AutoVue Server component on Windows or Linux.

You must run the AutoVue for Agile PLM Installer on the Application Server and all File Managers as well as the machine where you wish to install the AutoVue Server. Select the AutoVue for Agile PLM option in the installer if you wish to install the AutoVue Server, and select the Upgrade AutoVue 20.2.2 Client Libraries option if you are running the installer on an Application Server or File Manager. If your Application Server or File Manager is installed on the same machine as AutoVue, then both the AutoVue for Agile PLM and the Upgrade AutoVue 20.2.2 Client Libraries options must be selected in the installer.

Note:

Before updating the AutoVue client libraries, ensure that you stop the file server and any additional Agile processes.

To install on Unix platforms:

Uninstall any previous versions of AutoVue.
Run the Red Hat Update Agent, up2date, to download the latest Xvfb and Mesa files.

Note:
AutoVue Server installer does not detect whether Mesa or Xvfb are installed.
Install Xvfb version 6.8.2 or later.

Ensure you install Xvfb with XRender and GLX extensions.
Install the latest Mesa package (recommended version is 6.5.1 or later).
Install the libsane package, if not already installed.
Install the libXp package, if not already installed.
Install the Wine RPM package "wine-av-20040914-21.i386.rpm" from Oracle AutoVue Open Source Components 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 AutoVue 20.2.2.
- Install Wine as a root user by running the following command:
  - #rpm -i wine-av-20040914-21.i386.rpm
Note:
Wine is installed in directory /usr/av.
Download Oracle AutoVue 20.2.2 from Oracle Software Delivery Cloud (http://edelivery.oracle.com).
Launch the AutoVue 20.2.2 Installer (Linux: setup_av_lin.bin).

Note:
For other supported platforms, run the respective .bin installers. (Solaris: setup_av_sol.bin /AIX: setup_av_aix.bin /Solx86: setup_av_solx86.bin/HP-UX: setup_av_hpux.binetc)
While running the above .bin file, provide the following installation details - location/appserver/filemanager info etc. The Install window appears.
Follow the instructions to proceed with the installation.
For information about any screen in the installer, click Help.
Click Next to proceed through the installer.

Note:
If you are installing on an Application Server or File Manager, check the Upgrade AutoVue 20.2.2 Client Libraries option on the Choose Install Components panel.
Click Done to finish the installation.

To install AutoVue on Windows Platform:

Download Oracle AutoVue 20.2.2 from Oracle Software Delivery Cloud (http://edelivery.oracle.com) to a temporary directory.
For Windows run the setup_av_win.exe from the temporary directory.
While running the above .exe file you have to provide installation details - location/appserver/filemanager info etc.
Follow the installer steps to install.
Click Finish to complete the AutoVue installation.

Note:
Before updating the AutoVue client libraries, ensure to stop the file server and any additional Agile processes.

After installing on the Application Server: After updating the client libraries, redeploy the application.ear file and restart the application server.

For instructions on restarting the application server, see either the Installing Agile PLM on Oracle Application Server or the Installing Agile PLM on Oracle WebLogic Server manual.

After installing on the File Manager: After updating the client libraries, redeploy the webfs.war file (Filemgr web application) on the File Manager.

To redeploy the File Manager:

Change to the TOMCAT_HOME\webapps directory.
- For Agile PLM 9.3.2 and later, TOMCAT_HOME is AGILE_HOME\FileManager
- For Agile PLM 9.3.1.x and 9.3.0.x, TOMCAT_HOME is AGILE_HOME\apache-tomcat-6.0.18
Verify there is a directory named Filemgr under the webapps directory.

Note:
The TOMCAT version bundled with Agile PLM 9.3.2 and later may not create a 'Filemgr' folder in the webapps directory.
If the Filemgr directory exists, then perform the following:

cd ..

mkdir webapps.old

Windows: move webapps\Filemgr webapps.old

UNIX: mv webapps/Filemgr webapps.old
Change to the TOMCAT_HOME\work\Catalina\localhost directory
- For Agile PLM 9.3.2 and later, TOMCAT_HOME is AGILE_HOME\FileManager
- For Agile PLM 9.3.1.x and 9.3.0.x, TOMCAT_HOME is AGILE_HOME\apache-tomcat-6.0.18
Remove the directory named Filemgr under the work directory.
Start TOMCAT.

Backup the application.ear and webfs.war files before upgrading the client libraries to version 20.2.2. If you are upgrading to version 20.2.2, the Profiles folder is also backed up and a new Profiles folder is created with the latest GUI files.

If you are upgrading from an earlier version:

Remove the CMF files of the previous version on the file vault.
To remove the CMF files, unzip the MetaFilesRemover.zip file and run the MetaFilesRemover utility located at agile_home\agileDomain\tools.

Usage: java -jar MetaFilesRemover.jar [-delete <value>] [-age <value>] [-size <value>] -basedir <value> -prefix <value> -serverURL <value> -username <value> -password <value> -dburl <value> -dbuserid <value> -dbpassword <value>

where
- delete deletes the metafiles.
- age specifies the last access time (day).
- size specifies file size (KB).
- basedir is the file vault location where the metafiles are removed.
- prefix is the file name prefix.
- serverURL is the location of the DMS service, for example, http://server.company.com:80/Agile/services/DmsService.
- username is the DMS service username.
- password is the DMS service password.
- dburl is the database location (ex: hostname.us.oracle.com:1521:agile9).
- dbuserid is the database user id.
- dbpassword is the database password for this user.