12 videos • 📅 2024-09-30 09:00:00 America/Bahia_Banderas
Watch Video
48:57
2024-09-30 11:03:24
30:21
2024-09-30 12:02:29
3:29
2024-09-30 12:34:41
1:04
2024-09-30 12:43:50
1:22
2024-09-30 13:06:34
5:52
2024-09-30 13:08:57
5:02
2024-09-30 13:30:59
12:33
2024-09-30 13:46:10
49:55
2024-09-30 15:00:01
6:21
2024-10-08 11:02:02
8:16
2024-10-08 12:05:49
3:03
2024-10-08 12:26:15

Course recordings on DaDesktop for Training platform

Visit NobleProg websites for related course

Visit outline: Talend Open Studio for ESB (Course code: talendesb)

Categories: SOA ESB Integration · Talend

Summary

Overview

This course session provides step-by-step instruction for setting up a PostgreSQL database environment using a provided backup file to support a case study involving two tables: caso_de_estudio and lenguaje. The trainer guides participants through downloading, extracting, and restoring the database via pgAdmin, clarifies which tasks require each table, and emphasizes documentation requirements (screenshots and logging) for completing 10 assigned TDI (Transformation Data Integration) tasks. The session includes real-time troubleshooting support for participants struggling with file location and restoration procedures.

Topic (Timeline)

1. Initial Setup and File Location Guidance [00:00:00 - 00:04:51]

The trainer begins by addressing a failed file restoration attempt, identifying that the backup file (Backup base de datos de caso de estudio) was not properly located or extracted. Instructions are given to navigate to the Downloads folder, then to a nested directory structure (TDI test → talent → TDQ) to locate the compressed backup file. Participants are directed to extract the archive, navigate into the extracted folder, and select the unzipped Backup file (no extension specified) for restoration. The trainer confirms the expected outcome: two tables (caso_de_estudio and lenguaje) should appear in the public schema after successful restoration.

2. Database Restoration Procedure via pgAdmin [00:04:52 - 00:08:16]

The trainer reiterates the restoration process using pgAdmin: right-click on the target database (caso_de_estudio), select “Restore,” and point to the location of the backup file. Emphasis is placed on changing the file filter to “All Files” to ensure visibility of the backup file, which may be mislabeled or unextended. Participants are instructed to confirm the file path (commonly in Downloads), initiate the restore, and wait for completion. After restoration, participants are told to refresh the schema view (F5) to verify the presence of the two required tables. The trainer notes that the correct environment is PostgreSQL, not MySQL, and explicitly instructs participants to close MySQL Workbench to avoid confusion.

3. Task Assignment and Table Usage Clarification [00:05:17 - 00:06:53]

The trainer clarifies that only Task 10 requires the lenguaje table; the first nine tasks use only the caso_de_estudio table. Participants are instructed to complete exactly 10 tasks from the provided list, documenting each with a screenshot and log entry in TDI. The session pauses to allow participants time to complete setup before beginning tasks, with the trainer offering real-time support for those encountering file or tooling issues.

Appendix

Key Principles

  • Database Environment: PostgreSQL is the required platform; MySQL Workbench must be closed to avoid confusion.
  • File Handling: Backup file is compressed; must be extracted before restoration. File name: Backup (no extension).
  • Schema Expectation: Restoration must produce exactly two tables: caso_de_estudio and lenguaje in the public schema.

Tools Used

  • pgAdmin (for database restoration)
  • File Explorer (for locating and extracting compressed backup)
  • TDI (for task execution and documentation)

Common Pitfalls

  • Confusing MySQL Workbench with pgAdmin.
  • Failing to extract the compressed backup file before restoration.
  • Not changing the file filter to “All Files” in pgAdmin, causing the backup file to be invisible.
  • Incorrect file path navigation (e.g., not ascending to talent or TDQ folder).

Practice Suggestions

  • Before starting tasks, verify table existence via pgAdmin refresh (F5).
  • Document every TDI task with a screenshot and written log, as required.
  • Double-check file location hierarchy: Downloads → TDQ → [extracted folder] → Backup.