Home
>
7. what projects have done
>
7.6 Re-usability
|
Previous
Next
|
|
|
|
|
|
|
|
Lots of working uPortal implementations, some at large US Universities. See uPortal Home page
http://mis105.mis.udel.edu/ja-sig/uportal/ .
|
|
The fact that the foundation on which GIMIS is built (ColdFusion) is scalable, the core database (MySQL)
is designed to handle replication and linked with the variety of data connections that GIMIS can handle,
the groundwork is set for a scalable system.
|
|
So far, so good. For example, the lecture attendance monitoring and recording system managed three
concurrent modules at different lecture theatres. The online enrolment copes with approx. two hundred
students enroling over a one hour period. As most of the services simply require a web browser then
client access can be spread out, avoiding high peak loads. There have been no signs of scalability
problems from mySQL, Tomcat, or Linux.
|
|
MARTINI is meant to integrate within the UEA IT network so that all network infrastructure, authentication
measures and content is scaleable to a university-wide extent. Hardware is specifically purchased with
the specification that it can handle numerous simultaneous accesses. Both users and data providers are
included in planning process so as to ensure acceptance and discovery of people and process issues.
|
|
SMILE is meant to integrate within the University of Sunderlands IT network, VLE (WebCT) and Student
Academic System (SITS) so that all network infrastructure, authentication measures and content is
scaleable to a university-wide extent. Hardware is UNIX based to comply with the University strategic plan.
|
|
Technically scalable by:
Multiple Servlet engines
Distributing EJBs and placing most business logic in EJBs
Run LDAP cache on separate hardware
Performance exceeds expectations with three sources on one machine
|
|
|
|
It should be reasonably easy to exchange data where XML and IMS are used. Where projects use Java
and/or XSLT there may also be scope for sharing certain classes or stylesheets. It should be easy to
share uPortal channels, if any of the other projects are using uPortal. The use of LDAP as an
authentication service provides a valuable common denominator from an integration point of view.
|
|
Where the other projects either require or produce a dataset, we can easily integrate that data. Where the
result of the other system is a displayed output (e.g. a web page), we can easily integrate both the result
and the request stream, either as a discrete page or as an embedded function. The use of LDAP-based
Active Directory as an authentication service provides a valuable common denominator from an
integration point of view.
|
|
The project has investigated using XML for a common student record exchange format.
To the extent that the software technologies are common, it could in principle interact with other database-
driven web-interface style systems
|
|
As many of the standards used amongst the 7/99 projects are similar, technical solutions may well be
able to be incorporated by MARTINI (eg. an IMS-XML "converter" that is better than our solution). However,
some projects have such specific parameters (eg. CoMantle using Colloquia) that interoperability may
not be possible. The use of LDAP as an authentication service provides a valuable common denominator
from an integration point of view.
|
|
Potentially - the Zope + CMF + Plone framework is open source and subscribes to open standards. The
CMFPortlet development (http://www.zope.org/Members/ausum/CMFPortlets) demonstrates what would
be required for Zope + CMF + Plone to become an agnostic framework that could compete with the likes
of uPortal; at present, though, CMFPortlets seem a one-man show. The use of LDAP as an
authentication-authorisation service provides a valuable common denominator from an integration point
of view.
|
|
TISR is a general metadirectory, potentially able to transform any input into (or from) IMS Enterprise, or
other XML formats. Integration prospects are good.
|
|
|
|