SLAC PEP-II
BABAR
SLAC<->RAL
Babar logo
HEPIC E,S & H Databases PDG HEP preprints
Organization Detector Computing Physics Documentation
Personnel Glossary Sitemap Search Hypernews
Unwrap page!
Comp. Search
Who's who?
Meetings
FAQ Homepage
Archive
Environment
Administration
New User Info.
Web Info/Tools
Monitoring
Training
Tools & Utils
Programming
C++ Standard
SRT, AFS, CVS
QA and QC
Remedy
Histogramming
Operations
PromptReco
Simulation Production
Online SW
Dataflow
Detector Control
Evt Processing
Run Control
Calibration
Databases
Offline
Workbook
Coding Standards
Simulation
Reconstruction
Prompt Reco.
BaBar Grid
Data Distribution
Beta & BetaTools
Kanga & Root
Analysis Tools
RooFit Toolkit
Data Management
Data Quality
Event display
Event Browser
Code releases
Databases
Check this page for HTML 4.01 Transitional compliance with the
W3C Validator
(More checks...)

How to use a Reference Server with Jas


To view reference histograms in Jas, you will need to:

  • Start up the reference server on your hbook file.
  • Connect a DOT-Jas server (JasInterfaceServer) to the reference server.
  • Start Jas.

Starting the reference server (HbkServer)

First you need to set your path correctly to find the HbkServer executable. Type:

srtpath 8.6.0 SunOS5

Now start up the reference server on your hbook file:

HbkServer -n <DotName> -f <filename>

The <DotName> you specify is the name your server will be bound to in the CORBA naming service. It automatically registers your server under the Dot context.

This should evoke the following simple response:

Server will not connect to a requestor

Starting the JasInterfaceServer

    First set your environment:
    srtpath 8.6.0 SunOS5
    
  • Now start the JasInterfaceServer. This reads the histograms out of the reference server using CORBA, and makes them available to JAS. This process may be run on a different host than the reference server.

    JasInterfaceServer -n <JasLabel>@Dot/<DotName> -u 5

    The name you specify in <JasLabel> is the name Jas will give the top level folder that your histograms appear under in the Jas histogram tree. The name you specify in <DotName> is the name you gave your Reference server.

    These names do not have to be the same. This means that if you are writing HTML/XML files to run with production servers, you may run a test reference server and have it appear in the Jas tree with the same name as the production servers would have.

    For example: If I knew that the real LiveFastMonitoring data that DQM's look at in IR-2 appears in the Jas tree under the folder 'LiveFastMon_R', I could start up a test reference server called 'ReferenceTest1', but have it appear in my local copy of Jas under a folder called LiveFastMon_R. The commands I would type to do this are as follows (assuming my environment is already set up as described above):

           HbkServer -n ReferenceTest1 -f my_hbook_file.hbook
           JasInterfaceServer -n LiveFastMon_R@Dot/ReferenceTest1
           

    In this way you are able to set up and test your XML/HTML pages in a way that recreates the environment in IR-2. When you are satisfied with how they look, you can move them into production without having to change my XML files at all.

    Also, a single JasInterfaceServer can connect to multiple reference servers. Simply specify a separate -n option for each server when starting the JasInterfaceServer. Each server will appear in a separate folder in the Jas tree.

  • You're now ready to set your environment, and start JAS.

    srtpath 8.6.0 SunOS5
    

    BabarJas --connect <hostname>/Histograms --startPage file:/path/to/your/html/start/page

    where <hostname> is the name of the host on which you are running the JasInterfaceServer.


Maintained by Kevin Rennert, rennert@slac.stanford.edu
Last Modified Feb 29, 2000