Multiple VMEs are introduced to spread resource utilization across separate systems. The database is shared, not separate. Each VME on the network uses the FSI data served up by the main server, the MDS Server. Processing done on that data occurs by transferring FSI data across the network to workspace in each separate VME, so the secondary machine’s CPU and memory resources are the one’s that control the performance.
On D3 Windows, each virtual machine (VME) must be on it’s own hardware system. There can be only one instance of the D3 executable, d3vme.exe, running on the system. Each VME shares the FSI data from the main server, the MDS Server. The licensing is stored in the FSI, so the only system that needs activation is the MDS server. User licenses are then shared among the VMEs. Each additional server requires an additional D3 server license.
The Main server is installed first, or in most cases, has already been installed and is a functioning D3 Windows system. It is defined as the one and only MDS server on the network. It uses the system ID to activate the total number of client licenses that were purchased.
To add a second VME, install D3 Windows on a second system as a server installation, and choose the Custom installation method. Deselect the ODBC Server option. Enter the name of the Main server where the FSI is located in the text box that prompts for MDS Server Name, and then continue with the installation.
The second VME should be at the same release and service pack level as the main server. Install the base release on the second system, then run the appropriate service pack upgrade. Run nt_upgrade on the second VME. Although the FSI is redundantly upgraded as well, this will not hurt the database. If you are prompted to activate the system you can continue. Click OK, then cancel out of the activation. It is not necessary to activate secondary VMEs.
Tape drive resources cannot be shared between the different VMEs. Each VME is limited to using the tape drives that are physically attached to the system that the VME is installed on.
Serial terminals are specific to each VME. If the secondary system has a serial controller and dumb terminals, those terminals only log in to the VME on the system where the serial controller is installed.
Printer resources are available the same way they are on the Main server. If the second system has printer resources available to Windows, they are accessible to the VME. Use the appropriate dev-make commands to configure the printers.
Printers can be shared among multiple VMEs. First, configure the printer in the VME on the system where the resource is available. Typically, this will be an existing printer already set up on a functioning system. Then, from the second VME, use the PickRemote device type in the dev-make command to access the first VMEs printer resource:
Syntax
dev-make -t PickRemote -n -a ",,"
where:
pib number of the source machine
remote VME computer name
pib# of the master process on the remote machine
connect timeout in milliseconds
Example
On Machine 1:
dev-make -t NTPrinter -n 5 -a " a valid printer name " startptr 1,1,1,s5 (s
On Machine 2:
dev-make -t PickRemote -n 3 -a "machine1,5,1000" startptr 0,0,1,s3 (s sp-assign f0 list md (p
The listing is sent to the " a valid printer name " printer that is installed on machine 1.