4.18 Data Networking
TEMS Discovery's architecture allows it to archive data networking; TEMS Discovery peers can share data and participate in distributed data processing.
The Data Networking configuration dialog can be accessed by selecting Data Networking from the Configuration menu on the Main Window.
After the settings on the Data Networking dialog have been made, the private data folder will be visible and can be shared by other TEMS Discovery peers. See
Project List for more information.
Note: TEMS Discovery peers must run in the same local network. In other words, TEMS Discovery cannot connect to TEMS Discovery peers through a router.
Make myself visible to peers. Check this option and provide the requested authentication information to make TEMS Discovery visible to other TEMS Discovery peers running on remote computers.
Machine Information:
• Machine IP. The IP address of the local computer running TEMS Discovery. This IP field will be filled automatically and is not editable.
• Use dedicated TCP port. The TCP port number used for TEMS Discovery communication can be a positive integer from 0 to 32768.
Important: If Windows Firewall is running on the computer that hosts TEMS Discovery, TEMS Discovery needs to be added to Windows Firewall as an exception to open the specific TCP port. Please refer to Windows Help for more information.
Authentication Methods. To verify the identity of users who attempt access, use the settings in this section to authenticate users and thus prevent unauthorized users from establishing a TEMS Discovery TCP connection.
• Anonymous access. Select this option to allow users to establish an anonymous connection. Your server logs on the user with an anonymous or guest account.
• Basic authentication. Select this option to enable the Basic authentication method for TEMS Discovery peers.
Important: Basic authentication results in the transmission of passwords across the network in an unencrypted form. It is possible for a third party equipped with a network monitoring tool to intercept usernames and passwords.
• Integrated Windows authentication. Integrated Windows authentication uses a cryptographic exchange to confirm the identity of the user. TEMS Discovery, serving as a data sharing server, will require that the user be a Windows user of the computer that hosts this instance of TEMS Discovery. (Please see Windows operating system Help for more information on how to add a user to a computer.)
Distributed data processing network. TEMS Discovery can also be configured to be involved or uninvolved in distributed data processing. Select one of the following options:
• Can not be a member. Prevent this computer from being involved in distributed data processing.
• Can be a member all day long. Allow this computer to be involved in distributed data processing at any time.
• Can be a member from x to y. Allow this computer to be involved in distributed data processing for a particular period only.
• Dispatcher. This computer will be involved in distributed data processing. It also serves as the dispatcher responsible for monitoring newly arriving drive test data, and dispatching processing tasks to the members of the distributing network.
Once a computer is assigned as Dispatcher, the members of the distributing network can be built by clicking Members of Distributed Network.
The distributed data processing task is configured in
Automatic Data Processing.
4.18.1 Data Networking Configuration
A typical data networking can be configured as described, and the typical data flow could be as follows:
1. The collected drive test data is uploaded to a data source server via internet.
2. A primary server, configured as the data processing dispatcher, continues to watch the data source. It will immediately dispatch the information to the available processing server, which processes the newly arrived data.
3. The processing server stores the data at a specific data storage location.
4. Reports can be sent by email, or deposited to a specific location via FTP.
5. The processed data can be shared by local TEMS Discovery users, or a TEMS Discovery application hosting the server through a LAN.
6. Remote users can log in to a TEMS Discovery application hosting server and access the processed data and report.
4.18.2 Distributed Processing System
In the following distributed processing system (DPS), PC1 is running TEMS Discovery designated as the dispatcher, PC2 through PC4 are running TEMS Discovery acting as remote processing servers, and PC5 can be a pure data storage server.
Once all servers are set up and PC1~PC4 are running TEMS Discovery Professional as described above, you can:
1. Create two mapped network folders.
These two mapped network folders will be accessible by all PCs with a common drive and folder name (e.g., x:\monitored_folder, y:\private_data_folder). These folders can be physically in one server or in separate servers.
− Shared Source Folder. Drive test data to be processed is placed in this folder. When the ADP task is created in the dispatcher, this folder will be configured to be monitored.
− Shared Private Folder. This folder will hold the processed data. For all PCs, set this folder as a Private Data folder in the
Options dialog (Configuration | Options | Data Storage).
2. Set each of the Processing Servers (PC2~PC4) as
Can be a member (
Data Networking).
4. Add Processing Servers (PC2~PC4) as members of a distributed network to Dispatcher PC1 (
Data Networking).
5. Create an ADP task in Dispatcher PC1 to monitor the Shared Source folder.
6. Start the ADP task from Dispatcher PC1.
This distributed processing system (DPS) will act once new log files arrive in the Shared Source Folder.
4.18.3 Use Private Data Folder as Public Data Folder
TEMS Discovery Enterprise File Mode configuration doesn’t allow remote users to access server data directly, given that it is not stored in SQL database. Remote local TDP users may tap into TDE FM Public Data Folder to manually download relevant project data, however that requires that TDE data is previously copied from Private Data Folder to Public Data Folder. Alternatively, TDE Private Data Folder may be designated as Public Data Folder to allow direct access by remote users, by enabling ‘Use Private Data Folder as Public Data Folder’ option available under Measurement Data Storage configuration. The main benefits of this approach are direct access to Enterprise server data (no need to setup manual or scheduled transfers of data from TDE Private Data Folder to Public Data Folder), no need to invest into additional Public Data Folder storage and no need for periodical Public Data Folder clean ups.
Download option will be enabled on remote side only if all data import for selected hierarchical level (project, dataset, log file) is completed.
Download initiated on any given hierarchy level will trigger data transfer attempt for drive test log files of selected hierarchy level, Scenario and UDR files of the parent DT project and all of the GeoArea files. Download transfer attempt will be executed if selected item is absent from remote client side or selected item Windows date/timestamp on the source side is newer than the one on the remote client side.
4.18.4 Automated TDE FM Data Download by TDP User
TEMS Discovery Enterprise File Mode configuration doesn’t allow remote users to access server data directly, given that it is not stored in SQL database. The option allows TDP users to setup subscription for TDE FM server data via user-configured project/dataset name filter.
Active subscription service will periodically query mapped TDE FM Private Data Folder (PrDF) and automatically download filtered data and it requires that
Use Private Data Folder as Public Data Folder option is activated on TDE FM server side.
‘TDE File Mode Data Filter’ configuration uses inclusion and exclusion key words to select projects/datasets for automated download. The configuration is fully integrated into 'Configuration Management' option for easy configuration sharing.
Automated download is executed for filtered items missing at local user side, or with newer date/timestamp. Project level automated download includes all underlying dataset data. Automated downloads include Scenario and UDR files of the parent project and all of the associated GeoArea files.
