14
CMW status 6 Feb. 2002 CMW status February 2002 Kris Kostro

CMW status 6 Feb. 2002 CMW status February 2002 Kris Kostro

Embed Size (px)

DESCRIPTION

CMW status 6 Feb CMW models and services Device/property model allows get/set/subscribe on properties of named devices. Data is transported as language-independent data objects. The core of implementation is RDA, it is Object-Oriented and is using CORBA. It is the mainstream of CMW. All CERN accelerator devices can be accessed today this way. Topic model is essentially based on JMS with some CMW- developed wrappers. A commercial product (SonicMQ) is assuring this functionality. It is currently little used. As it is standard, commercial product ideal for loosely-coupled systems, we want to promote use of it. Services provided by CMW include Device Naming Service, Database Service, CMW Device Explorer and administration facilities.

Citation preview

Page 1: CMW status 6 Feb. 2002 CMW status February 2002 Kris Kostro

CMW status 6 Feb. 2002

CMW statusFebruary 2002

Kris Kostro

Page 2: CMW status 6 Feb. 2002 CMW status February 2002 Kris Kostro

CMW status 6 Feb. 2002

OutlineCMW components (1 slide)Status of components and services (4 slides)Relations with supported clients (5 slides)

Page 3: CMW status 6 Feb. 2002 CMW status February 2002 Kris Kostro

CMW status 6 Feb. 2002

CMW models and servicesDevice/property model allows get/set/subscribe on properties of named devices. Data is transported as language-independent data objects. The core of implementation is RDA, it is Object-Oriented and is using CORBA. It is the mainstream of CMW. All CERN accelerator devices can be accessed today this way.Topic model is essentially based on JMS with some CMW-developed wrappers. A commercial product (SonicMQ) is assuring this functionality. It is currently little used. As it is standard, commercial product ideal for loosely-coupled systems, we want to promote use of it.Services provided by CMW include Device Naming Service, Database Service, CMW Device Explorer and administration facilities.

Page 4: CMW status 6 Feb. 2002 CMW status February 2002 Kris Kostro

CMW status 6 Feb. 2002

Device/Property modelRDA

Stable since Oct. 2001. New release with cleanups (February)Scheduled development – Asynchronous support in server, access control (Spring 2002)

Device APICurrent version as of Oct. 2001. Improved (final) version being prepared (February)

Server FrameworkNew Framework since OctoberStable. No major changes planned

Page 5: CMW status 6 Feb. 2002 CMW status February 2002 Kris Kostro

CMW status 6 Feb. 2002

CMW – made serversPS Server

Stable – will be deployed on start – upPlanned improvements concern server generation

SL-Equip serverRecently ported to the new frameworkFull SL-Equip functionality supportedSL-Equip devices are being defined in DB (April)Can run as GW on Linux or native on LynxOS 3.1To be stress-tested and used for Passerelle (April)

OPC serverOriginal version as of April 2001Has to be ported to the new server framework (Summer 2002)

Page 6: CMW status 6 Feb. 2002 CMW status February 2002 Kris Kostro

CMW status 6 Feb. 2002

Topic model, ServicesJMS SonicMQ

StableExplore & promote use

Naming servicesStable

Database ServicesNew DB for OPC and SL-Equip definitions (April)

Explorer and administration servicesNew version for May 2002

Page 7: CMW status 6 Feb. 2002 CMW status February 2002 Kris Kostro

CMW status 6 Feb. 2002

OtherDocumentation

Full programming documentation available as JavaDoc and Doxygen for C++Software User Manual available (~50 pages) but not completed yet

Deployment & versioningManaged by RazorRelease management not existing

LynxOS3.1 in SLBeing introduced slowly

Page 8: CMW status 6 Feb. 2002 CMW status February 2002 Kris Kostro

CMW status 6 Feb. 2002

Supported clientsPS application section (Michel Arruat)

At the level of Device API. Existing base of Java applications

LHC Power ConvertersCMW evaluationSpecial version to test thread-pool for asynch requestsHad to go through Server Framework changeWas suffering from non-existing release managementCMW will provide asynchronous get/set support in serverCMW is well-adapted to the problem, provides suitable architecture

Page 9: CMW status 6 Feb. 2002 CMW status February 2002 Kris Kostro

CMW status 6 Feb. 2002

Supported clients (cont.)RF (Luca Arnaudon & Olivier Brunner)

Got application for Kfocus using OPC server running in 2 weeks without previous Java knowledgePrepared to use CMW for a setup with Compact PCI and Acquiris card + OPC server + VME to control timinguse Java Dataviewer to display mountain range

SPS Passerelle project (Excel access)Dormant since the first version has been demonstratedHas to implement subscription. Can profit from new SL-Equip server.

Page 10: CMW status 6 Feb. 2002 CMW status February 2002 Kris Kostro

CMW status 6 Feb. 2002

Supported clients (cont.)BI (BISCOTO)

Technical discussion with JJ End of JanuaryDiscussed all detailsNo technical problems – waiting for JJ to go ahead with prototypeShould be straightforward as API similar to SL-Equip

Page 11: CMW status 6 Feb. 2002 CMW status February 2002 Kris Kostro

CMW status 6 Feb. 2002

SPS2001 and CMWDeadlock between End of 1999 and Oct 2001

Concept of contracts has been defined in-line with device/property model1999/2000 MW evaluation and designSeries of meetings Sept/Oct 2000

New SPS2001 Project Leader November 20016 Dec 2001 meeting between CMW and SPS2001

Kris makes a proposal on interaction CMW/Equipment/SPS2001Concluded that SPS2001 will attempt to use CMW to access SPS BCT and Multitune measurementsAttempt to understand measurements within SPS2001

19 December meeting on measurements, Kris asks for a simple measurement framework agreed with BIAttempted to analyze MKP server

Page 12: CMW status 6 Feb. 2002 CMW status February 2002 Kris Kostro

CMW status 6 Feb. 2002

SPS2001 and CMW (cont.)Meeting Mid January

Mike asks for a combined solution (SPS2001 server “plugged” into CMW)Michel defines “MW independent contract framework”Do not understand!

If CMW should be used by SPS2001Accept device/property get/set/subscribe modelDefine data representation (CMW or SPS2001 style)Should be possible to use CMW servers but a combined CMW/SPS2001 server framework is possible.Self-describing capabilities can be added easily to CMW servers.Additional requirements such as client ID can be added.

Page 13: CMW status 6 Feb. 2002 CMW status February 2002 Kris Kostro

CMW status 6 Feb. 2002

October 2000 conclusion(by Kris)

Kris reported from the 5 meetings in which he, Vito, Marc and Francesco from the MW team participated. For Kris the conclusions were not satisfactory as no edge-cutting decision was taken. Pierre Charrue has requested the following:Modifying the CMW and SPS2001 API's such that they are identical. (the conclusion from the presentation was that the API's are almost the same anyway). MW shall support requirements of SPS2001 such as automatic reconnection, client identification and "support for dynamic devices" the latter being a rather vague concept. SPS2001 shall provide precise contract definition.

Kris reckons that there is no technical problem to fulfill the requirements, except that the "dynamic devices" would have to be better defined.

Page 14: CMW status 6 Feb. 2002 CMW status February 2002 Kris Kostro

CMW status 6 Feb. 2002

User written

Middleware

Existing or off-shelf

Server Framework API (C++, Java)

Physical Devices (RF, BT, BI, Powering)

Java Control Programs

Middleware Client APIDevice/Property Model Topic Model

CMW Architecture

NamingService

Configu-rationService

RAD programs(VB, Excel) C Programs

ServersC

lients

Virtual Devices(Java, C++)

SL-EquipServer

PS-GMServer

OPCGateway

NewServers

CMW Infrastructure

RDA, CORBA, JMS