ota guide

7/28/2019 Ota Guide

1/23

Integrating Oracle iLearning withOracle Training Administration

1

Integrating OracleiLearning withOracle TrainingAdministration

7/28/2019 Ota Guide

2/23

2 Using OTA and OiL

Using Oracle Training Administration with Oracle iLearning

The integration of Oracle Training Administration (OTA) with OracleiLearning (OiL) enables OTA customers to administer, design, and offeronline training events to their own employees.

The first phase of OTAs integration with OiL maintains each productsdistinct identity, using XML and concurrent processing to shuttleinformation between applications, combined with a selfserviceinterface to handle eclass enrollments and player access.

For general information concerning OiL, visit the OiL web site atwww.oracle.com/ilearning.

For specific information concerning OiL site administration within theintegration, see Oracle iLearning: Site Administration Guidelines forthe OTA Integration, available from Metalink.

For specific information regarding the creation and distribution ofRCOs and offerings within the integration, see Oracle iLearning:Content Assembly and Scheduling in the OTA Integration, availablefrom Metalink.

Terminology

OTA and OiL use different terms for a few key concepts. The terms areoften functionally equivalent, not exact: for example, OiL RCOs containthe actual course content, while activity versions only reference theresources that may constitute course materials.

OTA OiLActivity (Activity version) Reusable Content Object (RCO)

Event Offering

SelfPaced Event eClass, eSeminar, or eStudy(selfpaced)

Students Learners

Business Groups

OTA Business Groups, whether global or local, map onetoone withOiL Sites (called by the OiL Site ID). In other words, each OTABusiness Group can share data with just one OiL Site ID. MultipleBusiness Groups cannot share a single OiL site, nor can a singleBusiness Group share multiple OiL sites.

7/28/2019 Ota Guide

3/23


3

Concurrent Programs

OTA and OiL exchange information by way of three XMLbasedconcurrent programs:

iLearning User XML Export (page 9), which exports user data toOiL;

iLearning Content and Offering Import (page 11), which extractsRCO and Offering data from OiL; and

iLearning Performance Import (page 12), which obtains usertraining history data from OiL

For instructions on how and when to run these programs, see

OTAOracle iLearning Implementation Steps: page 6

Activities and Events

All OiL RCOs transfer into OTA as activities of the type OTAiLearning Activity (or another activity type you create and specify inthe OTA:Default Activity for iLearning system profile). You can query

imported RCOs as activities in the Activities window.In general, if you can update a field in one application, you cannotupdate it in the other. For example, RCOs imported from OiL preventdata entry into several fields in the Activities window. To changeinformation such as Activity Name, Description, Audience, andLanguage, you must change the RCO from within OiL, then import theRCO again.

SelfPaced Events

The integration uses a new event type and window called SelfPacedEvent. The window closely resembles the Scheduled Event window.When you import offerings from OiL, they become selfpaced orscheduled events, depending on the offering type.

You can query these events in their respective windows or search for

them in the Event Search window, just as you would any eventoriginating in OTA. The main difference is that, as with the importedactivities, you cannot update fields containing information originatingin OiL.

Note: You cannot create sessions for a SelfPaced Event.

7/28/2019 Ota Guide

4/23

4 Using OTA and OiL

Enrollments

OTA handles all enrollments. Do not enroll or unenroll learners fromthe OiL admin interface.

CrossChargingLearners can cancel enrollments if their status is Placed, Requested, orWaitlisted, but their cost center is charged once the OiL Player has run.

Learners can select a cost center from the popup list in the selfserviceenrollment window if:

crosscharging is enabled, and

crosscharging defaults to their primary assignment, and they are assigned to multiple cost centers

Approvals

Workflow defaults to SelfApproval. The implementation steps detailthe tasks necessary to require Manager Approval.

SelfService Interface

The integration employs a redesigned Oracle Training SelfServiceinterface. Features include:

Combined Enroll in a Class and Cancel Enrollment

Users can enroll and unenroll from the same set ofwindows.

Views

From a single starting point, users can view Current andPlanned Training, Cancelled Training, Completed Training,and Expired Training (for selfpaced events, contentproviders can set deadlines for course completion).

Additional Training

Managers and employees can view training events takenoutside of OTA in addition to those administered withinOTA.

Search Results

The Search Results window shows both Activities andEvents, and enables enrollment in the events shown.

7/28/2019 Ota Guide

5/23


5

Save For Later

Users can put transactions on hold for later retrieval andaction.

Dynamic Approvals

Users can select additional approvers from the Reviewwindow.

Configuration

System administrators have greater latitude in configuringthe user interface.

7/28/2019 Ota Guide

6/23

Step 1

6 Using OTA and OiL

OTAOracle iLearning Implementation Steps

OTA installed with... required steps optional steps

Oracle iLearning Step 1Step 10 Step 11Step 12

no Oracle iLearning none none

Oracle iLearning Implementation Guidelines

The Oracle iLearning site specifically serves internal users requiringboth webbased and instructorled training, and who are registeredusers within the OTA application. This integration does not currentlysupport external usersonly your organizations employees can enrollin and take courses originating in OiL. Create a separate site, or subsite, in OiL for these external users.

Note: For simplicity, throughout this document we abbreviateOracle iLearning to OiL.

The following instructions assume that you are familiar with thegeneral concepts of OiL. Each section describes the specificrequirements and restrictions in an OTAintegrated implementationonly. For detailed training and instructions on all OiL features andfunctionality refer to the OiL help system and online training courses.

OTA Setup for Oracle iLearning

The OTAside setup consists primarily of two tasks: setting systemprofiles and preparing for the transfer of data between OTA and OiL.Optional setup steps include workflow and selfservice configuration.

Before you begin your implementation of the integrated products,please review Using Oracle Training Administration with OracleiLearning: page 2.

Oracle iLearning: Perform Initial Site Setup

1. Create an OiL site. Contact your Oracle representative to obtainnecessary user information, including an administrator username

and password.2. Log in to your OiL site using the administrator username and

password.

Note: All usernames and passwords in OiL are case sensitive.3. From the Users tab, create one organization called OTA Learner.

This integration does not support multiple organizations.

7/28/2019 Ota Guide

7/23

Step 2

Step 3


7

4. Define default selfenrollment conditions for the OTA Learnerorganization. Select the site name in the navigator tree. Navigate toMore, then Manage Enrollment Conditions. Add OTA Learner tothe selfenrollment condition.

5. Define the languages available to content assemblers in OiL. On thesite properties page, enter the uppercase language codes found inthe standard Oracle Applications (FND) table (page 22). Enter thevalues from the Language_code column into the Name field. Notethat this list of language codes applies to content metadata only,not to the OiL interface itself. The language table does not indicatethe languages into which the OiL interface itself is translated.

Warning: Use only the languages and codes appearing in thetable. You must enter at least one language code.

6. Define Trusted URLs for the OiL site. Trusted URLs enable the userto be authenticated in OTA, then gain immediate access to the OiLplayer at run time.

Determine all URLs in OTA from where users will launch the OiLplayerthat is, all your OTA SelfService URLs. On the TrustedURLs page for the site, enter the URLs for each OTA page.

Note: The URLs within OTA are often long and may differeven for the same pages, because of multiple parameters.Therefore, minimize the URL string by using the starts withoption. For example: mymachine.cisco.com/somepath/.

OTA: Obtain Oracle iLearning Site ID

Obtain the OiL Site ID, which is the number displayed in brackets tothe right of the site name in the Navigator. You need this number to setthe OTA:iLearning Site ID profile (page 9) and run the concurrentprograms.

Oracle iLearning: Prepare Admin User Groups and Users

1. Create user groups for three types of OiL administrators. Name thegroups Site Admin UG, Content Assembler UG, and Scheduler UG.

2. Grant appropriate privileges to each of the user groups:

Grant the Site Admin role to Site Admin UG.

Grant the Content Assembler role to Content Assembler UG.

Grant the Scheduler role to Scheduler UG.

7/28/2019 Ota Guide

8/23

Step 4

Step 5

8 Using OTA and OiL

3. Create additional administrator users. If specific employees mustcreate RCOs (Reusable Content Objects) and offerings, add a newadministrator user for each.

For each employee who requires an administrator role, you must

create a user name that is completely different from theemployees OTA user name. We recommend you adopt astandard naming convention for all admin users that you create.You might choose the employees OTA username with anadditional prefix or suffix. For example, OTA userjsmith mighthave an OiL admin userjsmith_admin.

Assign each administrator to the relevant user group. If one useroccupies a dual rolecontent assembly and scheduling, forexampleassign both roles to the same user.

Notify each user of their administrator username and password.

Warning: Do not use the employees OTA username for their adminaccount. OTA users have learner access only, and must accessthe OiL player from OTA. OiL administrators must alwaysparticipate in their learning through OTA screens using theirOTA user, not by entering OiL directly.

OTA: Create Default Activity Type

From the Activities window, create a default Activity Type namedOTA iLearning Activity. All imported RCOs must appear under thisactivity type.

See: Creating an Activity, Using Oracle Training Administration

OTA: Set System Profiles

Switch to the System Administrator responsibility.

Set three system profiles:

OTA:Default Activity for iLearning

For any responsibilities you have designated as OTAadministrators, enter OTA iLearning Activity at theResponsibility level.

OTA:iLearning Site Address

For any responsibilities you have designated as OTAadministrators, enter the OiL Site URL (Web address) provided

by the OiL System Administrator (the hosted site URL istypically http://ilearning.oracle.com).

7/28/2019 Ota Guide

9/23

Step 6


9

You must then repeat the step for any responsibilities to whichyou have given SelfService access.

Warning: Omit any slash (/) at the end of the URL, or the linkwill fail.

OTA:iLearning Site ID

Enter the OiL Site ID number provided by the OiL SystemAdministrator.

You must then repeat the step for any responsibilities to whichyou have given SelfService access.

See: Setting User Profile Options, Oracle Applications System

Administrators Guide

OTAOiL: Import Users into OiL

Every person you want to enable to take OiL classes must be entered asa person in OTA. To enable OiL to recognize these users, in OTA youcreate an export file using the iLearning User XML Export concurrentprogram. Then in OiL, you import the data from the export file.

After the initial export, you should manually submit this program atregular intervals, to add new users and update existing ones. Wesuggest at least once a week, but you can vary that according to thenumber and stability of your workforce.

Warning: Running this program establishes a permanent linkbetween your Business Group and its corresponding Site ID.Before you run this or either of the other two concurrentprograms, ensure that you are signed into the correct BusinessGroup and that you have entered the correct Site ID into theOTA:iLearning Site ID profile.

OTAside tasks

Execute the iLearning User XML Export program from your OTAadministrator responsibility.

See: Concurrent Programs Window, Oracle Applications System

Administrators GuideThe User Export program takes three parameters: iLearning Site ID,Start Date (and time), and End Date (and time). In the Site ID field,enter the number you entered in the OTA:iLearning Site ID profile.

Warning: Initially, you may need to export thousands ofusers, especially if you have chosen to use a global BusinessGroup. To ensure smooth operation, we suggest that you adjust

7/28/2019 Ota Guide

10/23

Step 7

Step 8

10 Using OTA and OiL

your start and end dates and times to restrict exports to nomore than 2,000 users at a time.

See: Creating a Business Group, Using Oracle TrainingAdministration

The User Export program generates an XML data file and a log file. Thedata file includes user names, HR (FND) user IDs, and a random stringthat uniquely identifies the user in OiL. To import the users into OiL,the OiL System Administrator must have physical access to the exportfile, which typically sits in the standard concurrent manager filedirectory.

Run the concurrent program manually, not automatically. This ensures

that the export does not run automatically more often than the manualimport in OiL.

OiLside tasks

The OiL administrator who performs the import must be a trusted andsecure user, as this user requires access to the OTA directory containingthe export file.

Ensure you select the OTA Learner organization before performing the

import. If you select the site and choose Import, you receive apermissions error. If you select a different organization, users areimported into the wrong organization. However, your site should haveonly one organization.

To perform the import, log in to the Admin user interface, select theOTA Learner organization, and click Import. The application promptsyou for the XML file name.

A password is randomly generated for each imported user. This is toprevent learners from accessing OiL directly. All learner access to OiLmust be through OTA.

Oracle iLearning: Site Administration Guidelines

The integration changes the behavior of both applications. OiL SiteAdministrators must be aware that OTA manages some tasks normally

performed in OiL. Some standard OiL features also function differently.

See Oracle iLearning: Site Administration Guidelines for the OTAIntegration: page 14

Oracle iLearning: Content Assembly and Scheduling Tasks

Content assembly and scheduling also changes under the integration. Itis important for all content assemblers and schedulers to be familiar

7/28/2019 Ota Guide

11/23

Step 9


11

with these changes. In some cases, the integration completely ignoresinapplicable field entries, but in other cases setting fieldsinappropriately may impair the ability of OTA to function correctly.

See Oracle iLearning: Content Assembly and Scheduling in the OTA

Integration: page 17

OTA: Import Content and Offerings from OiL

To import activity (Reusable Content Object or RCO) and event(Offering) information from OiL, use the iLearning Content andOffering Import concurrent program.

Each new or modified RCO is exported from OiL if (and only if) a

published Offering exists for the RCO in OiL. OTA creates a new Activity for each new RCO created since the

previous import.

OTA updates the Activity related to a modified RCO, if theActivity already exists for this same RCO.

Activities are updated only if the relevant RCO has beenmodified since the last export.

A published Offering must exist in order to prevent unfinishedwebbased events being exported from OiL prematurely and

becoming available to learners in OTA.

Unlike the User Export program, you can run the Content Importprogram automatically, at regular intervals. We suggest once a week,though you may run it more often if your content changes frequently.

Warning: Whatever interval you choose, be sure to follow theimport with a quick review of the valid assignments forimported events. Until you restrict events in the ValidAssignments window, any employee can enroll in any event.

Before the Content Import program runs, the OiL site administratorshould run the OTA Import Validation Report (page 16) to reveal fieldlength errors and duplicate names.

The Content Import program takes 10 parameters: Start Date, EndDate, Activity Type (which should be OTA iLearning Activity orwhatever you have used as the default), OiL Site ID, OiL Admin UserName and Password, Server Proxy Set (the default is TRUE), ServerProxy Port, Server Proxy Host, and iLearning Site Address (if your OiLsite is hosted, the address is normally http://ilearning.oracle.com).

When you schedule this program to repeat periodically, be sure tocheck the Increment date parameters each run check box.

7/28/2019 Ota Guide

12/23

Step 10

Step 11


You can query any offerings imported with the delivery methodeStudy from the OTA SelfPaced Event window. You can query anyofferings imported with the delivery method Scheduled from theOTA Scheduled Event window. If OiL delivery methods do not alreadyexist in OTA, the application creates them automatically.

Warning: Do not use duplicate RCO or Offering names. Suchrecords fail to import.

OTA: Import Training History Data

To import the results of employees online training, run the iLearningPerformance Import concurrent program.

The program automatically transfers enrollments and results bymapping OiL statuses to OTA enrollment statuses:

OiL statuses Not Attempted, Attempted, Incomplete, and Failed mapto OTA status Placed.

OiL statuses Passed and Complete map to OTA statusAttended.

The Performance Import program optionally transfers Score, Time (tocomplete), and the number of completed and total modules (4 of 6, forexample).

The log file contains the number of history records updatedsuccessfully and the number that failed.

The Performance Import program uses the same 10 parameters takenby the Content Import program.

We suggest that you run the program quite oftenhourly or even more

often, depending on the size of your internal training business (largerbusinesses may desire more frequent runs). When you schedule thisprogram to repeat periodically, be sure to check the Increment dateparameters each run check box.

Configure Oracle Workflow

The integration defaults to SelfApprovalthat is, any users can enrollthemselves in any available course without a managers approval. Ifyou want to require Manager Approval, you must configure OracleWorkflow by changing a setting in two functions.

In the Cost Center and Review Page functions, change theHR_APPROVAL_REQ_FLAG to Yes. To do so, explore each function inthe process, then click on the Node Attribute tab.

Note: Do not change the value of the attribute at the Attributelevel.

7/28/2019 Ota Guide

13/23

Step 12


13

For standard Workflow procedures, consult the Oracle Workflow Guide.

Configure SelfService OTA

The selfservice side of the integration gives you the option of hiding

default columns or revealing hidden ones. Be careful, of course, not tohide information the user might require.

By enabling Special Instructions in AK, you can enable learners to enteradditional enrollment detailsthat is, the Delegate BookingDescriptive Flexfieldas they enroll (or cancel an enrollment) from theselfservice interface.

See: Implementation Steps, Implementing Oracle SelfService Human

Resources (SSHR).

7/28/2019 Ota Guide

14/23


Oracle iLearning: Site Administration Guidelines for the OTAIntegration

Features you should not implement in an OTAintegrated Oracle

iLearning instance include: Categories: The concept of categories in OiL is completely

different from categories in OTA. The integration ignores OiLcategories.

Enrollment: Never unenroll a learner directly from OiL. Alwaysuse OTA to unenroll learners from events.

Enrollment Conditions: Do not add enrollment conditions to

anything other than the site level. Always use selfenrollmentconditions to enroll anyone (in your OTA Learner organization)in any courses in OiL.

The enrollment must remain completely open, since OTAcontrols access to all courses. Restricting enrollment at anyother level will prevent access from OTA.

To control access to courses, set the assignment feature in

OTA, after the offering and content object information istransferred from OiL to OTA.

If an administrator manually enrolls a user in an OiLoffering using the Enrollment List, the learner is notautomatically enrolled in the OTA event. The user must stillenroll in the course within OTA to gain access.

Imported Users: Do not manually update any user (learner)

information in OiL that was transferred from the OTA or HRsystem. Manual changes to imported users will be lost when thenext user import is performed. However, updates toadministrative users, created manually within OiL, are allowed.

Organizations: Do not create an organization or managerhierarchy manually in OiL. Create only one organization, OTALearner. Multiple OiL organizations are ignored by the

integration, and should not be manually maintained in OiL. Payment Server: Use the OTA payment mechanism, not the OiL

payment server functionality.

Permissions: Do not grant OiL permissions to imported OTAusers (learners). Any administrative permission for a userdisables the Trusted URL feature that allows seamless login

between the two products for that user. For users who require

7/28/2019 Ota Guide

15/23


15

permissions to perform administrative duties in OiL, create aseparate user name and password manually in OiL.

Resource Management: Use the OTA scheduling mechanism tomanage resources, once the offering and content information is

transferred. The integration ignores OiL resource managementfunctionality, including resource types, resources, and bookingresources.

Waitlisting: Set up waitlisting through OTA. Do not use the OiLwaitlisting feature.

Other OiL features change under the integration:

Announcements: OTA learners do not see any type of OiL

announcement (site, content, or offering level). However,administrative users who log in directly to OiL can viewannouncements.

Content Folders: Creating an extensive folder hierarchy mayassist a site administrator in assigning permissions to individualadministrators on related content, and in organizing and locatingcontent within OiL. However, OTA does not use OiL folders.

Content Types: You can create or modify your content typehierarchy for use by the content assemblers. However, thisinformation has no bearing on the integration, since it isviewable only from within OiL.

Custom Attributes: OiL custom attributes are applicable for userobjects only, not content objects, since the content description isnot visible to learners. Ensure you create user custom attributes

in OiL before exporting or importing users. Export your usersfrom OTA using the appropriate XML format, and import theusers into OiL.

Custom Reports: An OiL custom report retrieves no OTAinformation.

Published Offerings: By default, all published offerings areimmediately available to all learners after an export of offerings

and content objects to OTA. To prevent some offerings beingimmediately available, use the following techniques:

Ensure the offering is not published until you want totransfer it to OTA

Change the offering start date to a date in the future

Change the assignment information on the OTA eventafter the transfer

7/28/2019 Ota Guide

16/23


References: Any reference material created on content objects isavailable to learners only while they are playing a course.

Roles: Roles, in the OiL permissions model, have no relevance tothe integration except to disable Trusted URL access from OTA

for administrative users. However, roles can assist managementof administrative users, such as assemblers and schedulers, inOiL.

Site Customization: Only the admin and player customizationsare available in the integration, since learners do not see the OiLhome page.

Time Zone: OTA uses the time zone exactly as entered in OiL.

Ensure that you set an applicable default time zone. Schedulerscan alter the time zone for specific offerings if necessary. Note,however, that OTA does not validate these changes.

User Groups: OiL user groups have no impact on theintegration. However, they may assist management ofadministrative users in OiL.

Validation Report: Before the iLearning Content and Offering

Import program runs, you should run the OTA ImportValidation Report to correct import errors before they occur. Thereport lists duplicate RCO and Offering names (page 19) as wellas fields that exceed the maximum allowed number of characters(page 19), all of which cause the import program to fail.

The OTA Import Validation Report is a custom report that yourun from the Reports tab in the Admin interface. If your site ishosted or installed, you may need to request this report fromyour Oracle account manager.

7/28/2019 Ota Guide

17/23


17

Oracle iLearning: Content Assembly and Scheduling Tasks

Content assembly and scheduling tasks are performed on an ongoingbasis by the administrator users, which a site administrator sets upwithin OiL. Different users can perform each role, or one user may

perform both roles.

Content assemblers and/or Schedulers create RCOs and Offerings inOiL. These objects are the basis for all webbased content transferred(exported) to OTA as Activities and/or Events.

The following sections highlight some features of OiL that are requiredin the standalone product, but which are not applicable whenintegrated with OTA, since OTA provides the frontend interface for

managing the relationship between content and learners.

It is important for all content assemblers and schedulers to be familiarwith these issues. In some cases, the integration totally ignoresinapplicable field entries, but in other cases setting fieldsinappropriately may impair OTA.

Overview of Content Assembly and Scheduling1. Create required RCOs in OiL.

Specify the language that the associated content is written in.

Define prerequisite RCOs, if required, to prevent learners fromplaying the current content until they have completed therequired RCOs. These prerequisites must be manually typed inthe Activity description field in OTA after export to notify the

learners in advance, before they attempt to enter the player.

2. Create Offerings in OiL.

When your RCOs are completed and ready for OTA learners,create and publish an offering. For new RCOs, the simplestmethod is to use the Offer command available on the RCOproperty sheet. This method publishes the RCO, creates an initialoffering, and publishes the offering.

Edit the offering. In the Player Preferences, it is vital to deselectExit. Optionally, edit other properties such as start or end date.

Warning: Failure to deselect Exit grants all learners access to allofferings (by giving learners access to the OiL home page).

7/28/2019 Ota Guide

18/23


Content Assembly Guidelines

Announcements: OTA learners do not see any type of OiLannouncement (site, content, or offering level). However,administrative users who log in directly to OiL can see

announcements. Assessments: Assessment tests are either topics within a content

structure, or standalone test objects that have offerings in theirown right.

Test topics themselves are not viewable from within OTA.

Learner test scores are only available directly within theOiL player, or from custom reports created and run fromOiL, since the OiL transcript page is not available withinOTA.

Learner test score information is not transferred to OTA ifthe test is a topic within a course.

Categories: The integration ignores OiL categories, which differcompletely from OTA categories.

Content Folders: Creating an extensive folder hierarchy greatlyassists content assemblers and schedulers in organizing andlocating content within OiL. However, OTA does not recognizeOiL folders.

Content Object hierarchy: The content object hierarchy for acourse is not transferred to OTA. Only the content objects thathave associated offerings are transferred to OTA. However,learners can view the content hierarchy when they play a course.

Content Object metadata: The integration ignores the followingmetadata, generated when creating content objects in OiL.

General: Hardware/Software, Requirements, MasteryScore, Mime Type, Author, Catalog, Catalog Number,Version

Content Location: External, iLearning Secured

Rights: Price, Monetary Unit, Copyright, Payment Server

Custom Attributes

Enter any additional OTArelated information only aftertransferring the offering and content object information from OiLto OTA.

7/28/2019 Ota Guide

19/23


19

Deletion: Never delete RCOs or Offerings after the concurrentprogram has passed them to OTA.

Duplicate RCO or Offering Names: Give each RCO andOffering a unique name. Duplicate names cause the OTA

Content and Offering Import program to fail.Note: Before the Content Import program runs, the OiL siteadministrator should run the OTA Import Validation Report toreveal field length errors and duplicate names.

Field Length Restrictions: RCO and Offering names must notcontain more than 80 characters each. RCO descriptions,audiences, and objectives must contain no more than 2000

characters. Payment Server: Use the OTA payment mechanism, not the OiL

payment server functionality.

Prerequisites: Prerequisites still work to restrict learner accessuntil a prerequisite is completed. However, be aware of thefollowing:

Since OTA does not recognize RCO hierarchies, the

Content Import program transfers descriptions only fromtoplevel RCOs, not from nested RCOs. Therefore, yourtoplevel RCO descriptions must include all critical RCOinformation, including prerequisites.

When launching a course, learners receive an errormessage if they have not met a required prerequisite. Theymust exit the player, and launch the prerequisite first.

Resource Management: Use the OTA scheduling mechanism tomanage resources, once the offering and content information istransferred. The integration ignores OiL resource managementfunctionality, including resource types, resources, and bookingresources.

Scheduling Guidelines

Enrollment: Never unenroll a learner directly from OiL. Alwaysuse OTA to unenroll learners from events.

Enrollment Conditions: Do not change the enrollmentconditions for any object.

The enrollment must remain completely open in OiL,since OTA controls access to all courses.

7/28/2019 Ota Guide

20/23


Restricting enrollment at any other level prevents accessfrom OTA.

Always use the selfenrollment condition to enrollstudents in OiL courses.

Do not manually enroll a user in an OiL offering using theEnrollment List; the learner is not automatically enrolled inthe OTA event. To gain access the user must still enroll inthe course within OTA.

To control access to courses, set the assignment feature inOTA, after the offering and content object information istransferred from OiL to OTA.

Event types: The only OiL event type that OTA supports is anOffering.

Do not create Open Chat or Open Forum events, as theyare not accessible from OTA. However, you can associateforums and chats with a specific offering, since these areavailable within the player when a learner launches therelevant content.

Do not create Integrated Learning events. This type ofevent is not transferred to OTA.

Offering properties: You can modify some properties of anOffering. However, several properties and sections on theOffering properties page do not apply to OTA, as the table belowspecifies.

7/28/2019 Ota Guide

21/23


21

Offering PropertySection

Applicable Not Applicable

General Name, Content Object,Description, Style (allexcept inClass, Offline)

Style=inClass, Offline(create any inClass of-feringsphysicalclassroom trainingeventsin OTA)

Student Access None All

Schedule All but Duration Duration

Repeat None All (Use the OTA eventsession feature)

Enrollment None All (Use the OTA wait-listing features)

Player Preferences All except those listedin the next cell

Exit, Rate

Warning: You must deselect Exit in every offering, to avoidgranting learners access to the OiL home page and thus to allofferings, bypassing the access control of OTA.

7/28/2019 Ota Guide

22/23


FND Language Codes for Oracle iLearning

Language_code Description

US AMERICAN

GB ENGLISHF FRENCH

FRC CANADIAN FRENCH

D GERMAN

DK DANISH

NL DUTCH

SF FINNISH

AR ARABIC

N NORWEGIAN

E SPANISH

S SWEDISH

ZHS SIMPLIFIED CHINESE

JA JAPANESE

KO KOREAN

PT PORTUGUESE

PTB BRAZILIAN PORTUGUESE

HU HUNGARIAN

ESA LATIN AMERICAN SPANISH

CS CZECH

BG CATALAN

HR CROATIAN

EL GREEK

IS HEBREW

I ITALIANLT LITHUANIAN

PL POLISH

RO ROMANIAN

RU RUSSIAN

SK SLOVAK

7/28/2019 Ota Guide

23/23


23

SL SLOVENIAN

TH THAI

TR TURKISH

ZHT TRADITIONAL CHINESE

EG EGYPTIAN

ota guide

Documents