Terminal Server Architecture

In a terminal server architecture, PeriData is installed only on the server. Multiple access to the app from different users is possible. Multiple access to the data files is also possible. The permission rights are controlled by the option ViewingMode at the viewing workstations. The workstation in the perimeter room needs a special solution. It depends on the mode of transmission (file or RS-232 cable)

This description can also be used for CITRIX server

TERMINAL SERVER

Install PeriData. Answer the question "Terminal Server with YES. Now the settings are correct

If PeriData was priorily installed, check the settings in the Options (Extra menu)

• Tab General: Viewing Mode = ON (default since V3.7.2.2)
• Tab Perimeter: each USER has his own Perimeter settings = ON. When switched on, a File "PeriWin_Opt_Are_User_Specific.txt" is written into the directory "C:\PeriDataExchange". Now, the setting cannot be reversed. The perimeter settings are now stored separately for each user (=terminal) into the registry "HKEY_CURRENT_USER".

NORMAL CLIENT PC

No configuration needed. PeriData runs in the RDP window in ViewingMode. On the local PC there is NO PeriData.

PERIMETER WORKSTATION
is a PC which are connected to a perimeter. Concerning configuration, there are 3 cases depending on the sending method used by the perimeter (details for each device type)

CASE 1: FILE export to the standard exchange directory on the local pc

Situation: Perimeter sends the data as a FILE

1A. INSTRUMENT

Alternatives:

• The perimeter control program is running on the local PC and exports the raw data ALWAYS to the standard exchange directory "C:\PeriDataExchange" >> no configuration needed
• The perimeter control program is CONFIGURABLE >> set the configuration to "C:\PeriDataExchange"
• The perimeter control program sends the data to ANOTHER folder and is NOT configurable >> an auxillary program (move app) moves the raw data from another directory into the standard import directory
• if the standard directory is not suitable >> see CASE 2 <

1B. LOCAL PC (outside of the RDP window)

• Create the directory "C:\PeriDataExchange" (the PeriData program is NOT installed). If the perimeter control program is not on the same PC, then share the folder.
• Check: (PeriData NOT running) Export/Send data from the perimeter >> new raw data files (extension *.pdi *.oc1 *.dcm - depending on the type) appear in the directory

CASE 2: FILE export to a directory on the server / other PC

Situation:The perimeter uses FILE export. The export/target directory is configurable. The standard exchange directory on the local PC is not possible or not wanted. ted

2A. SERVER / other PC

• Create the special directory -- IMPORTANT: Each perimeter workstation needs a SEPARATE directory on the server to avoid a data mismatch from different devices. The name should define the workstation (user name, location) clearly. Example: ..\Peri_AntwerpZuid_Room3
• Share the folder.
• Check: Perform an export action on the perimeter >> new raw data files (extension *.pdi *.oc1 *.dcm - depending on the type) appear in the directory

2B. INSTRUMENT

• perimeter control program: configurate the export directory (UNC path or drive mapping)
• Check: (PeriData NOT running) Export/Send data from the perimeter >> new raw data files (extension *.pdi *.oc1 *.dcm - depending on the type) appear in the directory

2C. LOCAL PC (outside of the RDP window)

No action required

CASE 3: Data are sent via CABLE

Situation: The perimeter uses cable transmission (RS-232). -- In the "Receiver Mode Solution" PeriData is running in TWO instances. On the terminal PC it is running in the "Receiver Mode" and stores the cable data to a raw data file in the IMPORT directory. On the terminal PC Peridata is running in normal mode and imports the raw data file into the database.

3A. INSTRUMENT

• Connect instrument and PC with the cable
• Setup the export parameters

3D. Alternatives

Other configurations are possible, e.g. with a serial ETHERNET adapter (e.g. MOXA). Please call our technical support, we like to give you advice.

Practical procedure of a data transmission (all cases):

1. RDP window: Start PeriData out of the EMR software >> PeriData is waiting for data

2. Perimeter or perimeter program on the PC, resp.: store a finished examination (triggers automatic data transmission if configurated) - or - open stored examinations and press "Export" or "Send" button >> examinations will appear in the PeriData of the RDP window

DONE !