RCMS 2 User Guide. Version 1.1. Grid Enabled Remote Instrumentation with Distributed Control and Computation

Transcription

1 Grid Enabled Remote Instrumentation with Distributed Control and Computation RCMS User Guide Version:. Authors: M. Gulmini CI identifier xxxxxxx_d_xxxxxx Version.

2 Revision History Date Version Description Author March, 00.0 Document creation M. Gulmini April 0, 00.0 Document finalization M. Gulmini July, 00. Update to RCMS. M. Gulmini August, 00. Installation script and Oracle DB A. Petrucci

3 CI Record Field CI Identifier Description Submission Date Submitted By Components Dependencies/Related External Identifier Point of Contact Comments Physical Location Description

4 Table of Contents RCMS Overview. RCMS Model. RCMS Services. RCMS states and commands RCMS. Release Overview RCMS Installation. Installation prerequisites.. Java installation.. Mysql installation.. Jakarta Tomcat installation. Checkout the code from CVS. 0. Running the installation script. Preparing the databases needed for running RCMS software. Configuring RCMS Release.. Configuring the Tomcat installation.. Configuring RCMS. Deploying RCMS Run the Hello Example. Compile and deploy the HelloStateMachine example. Fill the Resource Service. It works Appendix A: Configuring and using Eclipse 0 Configuring Eclipse IDE 0 Tomcat plugin configuration (mandatory) 0 Lomboz Plugin configuration (compulsory) Properties page Download RCMS Eclipse projects from CVS Creating Projects for the State Machines

5 RCMS User Guide 0 RCMS Overview RCMS Date: 0//00. RCMS Model The RCMS (Run Control and Monitor System) is defined as the collection of hardware and software components responsible for controlling and monitoring the CMS experiment during data-taking. The RCMS views the experiment as a collection of partitions. A partition is a configurable group of resources. Multiple partitions can be active concurrently, allowing several sections of the experiment to run independently. A number of DAQ sub-systems are involved in datataking (see figure ). Any sub-system can be partitioned and different partitions can be operated concurrently. UI RCMS Session Manager Services Services Connection EVB Ctrl DCS Ctrl TRG Ctrl CS Ctrl EVF Ctrl SubDet Ctrl FED Builder RU Builder Calo Mu GTP EVB Sub-System TRG Sub-System EVF Sub-System 0 0 DCS Sub-System CS Sub-System Sub-Detector System Figure : Session Managers and Sub-Systems defined in the RCMS The running of a partition is defined as a session. Each session is associated with a Session Manager (SMR) that coordinates user access to the session and propagates commands from the users to the Sub-System Controllers (SSCs). Multiple sessions may coexist and run concurrently. A Sub-System Controller consists of a number of Instrument Managers (IMs) and local services. One Instrument Manager is instantiated for each sub-system partition. A IM receives requests from the corresponding SMR and transforms them into commands for the sub-system resources. The results of performed actions are logged and analyzed by the RCMS.. RCMS Services A number of services support the interaction with the user to manage sub-system resources. Figure shows a block diagram of the RCMS with the services defined so far. Page of

6 RCMS User Guide Date: 0// Figure : Block Diagram of the Run Control and Monitor System The Security Service provides facilities for user authentication and authorization, including data encryption when demanded. It manages the user database where profiles are stored, including access rights and a working history. The Resource Service handles all the resources of the DAQ, including partitions. A resource can be any hardware or software component involved in a DAQ session. Resources can be discovered, allocated and queried. Partitions can only use available resources. The Information and Monitor Service collects messages and monitor data coming from DAQ resources and RCMS components and stores them in a database. There are several types of messages collected from the sub-systems. The messages are catalogued according to their type, severity level and timestamp. The Information and Monitor Service can publish the information to subscribers. These subscribers can register for specific messages categorized by a number of selection criteria, such as timestamp, information source and severity level. The Job Control is a utility that allows the remote execution and supervision of any software process involved in data-taking. It is used to start, stop and monitor the software infrastructure of the RCMS and the DAQ software components. The Problem Solver has to identify malfunctions of the DAQ system and determine possible recovery procedures. It subscribes to the IMS to receive the information it is interested in. The information is processed by a correlation engine and the result is used to determine a potential recovery action.. RCMS states and commands The Instrument Managers (IM) are objects which implement finite state machines. The states and transitions are customizable to the needs of the controlled resources. A partition can contain other partitions, through which a hierarchical organization of finite state machines is possible. The communication of states and commands between Instrument managers and resources and amongst Instrument managers is achieved through SOAP messages with a defined XML schema. If a command is sent from a IM to a resource, the resources reply should be immediate, acknowledging the reception. The resource sends another message to the IM once the command is executed and a state transition has occurred. Page of

7 RCMS User Guide Date: 0// RCMS. Release Overview The RCMS. software is composed of the following main packages: RCMS framework o Instrument Manager Framework o Resource Service o Generic Control Graphical User Interface (GUI) Instrument Manager State Machines Example implementations RCMS tools o DuckCAD o Log Collector The Instrument Manager Framework provides a set of facilities to control DAQ applications. Hierarchies of Instrument Managers are supported. The Resource Service (RS) provides configuration information of the control structure, and together with a Resource Service Database for XDAQ applications, called RSX, provides the meanings for a full configuration of your DAQ system. In this release the RSX is implemented together with the RS and not as a separate database. The DuckCAD is a graphical utility to generate DAQ and control configurations then stored in the Resource Service. The Log Collector is a service to collect log information both from RCMS and XDAQ world. Log messages can be visualized, stored into a database, or dispatched to clients through a JMS (Java Message Service) system. This User Guide provides information on how to install and deploy the RCMS framework. Documentation for RCMS tools, DuckCAD and Log Collector, can be found in separate documents. [][][] Page of

8 RCMS User Guide Date: 0// RCMS Installation This section explains how to install the RCMS Framework software. Paragraph. explains how to checkout the software from CVS. A perl installation script can then be used in order to perform the full installation, included the Hello example. The following paragraphs explain the installation procedure when the script is not used. They can also be useful in case of problems with the script. Appendix A provides some information if you want to install and use the Eclipse IDE.. Installation prerequisites The following external packages are needed in order to run RCMS software: Java..x mysql DBMS Jakarta Tomcat.0.x If you have already these packages installed in your system skip this section and go to section.. Support for Oracle 0g is also provided. Skip the mysql section if you plan to use Oracle instead... Java installation The RCMS software needs an installation of the Java Platform Standard Edition.. If you already have it in your system skip this paragraph. You can download the Java JSE.. from the Java Web Site ( ), and follow the installation procedure for your system. For a Linux system you could for instance download an RPM file (jsdk- 0-linuxi-rpm.bin) into a directory of your choice and install it. > chmod +x jsdk- 0-linux-i-rpm.bin >./jsdk- 0-linux-i-rpm.bin > rpm -i jsdk- 0-linux-i.rpm The new installation can be found in the directory /usr/java/jsdk.._0. In order to make sure that you always pick the correct executables of the java environment you should set your PATH to the directory where the java binaries can be found. If you use the tcsh shell you can add in your.tcshrc file the lines: Page of

9 RCMS User Guide Date: 0// > setenv JAVA_HOME /usr/java/jsdk.._0 > setenv PATH ${JAVA_HOME}/bin:$PATH For a bash shell: > export JAVA_HOME=/usr/java/jsdk.._0 > export PATH= /usr/java/jsdk.._0/bin:$path If you have problems to install java, see the documentation in Mysql installation The RCMS software have been tested both on mysql and mysql versions. The development has been done using a mysql..0 version running on a Linux SLC. The mysql CERN version. has also been used. If you want to install a mysql version..0 have a look at the following instructions. Download the mysql database server..0 from chose MySQL., select the version you need. For example mysql-standard-..0a-pc-linux-gnu-i.tar.gz copy the file mysql-standard-..0a-pc-linux-gnu-i.tar.gz in some place. For example in usr/local/ execute this group of commands: shell> groupadd mysql shell> useradd -g mysql mysql shell> cd /usr/local shell> gunzip < /PATH/TO/MYSQL-VERSION-OS.tar.gz tar xvf - shell> ln -s FULL-PATH-TO-MYSQL-VERSION-OS mysql shell> cd mysql shell> scripts/mysql_install_db --user=mysql shell> chown -R root. shell> chown -R mysql data shell> chgrp -R mysql. shell> bin/mysqld_safe --user=mysql & For any problems you find refer to the documentation in See also the README and INSTALL-BINARY file in the directory FULL-PATH-TO- MYSQL-VERSION-OS (for example: mysql-standard-..0a-pc-linux-gnu-i)... Jakarta Tomcat installation The RCMS software needs an Apache Jakarta tomcat.0.x installation. The software has been developed and tested using the version.0. running on a Linux SLC machine. The Apache Jakarta tomcat is available on the RCMS web site. Page of

10 RCMS User Guide Date: 0// The Jakarta tomcat.0. for Linux is available on the RCMS web site ( If you want install and try another Tomcat version (not recommended) follow the instructions below. Download the Tomcat version.0. from the jakarta site. chose Tomcat, Tomcat,.0. Binary for your operating system. Linux: jakarta-tomcat-.0..tar.gz o Gunzip the file in some place, usually in /usr/local using tar -xzvf jakarta-tomcat-.0..tar.gz o This create a directory containing the Application Tomcat, usually jakarta-tomcat-.0. o Set the system variable: (for example) export CATALINA_HOME=/usr/local/jakarta-tomcat-.0. for bash or korn shell (bash, ksh) setenv CATALINA_HOME /usr/local/jakarta-tomcat-.0. for c shell (tcsh, csh) Windows: jakarta-tomcat-.0..zip o Gunzip the file in some place. o This create a directory containing the Application Tomcat, usually jakarta-tomcat-.0. o Set the System Variable in the Control Panel. (CATALINA_HOME) To start and stop tomcat use the startup.sh and shutdown.sh for linux, and startup.bat and shutdown.bat for windows in $CATALINA_HOME/bin.. Checkout the code from CVS. The RCMS source code is available on the CERN CMS CVS server. This paragraph explains how checkout the software. It is assumed that the user shell is tcsh, and that the installation directory is CheckoutDir (please replace CheckoutDir with the full path to your installation directory). Set the environment variable CVSROOT to point to the CMS CVS server. If you are at CERN: > setenv CVSROOT :kserver:cmscvs.cern.ch:/cvs_server/repositories/tridas If you are outside CERN you can use the anonymous login: > setenv CVSROOT :pserver:anonymous@cmscvs.cern.ch:/cvs_server/repositories/tridas > cvs login using the password passwd Page 0 of

11 RCMS User Guide Date: 0// Go to the installation directory. > cd CheckoutDir Now you can checkout release of the RCMS source code. The module name is TriDAS/RunControl. Verify the last stable tag on the RCMS web site ( ), and checkout it. > cvs co -P -r <cvs_tag> TriDAS/RunControl At the moment of writing the tag is RCMS 000. Assume that the RCMS installation directory is RCMSInstallationDir. The RCMSInstallationDir/framework directory contains the RCMS framework. The RCMSInstallationDir/statemachines directory contains statemachines developed as examples or as software components by the DAQ group. You can take these state machines as examples for developing your own State Machine and run it into the Instrument Manager Framework. The RCMSInstallationDir/tools directory contains RCMS utilities. The first release provides the DuckCAD utility for generating XDAQ and RunControl configurations, and the Log Collector tool for collecting, storing and visualize both RCMS and XDAQ log messages. If you prefer you can also checkout separately the three directories. > cvs co -P -r <cvs_tag> TriDAS/RunControl/framework > cvs co -P -r <cvs_tag> TriDAS/RunControl/statemachines > cvs co -P -r <cvs_tag> TriDAS/RunControl/tools. Running the installation script The RCMS. Release provides an installation script that performs the tasks explained in the following paragraphs. The script assumes that you are using a mysql database. It installs the RCMS framework, and the RCMS Log Collector tool. The steps for running the Hello Example explained in paragraph are also performed. If you want to use the installation script you must set three environment variables:. RCMS_HOME Page of

12 RCMS User Guide Date: 0// JAVA_HOME. CATALINA_HOME For instance: > setenv RCMS_HOME RCMSInstallationDir > setenv JAVA_HOME /usr/java/jsdk.._0 > setenv CATALINA_HOME /users/rcms/jakarta-tomcat-.0. Go in the directory RCMSInstallationDir/framework/installation/ and type : > perl./installrcms.pl and follow the instructions. Be careful: If during the installation procedure you choose a database name of an existing database, all data of that database will be lost! If you use that script keep the following paragraphs as a reference guide in case of problems.. Preparing the databases needed for running RCMS software This RCMS release needs an installation of a mysql DBMS (see paragraph.). Oracle 0g DBMS is also supported. Two databases are needed: - Resource Service database - Realm database (tomcat users and roles) In the directory RCMSInstallationDir/framework/installation/configuration/databases/mysql you can find two SQL scripts for the creation of the two databases. A directory for Oracle exists as well: RCMSInstallationDir/framework/installation/configuration/databases/oracle The Realm script creates a database named realm. This database stores RCMS users, passwords, and permissions. It is used by tomcat to check if a user can access the RCMS services. By default the script creates a user rcms with password rcms. If you want to change these default values modify the mysqlrealm.sql or the oraclerealm.sql according to your needs. The script can be run from the mysql prompt with the command: mysql> source mysqlrealm.sql; In the sqlplus prompt with the command: Page of

13 RCMS User Guide Date: 0// Be careful: the Realm script deletes a previous realm database if it already exists. The RSConfig script initializes the Resource Service database tables. The RS database will be used to store the RCMS configurations for your DAQ and RCMS system. From the mysql prompt create a new database (for instance rs) and run the script: mysql> create database rs; mysql> use rs; mysql> source mysqlrsconfig.sql; In the sqlplus prompt with the command: Now for MySql we have to grant the privileges to the new databases. For the tomcat realm database: > GRANT ALL PRIVILEGES ON realm.* TO realmuser@% identified by realmpassword; > GRANT ALL PRIVILEGES ON realm.* TO realmuser@localhost identified by realmpassword; where realmuser and realmpassword are mysql users. For the RS database: > GRANT ALL PRIVILEGES ON rs.* TO rsdbuser@% identified by rsdbpassword; > GRANT ALL PRIVILEGES ON rs.* TO rsdbuser@localhost identified by rsdbpassword; where rsdbuser and rsdbpassword are mysql users. A suggestion: probably you use the same mysql installation for realm and rs database. So you can use the same mysql user and password for realmuser and rsdbuser (for instance rcms and rcms).. Configuring RCMS Release This paragraph explains the steps to perform in order to configure the RCMS software... Configuring the Tomcat installation In this paragraph we assume that your environment variable CATALINA_HOME is set to your Jakarta tomcat installation. Page of

14 RCMS User Guide Date: 0// > setenv CATALINA_HOME <Jakarta-tomcat-.0.-installation> RCMS needs a tomcat installation configured to use a Realm mysql database (see paragraph.) to store tomcat user names, passwords and permissions. Make the mysql driver visible to tomcat (the driver is available in the RCMS distribution): > cp RCMSInstallationDir/framework/rcms/WEB-INF/lib/mysql-connector-java-..-bin.jar ${CATALINA_HOME}/common/lib Modify the tomcat server.xml configuration file located in the directory $CATALINA_HOME/conf. Set here the correct information about the realm database you created in paragraph.. The directory RCMSInstallationDir/framework/configuration/tomcat contains an example configuration file (server_example.xml). Tomcat by default runs on port 00. Modify the server.xml if you want to change this default port. More information can be retrieved on the Apache web site ( Configuring RCMS All the configuration files needed by the RCMS services are located in the directory RCMSInstallationDir/TriDAS/RunControl/framework/installation/configuration. Here is the list of the configuration files: o rcms_build.properties o RCMS.properties o logjdefault.properties o web.xml Go to the configuration directory: > cd RCMSInstallationDir/TriDAS/RunControl/framework/installation/configuration The rcms_build.properties file is used by the ant build scripts to compile and deploy the software. RCMS base directory and Jakarta Tomcat full path have to be specified: rcms.home=rcmsinstallationdir/framework catalina.home=<your_tomcat_installation> For instance: rcms.home=/users/rcms/tridas/runcontrol/framework catalina.home=/users/rcms/jakarta-tomcat-.0. The RCMS.properties file contains the configuration information that allows the RCMS services to connect to the RS database: Page of

15 RCMS User Guide Date: 0// dburl=<jdbc_url_for_db_connection> user=rsdbuser password=rsdbpassword For instance: dburl=jdbc:mysql://localhost:0/rs ( for oracle jdbc:oracle:thin:@oracms.cern.ch::cmsomds) user=rcms password=rcms The logjdefault.properties file is used by the RCMS services to send logj log messages. Log messages can be sent to a file, to the console, directly to Chainsaw, or to the RCMS Log Collector. See the logj and the Log Collector documentation for more details. By default log messages are stored in a file. The perl installation script modifies it in order to use the RCMS Log Collector. The web.xml file is the descriptor for the RCMS web application. This file contains several information. You might need to modify the resourceserviceendpointaddress entry that is used by the GUI: <param_name> resourceserviceendpointaddress </param_name> <param_value> <param_value> Once you have modified all the configuration files you can run the ant build script located in the same directory. Use classic-ant on Linux machines. > classic-ant The ant script copies the configuration files in other directories of the RCMS source code and prepares in this way a RCMS directory structure ready to be deployed. Every time you modify one of these files you need to run again the ant script, and redeploy the RCMS web application (see next paragraph).. Deploying RCMS Once you have configured the RCMS you need to deploy it. Go to the directory RCMSInstallationDir/framework/installation/deployment > cd RCMSInstallationDir/framework/installation/deployment Run the deployment build file using the release target: > classic-ant release Page of

16 RCMS User Guide Date: 0// The RCMS framework is now ready to be used. Just startup your tomcat installation: > cd ${CATALINA_HOME} > bin/startup.sh Connect now with a browser to For instance You should see the RCMS web page. A login and password will be asked. Type your tomcat realm user and password (for instance rcms as user, and rcms as password). Clicking on Configuration Chooser you should see an empty blank page. The reason is that you do not have any configuration inserted in your Resource Service. Next chapter will explain how to configure and run your first Hello Example. Page of

17 RCMS User Guide Date: 0// Run the Hello Example Once you have correctly installed the RCMS software you need to install and run your first Hello Example. The directory RCMSInstallationDir/statemachines/examples contains a directory named HelloStateMachine.. Compile and deploy the HelloStateMachine example The HelloStateMachine example is a simple Instrument Manager State Machine implementation that does not control any resource, but simply changes its State upon the reception of commands from the GUI. The document RCMS Finite State Machines explains how to write your own State Machine implementation, and how to compile and deploy it. For your first example just follow the following steps. Go to the HelloStateMachine example directory: > cd RCMSInstallationDir/statemachines/examples/HelloStateMachine Go to the installation directory: > cd installation Compile and deploy the State Machine: > classic-ant The build script should work as it is. If not edit the build.xml and verify if the path to the rcms_build.properties file is correctly set. Go to your web browser. The link shows a directory listing. It must contain the HelloStateMachine.jar file. Page of

18 RCMS User Guide Date: 0// Fill the Resource Service In order to run our Hello example The Resource Service database has to be filled with the proper configuration. The are two main tools to fill the database: o The DUCK (Data Utility for Configuration Knowledge) o The DUCK-CAD: a graphical user interface. Both the tools have their own manual where you can find more detailed information. In order to provide the configuration for our Hello example we use the DUCK tool. The tool reads configuration information from a file and stores them into the Resource Service database. Go to the duck directory of the HelloStateMachine example: > cd RCMSInstallationDir/statemachines/examples/HelloStateMachine/duck The directory contains two duck files: hello.duck and hellotop.duck. hello.duck fills the Resource Service with a very simple configuration, just a Instrument Manager, while hellotop.duck fills the RS with a configuration containing two Instrument Managers; a top one that controls a leaf one. Let us use the simplest configuration; hello.duck. The hello.duck file needs a few modifications related to your specific configuration. rcms is the owner of the configuration you are going to store. The owner must be a tomcat user as defined in the realm database. Replace rcms with your_realmuser if you did not choose rcms as user name. The URL has to be replaced with the actual host and port where you are running your tomcat. Now you can run the DUCK tool: > java jar RCMSInstallationDir/tools/DuckCAD/DuckConfiguratorParser/duck.jar hello.duck rsbduser rsdbpassword rs_jdbc_url Where rsdbuser and rsdbpassword are the mysql user and password for the Resource Service DB, and rs_jdbc_url is the JDBC url of your RS DB. For instance: > java jar /users/rcms/tridas/runcontrol/tools/duckcad/duckconfiguratorparser/duck.jar hello.duck rcms rcms jdbc:mysql://localhost:0/rs Page of

19 RCMS User Guide Date: 0// It works The HelloStateMachine was compiled and deployed. The configuration was inserted in the Resource Service database. Now you should be able to drive the Hello Instrument Manager using the web GUI. Clicking on Configuration Chooser you see a Directory named Hello. Clicking on the Hello directory the configuration hellosimple appears. Clicking on the hellosimple configuration a control page containing the chosen configuration is displayed. Click now on the Create button. The Instrument Manager is created and our HelloStateMachine.jar is loaded. The HelloStateMachine allows three commands: GoToInit, GoToHello and Reset. Clicking on them the State Machine changes its state. The Destroy button will kill the Instrument Manager. The Detach button will just disconnect the GUI from the Instrument Manager, without killing it. After a Detach the Attach button will allow to reconnect the GUI to the Instrument Manager previously created and running on your tomcat. The Status Display button will show a tree containing the Status of all the resources defined in your configuration. The Refresh button will just Refresh the GUI. The Diagnostic Page tab will move your GUI to a page where some useful information is displayed. Here you can see the Instrument Manager instances running on tomcat, the configuration of the logj logger and of the Resource Service DB. Page of

20 RCMS User Guide Date: 0// Appendix A: Configuring and using Eclipse The Eclipse Integrated Development Environment ( ) is a tool used to develop the RCMS software. The RCMS can of course be deployed and used without the Eclipse platform. Eclipse can also help the development, debugging and deployment and of User Custom State Machine code. If you want to use Eclipse this appendix provides some information on how to configure and use it with the RCMS software. Configuring Eclipse IDE First of all you need to install the Eclipse platform on your system. At the purpose follow the instructions on the Eclipse web site. Eclipse can work together with your tomcat installation. You will have full tomcat support only if you install Eclipse on the same host where you run your tomcat. Many plugins can be installed on the Eclipse platform to perform several task. Tomcat plugin configuration (mandatory) Download and install Tomcat before using this plugin. Plugin activation for Eclipse.0 : select menu 'Window->Customize Perspective...->Commands', and check 'Tomcat' in 'Available command groups' Set Tomcat home : Window -> Preferences, select Tomcat and set Tomcat home. Set Context files in Context Declaration Mode. This plugin launches Tomcat using the default JRE checked in Eclipse preferences window. To set a JDK as default JRE for Eclipse open the preference window : Window -> Preferences -> Java -> Installed JREs. This JRE must be a JDK (This is a Tomcat prerequisite). The plugin sets itself Tomcat classpath and bootclasspath. Use Preferences -> Tomcat ->JVM Settings, only if you need specific settings. Page 0 of

21 RCMS User Guide Date: 0//00 Lomboz Plugin configuration (compulsory) The Lomboz plugin is needed only for RCMS internal development and not for Custom State Machine development. Plugin Activation: Once installed, Lomboz plugin must be activated. Lomboz currently adds actions, wizards and views to the Eclipse environments. To activate these add-ons: 0 Select menu Window>Customize Perspective..., in the Shortcuts tab choose 'Submenus: New' check all Lomboz related items. (Click OK button). Select menu Window>Customize Perspective...', in the Shortcuts tab choose 'Submenus: Show View' check Lomboz Views', JEE View. (Click OK button) Select menu Window>Customize Perspective...', in the Commands tab in the availabe commands tab, check Lomboz Actions. (Click OK button). Page of

22 RCMS User Guide Date: 0//00 Select menu Window>Preferences', in the Workbench->Label Decorations, check Lomboz JEE Decorators. Once you confirmed your selections, you will see the newly added Toolbar button: and the new the new wizards will be available to you from the New project dialog and the quickly accessible New Items menu. Page of

23 RCMS User Guide Date: 0//00 You must complete the following minimum configurations before you can start using Lomboz as your JEE development tool. Global Settings : Most application servers use the standard Java compiler (javac) to compile JSP files. Javac is found in the tools.jar distributed with standard Java JDKs (NOT JREs). You must select the tools.jar that will be used by the application servers here. It is normally found inside the lib folder under the JDK installation ( for instance the path is /usr/java/jsdk.._0/lib/tools.jar). 0 Page of

24 RCMS User Guide Date: 0//00 0 Server Definitions: Lomboz can work with almost all Java application servers. You will have to set these parameters so that Lomboz can create scripts which point to the right places. The parameters you set here are used for setting default values for launching the servers and finding the location for deploying Web applications (.war files) and EJB jar files. These files are stored in a folder named "servers" inside the plugin. Lomboz scans the folder everytime it needs a definition. Adding a new server type is adding one of these files into this folder. In order to use (activate) any of these definitions you must ALWAYS visit the Lomboz preferences. This will load the files in the servers folder into eclipse. Next task is to check and set the properties and classpaths defined for these servers. Although there are predefined values for these properties, it is most likely that they are incorrect for your configuration. It is very important that you click APPLY after any change. Page of

25 RCMS User Guide Date: 0//00 0 Properties page To change the properties open the preferences dialog from Workbench -Preferences menu and highlight the Lomboz server definitions item in the list. You must enter the following parameters: Classpath variables: In order for Lomboz to find the proper application server classes without hard coding them into Java projects we use classpath variables. These class variables are automatically added into the Eclipse environment each time you apply these properties. To verify that these variables are set, open the preferences dialog from Workbench - Preferences menu and Expand the Java item first highlight the Classpath Variables item under the Java list. You SHOULD SEE the values such as WEBLOGIC00, JBOSS00 and TOMCAT0 etc, which will point to the application server directories. All server definitions have these variables. You can now choose a name for the classpath variable you would like to use and set the path for this variable. These settings will be used to add a classpath variable, which you can verify by looking at the Java classpath variables page as described above. The jar files and libraries you will chose in the next few steps will be relative to this classpath variable. Tomcat: Parameter Description Server Home Directory The path to the application server installation directory Download RCMS Eclipse projects from CVS Open a New Eclipse Project. Select Checkout Projects from CVS. Set the CERN CMS TriDAS configuration for cvs: Host: cmscvs.cern.ch Repository: /cvs_server/repositories/tridas User: <your_username> Password: <your password> Connection Type: extssh Click on Next. Select Use an Existing Module. Select the Folder RunControl/framework Click on Next. Checkout as a project in the workspace. Click on Next. Page of

26 RCMS User Guide Date: 0// Use default workspace location. Click on Next. In the Select Tag Window Click on Refresh from Repository. Then choose the tag you want. Click on Finish. Now you have an Eclipse project called framework. Change the Properties of the framework Project: - Right click on the Project and select Properties. - Select Tomcat. - Check if the is a Tomcat Project is selected. If so remove it. Click on Apply and then OK. - Return into the properties of the framework project. - Select Is a Tomcat Project - Put /rcms as Context Name - Put /rcms as Web Application root Creating Projects for the State Machines Download using CVS the State Machine examples as new Eclipse projects. The examples are in the cvs folder RunControl/statemachine/examples. Once you have checked out the State Machine you might need to change the Eclipse Project properties. It depends on the RCMS framework Project in order to compile. - Right click on the Project and select Properties. - Select Java Build Path. - Select Projects. - Click on the framework Project. When you want to deploy your custom State Machine follow the same step described in paragraph.. Page of

27 RCMS User Guide Date: 0//00 References [] DuckCat Manual [] RCMS Manual Page of