100 likes | 110 Views
This proposal outlines the internal and external structure of SoftIOCs and suggests a directory structure for managing multiple SoftIOCs. It also discusses the migration of an application to a krynfs-cluster and the directory structure for the Channel Archiver CARv2.
E N D
SoftIOC directory Structure Proposal • We have a lot of softIOC application in different places (e2t, snmp, rtemsDIMM …) • Internal structure of SoftIOC • Proposal about external Structure(under vxBoot)
Creating and initializing a new app Example from APS web-page: • Create a new directory and run makeBaseApp.pl from within that directory mkdir lectureExample cd lectureExample makeBaseApp.pl -t example first • Provide full path to makeBaseApp.pl script <base>/bin/<arch>/makeBaseApp.pl • The template is specified with the ‘-t’ argument • The application name (firstApp) is specified with the ‘first’ argument
Internal structure : • Internal structure :
SoftIOC under our Sun: • External is /vxBoot/softIOC/ioc/appTop • But for bin structure has to be more complicated /vxBoot/softIOC/bin/$OS/$OSver/$EpRel/base OS is {Linux,win32} OSver={Suse,SL3;XP} EpRel=EpicsR3.14.7 … This directory created only from CVS and becomes frozen forever.
Multiple Soft-IOC under one Linux-box • It’s possible start a lot of softIOC under one host cd e2tIOC-mkkPowStat/iocBoot/ioce2t/ st.cmd ….. cd e2tIOC-north/iocBoot/ioce2t/ st.cmd ….. cas warning: Configured TCP port was unavailable. cas warning: Using dynamically assigned TCP port 37364, cas warning: but now two or more servers share the same UDP port. cas warning: Depending on your IP kernel this server may not be cas warning: reachable with UDP unicast (a host's IP in EPICS_CA_ADDR_LIST)
Multiple Soft-IOC directory structure proposal: Can be flat with prefix “iocLogicalName” Example e2tIOC-mkkInfraStruct/ e2tIOC-mkkPowerSt/ e2tIOC-north/
Channel Archiver = CAR v2 CARv2 Test environment working under /applic/bin/archiver/tests Migration to krynfs-cluster under /data2
CARv2 applications: • All application as StripTool and IDL and new Java interface will work through AAPI-protocol without big changes. • See IDL under kryomenu->Test • StripHistoryTool under kryomenu->Test as well • Java app under O:\Application\AAPI-Web\AAPI-2005 • Web-tool not finished yet.