PeopleSoft Campus Solutions ↔ Brightspace LMS Roster and Grade Sync

// Middleware: PeopleSoft Enrollment → Brightspace Enrollment Mapping
// Trigger: PS_CLASS_TBL enrollment changes via Integration Broker

// 1. Inbound payload from PeopleSoft (REST/Webhook)
{
  "EMPLID": "01458932",
  "CRSE_ID": "CS-201-01",
  "TERM": "2024-FALL",
  "CLASS_NBR": "45678",
  "ENROLL_STATUS": "E",
  "STRM": "2440",
  "CRSE_GRADE_OFF": "A"
}

// 2. Middleware resolves Brightspace org unit and user identifiers
orgUnitId = resolveBrightspaceOrgUnit(CRSE_ID, TERM)
userId = resolveBrightspaceUser(EMPLID)

// 3. Outbound call to Brightspace LMS API
POST https://{brightspace-domain}/d2l/api/lp/1.43/enrollments/
Content-Type: application/json
Authorization: Bearer {D2L_API_TOKEN}

{
  "OrgUnitId": orgUnitId,      // e.g., 67890
  "UserId": userId,          // e.g., 12345
  "RoleId": "Learner",     // Student role = 3
  "IsCancelled": false
}

// 4. Grade Passback via LTI Assignment and Grade Service
POST https://{brightspace-domain}/d2l/api/grades/1.43/{orgUnitId}/grades/
{
  "GradeObjectType": "Numeric",
  "Name": "CS-201-01 Final Exam",
  "ShortName": "FINAL",
  "MaxPoints": 100,
  "CanExceedMaxPoints": false
}

// LTI Grade Passback (AgsService) - sent back to PeopleSoft
POST {LineItem.url}/lineitems/{lineItemId}/scores
{
  "userId": "https://lms.example.edu/d2l/api/lp/1.43/users/{userId}",
  "gradeGiven": 92,
  "timestamp": "2024-12-15T14:30:00Z",
  "activityProgress": "Submitted",
  "gradingProgress": "FullyGraded"
}

How we'd take this from discovery to a production-safe cutover — the phases, the canonical mapping, and the edge cases that bite.

This implementation pathway covers the middleware integration between Oracle PeopleSoft Campus Solutions and Brightspace LMS, enabling automated roster synchronization and LTI-based grade passback. The solution uses PeopleSoft Integration Broker as the source of truth for enrollment data, a middleware layer for transformation and orchestration, and Brightspace's Data Sets API for roster management combined with LTI Advantage for grade synchronization.

Implementation Phases

1. Environment Assessment and Credential Procurement — Validate access to PeopleSoft Integration Broker (IB) domain configuration, confirm Brightspace API credentials with LMS admin, establish middleware runtime environment, and review current enrollment data structures in STDNT_CAR_TERM and CLASS_TBL.
2. PeopleSoft Web Services Configuration — Enable and configure Integration Broker in PeopleSoft; create asynchronous service operations for enrollment events (STUDENT_ENROLLMENT message); expose STUDENT_REGISTRATIONS component interface for bulk extraction; configure target connectors for HTTP-based middleware consumption.
3. Middleware Transformation Layer Development — Build integration flows in the chosen middleware (MuleSoft, Boomi, or custom); implement PeopleSoft XML-to-JSON transformation; construct Brightspace Data Sets payload structure; develop error handling with dead-letter queues for failed transformations.
4. Brightspace Roster Import Configuration — Configure Brightspace org unit structure (offerings and sections hierarchy); set up CSV async import for enrollment via /d2l/api/lp/<version>/import/; map PeopleSoft term codes (STRM) to Brightspace semester identifiers; test with synthetic enrollment records.
5. LTI Advantage Grade Passback Setup — Register PeopleSoft as an LTI 1.3 Tool Provider in Brightspace; configure lineitem creation scope for grade columns; implement assignment grade sync endpoint receiving LineItem and Result POSTs; validate JWT token exchange with Brightspace's platform OAuth2 endpoint.
6. Full Load and Delta Sync Validation — Execute initial bulk roster load for current term; compare enrollment counts between ENRL_ACTIVITY and Brightspace section rosters; validate LTI grade passback for sample assignments; log discrepancies for reconciliation.
7. User Acceptance Testing and Cutover — Conduct parallel-run with manual enrollment for one test section; verify dropped students reflect within sync interval; confirm grade updates propagate back to PeopleSoft grading tables; switch production flag and monitor for 72-hour stability window.

Canonical Field Mapping

Edge Cases

• Double enrollment across term variants — Students repeating a course in consecutive terms may have duplicate EMPLID + CRSE_ID entries; Brightspace section matching must include STRM to prevent incorrect roster additions.
• Section cross-listings — PeopleSoft CRSE_ID with multiple CLASS_NBR values (split sections) must map to a single Brightspace section or instructor receives duplicate grade columns; validate with academic scheduling team.
• LTI grade score type mismatch — Brightspace may expect decimal while PeopleSoft CRSE_GRADE_OFF contains letter grades; implement grade translation table before posting to LTI resultScoreMaximum.
• Mid-term section merges — If PeopleSoft consolidates sections post-enrollment, Brightspace sections retain orphaned enrollments; middleware must detect CLASS_NBR changes and re-map enrollments.
• Late enrollment processing lag — Bulk nightly sync may miss students added within 24 hours of grade submission; configure PeopleSoft IB to trigger real-time enrollment events for high-stakes courses.
• Grade rollback in PeopleSoft — If an instructor corrects a grade post-sync, LTI does not support grade updates without re-submission; middleware must track ltiResult.sourcedId to resubmit corrected values to the same lineitem.

Cutover

Cutover requires a reversible migration strategy to protect academic records. Before switching to automated sync, export current Brightspace enrollment rosters as a snapshot and store alongside PeopleSoft STDNT_ENRL extract. Configure middleware to operate in shadow mode for the first production term—validating data without writing—then compare counts by section and resolve discrepancies in PeopleSoft before committing. Implement a cutover hold period of 48 hours during which manual enrollment in PeopleSoft remains authoritative; if corruption occurs, disable Brightspace grade passback, restore rosters from the snapshot, and re-enable sync after identifying the failing record. All automated operations must write audit logs to INTEGRATION_LOG (PeopleSoft) and Brightspace API audit endpoints with timestamps, record counts, and error codes for post-incident reconciliation.