| OracleÆ AutoVue for Agile PLM Installation and Configuration Guide Release 21.0.0 E61176-01 |
|
 Previous |
 Next |
| OracleÆ AutoVue for Agile PLM Installation and Configuration Guide Release 21.0.0 E61176-01 |
|
Previous |
Next |
This chapter describes how to install AutoVue for Agile PLM on Windows and Linux OSes. The AutoVue for Agile PLM installer updates the Agile PLM Application Server and File Manager components for Agile PLM version 9.3.4, 9.3.3, 9.3.2, 9.3.1.x and 9.3.0.x on all platforms. It also installs the AutoVue server component on Windows or Linux.
|
Note: When upgrading your installation of AutoVue for Agile PLM, do not cancel the installation process once it has begun. Canceling the installation may leave your current installation of AutoVue for Agile PLM unusable. |
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 AutoVue Client Libraries option if you are running the installer on an application server or File Manager. If it is required to install the AutoVue server on the same machine with the application server and File Manager, then both the AutoVue for Agile PLM and the AutoVue 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. |
If you are upgrading from AutoVue for Agile PLM 20.1.x/20.2.x, you do not need to run the uninstaller before you install AutoVue for Agile PLM 21.0.0. You can just run the installer for AutoVue for Agile PLM 21.0.0. The installer detects if AutoVue for Agile PLM 20.1.x/20.2.x is installed on your machine. If it is installed, the installer backs up required data, uninstalls version 20.1.x/20.2.x and then installs 21.0.0 to the same location. If you already have 20.2.x, with codebase (client JAR files) set in Jetty, the installer will upgrade to AutoVue for Agile PLM 21.0.0.
If installing on a Linux OS, make sure you have the correct version of WINE installed. The version of WINE compatible with AutoVue for Agile PLM 21.0.0 is wine-av-20040914-24.i386.rpm. You can download this version of WINE from http://oss.oracle.com/AutoVue.
|
Note: It is recommended to delete all cached and streaming files when updating AutoVue for Agile PLM. |
Below is the list of data that is migrated if you are upgrading:
Settings in jvueserver.properties are migrated to the new version.
The installer upgrades the previous configuration settings from allusers.ini and jvueserver.properties when you install the new version.
Any changes made to default.ini and allusers.ini are migrated to the new version.
AutoVue for Agile PLM user profiles are left as is.
The following are left as is since they are read by the new version of AutoVue:
Server-managed markups
Any stamps and stamp libraries
Intellistamps and definitions
On Linux, changes made to <AutoVue for Agile PLM Install Root>/config/jvuew_config are left as is since this will be read by the newer version of AutoVue.
Custom log settings: If you had custom log settings, these are migrated to the newer version of AutoVue for Agile PLM.
Changes made to markup policy file are migrated to the newer version of AutoVue for Agile PLM.
Any changes made to format-specific files such as color maps, font maps, fonts are migrated to the newer version.
The following are not migrated and must be migrated manually:
GUI files: If you created custom GUI files, you must make sure to migrate the GUI settings. In order to migrate GUI, it is recommended that you run a diff utility between your current version's default.gui and your custom GUI. Identify what GUI components have been updated. Manually apply these settings to 21.0.0 GUI file.
If you are upgrading AutoVue for Agile PLM from version 20.x or earlier, you must manually move your configuration settings from your version to AutoVue for Agile PLM 21.0.0. You must first uninstall any service packs that are installed for that version of AutoVue for Agile PLM and then uninstall your previous version before installing the new version of AutoVue for Agile PLM. Before you uninstall, you must backup all required data. Once you install 21.0.0, you must migrate your past data to 21.0.0. Below is what you need to backup and migrate manually:
Custom settings in jvueserver.properties
Custom settings in VueServer.ini. As of version 20.1, settings in VueServer.ini have been migrated to jvueserver.properties. Refer to the Oracle AutoVue 20.1 Release Notes for a mapping of VueServer.ini option to jvueserver.properties parameter.
Custom settings in default.ini and allusers.ini should be backed up and migrated to the new version.
User-specific INI files should be backed up and copied over to the Profiles folder of the new installation.
GUI files: If you created custom GUI files, you must make sure to migrate the GUI settings. In order to migrate GUI, it is recommended that you run a diff utility between your current version's default.gui and your custom GUI. Identify what GUI components have been updated. Manually apply these settings to 21.0.0 GUI file.
Custom log settings: If you had custom log settings, apply them manually on the new version of AutoVue.
Stamp attributes and settings from the dmstamps.ini file (located in the <AutoVue for Agile PLM Install Root>\bin directory) should be copied over manually to the new version
Markup files, if markups are being managed by the AutoVue server (located in the <AutoVue for Agile PLM Install Root>\bin\Markups directory) should be backed up and copied over to the new version of AutoVue.
Custom markup symbol libraries (located in the <AutoVue for Agile PLM Install Root>\bin\Symbols directory) should be backed up and copied over to the new version of AutoVue.
If MarkupPolicy.xml located at <AutoVue for Agile PLM Install Root>\bin was modified, it should be backed up and changes to the policy should be manually applied to the new version.
On Linux installations of AutoVue for Agile PLM, backup the jvuew_config file (located in the <AutoVue for Agile PLM Install Root>/config directory) if it was modified and apply the changes manually to the new version.
Any changes made to format-specific files such as color maps, font maps, fonts must be backed up and these changes should manually be applied to the new version.
To install AutoVue for Agile PLM on Windows Platform:
Download Oracle AutoVue 21 for Agile PLM Media Pack listed under the product Oracle Agile Applications product pack from Oracle Software Delivery Cloud or edelivery (http://edelivery.oracle.com) to a temporary directory and extract its contents.
For Windows run the setup_av_win.exe from the temporary directory.
Proceed to Running the Installation Program.
The installation program prompts you to enter specific information about the system and configuration. See the Table 6-1, "Installation Instructions" for what you have to do during the installation.
Table 6-1 Installation Instructions
| In this window... | Perform the following action... |
|---|---|
|
Welcome to AutoVue for Agile PLM Installation |
Click Next to proceed with the installation. |
|
Customer Information |
Enter the User Name and Company Name. Click Next. |
|
Choose Install Component (s) |
By default, the AutoVue Server and AutoVue Client Libraries check boxes are selected. Click Install. Note: Refer to Deployment Scenarios to determine what components are required for your installation. |
|
Installation Location |
Enter the location or folder where you want to install the selected AutoVue components in the Specify where to install the selected AutoVue component(s) box. Click Next. |
|
AutoVue Server |
Enter the host name and the port number of the AutoVue server that Agile File Manager will connect to. Click Next. Note: Ensure that you enter fully qualified machine/domain name for the Host Name. Example: host.domain.com (machinename.domianname). |
|
AutoVue Product |
Choose the AutoVue product that you have licensed. Click Next. |
|
Choose Shortcut Folder |
Here you can choose where you want to create the product icons. Following are the options:
Note: In case you select the Create Icons for All Users, then the product icon appears as a short cut for all users. Click Next. |
|
Pre-Installation Summary |
Review the Product Name, Install Folder, Shortcut Folder, Product Features, Disk Space Information (for Installation) and additional information before continuing with the installation. After the review, click Install. |
|
Install Complete |
Click Finish to complete the installation. |
|
Note: Before installing the AutoVue client libraries, remember to stop the file server and any additional Agile processes. |
After installing on the Application Server: After installing the AutoVue client libraries, redeploy the application.ear file and restart the application server.
For instructions on restarting the application server, refer to either the Installing Agile PLM on Oracle Application Server or the Installing Agile PLM on Oracle WebLogic Server manuals.
After installing on the File Manager: After installing the AutoVue client libraries, redeploy the webfs.war file (Filemgr web application) on the File Manager.
To install AutoVue for Agile PLM on Linux platforms:
Uninstall any previous versions of AutoVue.
Run the Red Hat Update Agent, yum up2date, to download the latest Xvfb and Mesa files.
|
Note: AutoVue installer does not detect whether Mesa or Xvfb are installed. |
It is recommended that AutoVue is installed in its own account to avoid any library conflicts between AutoVue and Agile or Oracle database.
Install the pre-requisites as described in Linux Prerequisites.
Download Oracle AutoVue for Agile PLM Media Pack listed under the product Oracle Agile Applications product pack from Oracle Software Delivery Cloud or edelivery (http://edelivery.oracle.com) and extract its contents.
Launch the AutoVue for Agile PLM installer (Linux: setup_av_lin.bin).
|
Note: It is recommended to run the AutoVue for Agile PLM installer UI on the server itself either through the primary display or, if installing remotely, by using vncserver. |
Follow the instructions to proceed with the installation. Select the components you would like to install.
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, select the AutoVue Client Libraries check box on the Choose Install Components panel. |
Click Done to finish the installation.
The AutoVue server can be installed on only Windows and Linux. However, Agile PLM application server and File Manager components can be installed on several other platforms including Solaris (SPARC), Solaris (x64), AIX (POWER) and HP-UX (Itanium). You can install AutoVue Client Libraries on any of these platforms.
Oracle AutoVue Client Libraries and integration components can be installed on the following platforms:
Table 6-2 Platforms and the corresponding executable file
| Platform | Executable File |
|---|---|
|
Solaris (SPARC) |
|
|
Solaris (x64) |
|
|
AIX (POWER) |
|
|
HP-UX (Itanium) |
|
Download Oracle AutoVue 21 for Agile PLM Media Pack listed under the product Oracle Agile Applications product pack from Oracle Software Delivery Cloud or edelivery (http://edelivery.oracle.com).
Extract the media pack and run the executable file.
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, select the Upgrade AutoVue 20.2.x Client Libraries check box on the Choose Install Components panel. |
Click Done to finish the installation.
For information on how to configure and re-deploy the File Manager, refer to the "Configuring the File Manager" chapter of the Agile Product Lifecycle Management Application Installation Guide located on the Agile OTN site http://www.oracle.com/technetwork/documentation/agile-085940.html.
|
Note: If you are upgrading from an earlier version it is required to run the MetaFilesRemover utility on all File Manager machines. |
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 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.
After you have installed the AutoVue client libraries and File Manager, you must verify that your integration works correctly with this version of AutoVue for Agile PLM. The following details the verification steps:
Start the AutoVue server, application server, and File Manager.
For each File Manager, verify the status of the VueServlet by accessing the File Manager configuration page:
http://fmhost:port/Filemgr/Configuration
