march 7th 2005 stefan koestner lhcb week ecs-tools for the ccpc/tell1 (installation): many...

Stefan Koestner LHCb week March 7th 2005

ECS-tools for the CCPC/Tell1 (Installation):

Many problems/user-requests already arises when installing the framework components.

We try to give here a brief guidance and a few tips to avoid common pitfalls.(as they happened to ourselves)

challenging Tell


(1) Create a PVSS project… tip: create once a blank project and whenever you need a new one copy it from there. (it is much faster!)

CCPC/FwHw Installation:

Give the name of the new project and the installation path. Tick that you want to register it. (so that it is selectable from the Console)


(2) Go to the ‘itcobe’ homepage: http://itcobe.web.cern.ch/itcobe/Services/Pvss/ Download the latest release of the JCOP framework and the Installation tool. (3) Extract the zip of the installation tool into your

project folder and start the project.



(4) After (or while) starting up always check the LogViewer if there are some mysterious warnings or error messages.

tip: sometimes it may happen that you cannot start up a project or switch to another one. Make sure that you have closed the PVSS help. (yes, although it is opened in a web browser it is somehow linked to the project!)


Also the LogViewers can give you troubles: Always check that they are closed when switching projects.


(5) From the graphical editor click (or choose from menu) ‘open panel runtime’.


(6) In the folder fwInstallation choose the panel ‘fwInstallation.pnl’ and start it.


(7) When your panel starts, it will ask you the destination directory of your installation. (it is the path where your framework components will be installed into) Give the directory of your project. (Some prefer to create their own directory for framework components. Common to each project. You have to click ‘create directory’ then.)


tip: Whenever you install something make sure the destination directory is the correct one. You can modify the path if you click on ‘Advanced Options’.


(8) Now specify the directory from where it shall make the installation (the directory which is containing your framework components). Choose the directory where you have unzipped the JCOP framework.


(9) From the JCOP framework you have to install ‘fwDIM’, ‘fwCore’ (containing FSM) and ‘fwConfigurationDB’ (needed for the recipes in the FwHw tool)

Check again if destination directory is correct.


(10) I don’t know if really required, but before continuing I prefer to restart the project:


Check the messages of the installation tool and the LogViewer if something mysterious has appeared.


(11) Download the zip of the ‘fwCcpc’ framework component (the page from where you got this tutorial) and unzip it. Open again the installation tool and choose this unzipped ‘fwCcpc’ directory.


(12) Start the installation of the ‘fwCcpc’ component. It will append three managers to your Console:PVSS00dim, a CONTROL manager (automatic subscription) and a user interface (the panel).


(13) After restarting your project the CCPC client should be ‘perfectly’ working… (supposing you have a server running and a DIM DNS node!)

…without supersticious intentions this became point ’13’.



tip: if you check the LogViewer after restarting your project you will find a Warning about the ‘external handler’. Simply ignore these warnings!

(they do not come from nor affect your Ccpc client component)



If not yet started, get the dim dns node from the JCOP framework. You will find it in the ‘bin’ directory: ‘Dns.exe’ (as you will have to launch it regularly put it at a more convenient place e.g. ‘Start’ menu)


tip: DID.exe and

DIMTree.exe are useful tools for debugging and understanding your DIM applications. (e.g. how many services are published on the dim dns node)


Now you have to tell your CCPC client (the PVSS project) where it can find thedns node (on which machine it is running). There are two possibilities …


First:From the Windows ‘Control panel’ under ‘System’ you can edit the environment variables.

In user variables add an environment variable with the name DIM_DNS_NODE and assign the name of the PC where the dns node is running.

DIM will take this variable as default location of the dns node.


Second:you can assign the dns node directly to PVSS00dim.


double click on PVSS00dim and edit manager properties. Add the option: –dim_dns_node PCName(it is the name of the PC where your dns node is supposed to run)


Log in on your ccpc and check status with: sudo service ccserv status(the server starts automatically after reboot)however you can start and stop it with: sudo service ccserv start/stop(check with your network administrator that you have the latest release)


The location of the dns node has to be edited on your ccpc in:/etc/dim.conf



As soon as the first server is found publishing his services on the dns node the status box becomes green.

You can select which ccpc you want to access from the combo box.When you confirm your selection the server version is prompted immediately. And if too low (not compatibel with client) a warning pops up.



On top of this you can now install the FwHw tool following the same procedures as before:download the zip and extract it , start the installation tool, install and restart your project.

If this button does not appear, you might not have installed ‘fwConfigurationDB’ from the JCOP framework.


“Bei diesem Licht, das uns zuerst begrüsst Von allen Völkern, die tief unter uns Schwer atmend wohnen in dem Qualm der Städte,Laßt uns den Eid des neuen Bundes schwören.”

Conclusion:

The intention of this slides was to give a brief guidance to ease your installation ‘pain’. If you find some annoyances tell us and share with your collaborators. (could save them time)

march 7th 2005 stefan koestner lhcb week ecs-tools for the ccpc/tell1 (installation): many...

Documents