[Building Sakai] [oae-dev] Sakai 2+3 hybrid deployment scenario Clarifications

[N. Matthijs]

It is probably worth pointing out that there are different flavors
of a Sakai 2+3 hybrid deployment. The first one, which will make
your Sakai CLE sites visible inside of OAE through a dashboard
widget and will allow you to look at your CLE sites inside of the
OAE UI, will be supported when the v1.0.1 release is out
(scheduled October 12).

In this case, it probably makes more sense for the OAE UI to
be the main access point, as the CLE portal wouldn't have
any references to OAE.

Hope that helps,
Nicolaas

> Responses inline� L
>
> Lance Speelmon, VP Sakai Development
> rSmart | 602.840.7300
>
> On Sep 19, 2011, at 7:31 AM, Mustansar Mehmood wrote:
>
>> Questions
>> Please clarify if my understanding is  off?
>
> Your understanding seems correct.
>
>> Do both the database vendors have to be the same ?
>
> No - you could, for example, run Oracle for CLE and MySQL for OAE.
>
>> Which sakai (two or three?) be the main access point for users?
>
> That is a good question. It is mainly a deployment decision that you will
> need to maker locally. It could be either or both. :) Depending on whether
> you want your users to know about one URL or two, and which user
> populations you are ready to send to which portal by default.  Sorry to be
> so vague, but you really do have a lot of flexibility and you need to
> tailor the solution to your own local needs.
>
> _______________________________________________
> oae-dev mailing list
> oae-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/oae-dev
>