Hi Gabe,
Is your FM up and running?
Besides that, check if your FM catalog (lucene?)
has a segments file in it, or if it was manually created.
It should not exist before you start FM.
Also does the command line API for FM work?
CC'ing dev@oodt.a.o.
Cheers,
Chris
Hey Gabe,
The FM browser view should work with any extended FM catalog class.
You can try a couple things:
1. Deploy the fmbrowser webapp and see if that works with your FM
2. Ensure your OPSUI context.xml (within tomcat/webapps/pcs-opsui/META-INF) has
all OODT properties correctly set.
It's possible that I didn't deploy the OpsUI correctly. I followed the
directions in
https://cwiki.apache.org/confluence/display/OODT/Quick+Start+for+PCS+OPSUI
for using an existing WAR file and put my context.xml file in the
tomcat/conf/Catalina/localhost directory.
To be honest, my experience
Hi Gabe,
You might want to try the following deploying your war file directly to
tomcat/webapps and making sure your context.xml file within
webapps/pcs-opsui/META-INF/context.xml is correct (has the correct FILEMGR_URL
etc)
If you do the above, make sure to first remove the context.xml file
Hi Gabe,
OCO2 and PEATE's FM Browser Pages with w/ the Column Based Catalog. Here are
our dependencies:
https://svn.apache.org/repos/asf/oodt/trunk/balance/modules/cas-browser, rvn
1339293
Org_Apache_Oodt_Balance-0.3.0.tgz
CAS_Filemgr-1.0.0.tgz
Org_Apache_Oodt_Security-0.3.0.tgz
-- cecilia
