Skip Headers

Oracle® Student Learning Implementation Guide Release 3.1.3 Part Number E21072-04 |
Home | Book List | Contents | Contact Us

Previous | Next
| PDF · Mobi · ePub

# D Default Content Integration

This release ships with default integration with Oracle Universal Content Management (UCM) and can be used with UCM straight out of the box.This appendix provides content configurations that may be easily and quickly applied to a default deployment of UCM 11g, which is known as "DCI" as described in Chapter 5.

## D.1 Prerequisites

Oracle Universal Content Management Content Server 11g has to be installed and Oracle Universal Content Management Inbound Refinery 11g is recommended for installation as well.

## D.2 Configuring Content Server

Log in to Content Admin Server.

### D.2.1 OSL Content Users

Users defined below have to be set up in Content Server using the User Admin applet.

Table D-1 Users definition

Users | Roles | Security Groups | Accounts
--- | --- | --- | ---
oslcontent | OSLSystemRole | OSLDocuments(RWDA), Public(RW) | OSL/oslcontent/main(RWDA)
oslmetadata | OSLMetadataRole | OSLDocuments(RWDA), Public(RW) | OSL(RWDA) All accounts(RWDA)

### D.2.2 Additional Configuration Variables

Click the General Configuration link. Add the following new configuration variables to the list of Additional Configuration Variables.

Table D-2 List of configuration variables

Variable Name | Variable Value | Usage
--- | --- | ---
SearchIndexerEngineName | OracleTextSearch | Index content items
CustomWebRoot | http://ipadderss:port | Content Server IP address, port
CustomParentLocation | http://ipadderss:port | LT IP address, port

### D.2.3 Content Security

Click the Content Security link. Enable the Allow author to delete revision option.

### D.2.4 Override Configuration Variables

Configuration variables listed below are set to default values by a custom component, so these variables should be commented from the list of Additional Configuration variables.

- IsAutoNumber= false

- AutoNumberPrefix=

- UseAccounts=false

## D.3 Component Deployment

Perform the following steps to deploy components.

### D.3.1 Custom Components Deployment

Click Component Manager and click Advanced Component Manager link. Then install and enable the custom components, which are available under `<OSL_INSTALL_DIR>/LearningTool/ContentIntegration/components/` folder.

1. OSL_Add_Cancel.zip

2. OSL_AdvSearchComponent.zip

3. OSL_CheckinLayout

4. OSL_ClassicSearchTemplate.zip

5. OSL_CustomAction.zip

6. OSL_DefaultEnv.zip

7. OSL_Home_Page_Content.zip

8. OSL_InterfaceChanges.zip

9. OSL_Javascript.zip

10. OSL_LocaleString.zip

11. OSL_RemoveStandardProfileLinks.zip

12. OSL_RemoveSwitchProfile.zip

13. OSL_School.zip

14. OSL_SearchResults.zip

15. OSL_SearchTemplate.zip

### D.3.2 Standard Components Deployment

1. If your UCM is already configured, do the following:

   1. Click Component Manager.

   2. Disable and then uninstall the SelectivelyRefineAndIndex component.

   3. Go to `<OSL_INSTALL_DIR>/LearningTool/ContentIntegration/components`, and then install and enable OSL_SelectivelyRefineAndIndex.zip.

2. If your UCM is not yet configured, do the following:

   1. Click Component Manager.

   2. Go to `<OSL_INSTALL_DIR>/LearningTool/ContentIntegration/components`, and then install and enable AdditionalSortFields.zip and OSL_SelectivelyRefineAndIndex.zip.

3. Restart the Content Server.

## D.4 UCM Schema Setup

1. Select Admin Applets from the Administration menu.

2. Click the Configuration Manager applet. This pops up the applet.

### D.4.1 Create Table

Click the Tables tab. Click the Create table button. Create two tables as specified below:

Table D-3 School

Name | Type | Primary
--- | --- | ---
SchoolId | Int | Yes
SchoolName | varchar(500) |
dDocAccount | varchar(100) |

Table D-4 Scope

Column | Data Type | Primary Key
--- | --- | ---
ScopeId | Int | Yes
ScopeName | varchar(500) |

Table D-5 Visibility

Column | Data Type | Primary Key
--- | --- | ---
dName | varchar(50) | Yes
dDescription | varchar(50) |

Table D-6 YesNo

Column | Data Type | Primary Key
--- | --- | ---
dName | varchar(25) | Yes
dDescription | varchar(25) |

Note:

On completion of all the setup, ensure that the School and Scope information are in sync with the OSL data. Refer to the script DB_Insert.sql available in <OSL_INSTALL_DIR>/LearningTool/ContentIntegration/scripts/ucm folder.

### D.4.2 Create View

Click the Views tab. Create two views as specified below:

Table D-7 Creating Views

View Name | Internal Column | Visible Column | Default Display Expression | Display (DisplayRule for all Locales) | Security
--- | --- | --- | --- | --- | ---
School_View | SchoolId | SchoolName |  |  | Select Use standard document security.
Scope_View | ScopeId | ScopeName |  |  |
Visibility_View | dName | dDescription | <$dDescription$> | <$lc(dDescription)$> |
YesNoAlt_View | dName | dDescription | <$dDescription$> | <$lc(dDescription)$> |

## D.5 Custom Metadata

1. Log in to Content Server user interface as administrator.

2. Select Admin Applets from Administration Menu.

3. Click the Configuration Manager applet. This pops up the applet.

4. Add the metadata listed below in the Informations tab.

   Table D-8 List of metadata

   Metadata Name | Metadata Type | Enabled in User Interface | Enabled for Search Index | Enable Option List | Use View | Field Caption | Select List Validated
   --- | --- | --- | --- | --- | --- | --- | ---
   Scope | Text | Yes | Yes | Yes | Scope_View | wwxScope | Yes
   Visibility | Text | Yes | Yes | Yes | Visibility_View | wwxVisibility | Yes
   Endorsed | Text | Yes | Yes | Yes | YesNoAlt_View | wwxEndorsed | Yes
   Searchable | Text | Yes | Yes | Yes | YesNoAlt_View | wwxSearchable | Yes
   OSL_SchoolId | Long Text | Yes | Yes | Yes | School_View | wwxSchool | Yes
   OSL_Tag | Long Text | Yes | Yes | No | None | wwxTag | No
   OSL_FrameworkItemId | Long Text | Yes | Yes | No | None | wwxFrameworkItem | No
   OSL_OutcomeStatementId | Long Text | Yes | Yes | No | None | wwxOutcomeStatement | No

   When the custom metadata are created, click the Update Database Design button found on the right of the screen. Only then, the changes get committed. Then go to options and click Publish Schema. Then click Options -> Exit to exit the screen.

   Now, it is recommended to restart the UCM Content Server.

## D.6 Add Profile Options

Click the Edit Values button for IdcProfile metadata listed in the Informations tab.

Click the Add button. Add the dProfileTriggerValue that are listed below with the same dProfileTriggerOrder 11.

- OSLPublic

- OSLSchool

- OSLDepartment

- OSLSchoolNotEndorsed

## D.7 Advanced Search Design

Click Advanced Search Design to modify the settings. The metadata that are defined as Filter Category are:

- Content Type (dDocType)

- Format (dFormat)

- Scope (xScope)

- Endorsed (xEndorsed)

Edit the metadata that are listed above and enable the Is a filter category option.

## D.8 Rules

Click the Rules tab. Select and delete the default HideStandardRules if it is listed.

## D.9 Roles/Groups/Permissions

Roles defined in the Content Server should match the OSL roles defined in OID. Create the Roles using User Admin applet.

1. Select Admin Applets from the Administration menu.

2. Click the User Admin applet. This pops up the applet.

   Table D-9 Creating Roles, Groups, and Permissions

   Role | Group | Permission
   --- | --- | ---
   SchAdminGroup | Public | RWDA
   DeptAdminGroup | Public | RWDA
   TeacherGroup | Public | RWD
   ParentGroup | Public | R
   StudentGroup | Public | R

## D.10 DCI Configuration Assistant

The steps to run DCI Configuration Assistant are given below:

1. Unzip DCI_Config_Assistant.zip file on to the server directory in which UCM is installed.

2. Modify the dci_configuration property that is available in EXTRACT_DIR/config/.

   Table D-10 Configuration property

   Property Name | Valid Value (Do not change) | Sample Property Value
   --- | --- | ---
   osl.dci.cs.url |  | idc://ipaddress:port ipaddress – Content server port –Intradoc port
   osl.dci.cs.username | sysadmin | Conent server admin username
   osl.dci.cs.password | idc | Content server admin password
   osl.dci.rule.src.path | ./rule/ |
   osl.dci.rule.dest.path |  | <UCM_DOMAIN_HOME>/cs/data/profiles/docum
   osl.dci.profile.src.path | /profile/ |
   osl.dci.profile.dest.path |  | <UCM_DOMAIN_HOME>/cs/data/profiles/docum
   osl.dci.search.pne.src.path | /searchtemplate/ |
   osl.dci.search.pne.dest.path |  | <UCM_DOMAIN_HOME>/cs/data/users/profiles/
   osl.dci.search.template.src.path | /searchtemplate/customlisttemplates/ |

   Log in to EM Console. Click Servers -> Content Server -><UCM server instance name>. Click the configurations link and check if IP address filter and the intradoc port have been set properly. For related information, see Oracle Student Learning Installation and Deployment Guide.

   Note:

   UCM_DOMAIN_HOME is the UCM directory inside the WebLogic domain of the UCM installation.

3. Ensure the JDK used to run the DCI Config Assistant is the latest, for example, JDK 1.6.To run the DCI Config Assistant run the following command:

       java -jar DCI_Config_Assistant.jar

4. Individual actions can be performed with the following commands:

       java -jar DCI_Config_Assistant.jar "Add Rule"
       java -jar DCI_Config_Assistant.jar "Copy Rule"
       java -jar DCI_Config_Assistant.jar "Add Profile"
       java -jar DCI_Config_Assistant.jar "Copy Profile"
       java -jar DCI_Config_Assistant.jar "Copy Template"

   Note:

   Initially, Search Templates are created for administrator user only. Only when a user has successfully logged in to the Content Server at least once, the search templates can be added. This can be accomplished by executing the DCI Configuration Assistant with "Copy Template" parameter.

## D.11 Inbound Refinery Setup

IBR server must be added as a Provider for Content Server before making any configuration changes.

1. Log in to Content Server user interface as administrator.

2. Click the Administration menu.

3. Click the Providers link.

   Verify that IBR is listed as an "Outgoing" provider.

   If the IBR provider is not listed, create a new Provider for IBR.

4. To create a new Provider for IBR.

   1. Click Add.

   2. Enter the details of the Inbound Refinery server:

      - Provider Name: IBR
      - Provider Description: IBR Provider
      - Server Host Name: IP address for IBR server
      - HTTP Server Address: <IP Address for IBR>:<IBR port>
      - Server Port: 5555
      - Instance Name: IBR_server1
      - Relative Web Root: /ibr/
      - Convertion Options: Enable "Handle Inbound refinery Conversion Jobs".

### D.11.1 File Formats Wizard (Content Server)

1. Click the Administration menu.

2. Click the Refinery Administration link.

3. Click the File Formats Wizard and select the following File Types.

   - GIF 87 Image

   - JPEG Image

   - PNG

   - Windows Bitmap Image

   - TIFF Image

4. Click the Update button.

### D.11.2 Inbound Refinery Conversion Options (Content Server)

1. Click the Administration menu.

2. Click the Refinery Administration link.

3. Click the Conversion Options link.

4. Enable the "When a conversion sent to an Inbound Refinery fails, set the conversion to Refinery Passthru" option.

### D.11.3 Conversion Listing (Inbound Refinery)

Log in to Inbound Refinery server as administrator.

1. Click the Conversion Settings menu.

2. Click the Conversion Listing. Verify that the following entries are selected:

   - Image Thumbnail

   - Native Thumbnail

   - MultipageTiff

### D.11.4 Additional Renditions (Inbound Refinery)

Enable the Create Thumbnail Images using Outside In option.

## D.12 Using Content Server in Non-English Environments

To use the Content Server in non-English environments, you must perform the following configuration tasks before and after installing the Content Server.

1. Set database encoding to AL32UTF8.

2. Select Locale under Administration > Localization.

3. Set the server locale in System Properties > Server.

4. If you are an individual user, set the locale in your profile using the User Profile > Locale menu.

Additionally, enter any custom data setup according the server locale. For example, for custom metadata LOVs, enter data using the selected language.