Frameset

The LMS must be able to function inside a frameset. Blackboard Learn will load the LMS pages inside a frame called top.content.

Web UI Changes

A number of small changes to the LMS Web UI will be required.  These changes are very LMS-specific. Here are a few examples of the changes made during the process of integrating CE4 and Vista:

• All HTML references to the frame top are replaced with top.content.
• Requests for the login page are redirected to AS's login page.
• A link is added from Vista's File Manager to the Content System file browser.
• The Logout link is hidden, since Blackboard Learn will manage this operation.

Authentication cookies

The LMS must be able to use cookie-based authentication, and these cookies must be issued for a domain that is common to both the LMS and AS server.

For example:

• Blackboard Learn server is running on as.mydomain.edu
• Campus Edition 6 server is running on ce6.mydomain.edu

In this scenario, the authentication cookie for Campus Edition 6 must use the domain .mydomain.edu, so that the Blackboard Learn server can issue cookies on its behalf.

Remote API

The LMS must provide some mechanism for accessing data (both reading and writing) from Java code executing on the Blackboard Learn server. If the LMS has an SDK that supports RPC, this is one way to access the data. Direct database access via JDBC would also be an option.

Communication Requirement

All LMS hardware must be set up to accept COBRA IIOP communication.