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
You can ignore the problem with the following file if it presents errors during an integrity check under UNIX: CAAPSNInteroperability.edu
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
The licensing system of the above V5 products is IBM License Use Management. More information on LUM can be obtained on the IBM web site at http://www.ibm.com/software/lum.
LUM does not need to be configured if your license is node locked.
For ENOVIA 3d com only:
when accessing CATIA data, ENOVIA 3d com uses by default a CATIA V5 server, one license is required for each user.
To use concurrent licenses, you need to install and configure a LUM server and configure LUM clients.
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.
IBM License Use Management may be obtained at no charge from:
http://www.ibm.com/software/awdtools/lum/support.html
The LUM license certificate has the following format:
|
The certificate should be saved in a temporary file with the ".LIC" extension, with the first line being "[LicenseCertificate]".
This is the certificate that the installation procedure prompts you to import. Do not import nodelock certificates using LUM utilities.
If needed, to import a certificate once the installation has been performed, instead of importing it during the installation, run "CATNodelockMgt.exe" for Windows or "CATNodelockMgt" for UNIX. This command is located in the code/bin directory. For Windows, you can access this tool from Start/Programs/Catia/Tools menu and by running the Nodelock Key Management tool.
See the ReadMe.txt file located on the CDROM for information on how to get the Windows target id.
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:
Furthermore, 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 at the following URL:
http://www.ibm.com/support/docview.wss?rs=886&context=SW860&uid=swg21204240
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.