SSB9 Troubleshooting Guide: Data Not Displaying Properly - Arch-Node/personal_studies GitHub Wiki

Back to High Level Steps

This guide helps diagnose and resolve issues where data is not displaying properly in Ellucian Self-Service Banner 9 (SSB9). The troubleshooting process covers frontend (UI), middleware, backend, and caching layers.

---

• Open Developer Tools (F12) → Console Tab.
• Look for JavaScript errors (e.g., TypeError, ReferenceError).
• Check for CORS errors (cross-origin resource sharing).

• Open Developer Tools → Network Tab.
• Look for API calls that fail (status 4xx or 5xx).
• Verify if the frontend is requesting the correct API endpoint.

• Ensure API calls are correctly structured in Angular services or React fetch/Axios.
• Example:

  fetch('/api/student/records')
    .then(response => response.json())
    .then(data => console.log(data))
    .catch(error => console.error('Error:', error));

• Check if the backend URL is correct in .env or config.js.

• If using Redux (React) or NgRx (Angular), ensure:
  • The store updates when API data is fetched.
  • Components correctly subscribe to state changes.
• Debug using:
  • Redux DevTools (React)
  • Angular DevTools (Angular)

• Check if the UI is binding data correctly:
  • Angular: *ngFor="let item of items"
  • React: {items.map(item => <div>{item.name}</div>)}
• Ensure there are no conditional checks incorrectly hiding data.

---

• Check NGINX, Apache, or Spring Cloud Gateway logs for incorrect routes.
• Verify API paths are configured correctly in the proxy:

  location /api/ {
      proxy_pass http://backend_server;
  }

• Verify if the API request includes a valid JWT token.
• Check if OAuth/SAML/CAS session tokens are expiring prematurely.

• If behind a load balancer (F5, NGINX, Apache mod_proxy), ensure:
  • The API traffic is reaching the correct backend.
  • Session stickiness is enabled if required.

---

• Check logs for errors in backend services:

  tail -f /var/log/tomcat/catalina.out
  tail -f /opt/ellucian/logs/banner9.log

• Look for SQL errors, timeouts, or authentication failures.

• Manually test API using:

  curl -X GET "https://banner.university.edu/api/student/records"

• If the response is empty:
  • Check database queries.
  • Ensure data exists for the logged-in user.

• Run SQL queries directly:

  SELECT * FROM student_records WHERE student_id = '12345';

• Ensure:
  • The data exists.
  • The API correctly queries the database.
  • Indexes and foreign key relationships are intact.

---

• Clear browser cache or force refresh (Ctrl + Shift + R).
• Test in Incognito Mode.

• Flush cache:

  redis-cli FLUSHALL

• If using Spring Boot caching, check if cached responses are outdated:

  @CacheEvict(value = "studentData", allEntries = true)

• If using a CDN, ensure the latest API responses are not stale.
• Purge CDN cache if necessary.

---

• Start with frontend debugging (console errors, API calls).
• Check middleware (authentication, API gateway, load balancing).
• Investigate backend logs, API responses, and database queries.
• Validate caching layers (browser, Redis, CDN).

By following this guide, you can systematically diagnose and resolve data display issues in Ellucian SSB9.

---