Hosting FAQ for System Integrators
Q: Where can i get access to software packages for the hosting environment?
A: Packages for download are available in the Open-Xchange maintenance portal
Q: Where can i get access credentials for the Open-Xchange portal
A: You need to register at the Open-Xchange web site
Q: Where can i get further assistance in case of installation/integration questions?
A: A forum for discussions is available on our web site
Q: How can i migrate my users and data from OX5 and OX EE to the new system
A: The recent (Beta-) Version of OX SE contains the pure groupware application. Front ends for administration as well as migration tools will follow later
Q: Is there a administration frontend to create and manage contexts, users, groups, resources
A: Provisioning is mormally done in a control center at hosters side. There, those tasks should be integrated.
Administration front ends for In-House deployments will follow soon.
Q: Where are the mails stored in the Open-Xchange server
A: The Open-Xchange server has no own email server included. The Open-Xchange server does access mailboxes from existing systems. Please have a look at our architecture white paper.
Q: What are the supported IMAP servers?
A: Currently, Cyrus, Dovecot and Courier are the supported IMAP servers. This is described in more detail in the installation manual.
Q: How can i create user objects (appointments,tasks,infostore items, pre defined UWA widgets) form extern for a customer?
A: you can use the JSON HTTP API used by the gui, a example is to be found here: Adding a pre defined UWA widget for a User
Q: What are UWA widgets for?
A: a description can be found in the Wiki on the Hyperion UWA page
Q: How can i have single sign on for my clients?
A: For implementing single sign on, easy login could be used
Q: I want to create my own login side for the Open-Xchange server. How can i do this?
A: Use easy login for this. A PHP example for easy login is also available.
Q: What APIs are available?
A: The APIs are to be found under Interfaces in this wiki
Q: Do i need to set module access for the context admin user and how do i do that?
A: for the context admin, all modules must be enabled the like the users in the context have
Q: Can the Open-Xchange GUI be used to replace my existing Webmail system?
A: Of course! the Open-Xchange GUI can be used to replace the existing Webmail system.
Q: When i create new users, they have only mail and contacts enabled, why?
A: The default module access is webmail, all others have to be enabled through te provisioning interface as described in the provisioning manual
Q: What is the context admin user for?
A: The context admin is a special user in the groupware who is able to log in to the GUI. This user gets shared items from deleted users on deletion.
Q: How do i report bugs to Open-Xchange?
A: Bugs are to be reported via the Open-Xchange ticket system. New tickets are created through an email to support@open-xchange.com. For those who have a support contract, the support registration code needs to be in the body of that email.
Q: Why is the link in notification mails broken?
A: The link is generated from the template in the configuration file /opt/open-xchange/etc/groupware/notification.properties
Q: Why do i get an error when i click on Extras in the groupware GUI?
A: Behind that extra link, there is a plugin which can also be a own developed one. The Default plugin, shipped with the software is to be configured in the file /opt/open-xchange/etc/groupware/configjump.properties
Q: What kind of authentication plugins are available?
A: The default plugin, shipped with the software, authenticates against the Open-Xchange
database. Other examples are included in the development documentation.
Q: How do i write a new authentication plugin so that authentication is done against my existing authority?
A: The manual for writing own plugins, can be found in the Open-Xchange Wiki
Q: Is there a limit for the number of users, groups and resources in a context?
A: basically there only is a theoretical limit of 2^31 for all together per context
Q: Why do resources need to have a email address and for what is it used?
A: A email address for a resource is required by outlook so that outlook is able to manage resources. The OX server does not sent emails to that address.