This task explains how to set up thin clients for accessing the Version
5 software over the network.
A thin client can run Windows XP.
This type of scenario is sometimes referred to as a "code server" scenario. The advantages of this type of scenario are:
The drawbacks with this type of scenario are:
Note that the default installation path can be:
|1. Log on as administrator onto the server computer,
install the Version 5 software, for example, in the following folder,
for example on 32-bit Windows XP Pro:
then share the disk and folders in the installation path.
|2. Log on as administrator onto the client computer.|
|3. Run the Windows Explorer.
You need to use the Explorer to connect to the server over the network
and access the
|4. Select Tools->Map Network Drive...
The Map Network Drive dialog box is displayed, and looks something like this:
|5. Select a drive.|
|6. Select the folder Program Files on the
server, and click Finish.
This is the folder containing the
Note that selecting the folder displays the server name and folder name in the Path field:
|In the All Folders list in the left window of the Explorer,
you will now see the connection to the server, for example:
where "server" is the server name, for example, and "F:" is the name of the drive you mapped.
|7. Still on the client computer, open a Command
Prompt window and go to the following directory:
where, for example, "F:" is the name of the mapped drive and represents
|8. Open a Command Prompt window
to go back to the directory where you were before,
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 an existing folder containing the environment on the client, if you intend to create an environment on the client as described in step 10a.
If you intend to use the environment on the server (step 10b), run the command:
This activates OLE support which ensures that double-clicking Version 5 document icons on the client will run a Version 5 session.
|9. Run the following command, depending on whether
you are running CATIA, ENOVIA DMU Navigator or DELMIA:
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.
|At this point, you have two possibilities:|
|10a. Create the runtime environment on the
To do so, you have two possibilities:
|10b. You can also access the server
environment via the network. To be able to do so, the code and the runtime
environment on the server must be installed in a shared location so you can
map it from the client.
For illustration purposes, let's suppose you installed the code for example on 32-bit Windows XP Pro in:
To facilitate access to the runtime environment over the network, the environment must be located in a shared easily accessible location, and NOT in the default location in the All Users profile on the server which is:
For illustration purposes, let's suppose you created the runtime environment on the server in the following shared location:
To access the environment over the network:
where "MyEnvironment" is an example for the name of the runtime environment on the server.
Note that this scenario will only work if the drive letter on the client and the drive letter on the server are identical. In certain cases, you may not be able to use the same drive letter on the client and the server. For example, the code is installed on "E:" on the server, but the drive "E:" on the client is not free, so you map the drive "K:". If you then try to start a session, the runtime environment will not be found because the paths referenced in the runtime environment point, for example, to "E:..." like this (32-bit code on Windows XP):
whereas on the client there is no software installed on the "E:" drive.
To bypass this problem, create a new global environment on the server using the following command:
where "\\servername\home" is the UNC name of the server and shared folder, and "NewEnvironment" is the new environment name. Creating a new environment this way will create the correct UNC paths as follows (32-bit code on Windows XP):
This time, your attempt to start a session will be successful if you use the following command:
Note also that if you disconnect the drive you mapped, you will have to remap it as before for the scenario to continue to work.
|11. 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.
|12. 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 Microsoft Windows installer if it is not installed on the workstation:
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.
|13. 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:
|14. 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 more information about the communications backbone, refer to Communications Backbone Files.
|15. 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.
|16. If you created an environment on the client, and want to
delete this environment, run the following commands:
To update the
registry (deactivate OLE support):
To delete the reference environment:
To delete the Start menu entries: