Just checking, I know it was mentioned about a year ago that maintaining
and keeping up to date on the installer was still an option... is there any
plans to do a 3.0 version installer?
I have tried to upgrade my OpenBD for a number of days and can't seem to
get it to play nice. I updated the jar files from the war downloaded from
the openBD site, and updated my JDK to 1.7... I keep getting this error on
start up:
Sep 16, 2015 9:18:40 AM org.apache.catalina.core.ApplicationContext log
SEVERE: StandardWrapper.Throwable
java.lang.NoSuchFieldError: LUCENE_30
at
com.bluedragon.search.collection.CollectionFactory.<clinit>(Unknown Source)
I know it has to do with something else being out of version but I'm not
sure what else to "replace" from the original install.
This seems to keep the blue dragon control panel application from starting,
but some of my other application seem to start
fine (but this is just one of our development servers and I don't want to
perform this on a production server with that error).
Thanks,
Alan
On Monday, April 21, 2014 at 1:57:28 PM UTC-4, Jordan Michaels wrote:
>
> If folks are still using the Vivio OpenBD installer and finding it
> useful, we're happy to maintain it and keep it up to date. We just don't
> want to invest time and effort into something that folks don't want or
> need.
>
> Warm Regards,
> Jordan Michaels
>
> On 04/21/2014 12:34 AM, Rawk wrote:
> > I figured out why admin settings wouldn't update on the fly after the
> > upgrade. Basically, the war file contains it's own OpenBD engine and is
> > intended to be root folder of your app (giving each app on the server
> > it's own engine). However, the viviotech installer is setup to use a
> > single engine for all apps. This explains other quirky behavior that
> > started happening. For example, scheduled tasks were running twice
> > because two engines were reading from the same bluedragon.xml. To
> > correct this, the idea is to use a single engine for all apps on the
> > server. Ignore the upgrade procedure from my original post and use the
> > following upgrade steps:
> >
> > 1. Install Java jdk (if not already installed)
> > 2. Shut down the Tomcat service
> > 3. Copy C:\openbd\tomcat\webapps\ROOT\WEB-INF\web.xml to the desktop or
> > somewhere you won't lose it
> > 4. Delete everything inside of the folder c:\openbd\tomcat\webapps\ROOT
> > 5. Download the newest OpenBD .war file from http://openbd.org and
> place
> > in the ROOT folder from step #4
> > 6. From command line, navigate to the ROOT folder and enter the
> > following command:
> > - "c:\Program Files\Java\jdk1.7.0_55\bin"\jar -xvf openbd.war
> > - your path may differ depending on your jdk version
> > 7. If you have any custom jars inside of c:\openbd\lib, make a backup of
> > them
> > 8. Delete all of the files inside of c:\openbd\lib
> > 9. Copy all of the files from C:\openbd\tomcat\webapps\ROOT\WEB-INF\lib
> > to c:\openbd\lib
> > 10. Copy all of the files from
> > C:\openbd\tomcat\webapps\ROOT\WEB-INF\webresources to
> > c:\openbd\webresources (overwrite conflicts)
> > 11. Delete everything inside c:\openbd\tomcat\webapps\ROOT\WEB-INF\
> > 12. Copy the web.xml file you saved in step #3 into
> > c:\openbd\tomcat\webapps\ROOT\WEB-INF\
> > 13. If you have any custom jars, put them back in c:\openbd\lib
> > 14. Start the Tomcat service
> >
> > --
> > --
> > online documentation: http://openbd.org/manual/
> > http://groups.google.com/group/openbd?hl=en
> >
> > ---
> > You received this message because you are subscribed to the Google
> > Groups "Open BlueDragon" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> > an email to [email protected] <javascript:>
> > <mailto:[email protected] <javascript:>>.
> > For more options, visit https://groups.google.com/d/optout.
>
--
--
online documentation: http://openbd.org/manual/
http://groups.google.com/group/openbd?hl=en
---
You received this message because you are subscribed to the Google Groups "Open
BlueDragon" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
