From: Malcolm T. <mt...@wu...> - 2009-06-22 18:40:12
|
Luca, Thanks for your help clarifying the configuration settings. I tried building again (after doing an 'ant clean' as suggested) and the 2nd time the build went through fine. Maybe the 'ant clean' was necessary? Thanks againm Malcolm On Monday 22 June 2009 01:05:21 pm Luca Clementi wrote: > Malcolm Tobias wrote: > > I'm attempting to set up my own local Opal server. > > > > I have a couple of configuration questions: > > > > - in etc/opal.properties, the examples for the opal.jobmanager parameter > > read: > > > > # full qualified class name (FQCN) of the job manager being used > > opal.jobmanager=edu.sdsc.nbcr.opal.manager.ForkJobManager > > # opal.jobmanager=edu.sdsc.nbcr.opal.manager.DRMAAJobManager > > # opal.jobmanager=edu.sdsc.nbcr.opal.manager.GlobusJobManager > > # opal.jobmanager=edu.sdsc.nbcr.opal.manager.RemoteGlobusJobManager > > > > If my system is named foo.bar.com and I wanted to use DRMAA, would > > I use: > > opal.jobmanager=com.bar.foo.opal.manager.DRMAAJobManager ? > > > > It's not clear whether the server used in the example is: > > opal.nbcr.sdsc.edu or nbcr.sdsc.edu or even manager.opal.nbcr.sdsc.edu > > Malcolm, > You have to use the Java Class FQCN not your server domain name. > > So basically you don't have to change anything, simply uncomment the > line you want to use and make sure to have only one line uncommented. > > E.g. for DRMAA: > > # full qualified class name (FQCN) of the job manager being used > # opal.jobmanager=edu.sdsc.nbcr.opal.manager.ForkJobManager > opal.jobmanager=edu.sdsc.nbcr.opal.manager.DRMAAJobManager > # opal.jobmanager=edu.sdsc.nbcr.opal.manager.GlobusJobManager > # opal.jobmanager=edu.sdsc.nbcr.opal.manager.RemoteGlobusJobManager > > > - step 3 reads: > > > > If you did not follow instructions to set up a real production database, > > modify the connection.url property inside etc/hibernate-opal.cfg.xml from > > jdbc:hsqldb:file:data/opaldb to > > jdbc:hsqldb:file:<absolute_path_for_data_dir>/opaldb. > > > > I did not set up a real production database. What path would I use > > to the opaldb? I don't see anything under the opal-ws-2.0/ directory. > > Just use the path where you would like to store your database data > files. We generally use $CATALINA_HOME/data. Make sure your tomcat user > can write in that directory and that it doesn't get deleted. > > > I also had one installation question. During the initial install, the > > 'ant install' step just hangs: > > > > [root@agave opal-ws-2.0]# ant install > > Buildfile: build.xml > > > > setenv: > > [mkdir] Created dir: /usr/local/src/opal-ws-2.0/build > > [mkdir] Created dir: /usr/local/src/opal-ws-2.0/build/classes > > > > compile: > > Trying to override old definition of task wsdl2java > > > > setenv: > > > > generateStubs: > > [mkdir] Created dir: /usr/local/src/opal-ws-2.0/build/gen > > [wsdl2java] WSDL2Java /usr/local/src/opal-ws-2.0/wsdl/opal.wsdl > > > > This is an older system, but the tools need for installing are relatively > > recent: > > > > [root@agave ~]# cat /etc/redhat-release > > Fedora Core release 6 (Zod) > > > > [root@agave ~]# ant -version > > Apache Ant version 1.7.1 compiled on June 27 2008 > > [root@agave ~]# java -version > > java version "1.6.0_14" > > Java(TM) SE Runtime Environment (build 1.6.0_14-b08) > > Java HotSpot(TM) Client VM (build 14.0-b16, mixed mode, sharing) > > > > Any suggestions for debugging this installation problem? > > That's very odd. The wsdl2java might takes some time expecially on older > system. > Please give it another try, do a ant clean and then do another ant > install, and try wait a little longer. > > If the process still hangs please let me know what the ant process is > doing (is it just blocked, is it doing CPU, did it fork another process, > etc.) the output of > ps aux > and > ls build/gen/edu/sdsc/nbcr/opal/ > would be useful to further debug the problem. > > Sincerely, > Luca -- Malcolm Tobias 314.362.1594 |