TERMINAL SERVER ARCHITECTURE

In a terminal server architecture, PeriData is installed only on the server. Terminals can start the PeriData app simultaneously. They are using individual options settings linked to the Windows user and stored in the registry of the user = terminal.

PeriData databases (*.PHF) can be accessed by multiple users simultaneously with readonly mode. Full permission (write access) is possible only for one user at a time. Therefore, the optione "ViewingMode" should be set at all terminals that are not receiving new data. The workstation in the perimeter room needs a special solution. It depends on the mode of transmission of the perimeter (file or RS-232 cable)

This description can also be used for CITRIX server

Installation and Configuration on the TERMINAL SERVER

Install PeriData. In the Configuration Assistant, answer the question "Is this a 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
• 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".

Installation and Configuration on a NORMAL CLIENT PC

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

Installation and Configuration on a CLIENT PC that RECEIVES NEW Data

The device, local PC and PeriData in the RDP window have to be configurated. The SENDING METHOD OF THE DEVICE is determing the configuration. There are 3 different cases:

CASE 1: FILE export to the STANDARD exchange directory on the local PC

1A. DEVICE

The perimeter sends data as a FILE. These are the possible situations:

• The device control program is running on the local PC and exports the raw data ALWAYS into the standard exchange directory C:\PeriDataExchange >> no configuration needed
• The device control program is running locally or elsewhere and is CONFIGURABLE >> set the export directory to C:\PeriDataExchange
• The device control program sends the data to ANOTHER folder and is NOT configurable >> install an auxillary program (polling and move app) that moves the raw data from the another directory into the standard import directory on the local PC
• 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 special directory on the server / other PC

Situation: The perimeter sends data as a FILE. The export/target directory of the device is configurable. The standard exchange directory on the local PC is NOT possible or NOT wanted.

2A. SERVER / other PC

• Create the special directory -- IMPORTANT: If serveral perimeter workstations use the same server, each workstation needs a SEPARATE exchange directory 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 (Everyone has full access)
• NOTE: the directory may be also on the device itself, e.g. on the HFA3-PC

2B. DEVICE

• Device 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: CABLE export

Situation: The perimeter is sending data with a cable (RS-232). -- PeriData will be active on TWO locations. On the local PC the RECEIVER AGENT is running and stores the cable data to a temporary file in the standard exchange directory. In the RDP-Window the PERIDATA MAIN APP is running and imports the temporary file into the database.

3A. DEVICE

Follow the description for the specific device type:

• Connect device 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 PeriData of the RDP window

DONE !