Hi Andras, thanks. All of that (used to be/is usually handled by Cloudera. But reading between the lines it seems as if that should still work. In that case I'll ping the Cloudera forum.
Cheers, Lars On Wed, May 16, 2018 at 4:02 PM, Andras Piros <[email protected]> wrote: > Hi Lars, > > glad to hear you trying out Oozie 5 :) > > As the *installation guide > <https://oozie.apache.org/docs/5.0.0/AG_Install.html#Oozie_Server_Setup>* > tells: > > > If a directory libext/ is present in Oozie installation directory, the > > oozie-setup.sh script will include all JARs in Jetty's > webapp/WEB_INF/lib/ > > directory. > > If the ExtJS ZIP file is present in the libext/ directory, it will be > > added to the Jetty's webapp/ directory as well. The ExtJS library file > > name be ext-2.2.zip . > > > Important is to do that during setup, before calling oozie-setup.sh or > before the first call to oozied.sh. > > Regards, > > Andras > > On Wed, May 16, 2018 at 3:19 PM, Lars Francke <[email protected]> > wrote: > > > Hi, > > > > I've just tested Oozie 5 via CDH6 beta and I can't get the Web console > > enabled using the "old" way there (dropping ext2.2 in /var/lib/oozie). > Now > > before I ping Cloudera itself I wanted to ask if anything has changed > here > > or if it _should_ work in Oozie 5? > > > > I know you switched from Tomcat to Jetty so things might have changed. > The > > docs are still the same. > > > > Cheers, > > Lars > > >
