Difference between revisions of "Archiver for EPICS"
From GlueXWiki
(→Archiver Engine Installation) |
(→RDB Archiver) |
||
| Line 22: | Line 22: | ||
* This created Archive Engine executable <i>/home/hovanes/css/ArchiveEngine/ArchiveEngine</i> | * This created Archive Engine executable <i>/home/hovanes/css/ArchiveEngine/ArchiveEngine</i> | ||
| − | == Archiver Configurator Tool Installation == | + | == Archiver Configurator Tool Installation == |
| + | * Here I assume that we are in Eclipse RCP session and the sources are imported when building the Archive Engine. | ||
| + | * Open <i>/org.csstudio.archive.config.rdb/ArchiveConfigTool.product</i> file. | ||
| + | * <b>Synchronize</b> and <b>Launch an Eclipse application</b> in the Overview tab. The launch should fail because it requires parameters, but I see the help message, so it runs properly. | ||
| + | * Export the product using <b>Eclipse Product export wizard</b> in the Overview tab: | ||
| + | *: <i>Root directory</i> = <i>ArchiveConfigTool</i> | ||
| + | *: <i>Destination Directory</i> = <i>/home/hovanes/css</i> | ||
| + | : uncheck <b>Generate metadata repository</b>, and click <b>Finish</b> button. | ||
| + | * This created Archive Engine executable <i>/home/hovanes/css/ArchiveConfigTool/ArchiveConfigTool</i>. | ||
| + | * I think the <b>ArchiveConfigTool</b> is defective. Also ANL test document said that they could not use "import" feature and they configured the database manually. | ||
= JLab MYA Archiver = | = JLab MYA Archiver = | ||
Revision as of 09:36, 2 November 2011
Contents
RDB Archiver
RDB Archiver is the new new version of the EPICS Channel Archiver which was widely used by the EPICS community. Channel Archiver kept the history in data file and had some kind of indexing scheme. The new RDB Archiver is a part of the Controls System Studio (CSS) and, as the name suggests, it utilizes databases to keep the archive engine configurations and the archived values. RDB Archiver can be used with both MySQL and Oracle (and probably others as well). Folks at ANL tested the RDB Archiver archiver with MySQL and I followed their example, and below you can find what I observed.
- To create CSS products one needs to have Eclipse RCP which I downloaded from Eclipse download page (version 3.7.0 Indigo) and installed in /usr/local/eclipse/indigo-3.7.0-rcp on my local machines.
- As CSS sources I used the SNS snapshot 3.0.2 posted on the SNS products web page. I unzipped the file and put it in ~/sns/source directory on my local computers.
- One also need MySQL server which is included in Linux distributions.
Archive Engine Installation
- Start Eclipse RCP
/usr/local/eclipse/indigo-3.7.0-rcp/eclipse
- Select /home/hovanes/css/source as Workspace since the CSS source was unzipped there.
- Import the sources into the Workspace by File->Import->General->ExistingProjectsIntoWorkspace->Next, select the /home/hovanes/css/source where the source is located using Browse button, and click Finish.
- Open /org.csstudio.archive.engine/ArchiveEngine.product file.
- Synchronize and Launch an Eclipse application in the Overview tab. The launch should fail because it requires parameters, but I see the help message, so it runs properly.
- Export the product using Eclipse Product export wizard in the Overview tab:
- Root directory = ArchiveEngine
- Destination Directory = /home/hovanes/css
- uncheck Generate metadata repository, and click Finish button.
- This created Archive Engine executable /home/hovanes/css/ArchiveEngine/ArchiveEngine
Archiver Configurator Tool Installation
- Here I assume that we are in Eclipse RCP session and the sources are imported when building the Archive Engine.
- Open /org.csstudio.archive.config.rdb/ArchiveConfigTool.product file.
- Synchronize and Launch an Eclipse application in the Overview tab. The launch should fail because it requires parameters, but I see the help message, so it runs properly.
- Export the product using Eclipse Product export wizard in the Overview tab:
- Root directory = ArchiveConfigTool
- Destination Directory = /home/hovanes/css
- uncheck Generate metadata repository, and click Finish button.
- This created Archive Engine executable /home/hovanes/css/ArchiveConfigTool/ArchiveConfigTool.
- I think the ArchiveConfigTool is defective. Also ANL test document said that they could not use "import" feature and they configured the database manually.
