This page describes the general information about procedures and known issues for installing and licensing the following products:
Use the following links to consult the official installation documentation:
Installing the Code on Windows
Installing the Online Documentation
General Procedure for Windows |
|
General Procedure for Unix | ||
|
WebSphere MQ, a corequisite for running the batch monitor, is not supported on Windows XP Professional x64 Edition.
A problem of incompatibility between 32-bit and 64-bit registration is the cause of the problem when a V5R17 GA 64-bit product line has been installed after a V5R15 GA 32-bit product line with two different administrator users.
This may lead to this type of message during an installation or
un-installation:
To repair this registry key, perform the following steps:
HKEY_CLASSES_ROOT\Wow6432Node\.CATPart\CATIA.Part\ShellNew
Unable to display the
current owner
is displayed. In this case, check the Replace
owner on sub- containers and objects
option, then click Apply
then OK. The following dialog box will be displayed: DS\ogg
is the administrator user which performed the 32-bit
installation.Unload_directory/intel_a/code/bin/V5Regserver -unset
In the CATIA Installation and Administration Guide, section "Distributing Version 5 on Windows", the scenario "Accessing the Software From a Thin Client" explains that you can:
Note that, in either case, you will not be able to run the Batch Management utility or the Settings Management utility.
If the installation stops during the unloading of the Manufacturing cabinet file and the following dialog box is displayed:
with the following message in the cxinst.log file:
Unload Manufacturing - CDROM 1
File UnloadDir\intel_a\control\Manufacturing.toc was not found
the problem may be due to the McAfee Anti-virus product.
The bypass is to open the McAfee VirusScan Console window and select
"Access Protection" in the Task list. Then, use the right mouse button or
Alt+Enter to display the "Access Protection Properties" window. Select the
tab "File, Share and Folder Protection" and uncheck the option:
Prevent access to suspicious startup items(.exe) **\startup\**\*.exe
Due to business process requirements and additional validation testing it is necessary to restate previously incorrect manufacturing product prerequisites.
When installing some CATIA configurations, if an error occurs related to the execution of the CORBAServerInfra_post module, please, ignore it. It will have no consequence on the usage of the installed solutions and products.
In the Version 5 Installation and Deployment Guide, section Deploying Instant Collaboration in IBM WebSphere Application Server, section Phase 1, the paragraph "V5 Collaboration Client" now reads:
Install the V5 runtime view of the VDM code on the V5 collaboration client:
Media: ENOVIA V5 VPM
Configuration: VDM containing VPM Navigator.
Note that you also have to install from the ENOVIA_DMU_Navigator media a configuration containing the DMU Navigator (for example, DM2). If no DMU license is present, you will not have access to certain functions.
In the following tables:
Yes | The command is available |
No | The command is not available or grayed out |
NA | Not applicable |
FUNCTIONS | CONFIGURATIONS --> | VDM | VDM + DM2 |
Peer-to-Peer mode | |||
INSTANT COLLABORATION TOOLBAR | |||
3D Conferencing icon | Yes | Yes | |
3D Conferencing window | |||
|
|
Yes | Yes |
|
Yes | Yes | |
|
No | Yes | |
|
No | Yes | |
|
|
No | Yes |
|
No | Yes |
FUNCTIONS | CONFIGURATIONS --> | VDM | VDM + DM2 |
Client/Server mode | |||
INSTANT COLLABORATION TOOLBAR | |||
Connectivity icon | Yes | Yes | |
Connectivity Toolbar | |||
|
Yes | Yes | |
|
|||
|
Yes | Yes | |
|
Yes | Yes | |
|
No | Yes | |
|
No | Yes | |
|
No | Yes | |
|
Yes | Yes | |
Instant Messaging icon | Yes | Yes | |
INSTANT MESSAGING TOOLBAR | |||
Create an Audio Meeting | Yes | Yes | |
|
No | Yes | |
|
Yes | Yes | |
|
Yes | Yes | |
|
Yes | Yes | |
3D Conferencing icon | No | Yes | |
3D Conferencing window | |||
|
No | Yes | |
|
No | Yes | |
|
No | Yes | |
|
No | Yes | |
|
No | Yes | |
|
No | Yes | |
Meeting Toolbar | Yes | Yes | |
|
No | Yes | |
|
Yes | Yes | |
|
Yes | Yes | |
|
Yes | Yes | |
|
Yes | Yes | |
|
Yes | Yes | |
|
No | Yes |
The sharing program may not work on the publisher side and the whiteboard may not be displayed on the listener side:
The same behavior has been found using the Microsoft Communicator client: it is not possible on the listener side to close the sharing window. If the listener kills the display sharing process using the Task Manager, the sharing window is no longer usable.
If you are using CATIA VPM Navigator in Single Sign-On mode on 32-bit Windows, you need to install the following packages on each client:
If a forward proxy is used along with HTTP Tunneling mode for ENOVIA V5 VPM client, and if Microsoft Internet Explorer is setup so as to use a proxy server through its "Use a proxy server for you LAN" option located in its 'Tools / Internet Options / Connections / LAN Settings' dialog, then the "Bypass proxy server for local addresses" option must be checked in the same dialog.
If Microsoft Internet Explorer is setup so as to use a proxy server through its "Use a proxy server for you LAN" option located in its 'Tools / Internet Options / Connections / LAN Settings' dialog, and the "Bypass proxy server for local addresses" option in the same dialog is not checked, then ENOVIA V5 VPM client will fail to connect to ENOVIA Server in HTTP Tunneling mode.
In the Single Sign-On Administration Console, the dialogs for updating or exporting credentials operation use a table view to display the user for which the operation is wanted. The maximum number of lines displayed in this table view can be changed using the following manipulations:
<os>/resources/dialog/updateCredentials.XMLDlg
using a text editor or an XML editor.<Table Name="Table1" onRowSelect="initApplicationComboBox"
Attribute="_UserList"/>
<Table Name="Table1" onRowSelect="initApplicationComboBox"
Attribute="_UserList" Height="100"/>
<Table Name="Table1" onRowSelect="initApplicationComboBox"
Attribute="_UserList" Height="50"/>
<os>/resources/dialog/ExportCredentials.XMLDlg
using a text editor or an XML editor.<Table Name="Table1" Attribute="_list"/>
<Table Name="Table1" Attribute="_list" Height="100"/>
<Table Name="Table1" Attribute="_list" Height="50"/>
If Single Sign-On mode for ENOVIA VPM Lifecycle Navigator Web is to be activated, it must be noted that ENOVIA V5 VPM Server will have to connect to the Single Sign-On Server which is embedded in the same Web application as ENOVIA VPM Lifecycle Navigator Web. In some situations, the web application is deployed on an IBM WebSphere Application Server, but used through some possibility authenticated reverse proxies. In such cases, the connection from the ENOVIA V5 VPM Server to ENOVIA VPM Lifecycle Navigator Web server must be setup so that it directly refers to the IBM WebSphere Application Server port and machine: the Single Sign-On mode will fail if ENOVIA V5 VPM Server is setup so as to connect to the Single Sign-On server through an authenticated reverse proxy.
In practice, this setup can be achieved by assigning proper host and port values to the CATJWSServiceDirectory and to the CATLoginServletHost environment variables; as described in "Activating SSO on the ENOVIA Server" subsection of the "Activating Single Sign-On" section of the Installation guide.
However, depending on the way ENOVIA VPM Lifecycle Navigator Web was first used, i.e., if it was used through the reverse proxy, the URL used by the ENOVIA V5 VPM Server to connect to the Single Sign-On server can incorrectly be switched to the reverse proxy.
If such behavior is observed, then the following
environment variables can be set at same place as
CATJWSServiceDirectory and to the CATLoginServletHost
environment variables; with the following values:
export CATJWSEPNormalizeFrom=http://www.galaxy.com:8080/mycompany
CATJWSEPNormalizeTo: this variable must be set to the
URL prefix (<protocol>://<host>:<port>/<rootURI>) of the ENOVIA VPM
Lifecycle Navigator Web application deployed on IBM WebSphere
Application Server : it will be used as the replacement text for the
prefixes of the URL that ENOVIA V5 VPM Server uses to connect to
the Single Sign-On Server. For example, on UNIX, the following line may
be added in runServerManager script:
export CATJWSEPNormalizeTo=http://internalvpm:9080/ENOVIAWEB
In "Common Installation and Administration Tools", "Miscellaneous
Installation Tasks on Windows -"Uninstalling Version 5", the following has
been added:
"Dassault Systemes Software Prerequisites x86 can be removed only once you
have uninstalled all
Dassault Systemes software."
In the Installation and Deployment Guide, section "Importing and Exporting Setting Files to/from XML Format", the introduction now reads:
This section explains how to import and export setting files to and from XML format.
Certain attributes in certain settings files, when exported to XML
format, cannot be converted to text. The following is a non-exhaustive list
identifying a certain number of settings file involved:
Exporting these settings files to XML format renders them unusable.
DSLS (Dassault Systemes License Server) is introduced in V5R21 as the licensing middleware for V5 products.
DSLS introduction has no impact on V5 business model and licensing model, which is still Concurrent User licensing.
DSLS supports nodelock licenses and licenses enrolled on a server.
DSLS can be configured as a standalone license server or a failover cluster composed of three license servers (similar to LUM HAL).
DSLS supports concurrent offline licensing. Extracting a license from a standalone or a failover server to a laptop is supported.
DSLS follows standard communication protocols (https). This allows an easy integration in Customer network architecture.
DSLS can be installed on Windows, Linux, AIX and Solaris Sparc.
DSLS administration tool provides both graphical and command-line interfaces.
All DSLS features are fully described in DSLS documentation. Please refer to it for obtaining all necessary details related to installation and administration of DSLS.
DSLS is already used by Dassault Systemes V6 products.
The same DSLS process can host V5 and V6 license keys and can grant simultaneously such licenses to V5 and V6 processes.
Minimum DSLS version able to serve V5R21 products is DSLS V6R2012 (6.211.0 - March 21, 2011).
By default, the license server list that can be accessed by the licensing clients is declared in the following file, on the client computers:
C:\Documents and Settings\All Users\Application Data\DassaultSystemes\Licenses\DSLicSrv.txt
C:\ProgramData\DassaultSystemes\Licenses\DSLicSrv.txt
/var/DassaultSystemes/Licenses/DSLicSrv.txt
Example of such a configuration file contents:
|
In this example, three logical license servers are declared, all listening on the default 4085 port.
The first logical server is a standalone server named serverA.
The second logical server is a failover cluster composed of serverB, serverC and serverD.
The third logical server is a standalone server named serverE.
Nodelock licenses are delivered as .LIC files. You can use DSLicMgt (DSLS Nodelock Key Manager) to import nodelock licenses.
Nodelock licenses (and extracted offline licenses on Windows) are stored in the following directory:
C:\Documents and Settings\All Users\Application Data\DassaultSystemes\Licenses
C:\ProgramData\DassaultSystemes\Licenses
/var/DassaultSystemes/Licenses
DSLS ComputerID is composed of 3 alphabetic characters + a dash + 16 hexadecimal characters.
Example: CPE-0370E01819E46601
This ComputerID is required when asking for DSLS license keys.
The ComputerID of a failover cluster corresponds to the three ComputerID of the three machines. Consequently, when requesting license keys for a failover cluster, you have to provide 3 individual ComputerID.
The ComputerID can be obtained either:
DSLicTarget -t
DSLicTarget (version 1.2)
WWN-42721022FAFE292A (based on network adapter: Intel(R) 82566MM Gigabit Network Connection )
DSLicMgtB -id
WWN-42721022FAFE292A
DSLS becomes a V5R21 prerequisite for all new customers.
For customers already working with previous V5 versions, IBM LUM 4 license
server
will be able to serve V5R21 processes but will be out of support on December 31,
2013.
Customer is then allowed to choose either to use LUM server and then switch
to DSLS server, or to immediately switch to DSLS server while deploying
V5R21 (recommended).
Administrator has to set the following environnement variable on client
computers in order to
activate old LUM licensing mode:
DSLICENSING=LEGACY
This mode will be removed in next V5 release.
DSLS license keys are not compatible with IBM LUM license keys: new licenses should be
obtained in order to run V5R21 with DSLS.
When requesting new license keys or renewing previous licenses, customers will have to indicate if DSLS OR LUM
license keys have to be generated.
The total number of keys (DSLS+LUM) cannot be greater than the entitled key number.
This new prerequisite applies to all V5R21 products from:
When the licensing client (for example CATIA) is on Windows, it uses by default the standard Microsoft https client communication layer. However this piece of software can be chatty.
Therefore, if needed to limit the number of exchanges between licensing client and license server, the following environment variable can be set in the licensing client environment:
DSY_DISABLE_WININET=TRUE
However a drawback exists when this variable is set: forward proxies are not taken into account.
Before uninstalling a DS License Server version on Windows OS, be sure to close:
Once enrolled in the DS License Server, the license keys and related usage data are saved in following folders, depending on operating systems, typically:
This folder and the files included in it must not be changed nor even moved, renamed nor access rights modified, when the DS License Server is not running.
Certain backup software products perform such forbidden changes. Configure your backup software to not backup this folder. If you wish to backup your license keys, you can either save the license keys you received (typically in one .LICZ file), or you can use the License > Save command in the License Administration tool.
If this rule is not followed, the need for refreshed license keys (typically
one .LICZ file) and for enrolling them will be mandatory.
The best way to avoid this inconvenience is to stop the DS License Server only during the few minutes necessary to upgrade it.
V5R21 is the last version for which LUM is supported. LUM support is dropped for next V5 release.
The latest certified LUM server level is LUM 4.6.8 Fix Pack 13. Lower versions are not supported.
This level can be obtained from DS Support web site at http://www.3ds.com/support/resource-library
Note that LUM 4.6.8 Fix Pack 14 is in regression compared to Fix Pack 13 and therefore is not supported.
Information about LUM can be obtained on the IBM web site at http://www.ibm.com/software/awdtools/lum/support.html
On Windows computers having more than one network card, it may happen that the Target ID used by different user accounts be not the same.
The problem can be fixed by setting "Full Control" permission for the registry key [HKEY_LOCAL_MACHINE\SOFTWARE\IBM\License Use Runtime]. This permission can be set for individual users or groups, or for Everyone:
Run Regedit
, Go to HKEY_LOCAL_MACHINE\SOFTWARE\IBM\License Use Runtime,
Right click on it, Select Permissions, Select the appropriate user and/or
group, and allow Full Control. Or add Everyone group and allow Full Control.
If an abnormal end occurs when running the i4_offline_mig
command, you must restart and then stop again the LUM license server.
For ENOVIA DMU only:
The licenses generated by IBM before December 2003 for the
ENOVIA DMU configurations based on DM1, DM2, DPS and PS1 possess an
obsolete format which does not work for concurrent offline licensing.
i4_offline_mig
4.6.8.13 allows these licenses to work.
You can find i4_offline_mig
4.6.8.13 in the following IBM site:
http://www-306.ibm.com/software/applications/plm/support/prodannounce.html,
or directly at the following URL:
ftp://public.dhe.ibm.com/software/applications/plm/support/lum/LUM46813-offline_mig.zip.