If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Migration of OX 6.4.2 (CVS) to 6.5.0 (packages)

Hi all,

as you may have noticed, Open-Xchange did a big step forward to provide their software to the opensource community. We recently started the public beta of Open-Xchange 6.5 and this will be the most up to date release. Starting with this public beta, we're maintaining software packages for various platforms, such as debian, ubuntu, opensuse/sles, centos/fedora/rhel.

Compared with the installation process based on CVS checkouts and compiling this one offers a much more stable and convenient way to administrate the Open-Xchange server. For all those fellow heroes out there who managed to set up their server based on CVS sources, this short manual should provide some guidance when moving to the packaged version.

Before you start, please notice: Open-Xchange is a Groupware, not a Mailserver. If you've used the installer scripts or the installation guide at the wiki, you may already have set up a OX:EE flavor environment. One major thing needs to be considered before migrating.
- There is no Admin GUI (was a unique feature of OX:EE, but not a core part of Open-Xchange)

Generally speaking you'll get a plain Groupware Server with a user interface but no graphical administration tools. This is not to upset anybody, but the Admin GUI was a unique feature of OX:EE and is not longer actively maintained with Open-Xchange 6.5. Of course there is still a very powerful command line interface that can do much more than the UI ever could.

The good news:
We're working on a integrated group/resource management plugin which allows to do most groupware related configuration right off the Groupware UI, without the need of a additional interface, this feature will be added with a upcoming release candidate or the final release fo Open-Xchange 6.5.

The following guide is very straightforward, if there are any detailed questions, don't hesitate to ask.

this changes the database property "imaplogin" of the user with user id 4 to the users username. Previously another login mechanism was used because the mailserver authenticated against pam->ox database, now the groupware needs to authenticate via a ordinary imap login, just like any other imap client does. This needs to be done for every user.

Probelm after update

Server response:
Database is locked or is now beeing updated, please try again later

Log
SEVERE: Database is locked or is now beeing updated, please try again later
com.openexchange.admin.rmi.exceptions.DatabaseUpda teException: Database is locked or is now beeing updated, please try again later
at com.openexchange.admin.rmi.impl.OXUser.checkSchema BeingLocked(OXUser.java:1288)
at com.openexchange.admin.rmi.impl.OXUser.list(OXUser .java:1065)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastSe rverRef.java:294)
at sun.rmi.transport.Transport$1.run(Transport.java:1 53)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport. java:149)
at sun.rmi.transport.tcp.TCPTransport.handleMessages( TCPTransport.java:466)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandl er.run(TCPTransport.java:707)
at java.lang.Thread.run(Thread.java:595)