The following topics are addressed in this document:
The licensing system of ENOVIA V5 VPM is IBM License Use Management. More information on LUM can be obtained on the IBM web site at http://www.ibm.com/software/lum or in the LUM 4.6.8 CDROM that may have been distributed with this V5 package.
Nodelock license keys are not allowed with ENOVIA V5 VPM. IBM License Use Management (LUM) is required to serve concurrent license keys across a network. A LUM configuration file (i4ls.ini) is required on clients to access concurrent license keys from license servers.
NOTE THAT LUM 5 IS NOT COMPATIBLE WITH THIS V5 DELIVERY. 4.6.8 level of LUM is required on all platforms for all product brands.
LUM 4.6.8 + 4.6.8.3 patch is the latest level certified by Dassault Systemes. It is recommended to migrate your LUM servers to this level.
If you install the ENOVIA_V5_VPM media for the client part, for example, the configuration DER, the CATIA media must be installed afterwards.
Furthermore, in the CATIA environment file, the JAVA_HOME variable must be set to the same value as in the ENOVIA_V5_VPM environment file.
The Installation and Deployment Guide, chapter "Activating Single Sign-On", section "Activating SSO in the Installation Path Deployed in the Web Application Server (Wintop or Webtop)" discusses two variables.
The following variables must be set like this:
SSOActivated=yes
SSOSecuredEnvironment=yes
in the SSOClient.properties
file in BOTH the installation of
the PLM Hub (ENOVIA V5 VPM server) AND of the Web server.
The SSO mode cannot be activated on ENOVIA V5 VPM server when this server is installed on Windows 2008 Server operating system.
In order to use the 2D or 3D Viewer, you must install and have all necessary licenses for 3dCOM. For more information on installation and licensing, consult 3d COM Classic Installation and Licensing.
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.
The correct path for ENVDir is:
-EnvDir |
The full directory path to the CATEnv directory. Example: -EnvDir /usr/DS/LCA17/CATEnv |
Note: creating data groups which reference to boolean attributes is no longer supported by the VPMPeopleEdit application.
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\""
Add the following to this section:
1024 is just an initial setting and it should be modified differently based on the number of users in production. You need to consider that every user is consuming between 5-9 connections. And the number of FD should be consistent with the total number of connections which can be used.
Example: For 200 users the ulimit for the FD should be set to 4096 or higher.
Add the following new topic:
Deploying a Web Application
in a Portal
The example in "Register the New Vault Server on the Orbix daemon" should now read:
Putit -h machine_name -shared VaultServerName "install_dir/code/command/catstart
-env \"env_name\" -direnv \"env_dir\" -run install_dir/code/command/runENOVVaultStarter
-object \" MyVaultOwner_UID MyVaultOwner_GID env_name env_dir\ ""
The following steps should be added to the section "Activating SSO on the Wintop Client":
4. For VPM Navigator, edit the file:
install_path/$os/resources/sso/SSOClient.properties
(UNIX)
install_path\$os\resources\sso\SSOClient.properties (Windows)
and set the following properties to "yes" (the default is "no"):
SSOActivated=yes
SSOSecuredEnvironment=yes
5. For VPM Navigator, export the CATJWSServiceDirectory
variable, for example:
export CATJWSServiceDirectory=http://loug3dsy.dsy.ds:9080/B19
On Windows Server 2008, due to some security constraints, two extra steps must be run:
CATJdeW2K8predeployment.exe
utility, then run the ActivateFullText.exe
utilityCATJdeW2K8postdeployment.exe
utility.In the Installation and Deployment Guide, chapters "Unloading Your Product Code on Windows/UNIX", the section about server timeouts has been rewritten. The instructions for individual server timeouts has been deleted, and the section "Modifying Server Timeouts" now reads:
Modifying Server Timeouts
-------------------------
This task explains how to modify the timeout of the ENOVIA V5 VPM, 3d com and Settings servers. Note that the Settings server is common to both ENOVIA V5 VPM and 3d com.
To control the timeout of all servers globally, add the following line:
set SERVER_TIMEOUT=<value in milliseconds> (Windows)
export SERVER_TIMEOUT=<value in milliseconds> (UNIX)
to the beginning of the file:
$install_path\code\command\runServerManager (Windows)
$install_path/code/command/runServerManager (UNIX)
Note: The default value is 3600000 milliseconds. The maximum value is
2142000000 milliseconds.
All processes started by the server manager then inherit the same
environment.
In the Installation and Deployment Guide, chapter "Unloading Your Product Code on Windows", section "ENOVIA V5 VPM Post-Installation Tasks", the following section has been added:
Note About Windows 2008 Server Support
----------------------------------------
If you are installing ENOVIA V5 VPM on Windows 2008 Server, you must add the following line:
IT_USE_GET_USERNAME = "FALSE";
to the files:
install_path\startup\orbix\config\common.cfg
install_path\startup\orbix\config\orbix3.cfg
Note that UAC must be deactivated on Windows Server 2008.
In the Installation and Deployment Guide, "Deploying ENOVIA Applications", chapter "Deploying ENOVIA Web Services", the section "Crash while running the ExtractDocument Web Service" has been removed.