5 Plugging in an Alternate Implementation

This chapter describes the process of how to plugin an alternate implementation of the OSL Content interfaces.

5.1 Plugging in an Alternate Backend Implementation

If required, an alternative implementation can be plugged in to OSL. This involves the following steps:

• Implementing CIWSI as expected by OSL and deploying it

• Configuring OSL to communicate with the alternate implementation

• Configuring security to access the alternate implementation

After configuration, OSL must be redeployed.

5.1.1 Configuring OSL to Connect to Alternate Backend Implementation

After implementing and deploying the alternate back end implementation, set the following properties in the OSL configuration file:

• osl.lt.service.content.contentProxytype: must be set to WS

• osl.lt.service.content.wsProxyGeneralContentServiceURL: service end point of the General Content Service Implementation

• osl.lt.service.content.wsProxyOSLContentServiceURL: service end point of the OSL Content Service Implementation

• osl.lt.service.content.wsProxyPublishServiceURL: service end point of the Publish Service Implementation

5.1.2 Configuring Security

OSL expects the alternate back end implementation to meet the security requirement as explained earlier. For related information, see the Oracle Student Learning Installation and Deployment Guide.

5.2 Plugging in with an Alternate ECMS UI

It is expected that the ECMS UI is customized according to the customer's specific needs. To help integrate the customized ECMS UI with OSL, a sample Reference Implementation for Oracle Universal Content Management (Oracle UCM) is provided with OSL. For further details, see the Oracle Student Learning Installation and Deployment Guide. You can also refer to the Readme.txt provided in the Reference Implementation package.