Information about installation of the on-line documentation can be found in the "On-line Documentation" page.
Information about installation can be found in the "V5 Installing and Licensing Instructions" page.
WARNING: Note that the installation of any Service Packs will re-deliver
files that you may have modified while working with the product. It is strongly
recommended that you backup all
.xml
files and the entire hierarchy
.../startup/
before re-installing.
If using interoperability, the following configuration is recommended:
ENOVIA DMU (the version of your DMU must be the same as the version of your ENOVIA 3d com installation; no previous version of ENOVIA DMU is supported)
ENOVIA VPLM ENOVIAVPM 1.6
Microsoft Internet Explorer 7.0
Server AIX 6.1 TL 2
Client Windows XP
ENOVIA 3d com 5.20
IMPORTANT: The CATIA level used by ENOVIA VPLM ENOVIAVPM and ENOVIA 3d com must be the same on a given server.
Note: ENOVIA VPLM ENOVIAVPM 1.2, 1.3, 1.4 and 1.5 are not supported.
ENOVIA 3d com Classic is NLS enabled.
For ENOVIA 3d com Classic, documentation is available in English and translated documentations will be available in German, French, Japanese, Chinese and Korean. Check availability dates for German, French, Japanese, Chinese and Korean documentation.
This chapter describes the installation method to install the functions of
ENOVIA 3d com. The
readme.txt
file contains the procedures
to install . This file can be accessed before installation by simply mounting
the CD-ROM and using a browser with the file path:
/cdrom/readme.txt
.
To copy the 3d com Installation guide (pdf format) for use during the installation | |
1. Insert the Documentation CDROM #2 into the CDROM reader. 2. Mount the CDROM. 3. Copy the installation documentation using the following command:
where |
To install the 3d com code | ||
1. You must be
super-user (root) to install the code. 2. Insert the Code CDROM into the CDROM reader. 3. Mount the CDROM, change directory to the mount point and enter the command:
or, if you don't want to hear music
A full self-explanatory graphical interface will appear, in which you can easily navigate. |
The installation of the Multi-PDM access drivers only requires the customization of a number of property files. For details, see the corresponding documentations found on the ENOVIA V5 3d com Documentation homepage:
Running batches using the Root userid on UNIX |
Do not run batches using the root userid on UNIX. |
"Bad options:" Message on Unix |
On Unix, you need to be root
before launching Release Setup in interactive mode (start or start -s ).
Otherwise, you will be prompted to log on as super-user and after having
entered the password, setup will end with the error message:
You must use option -u to specify where is your GA Installation. |
"Cannot save files before setup of Release" Message |
If the following message appears:
Please free space in the temporary directories:
When installing this Release in automatic commit mode, invalid required disk space is computed and it may be unable to install it. Even if it won't be used, please free disk space. |
Installation of MetaSearch on Windows with CATIA V5 |
There is a known problem where the installation of the 3d com MetaSearch server on the same Windows machine as CATIA V5 may cause CATIA default files to be updated. This may change the expected behavior of CATIA V5. Uninstall does not work consistently and may not return files to their original state. Until a fix is available it is recommended that the Metasearch server not be installed on a Windows machine already installed with CATIA V5. |
Use of VPM with an Oracle database |
You have to re-launch the orbix daemon which is launched automatically at the end of the installation. Else, it will be impossible to load a model stored in VPM in a 3dcom viewer |
Server environments use by default the folder referenced by the CSIDL_COMMON_APPDATA path for the .CATUserSettingPath variable. This folder is usually:
C:\Documents and Settings\All
Users\Application Data
and is used to contain a variety of files, including user settings located in the Dassault Systemes folder.
Typically, the authorizations given to the CATUserSettingPath may not be sufficient. By default, the folder:
C:\Documents and Settings\All
Users\Application Data
does not provide write access for normal end users. The default authorizations on the folder:
C:\Documents and Settings\All Users
and all the subfolders it contains are:
Administrators - Full Control
Power Users - Change (Read/Write)
Everyone - Read
System - Full Control
Consequently, make sure that end users using server-type environments have sufficient authorizations (MODIFY+WRITE) for at least the folder:
C:\Documents and Settings\All
Users\Application Data\Dassault Systemes
to be able to write their settings to (and modify their settings in) this folder.
In the ENOVIA Vault Client Configuration panel, you should leave the checkbox unchecked and then click the Next button.
Note: if the WebSphere Application Server cannot be stopped and a message like this is displayed:
The server "server1" cannot be reached. It appears to be stopped.
run the following commands to kill the WAS process:
ps -ef | grep java
kill -9 java process
where java process is the name of the appropriate WAS server process.
Furthermore, if the WebSphere Application Server was still running when you
launched the WASSetupUI
command, restart the server once the
command has been executed.
The "Additional Server Software Requirements" under section "Software Requirements" of the "Installation and Deployment Guide" for 3dcom classic now specifies that the supported level of Apache is Apache Server 2.2.3.
In the section "Post Installation for 3d com Server on UNIX/Windows",
"Configure the HTTP Server", the lines to be added to the end of the
httpd.conf
configuration file are now:
Alias /enovia_portal/ %installation_path%/intel_a/docs/
Alias /Views/ "<installation_path>/Views/
ScriptAlias /cgi-bin/ %installation_path%/intel_a/docs/cgi-bin/
On UNIX, if you do not perform the PLM Database setup procedure, the following message appears in the window from which you started the PLMDBSetup procedure:
PLMDBSetup program aborted
This is misleading to users who may have successfully completed the Clash setup procedure but did not not complete the PLMDBSetup procedure. If this is the case, simply ignore the message.
In the Installation and Deployment Guide, chapter "Installing the Vault Server Manually", section "Register the New Vault Server on the Orbix daemon", a backslash was missing from the vault starter command which should be:
Putit h reverdsy shared ENOVIAVaultServer /usr/DassaultSystemes/B19/solaris_a/startup/orbix/code/command/catstart
env \"ENOVIA_V5_VPM.V5R19.B19"\ direnv \"/CATEnv\" -run /usr/DassaultSystemes/B19/solaris_a/startup/orbix/code/command/runENOVVaultStarter
object \"1400 360 ENOVIA_V5_VPM.V5R19.B19 /CATEnv\""
Information about licensing can be found in the "V5 Installing and Licensing Instructions" page.