Distributing the Software in Compressed Form

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:

C:\Program Files\Dassault Systemes\B18 (Windows XP Pro)
C:\Program Files\Dassault Systemes\B18 (64-bit code on Windows XP Professional x64 Edition)
C:\Program Files (x86)\Dassault Systemes\B18 (32-bit code on Windows XP Professional x64 Edition)
  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:
  • reinstall everything in compressed form
  • or use the CATDeltaInstall utility.
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:

C:\Program Files\Dassault Systemes\B18
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:

E:\Program Files\Dassault Systemes\B18
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:

INTEL (32-bit media)
WIN64 (64-bit media)

and run the following commands for 32-bit media:

msiexec /i InstallDSSoftwarePrerequisites_x86.msi /q (for 32-bit Windows)
msiexec /i InstallDSSoftwarePrerequisites_x86_x64.msi /q (for 64-bit Windows)

and the following command for 64-bit media:

msiexec /i InstallDSSoftwarePrerequisites_x86_x64.msi /q for 64-bit Windows)

6. In a Command Prompt window, go to the following directory:

E:\Program Files\Dassault Systemes\B18\intel_a\code\bin (Windows XP Pro)
E:\Program Files\Dassault Systemes\B18\win_b64\code\bin (64-bit code on Windows XP Professional x64 Edition)
E:\Program Files (x86)\Dassault Systemes\B18\intel_a\code\bin (32-bit code on Windows XP Professional x64 Edition)

then run the following command using exactly the syntax indicated, depending on whether you are running CATIA, ENOVIA DMU Navigator or DELMIA:

cnext /regserver -env MyEnvironment -direnv MyEnvDirectory
dmu /regserver -env MyEnvironment -direnv MyEnvDirectory
delmia /regserver -env MyEnvironment -direnv MyEnvDirectory

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:

setcatenv -tools -cs MyProductLine

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:

  • from the directory E:\Program Files\Dassault Systemes\B18\intel_a\code\bin, run the following command:

setcatenv -p "E:\Program Files\Dassault Systemes\B18" -e MyEnvironment -d MyEnvDirectory -a global -desktop yes -cs MyProductLine

where "MyEnvironment" is the name of the environment, "MyEnvDirectory" is the name of the folder containing the environment and "MyProductLine" is the name of the product line.

  • or, use the Start->Programs->MyProductLine->Tools->Environment Editor V5R18 command. In this case:
  1. Select the Environment->New command to display the New Environment dialog box.
  2. Select the Options menu, then the Set Global Storage Directory command, and set the environment storage directory to the same location you set in step 7.
  3. Enter the same environment name you also set in step 7.
  4. Enter the path of the shared installation folder on the server as follows:
    E:\Program Files\Dassault Systemes\B18
  5. Select Global for the Mode.
  6. Select your Product Line.
  7. Click OK.

In both cases, a global environment is created on the client computer which can be used by all users who log onto the client.
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 command:

VE0IFONT.exe -env MyEnvironment -direnv MyEnvDirectory

from the directory:

E:\Program Files\Dassault Systemes\B18\intel_a\code\bin (Windows XP Pro)
E:\Program Files\Dassault Systemes\B18\win_b64\code\bin (64-bit code on Windows XP Professional x64 Edition)
E:\Program Files (x86)\Dassault Systemes\B18\intel_a\code\bin (32-bit code on Windows XP Professional x64 Edition)

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:

msiexec /q /i pathcdrom\VBA\VBA6.msi

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 client.

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:

  1. Log on as administrator.
  2. Open a Command Prompt window and go to the installation directory, for example:

    E:\Program Files\Dassault Systemes\B18\intel_a\code\bin
  3. Enter the command:

    setV5Ports

    \\Server\\Program Files\Dassault Systemes\B18\intel_a\code\bin\BBDemonService -create

where "server" is the name of the server machine. The UNC path must be used imperatively.

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:
  1. Open a Command Prompt window.
  2. Go to the following directory, for example for 32-bit Windows XP Pro:

    E:\Program Files\Dassault Systemes\B18\intel_a\reffiles

  3. Enter the command:
    lumdevdi.exe
    You must run this command only from the specified directory because it contains the file LUMDriver.sys required for the command to work.
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 menu.

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):

CNEXT /unregserver -direnv MyEnvDirectory -env MyEnvironment
DMU /unregserver -direnv MyEnvDirectory -env MyEnvironment
DELMIA /unregserver -direnv MyEnvDirectory -env MyEnvironment

To delete the reference environment:
delcatenv -d MyEnvDirectory -e MyEnv -a global -desktop yes -cs MyProductLine

To delete the Start menu entries:
delcatenv -tools -cs  MyProductLine