Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/kenri89/PROYECTO_UTP_AED_1_1/llms.txt

Use this file to discover all available pages before exploring further.

This guide walks you through everything you need to have the Sistema de Gestión Académica running on your machine and logged in as one of the three default users. By the end you will have created the SQL Server database, configured your connection credentials, compiled the project with Apache Ant, and verified role-based access through the login screen.
Prerequisites before you begin:
  • Java 21 or later installed and available on your PATH
  • Microsoft SQL Server running locally (any recent Express or Developer edition works)
  • Apache Ant installed, or NetBeans IDE (which bundles Ant automatically)
  • Git to clone the repository: git clone https://github.com/kenri89/PROYECTO_UTP_AED_1_1.git
1

Create the database

Open SQL Server Management Studio (SSMS) or any SQL Server client and run the following statement to create the database:
CREATE DATABASE iestp_peru_japon;
GO

USE iestp_peru_japon;
GO
Next, execute the full schema.sql file from the project root against that database. This creates the five required tables and inserts the three default users:
TableDescription
usuariosAuthentication table — stores username, password, and role
CursosCourse catalog with code, name, credits, and semester
EstudiantesStudent records keyed on carnet
MatriculasEnrollment records linking a student carnet to a course code
SolicitudesAcademic requests submitted by students
From SSMS, use File → Open → schema.sql and click Execute, or run it from the command line:
sqlcmd -S localhost -U sa -P your_password -i schema.sql
2

Configure credentials

Open src/config.properties in any text editor and update the values to match your SQL Server installation:
# Configuracion de base de datos
db.server=localhost
db.port=1433
db.name=iestp_peru_japon
db.user=sa
db.password=your_password
db.encrypt=true
db.trustCertificate=true
The ConexionSQL utility reads this file at startup using ConexionSQL.class.getClassLoader().getResourceAsStream("config.properties"). All seven properties (db.server, db.port, db.name, db.user, db.password, db.encrypt, db.trustCertificate) must be present or the JDBC connection will fail and the application will fall back to local TSV files.
3

Build and run

From the project root directory, compile and launch with a single Ant command:
ant run
Ant reads build.xml (which delegates to nbproject/build-impl.xml), compiles all sources under src/, bundles the libraries from lib/, and launches the main class gui.Main.Alternative — NetBeans IDE:
  1. Open NetBeans and choose File → Open Project.
  2. Navigate to the cloned repository root and open it as an Ant project.
  3. Press F6 (or click the Run Project button) to build and run.
A login window titled “Inicio de Sesión” will appear once startup completes. The Logback console will print:
INFO  gui.Main - Iniciando Sistema de Gestión Académica - PROYECTO_UTP_AED_1
INFO  gui.Main - Ventana de login abierta
4

Log in

The schema seeds three default accounts. Enter the username, password, and select the matching role from the drop-down before clicking Ingresar:
UsernamePasswordRole (drop-down)Access
admin1234AdministradorFull access — courses, students, enrollment, history, requests, and admin request management
secretaria1234SecretariaCourses, students, enrollment, and student requests
estudiante1234EstudianteOwn enrolled courses, academic history, and submitting requests
On successful login, a welcome dialog confirms your role and the main window (MenuPrincipal) opens showing only the navigation buttons that apply to your role.
Local TSV fallback: If SQL Server is not reachable at startup, the application automatically reads and writes data to tab-separated files stored in the ~/.proyecto_utp_aed_datos/ directory in your home folder (PersistenciaAcademica handles this transparently). Changes made in offline mode are persisted to those TSV files and will be available the next time you run the application without a database connection.

Build docs developers (and LLMs) love