|
![]() |
![]() |
![]() |
![]() |
![]() |
|
ATRAK-Xrecorder Detailed
Main Functionality ATRAK-Xrecorder - Software The ATRAK-RECORD/REPLAY software resides on each Controller Working Position (CWS) which will record the X events of that particular display. The contents of the recorded data will be captured and then archived to a central repository server.
ATRAK-Xrecorder - Private network ICC recommends that where a large number of CWS are to be recorded each CWS should be upgraded with an additional suitable network adapter and switches to form a private switched network for transmission of recorded data to the central archiving server. The introduction of a private network will ensure that there is no burden put upon the live operations network. ATRAK-Xrecorder - X Archiver server The replay of any CWS should ideally not take place on the original CWS or any operational CWS positions. Therefore, it is recommended that all recorded date is stored in a central repository that will have individual directories for each CWS position recorded for each day. This process is known as ATRAK - X Archiver and is a modular system that is divided into three components: - ATRAK Record/Replay client The ATRAK record/replay client (RPC) is responsible for basic recording andreplay of X Protocol. On recording, the client converts X protocol to a data stream fit for archival. This data stream is sent over the private network to a central archival server. ATRAK X Archiver The ATRAK - X Archiver module is responsible for archiving, organising, time-stamping, and retrieval of X Protocol data recorded by RPC . ATRAK User console The ATRAK user console is a GUI based interface tool to control ATRAK record/replay clients and archive server activity. It graphically represents ATRAK record/replay clients archive servers, and archive data so that the user can manipulate them. From the ATRAK user console, users can start and stop recordings and replays and control other aspects of client and server behaviour. Replay of recorded data On replay, the ATRAK RPC receives a data stream from the archival server and converts it back to X Protocol. Commands and recording stream data are communicated via TCP/IP sockets. Since these components communicate with each other via TCP/IP, they can be located anywhere on a local area network. In the ATC environment it is not recommended that the ATRAK user console be run on the same machine as an ATRAK RPC. If the replay of recorded data takes place on a CWS outside of operations it will be necessary to configure a dedicated replay CWS for each application recorded. The ATRAK - X Archiver and ATRAK user console provide replaying of time stamped recordings, selective replay speed and offer various replay controls. Through the ATRAK user console GUI interface access is given to the replay CWS. This should accurately match the originating operation CWS for accurate replay i.e. replicated workstation, monitor, and graphics card. Central Repository Where the number of CWS 's is substantial ICC recommends a central repository for recorded data. This centralised storage is based on proven RAID technology with sufficient capacity to meet the recommended number of days of operational data. The online storage facility is configured to provide sufficient capacity for optimum performance and potential growth, and ensure suitable manageability to backup an agreed minimum of days of off line storage for all ATRAK CWS positions. This centralised repository can then be accessed by any replay workstation for any CWS position It is recommended that an agreed minimum number of days of recorded operationaldata is to be stored off line. In order to facilitate this requirement, ICC recommends the implementation of a suitable tape library to transfer “online” data from the centralised raid array to an “off-line” media. The recorded data will be compressed prior to any archiving to tape by the Record process.
|
| © 2008 Ifield Computer Consultancy Limited |