This task explains how to distribute the software in compressed form to
another computer. The idea is to perform an installation on a server,
compress the code, send the compressed code to another computer,
decompress it and perform local operations on the computer to be able to
run the decompressed code.
The default installation path can be:
|Note that you cannot first install a GA level in compressed form, then
install a service pack in normal installation mode. In this particular
case, you have two solutions:
|1. Log on as administrator onto the server computer,
install the Version 5 software in the following folder, for example
on 32-bit Windows XP Pro:
|2. Compress the software using a popular compression software product (for example, WinZip), and send it to the client computer on which it is to be used.|
|3. Log on as administrator onto the client computer on which you want to use the software.|
|4. Once you have retrieved the compressed package, extract it to
a folder, for example:
|5. You will need to install the VC8 Runtime prerequisite on each client computer. This has to be installed before running
any Version 5 executable programs on this platform.
To do so, open a Command Prompt window, go to the first CD-ROM folder, then to the folder:
and run the following commands for 32-bit media:
and the following command for 64-bit media:
|6. In a Command Prompt window, go
to the following directory:
then run the following command using exactly the syntax indicated, depending on whether you are running CATIA, ENOVIA DMU Navigator or DELMIA:
where "MyEnvironment" is the name of the environment, and "MyEnvDirectory" the name of the folder containing the environment, if you intend to create an environment on the client as described in step 8.
This activates OLE support which ensures that double-clicking Version 5 document icons on the client will run a Version 5 session.
|7. Run the following command:
to set up the Start->Programs->MyProductLine->Tools menu containing the Batch Management V5R18, Environment Editor V5R18, Nodelock Key Management V5R18, Printers V5R18, Settings Management V5R18 and Software Management V5R18 commands.
|8. Create the runtime environment on the
client, for example using the paths for 32-bit
Windows XP Pro.
To do so, you have two possibilities:
|Instead of creating an environment on the client computer, you can use access the environment on another computer via the network. For more details, refer to step 10b in Accessing the Software From a Thin Client.|
|9. If you require extended font support, run the following
from the directory:
For more information, refer to "Using and Customizing Fonts" in your Infrastructure Users Guide.
|10. If you want to record and replay macros, and Microsoft
Visual Basic for Applications (VBA), Version 6.0 is not already installed
on your client, you have to install VBA manually from the product CD-ROM.
To install VBA6 on all Windows platforms, run the command:
However, note that VBA is supported on Windows XP Professional x64 Edition with Version 5 32-bit code.
|11. If you need access to the communications backbone and
peripheral device broker, the associated port numbers must be set up on the
Used to support process interoperability (for example, between CATIA and DMU), the backbone needs to be set up on each computer running applications which need to communicate.
To set up the ports using the default values, for example for 32-bit Windows XP Pro:
For more information about the communications backbone, refer to Communications Backbone Files.
|12. If you intend to extract offline licenses for use on the client, and
the client happens to be a laptop (as described in
Enabling Concurrent Offline Licensing),
you must install the LUM driver as follows:
|13. If you created a runtime environment on the client, start a
session by double-clicking the environment icon on the desktop or by
selecting the command to start the product from the Start->Programs
Make sure that you have set up your licenses (either network or nodelocked) before starting a session.
|14. If you want to delete the environment created on the client,
run the following commands.
To update the registry (deactivate OLE support):
To delete the reference environment:
To delete the Start menu entries: