I got it running pretty easy with Oozie 3.2.0.

It only started though when I followed the steps under "GETTING STARTED", i.e.:

- Set oozie URL in oozie.properties
- ./sbt
- sbt> container:start

After this I browsed to http://localhost:8080 and it works great.


But, when Itried to follow the deployment notes and run using the jar I get a 
class not found exception:
Here's what I did:

- ./sbt assembly
- java jar target/oozie-web-assembly-0.1.0-SNAPSHOT.jar 8080

Here's the exception:

Exception in thread "main" java.lang.NoClassDefFoundError: jar
Caused by: java.lang.ClassNotFoundException: jar
    at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
Could not find the main class: jar.  Program will exit.



Did I miss something?



________________________________
 From: Matthew Rathbone <[email protected]>
To: [email protected] 
Sent: Wednesday, October 17, 2012 11:24 AM
Subject: Re: Alternative web dashboard for apache oozie
 
There are a couple of screenshots on the github page, the easiest way to
check it out is to run it. It only requires 1 config change and it's good
to go.

On Tue, Oct 16, 2012 at 7:19 PM, Mona Chitnis <[email protected]> wrote:

> Great job! Could you possibly provide us with some more screenshots?
> --
> Mona Chitnis
>
>
>
>
> On 10/16/12 2:56 PM, "Matthew Rathbone" <[email protected]> wrote:
>
> >Yeah, you could go direct to SQL, but it seems much nicer and cleaner to
> >use the API. It also means it's pretty easy to hook up other actions like
> >job submission, canceling, retries, etc.
> >Theoretically this also shields the user from schema changes that don't
> >affect the API, plus it's pretty damn fast actually, surprisingly so.
> >
> >
> >
> >
> >On Tue, Oct 16, 2012 at 4:01 PM, Matt Goeke <[email protected]>
> >wrote:
> >
> >> This is awesome! Amusingly enough this was something I had in our
> >>private
> >> JIRA to work on but we have been too busy trying to production-ize the
> >> deployment of our workflows/coordinators. I am curious about something I
> >> read on the main github page and will have to see if I can dig through
> >>your
> >> source soon so feel free to correct me if I am wrong: could using the
> >>oozie
> >> client for querying be avoided completely by just hitting the schema
> >> directly? There is very little I have found I needed to go through the
> >> client/CLI for that I couldn't write simple SQL to get.
> >>
> >> Either way I commend you guys for open sourcing it and this is extremely
> >> helpful!
> >>
> >> --
> >> Matt
> >>
> >> On Tue, Oct 16, 2012 at 3:42 PM, Matthew Rathbone
> >><[email protected]
> >> >wrote:
> >>
> >> > Hey guys,
> >> >
> >> > We just open sourced a small dashboard we use for monitoring our oozie
> >> > jobs, thought I'd share:
> >> > https://github.com/foursquare/oozie-web
> >> >
> >> > It originated from a hack-day project here at foursquare with the
> >>goal to
> >> > make it a little easier to find and link to job detail pages.  It's a
> >> very
> >> > simple web-server that uses the java OozieClient to query for jobs.
> >>It's
> >> > only built for the CDH3 version of oozie at the moment (2.3.2), but
> >>we'll
> >> > be updating it soon for cdh4 which is oozie 3.something.
> >> >
> >> >
> >> > Would love opinions and feedback! Having great success with Oozie
> >>here at
> >> > foursquare. Here's the accompanying blog post:
> >> >
> >> >
> >>
> >>
> http://engineering.foursquare.com/2012/10/16/open-sourcing-our-dashboard-
> >>for-apache-oozie/
> >> >
> >> > Thanks,
> >> > --
> >> > Matthew Rathbone
> >> > Foursquare | Software Engineer | Server Engineering Team
> >> > [email protected] | @rathboma <http://twitter.com/rathboma> |
> >> > 4sq<http://foursquare.com/rathboma>
> >> >
> >>
> >
> >
> >
> >--
> >Matthew Rathbone
> >Foursquare | Software Engineer | Server Engineering Team
> >[email protected] | @rathboma <http://twitter.com/rathboma> |
> >4sq<http://foursquare.com/rathboma>
>
>


-- 
Matthew Rathbone
Foursquare | Software Engineer | Server Engineering Team
[email protected] | @rathboma <http://twitter.com/rathboma> |
4sq<http://foursquare.com/rathboma>

Reply via email to