Skip Headers
Oracle® Student Learning Installation and Deployment Guide
Release 3.1.3
Part Number E20664-04
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Feedback page
Contact Us
Go to previous page
Previous		 Go to next page
Next
PDF · Mobi · ePub

6 Configuring Oracle Universal Content Management Default Integration

Integrate the OSL Learning Tool with an External Content Management System (ECMS) from which users can add content when working with rich data. ECMS is also used as a file storage and delivery system to store and supply objects created and used in the OSL Learning Tool.

By default, this release is integrated with Oracle Universal Content Management (UCM). For information about the OSL content integration architecture, see Oracle Student Learning Programmer's Guide.

Note:

Section 6.1, "Content Server 10g Configuration", Section 6.2, "Content Server 11g Configuration", and Section 6.3, "Configuration of Content Servers 10g and 11g" are applicable for configuring the OSL default integration with Oracle UCM.

Configuring the OSL default integration with Oracle UCM involves the following:

Note:

All configuration on the OSL side is specified in the osl_configuration.properties file. The detailed description of each property is available in Section 9.1.5, "Updating Content Integration Configuration".

6.1 Content Server 10g Configuration

To configure Content Server 10g, perform the steps in the subsections.

6.1.1 Configuring OID as Security Provider for UCM

To allow access to all OSL users, configure UCM with an LDAP provider where the LDAP server is the OID used by OSL.

To configure the LDAP provider for UCM:

  1. Open a Web browser.

  2. Open the Oracle UCM URL.

  3. Log in as sysadmin.

  4. Choose Administration > Providers.

  5. Choose Add in ldapuser.

  6. Provide the following information:

    1. Provider name: OID

    2. Provider class: intradoc.provider.LdapUserProvider

    3. Connection class: intradoc.provider.LdapConnection

    4. Source Path: <A unique string that identifies the LDAP provider>

    5. LDAP server: <Host name or IP address of the OID server used by OSL>

    6. LDAP suffix: <LDAP suffix of user base DN. Example: dc=...>

    7. LDAP port: <Port of the OID server used by OSL>

    8. Use Group Filtering: select

    9. Role Prefix: cn=Groups

    10. LDAP Admin DN: <administrator account of OID, Example: cn=orcladmin>

    11. LDAP Admin password: <password of the OID administrator>

  7. Restart Oracle UCM.

  8. Log in to Oracle UCM again.

  9. Select Administration > Providers.

  10. Verify that the connection status of the new LDAP Provider is Good.

You can find information about External Security:LDAP in Managing Security and User Access for Content Server in the Oracle Universal Content Management Documentation at

http://download.oracle.com/docs/cd/E10316_01/ouc.htm

6.1.2 Enabling Intradoc Communication

Communication between the default OSL content integration with Oracle UCM is made through the Intradoc protocol. To enable such communication, configure Oracle UCM to trust the OSL server.

  1. Log in to the Oracle UCM server.

  2. Open the $UCM_HOME/server/config/config.cfg file.

  3. Add the IP address of the server where you want to deploy OSL Learning Tool, to the SocketHostAddressSecurityFilter property.

  4. Restart the UCM server.

    1. Log in to Oracle UCM web from browser as sysadmin.

    2. Select Administration > Admin Server to launch the UCM Admin Server web.

    3. Click Restart for the appropriate UCM server instance.

6.2 Content Server 11g Configuration

To configure Content Server 11g, perform the steps in the subsections.

6.2.1 Configuring OID as Security Provider for Content Server 11g

Set up the Content Server to use OID as the security provider.

To define a Security Provider for UCM WLS:

  1. Open the UCM WLS Administration Console:

    http://<UCM_WLSHostName>:<UCM_WLS_PORT>/console

  2. Log in to the console using an administrator account.

  3. In the UCM WLS console, select Security Realms > myrealm (default) > Providers (tab).

  4. In the Authentication Providers table, select New.

  5. Enter a name for the authentication provider in the Name field, for example OSL_OID.

  6. Choose OracleInternetDirectoryAuthenticator from the Type list.

  7. Click OK.

    An authentication provider is created in UCM WLS.

  8. On the Providers tab, select the new authentication provider instance to navigate to its configuration page.

  9. Select the Provider Specific tab under the Configuration tab.

  10. Edit the properties in the Provider Specific configuration as shown in Table 6-1.

    Table 6-1 Provider Specific Properties

    Attribute Value Meaning

    Host

    <OID hostname>

    		  

    Port

    3060

    Default non-SSL OID port

    Principal

    cn=orcladmin

    Administrator account to connect to OID

    Credential

    <orcladmin password>

    Password for OID administrator account

    Confirm Credential

    <orcladmin password>

    		  

    User Base DN

    <OID User Search Base>

    Value of the User Search Base attribute in OID. You can find this value on the OID administration page.

    The format of this value is: cn=users, dc=...

    Use Retrieved User Name as Principal

    Check

    Specifies whether the user name retrieved from OID is used as the Principal in the Subject.

    Group Base DN

    <OID Group Search Base>

    Value of the Group Search Base attribute in OID, can be looked up in the OID administration page.

    Value looks like: cn=Groups, dc=…

    Propagate Cause for Login Exception

    Check

    Propagates OID exceptions to ECM WLS to show in the console and logs.

  11. Click Save.

  12. Restart the UCM WLS instance.

  13. Log in to the UCM WLS console.

  14. Select Security Realms > myrealm (default) > Users and Groups (tab).

    You can see the OID Users and Groups.

  15. Modify the Control Flag attribute of the security provider so that OSL users must be authenticated only against OID:

    1. Select Security Realms > myrealm (default) > Providers > [security provider name] > Configuration > Common.

    2. Set Control Flag to Sufficient.

  16. Reorder the new security provider to be the first authentication provider.

  17. Restart the UCM WLS instance.

In addition to the above configuration, you must:

  • Add two users, oslcontent and oslmetadata, to the DefaultAuthenticator.

  • Set default passwords for these users.

6.2.2 Enabling Intradoc Communication

To enable Intradoc communication:

  1. Log in to UCM Enterprise Manager.

  2. Click Farm > Content Management > Universal Content Management > Content Server > Oracle UCM - Content Server.

  3. From the menu, select the UCM > Configuration.

  4. Enter a value for Intradoc ServerPort.

  5. Add the IP address of the server to which to deploy OSL Learning Tool, to the IP Address Filter property.

  6. Restart the Admin Server and Content Server.

6.2.3 Setting the Content Type

The predefined document types available in Content Server 11g include Application, Digital Media, and Document. You can set one of these values in the OSL configuration properties file as follows:

osl.lt.content.ucmIntegration.oslContentDoctype=Application

6.3 Configuration of Content Servers 10g and 11g

Below are the configuration steps for Content Server 10g and 11g.

6.3.1 Configuring the Default Server Integration

OSL provides default implementation of the Content Integration Web Services Interface to communicate with Oracle UCM. To support this implementation, configure the following:

  • Web service end point URIs

  • Configurations related to General Content storage and access

  • Configurations related to General Content reference metadata tagging

  • Configurations related to OSL Content storage and access

  • Configurations related to exported learning item storage and access

Ensure that all the mandatory properties that do not have default values are assigned valid values. For more information, see Chapter 9, "Deploying OSL Learning Tool Admin and OSL Learning Tool".

6.3.1.1 Configuring Web Service End Point URLs

By default, the OSL content integration does not use Web service to communicate with the OSL Learning Tool server. You can ignore this section if you are using the default OSL content integration.

However, if you are developing a custom implementation of content integration, you must expose the implementation as a set of web services. This functionality is specified in the "Content Integration Web Services Interface" section of the Oracle Student Learning Programmer's Guide. You must update the following properties in the OSL configuration file:

  • osl.lt.service.content.contentProxytype: 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

6.3.1.2 Configuring General Content Storage and Access

Information about configuring General Content Storage and access is available in Oracle Student Learning Implementation Guide.

6.3.1.3 Configuring General Content Reference Metadata Tagging

The default Content Integration supports metadata tagging for General Content. For detailed information about associateContent service, see Oracle Student Learning Programmer's Guide. The default setting assumes that the required OSL related metadata fields are available in Oracle UCM. You must map these metadata fields to OSL context fields in the OSL configuration file. When a General Content document is referenced from OSL Learning Tool, context information is associated to that document as metadata for each mapping.

Configuring General Content Reference Metadata involves:

  • Configuring the mapping of OSL context to UCM metadata.

  • Configuring metadata users to tag General Content documents with the OSL context.

  • Configuring searchability based on the OSL context.

The following properties map the OSL context to UCM metadata:

  • osl.lt.content.ucmIntegration.metadata.OutcomeStatementId = xOSL_OutcomeStatementId

  • osl.lt.content.ucmIntegration.metadata.FrameworkItemId = xOSL_FrameworkItemId

  • osl.lt.content.ucmIntegration.metadata.CourseTagName = xOSL_Tag

The default values are given for each property. The naming of custom metadata can vary depending on individual UCM setup.

To associate metadata with a General Content reference, OSL must have write permission to the General Content. Therefore, you must create a special user that has write permission on all security groups encompassing General Content. This user is named OSL metadata user. The role of this user is named OSL metadata role. See Table 6-2, "Configuring OSL Metadata User" for details:

Table 6-2 Configuring OSL Metadata User

User Role Security Groups Accounts

oslmetadata

OSL metadata role

  • OSL Documents (RWDA)

  • Public (RW)

  • OSL (RWDA)

  • All accounts (RWDA)

The following properties allow configuring the searchability of General Content based on OSL context.

  • osl.lt.content.ucmIntegration. search.FrameworkItemId

  • osl.lt.content.ucmIntegration. search.OutcomeStatementId

  • osl.lt.content.ucmIntegration. search.CourseTagName

For each property mentioned above, you can set a search substring such as "Metadata-Name <matches> '%1s'". This search substring is used to build the search URL.

6.3.1.4 Configuring OSL Content Storage and Access

OSL content is stored in a security group called OSLDocuments (the OSL Storage Security Group).

  1. Log in to Content Server.

  2. Click Administration.

  3. Click Admin Applets.

  4. Create and configure the OSL content user as specified below:

    Table 6-3 Configuring OSL Content User

    User Roles Security Groups Accounts

    oslcontent

    OSLSystemRole

    OSLDocuments(RWDA), Public (RW)

    OSL/oslcontent/main(RWDA)

6.3.1.5 Configuring Exported Learning Item Content Storage and Access

To configure exported learning item content storage and access, create and configure TeacherGroup as specified in Table 6-4, "Configuring TeacherGroup":

Table 6-4 Configuring TeacherGroup

Roles Security Groups Accounts

TeacherGroup

Public(RWD)

Public(RWD)

OID is the security provider for UCM. Therefore you must define the account in OID. For details on configuring OID, see Appendix D and E of the Oracle Student Learning Implementation Guide.

Configuring Parameters in OSL

After configuring content storage and access in Oracle UCM, update the OSL configuration file with the input value. The configuration properties include:

  • osl.lt.content.ucmIntegration.oslContentDoctype = Application

  • osl.lt.content.ucmIntegration.oslContentSecurityGroup = OSLDocuments

  • osl.lt.content.ucmIntegration.oslContentUser = oslcontent

  • osl.lt.content.ucmIntegration.oslContentMainAccount = OSL/oslcontent/main

  • osl.lt.content.ucmIntegration.oslContentAutoDocname = false

  • osl.lt.content.ucmIntegration.publishedContentSecurityGroup = Public

  • osl.lt.content.ucmIntegration.publishedContentAccount = Public

  • osl.lt.content.ucmIntegration.publishedContentProfile = OSLPublic

The default values are given for each property. The naming of users, accounts, security groups, and so on, can vary depending on individual UCM setup.

6.3.2 Content UCM Reference Client Integration

OSL includes a reference implementation of the Content Integration Client Interface. This implementation adds an option to add selected content items to OSL for two scenarios:

  • Inserting a General Content reference to rich data

  • Inserting a published learning item to a lesson plan

  1. Log in to the Content Admin Server.

  2. Click General Configuration.

  3. Add the following new configuration variables to the Additional Configuration Variables list.

    Table 6-5 List of configuration variables

    Variable Name Variable Value Usage

    CustomWebRoot

    http://ipadderss:port

    Content Server IP address, port

    CustomParentLocation

    http://ipadderss:port

    LT IP address, port

  4. Click Component Manager.

  5. Install and enable the following custom components available in the <OSL installation directory>/LearningTool/ContentIntegration/components folder.

    • OSL_CustomAction.zip

    • OSL_Javascript.zip

    • OSL_LocaleString.zip

  6. Restart the Content server.

Go to previous page
Previous		 Go to next page
Next
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Feedback page
Contact Us