ENOVIA V5 VPM Installation Instructions

 

The following topics are addressed in this document:


Licensing Information

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.

JAVA_HOME Variable

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.


Single Sign On

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.

 


2D and 3D Viewers

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.

 


Misleading Message after PLMDBSetup

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.

 


Document Addendum to Migrating from ENOVIA V5 VPM V5R18 to ENOVIA V5 VPM V5R19 on UNIX document.

The correct path for ENVDir is:

-EnvDir The full directory path to the CATEnv directory.

Example:

-EnvDir /usr/DS/LCA17/CATEnv

Documentation Change: Data Groups in P and O

Note: creating data groups which reference to boolean attributes is no longer supported by the VPMPeopleEdit application.

Documentation Change: Erroneous Vault Starter Command

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\""

Documentation Change: Modifying the ulimit Data Setting

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.

Documentation Change: New Topic - Deploying a Web Application in a Portal

Add the following new topic:

Deploying a Web Application in a Portal

 

Documentation Change: Installing the Vault Server Manually

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\ ""

Documentation Change: Activating SSO on the Wintop Client

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