User:Malasa: Difference between revisions

From Open-Xchange
No edit summary
No edit summary
 
(10 intermediate revisions by 2 users not shown)
Line 1: Line 1:
Hello world
Hello world - justatest


Open-Xchange Architecture Overview
---- everthing below is wip ----


[[File:ox_architecture.png]]
==POC installation==


<span style="background:#FFFF00">User                                                                                                  </span>
This document shows the requirements of some typical proof of concept installations.
*1 All communication from and to the user can be encryptet with HTTPS
*2 Im/Export of userdata:
** General [[HTTP API]] overview
** [[Using the import servlet]], [[Building an importer]]
** [[Using the export servlet]], [[Building an exporter]], [[ Export icl/vard]],
*3 [[OX Mobile Web App]]
*4 [[OXtender for Business Mobility Installation Guide]]
*5 [[OXtender 2 for Microsoft Outlook]]
*6 [[Caldav carddav Bundles]], [[SetUpMacCalCardDAVClients|Setup Mac Cal/CardDAV Clients]]
*7 webdav


<span style="background:#FFA500">Administrator
A POC can be make with different setups, depending on the goal of the installation.
</span>
*11
*12 [http://software.open-xchange.com/OX6/doc/OX6-Provisioning/ Comandline tools]
*13 RMI [http://software.open-xchange.com/OX6/doc/RMI/admin-core/ Core] API, RMI [http://software.open-xchange.com/OX6/doc/RMI/admin-hosting/ hosting] API
*14 [[Open-Xchange-SOAP]], [http://software.open-xchange.com/OX6/doc/SOAP/admin/OX-Admin-SOAP.html SOAP API], [[POAIntegrationGuide| POA integration guide]], [Open-Xchange_cPanel_Installation| cPanel installation]]
*15 Athentification via plugins
**[[Authentication IMAP Plugin description]]
**[[OX and Samba Login through LDAP]]
** Database
** custom
*16 [[OX_monitoring_interface]], [[OX_munin_scripts]]


<span style="background:#E5E5E5">Backend
The goals could be:
</span>
* test Open-Xchange in general
*21
* test with existing environment
*22
* test a clustered setup
*23
*24 Mail Abstraction Layer
*25 Storage
** NFS
** Local filesystem
** custom


<span style="background:#00FF00">Social/Public Data</span>
*31 Integration of google calendar
*32 External messaging services: Facebook, Twitter, SMS/MMS
*33 Contacts integration from Xing, LinkedIN (configurable via the wizard)
*34 External email accounts can be integrated as long the provide pop3 or IMAP
** links zum wizard


<span style="background:#D8E5E5">Plugins</span>
It should be defined what the customer wants to test:
* webmail/groupware/infostore
* Outlook oxtender
* Business mobility (EAS)
* mobile gui
* everything
 
 
Here are some examples of the sizing of a POC installation. Usually 'small' should do it, if the customer wants to test with a lot of accounts (especially also EAS/Outlook) 'medium' is recommended.
 
{| class="poc size"
|-
|
! small
! medium
! cluster
|-
| Hardware
| VM, 2GB memory
| VM, 8GB memory
| 2x OX 8GB, 2x DB, external IMAP/SMTP, NFS, loadbalancer
|-
| Storage
| 20GB local
| 40GB local
| OX 40GB local, DB 20GB local, NFS 20GB
|-
| DB
| local
| local
| 2x DB VM/Server
|-
| SMTP/IMAP
| local/external
| local/external
| external
|-
|OS
|colspan="3" style="text-align: center;" |one of the supported (Debian6, RHEL5/6, CentOS5, SLES11)
|}
 
These are the minimum requirements. The used storage depends on the amount of users want to test the POC. A VM can be replaced with real hardware if wanted or run at a service provider in the cloud.
 
===1st mail to customer===
 
This is usually done during some calls, if not use this template. The second part, what we need, is always needed:
 
<pre>
Dear Customer,
 
The proof of concept installation  can be make with different setups, depending on the goal
you have.
 
please identify the goals:
* test Open-Xchange in general
* test with existing environment
* test a clustered setup
 
please identify what you want to test:
* webmail/groupware/infostore
* Outlook oxtender
* Business mobility (EAS)
* mobile gui
* webdav access (for the infostore)
* Mac OS X access
* everything
 
The smallest needed setup would be:
VM/real hardware with 2GB of memory, 20GB of local storage, an installed supported OS (Debian6, RHEL5/6, CentOS5, SLES11). If you want to test the system with https (which is recommended) we need a valid certificate for the server installed.
 
We need:
 
- server address/name
- ssh root access to the server from <our external ip's>, ssh keys attached
- http access  to the server from <our external ip's> on port 80 and/or 443 (if https is used)
- access to a working smtp and imap server if you want to send and receive mails.
- imap account of the testuser with password if applicable.
 
 
</pre>
 
===POC license key===
Order the license key from our sales department.
 
===Installation===
 
After getting back the needed information the system can be installed. Update the system first if necessary.
 
Adding the needed repositories (ox, updates!, oxtenders, mobile etc. if needed).
 
The Open-Xchange installation itself should be done as described in the [[Main_Page_HESE#quickinstall|installtion guide]].
 
The simplest thing is to use imap authentication.
 
2do:
push config
mobile config
webdav config
caldav/varddav
 
Custom plugins should be defined in a SOW.
 
====Branding====
A very small and quick branding would be the change of the [[Gui_Plugin_Development|window title]], this will help you too, and maybe a change of the logo. Extended branding should be defined in a SOW.
 
====Testing====
 
All installed plugins have to be tested.
 
2do: a list of tests
 
===2nd mail to customer===
<pre>
Dear customer,
 
the setup of the server is ready.
 
url:<pocurl>
user:<testuser/password>
 
You can create new accounts as user root on the comandline on the server. Keep in mind that you first have to create the needed imap accounts as well.
 
2do: <insert an example cmdline createuser with prefilled data>
 
You can find more information about the groupware handling if you click on the question mark in the upper right corner and select help.
 
<use the sections if applicable>
If you want to test Outlook, please look at the [http://software.open-xchange.com/OX6/doc/Outlook-OXtender/OX6-OXtender2-for-Microsoft-Outlook-English.pdf documentation]
 
2do: more documentation sections for other plugins.
 
</pre>

Latest revision as of 07:46, 10 September 2015

Hello world - justatest


everthing below is wip ----

POC installation

This document shows the requirements of some typical proof of concept installations.

A POC can be make with different setups, depending on the goal of the installation.

The goals could be:

  • test Open-Xchange in general
  • test with existing environment
  • test a clustered setup


It should be defined what the customer wants to test:

  • webmail/groupware/infostore
  • Outlook oxtender
  • Business mobility (EAS)
  • mobile gui
  • everything


Here are some examples of the sizing of a POC installation. Usually 'small' should do it, if the customer wants to test with a lot of accounts (especially also EAS/Outlook) 'medium' is recommended.

small medium cluster
Hardware VM, 2GB memory VM, 8GB memory 2x OX 8GB, 2x DB, external IMAP/SMTP, NFS, loadbalancer
Storage 20GB local 40GB local OX 40GB local, DB 20GB local, NFS 20GB
DB local local 2x DB VM/Server
SMTP/IMAP local/external local/external external
OS one of the supported (Debian6, RHEL5/6, CentOS5, SLES11)

These are the minimum requirements. The used storage depends on the amount of users want to test the POC. A VM can be replaced with real hardware if wanted or run at a service provider in the cloud.

1st mail to customer

This is usually done during some calls, if not use this template. The second part, what we need, is always needed:

Dear Customer,

The proof of concept installation  can be make with different setups, depending on the goal
you have.

please identify the goals:
* test Open-Xchange in general
* test with existing environment
* test a clustered setup

please identify what you want to test:
* webmail/groupware/infostore
* Outlook oxtender
* Business mobility (EAS)
* mobile gui
* webdav access (for the infostore)
* Mac OS X access
* everything

The smallest needed setup would be:
VM/real hardware with 2GB of memory, 20GB of local storage, an installed supported OS (Debian6, RHEL5/6, CentOS5, SLES11). If you want to test the system with https (which is recommended) we need a valid certificate for the server installed.

We need:

- server address/name
- ssh root access to the server from <our external ip's>, ssh keys attached 
- http access  to the server from <our external ip's> on port 80 and/or 443 (if https is used)
- access to a working smtp and imap server if you want to send and receive mails. 
- imap account of the testuser with password if applicable.


POC license key

Order the license key from our sales department.

Installation

After getting back the needed information the system can be installed. Update the system first if necessary.

Adding the needed repositories (ox, updates!, oxtenders, mobile etc. if needed).

The Open-Xchange installation itself should be done as described in the installtion guide.

The simplest thing is to use imap authentication.

2do: push config mobile config webdav config caldav/varddav

Custom plugins should be defined in a SOW.

Branding

A very small and quick branding would be the change of the window title, this will help you too, and maybe a change of the logo. Extended branding should be defined in a SOW.

Testing

All installed plugins have to be tested.

2do: a list of tests

2nd mail to customer

Dear customer,

the setup of the server is ready. 

url:<pocurl>
user:<testuser/password>

You can create new accounts as user root on the comandline on the server. Keep in mind that you first have to create the needed imap accounts as well.

2do: <insert an example cmdline createuser with prefilled data>

You can find more information about the groupware handling if you click on the question mark in the upper right corner and select help.

<use the sections if applicable>
If you want to test Outlook, please look at the [http://software.open-xchange.com/OX6/doc/Outlook-OXtender/OX6-OXtender2-for-Microsoft-Outlook-English.pdf documentation]

2do: more documentation sections for other plugins.