Skip Headers

Oracle® Student Learning Programmer's Guide Release 3.1.3 Part Number E20666-04 |
Home | Book List | Contents | Contact Us

Previous | Next
| PDF · Mobi · ePub

# 3 Overview

This chapter provides an overview of the OSL content integration interfaces.

OSL uses an External Content Management System (ECMS) for the rich data functionality used in instructions, overviews, journal details, and so on. This functionality allows an OSL user to insert hyperlinks and images, attach files and audios to a rich data. In addition, exported learning items are stored in the ECMS.

The following block diagram briefly explains the architecture of OSL interactions with ECMS.

Figure 3-1 OSL Interactions with ECMS

Figure 3-1 shows two interfaces of OSL Content Integration, one on the client-side (UI level integration) and the other on the back end (server-side integration).

These two interfaces are:

- Content Integration Client Interface (CICI)

- Content Integration Web Services Interface (CIWSI)

Table 3-1 list the terms used in OSL Content Integration.

Table 3-1 Definition of Terms

Term | Definition
--- | ---
Content Integration Backend | Implementation of CIWSI. OSL ships with a default implementation for Oracle Universal Content Manager (UCM), which uses RIDC to communicate with UCM back end.
ECMS UI | User interface rendered by the ECMS. There are two user interfaces that ECMS should render: ECMS Search Results UI ECMS Update Metadata UI OSL spawns these user interfaces as part of OSL functionality.
ECMS Update Metadata UI | User interface that is rendered by the ECMS for updating the metadata after publishing an exported learning item to ECMS.
ECMS Search Results UI | User interface that is rendered by the ECMS to list General Content.
Exported Learning Item | A package created after exporting learning item data. This package is in a ZIP format.
External Content Management System (ECMS) | Any Content Management System which supports versioning.
General Content | Content stored within ECMS and referenced within OSL and other applications such as portal or collaborative services. These are displayed in OSL as inserted hyperlinks and images in the rich data.
OSL Backend and ECMS Backend | The respective servers.
OSL Content | File attachment and audio that a user directly attaches to an OSL object. Such content is typically stored in the ECMS but partitioned separately from general content.
OSL Content User | Default back end implementation uses this UCM user to access OSL Content. This user should have RWD access to the Temporary and to the Permanent Accounts and OSL Storage Security Group.
OSL Context | Context in relation to the use of general content within OSL. For example, the class id, class name, and so on.
OSL Metadata User | The default back end implementation uses this UCM user to update the medata of General Content when associating context. This user should have RW access to all the General Content.
OSL Storage Security Group | The default back end implementation uses this UCM Security Group to store all the content that is checked in from OSL.
OSL UI | Teacher/Parent/Student Learning Tool user interface.
Permanent Space | Permanent space in the ECMS partitioned separately from General Content to store saved OSL Content.
Permanent Storage Account | The default back end implementation uses this UCM account to store permanently all OSL Content.
Rich Data | An OSL component that abstracts HTML content with inserted content references and images, file attachments, and audio recordings. This component is used for instructions, teacher overview, student overview, journal, submission, discussion, and observation details.
Search Filter | General Content listing filter. This filter could be used to filter out only the images, learning items, or any content type.

## 3.1 Content Integration Client Interface

The Content Integration Client Interface abstracts UI (browser) level interaction between the OSL UI and the ECMS UI. This service provides an interface for:

- Inserting General Content references to Rich Data

- Inserting an exported learning item into a lesson plan

The following URL abstracts the interface:

`http://<HOST:PORT>/<APP-ROOT>/common/default/richdata/script.jspx?cid=<CON-ID>&cvid=<CON-VER-ID>&curl=<CON-URL>`

It is expected that the ECMS UI should invoke this URL. Please refer to the Oracle Student Learning Installation and Deployment Guide for further details.

Table 3-2 List of Attributes

Name | Mandatory | Description
--- | --- | ---
HOST | Yes | Host of OSL Web (LTWeb) deployment.
PORT | Yes | Port of OSL Web (LTWeb) deployment. For LT that is SSO enabled, the port number should be the SSO port number.
APP-ROOT | Yes | Application root of OSL Web (LTWeb) deployment.
CON-ID | Yes | Content Identifier of content to be inserted to rich data or lesson plan.
CON-VER-ID | No | Content Version Identifier of content to be inserted to rich data or lesson plan.
CON-URL | Yes | Content URL.

## 3.2 Content Integration Web Services Interface

The Content Integration Web Services Interface (CIWSI) abstracts all ECMS interactions with OSL at the back end.

It comprises of three service interfaces:

- General Content Service

- OSL Content Service

- Publish Learning Item Service

For more related information about these service interfaces, see Chapter 4, "Web Services".

## 3.3 Security

CIWSI should be secured services and should use the following Security Policy:

- `oracle/wss_username_token_service_policy`

  This security policy requires username and password tokens in the SOAP Header. It is expected that OSL communicates with CIWSI using a single dedicated user. For related information about user configuration, see the Oracle Student Learning Installation and Deployment Guide.

## 3.4 WSDL and XSD files

The WSDL and the associated XSD files are available in the product install footprint. Navigate to `<OSL_INSTALLATION_DIR>/ContentIntegration/wsdl` to locate these files.