Wayne Salter, CERN IT-CO LHC Data Interchange Working Group (LDIWG) Phase 2 Brief Status Report - II

W. SalterLDIWG 2 Status - I uDIP abstract API has been defined uTwo products were selected for evaluation (DIM and SonicMQ) uThe DIP API was implemented for both products (Java/C++, Linux/Windows) uIndependent testing was done on both implementations uBoth products (more or less) passed test cases uDIM selected due to lower cost and simpler maintenance philosophy

W. SalterLDIWG 3 Status - II uDIP is a simple and robust publish/subscribe system which supports an on-change data exchange uDIP supports primitives, arrays of primitives and complex structures of primitives uDIP API provided for C++/Java and Windows/Linux uThe DIP data format includes a timestamp and quality flag uThere is a negotiated contract between the consumer and the provider. Hence, the consumer is expected to know the name of the data item, its meaning and its data type uThere can only be one publisher per item

W. SalterLDIWG 4 Status - III uDIP API (C++/Java, Windows/Linux) in EDMS uDIP tutorial in EDMS uDIP Java documentation in EDMS uDIP C++ documentation in development uDIP Oracle-based repository/Web-based browsing mechanism in development uDIP integration with PVSS, CMW and TCR infrastructure scheduled to be complete in June t_id=457113&version=1

W. SalterLDIWG 5 DIP Integration DIP Product API DIP Product DIP API Domain Code Domain Product API Domain Product DIM DIM API Defined by LDIWG Domain specific e.g. PVSS API e.g. PVSS, CMW

W. SalterLDIWG 6 DIP Problem Statement DIP should be able to exchange relatively small amounts of real-time data between very loosely coupled heterogeneous systems. These systems do not need very low latency. The data is assumed to be mostly summarised data rather than low-level parameters from the individual systems, i.e. cooling plant status rather than the opening level of a particular valve.