ENOVIA V5 VPM Installation Instructions

Warning.

The following features are not supported in this current delivery:

 

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.

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.

LUM 4.6.8 Fix Pack 13 is required on all platforms for all product brands.


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.

The SSO mode cannot be activated on ENOVIA V5 VPM server when this server is installed on Windows 2008 Server operating system.

 


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: Note About Windows Server 2008 Support

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

Documentation Change: UAC on Windows Server 2008

Note that UAC must be deactivated on Windows Server 2008.

Documentation Change: Problems with the Fetched Query Function in ENOVIA V5 VPM

In the Installation and Deployment Guide, chapter: "Setting Up Databases for the ENOVIA Version 5 Server on Windows/UNIX - Problems with the Fetched Query Function in ENOVIA V5 VPM - DB2",  the first paragraph and the example should read as follows:

"When creating the database, if you have chosen to use a specific codeset instead of the default Unicode, add the COLLATE USING IDENTITY option to your CREATE DATABASE statement.

Example:

CREATE DB mydb ON mypath USING CODESET IBM-1129 TERRITORY VN COLLATE USING IDENTITY

Documentation Change: Installing ENOVIA LCA on AIX Using DB2 9.1

In the Installation and Deployment Guide, "Installing and Deploying Version on AIX", chapter "Setting Up the PLM Database", add the following remark to the introduction.

When Installing ENOVIA on AIX using a DB2 9.1 client configured with AUTHENTICATION=client you may get the following error:

Starting PLMDBSetup program. Please wait...
Fortran initialization Malloc Buckets: Value specified
for bucket_sizing_factor:n configuration option is
invalid. This value must be a multiple of 16. Using
default value of 64 for bucket sizing factor.

In order to avoid this, we recommend that you to change the DB2 client configuration to AUTHENTICATION=server.