Oracle® Student Learning Implementation Guide Release 3.1.3 Part Number E21072-04 |
|
|
PDF · Mobi · ePub |
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.
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.
Log in to Content Admin Server.
Users defined below have to be set up in Content Server using the User Admin applet.
Click the General Configuration link. Add the following new configuration variables to the list of Additional Configuration Variables.
Perform the following steps to deploy components.
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.
OSL_Add_Cancel.zip
OSL_AdvSearchComponent.zip
OSL_CheckinLayout
OSL_ClassicSearchTemplate.zip
OSL_CustomAction.zip
OSL_DefaultEnv.zip
OSL_Home_Page_Content.zip
OSL_InterfaceChanges.zip
OSL_Javascript.zip
OSL_LocaleString.zip
OSL_RemoveStandardProfileLinks.zip
OSL_RemoveSwitchProfile.zip
OSL_School.zip
OSL_SearchResults.zip
OSL_SearchTemplate.zip
If your UCM is already configured, do the following:
Click Component Manager.
Disable and then uninstall the SelectivelyRefineAndIndex component.
Go to <OSL_INSTALL_DIR>/LearningTool/ContentIntegration/components
, and then install and enable OSL_SelectivelyRefineAndIndex.zip.
If your UCM is not yet configured, do the following:
Click Component Manager.
Go to <OSL_INSTALL_DIR>/LearningTool/ContentIntegration/components
, and then install and enable AdditionalSortFields.zip and OSL_SelectivelyRefineAndIndex.zip.
Restart the Content Server.
Select Admin Applets from the Administration menu.
Click the Configuration Manager applet. This pops up the applet.
Click the Tables tab. Click the Create table button. Create two tables as specified below:
Name | Type | Primary |
---|---|---|
SchoolId |
Int |
Yes |
SchoolName |
varchar(500) |
|
dDocAccount |
varchar(100) |
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.Click the Views tab. Create two views as specified below:
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)$> |
Log in to Content Server user interface as administrator.
Select Admin Applets from Administration Menu.
Click the Configuration Manager applet. This pops up the applet.
Add the metadata listed below in the Informations tab.
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.
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
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.
Roles defined in the Content Server should match the OSL roles defined in OID. Create the Roles using User Admin applet.
Select Admin Applets from the Administration menu.
Click the User Admin applet. This pops up the applet.
The steps to run DCI Configuration Assistant are given below:
Unzip DCI_Config_Assistant.zip file on to the server directory in which UCM is installed.
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.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
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.IBR server must be added as a Provider for Content Server before making any configuration changes.
Log in to Content Server user interface as administrator.
Click the Administration menu.
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.
To create a new Provider for IBR.
Click Add.
Enter the details of the Inbound Refinery server:
Click the Administration menu.
Click the Refinery Administration link.
Click the File Formats Wizard and select the following File Types.
GIF 87 Image
JPEG Image
PNG
Windows Bitmap Image
TIFF Image
Click the Update button.
Click the Administration menu.
Click the Refinery Administration link.
Click the Conversion Options link.
Enable the "When a conversion sent to an Inbound Refinery fails, set the conversion to Refinery Passthru" option.
To use the Content Server in non-English environments, you must perform the following configuration tasks before and after installing the Content Server.
Set database encoding to AL32UTF8.
Select Locale under Administration > Localization.
Set the server locale in System Properties > Server.
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.