Easylib

Easylib Help

Server Health Check – EasyLib

DB Systems List – Server Health Check

The DB Systems List screen in EasyLib acts as a Server Health Check & SSL Monitoring Dashboard. It gives administrators a real-time overview of all EasyLib system instances, helping them monitor availability, security, and system status.

What This Screen Explains / Shows

1. Overall System Availability

  1. Displays all EasyLib Production and Test systems in one place.
  2. Shows whether each system is Active or Down.
  3. Helps quickly identify server outages or inaccessible sites.

2. Database & Instance Mapping

  1. Clearly maps:
  2. System Name
  3. Database Name
  4. Instance Name
  5. Helps administrators understand which database belongs to which institution/system.

3. System URL Monitoring

  1. Shows the live URL of each system.
  2. Used to verify:
  3. Website accessibility
  4. SSL certificate validity
  5. Correct domain configuration

4. Environment Identification

  1. Differentiates between:
  2. Production (Live systems)
  3. Test (Testing / staging systems)
  4. Prevents accidental actions on live environments.

5. SSL Certificate Health Check

This is a key server health feature of the screen.

  1. Displays:
  2. SSL Expiry Date & Time
  3. SSL Check Status (Valid / Expired / Null)
  4. Allows:
  5. Manual SSL validation using Check SSL button
  6. Bulk SSL checks using Check All SSL

6. Proactive Security Monitoring

  1. Buttons like:
  2. List Expired SSL
  3. List SSL Expiring Soon
  4. Help administrators:
  5. Detect security risks early
  6. Renew certificates before expiry
  7. Avoid browser security warnings

7. Last Verification Tracking

  1. Checked Date column shows:
  2. When the server/SSL was last verified
  3. Ensures checks are:
  4. Regular
  5. Documented
  6. Auditable

8. Organization-Level Mapping

  1. Organization ID links systems to internal records.
  2. Useful for:
  3. Support
  4. Audits
  5. License management

Customized Report

1. Introduction

The Customized Report – Database Systems module allows administrators to generate dynamic, filter-based reports on EasyLib system instances. This report helps in server health tracking, system auditing, and operational monitoring by letting users choose and display only the required data fields.

2. Access Path

Database Systems Reports ? Customized Report – Database Systems

3. Purpose of Customized Database System Report

  1. Generate custom server health and system status reports
  2. Monitor application availability across institutions
  3. Track last update and verification details
  4. Support audits, reviews, and management reporting
  5. Export reports for documentation and compliance

4. Screen Layout Overview

The screen is divided into two main sections:

  1. Field Selection Panel (Left Side)
  2. Report Result Grid (Right Side)

5. Field Selection Panel (Left Side)

This panel allows users to select which fields should appear in the report.

Available Fields

Field Name Description
System ID Unique identifier of the system
System Name Institution or system name
Database Name Name of the database
System URL Live system URL
IP URL Server IP address or IP-based URL
Application Status Active / Failed status
Checked Date Last server health check date
Contact Phone Institution contact number
Contact Email Institution email address
Server Name Name of hosting server
Last Updated By User who last updated system details

Selected fields dynamically control the report output.

6. Report Result Grid (Right Side)

Displays the report based on selected fields.

Column Explanation (As Displayed)

Column Explanation
System ID Unique system number
System Name Name of institution/system
Database Name Associated database
System URL EasyLib application URL
IP URL IP-based access URL
Current Status System availability (Active / Failed)
Checked Date Last verification date
Last Updated By User who last updated details

7. Action Buttons

Export

  1. Exports the customized report to:
  2. Excel
  3. CSV (as configured)
  4. Useful for audits, sharing, and documentation.

Show/Hide Columns

  1. Allows users to:
  2. Customize visible columns
  3. Simplify reports
  4. Focus on specific health indicators

8. Report Controls

Show Entries

  1. Controls number of records displayed per page.

Search Box

  1. Enables quick filtering by:
  2. System Name
  3. Database Name
  4. URL
  5. Status

9. Use Cases

  1. Monthly server health reporting
  2. System audit preparation
  3. Tracking inactive or failed systems
  4. Monitoring update responsibility
  5. Management and compliance reviews

10. Best Practices

  1. Include Checked Date and Status for health tracking
  2. Export reports periodically for records
  3. Customize reports for different stakeholders
  4. Review failed systems regularly

11. Relation to Server Health Check

This report complements:

  1. DB Systems List
  2. Server Details
  3. SSL Monitoring

By providing historical and customized views of server health data.

Server Details – EasyLib

1. Introduction

The Server Details module in EasyLib maintains a central repository of server infrastructure information. It enables administrators to track server identity, IP configuration, open ports, service providers, usage status, and support contacts, which are critical for server health monitoring, troubleshooting, and maintenance.

2. Access Path

Database Systems Reports ? Server Details

3. Purpose of Server Details

  1. Maintain accurate server inventory
  2. Monitor server usage status (Active / Inactive)
  3. Track network and port configuration
  4. Store service provider and support contact details
  5. Support quick troubleshooting during outages

4. Screen Overview

The Server Details screen displays a tabular list of all servers registered in EasyLib, with options to add, search, edit, and manage server records.

5. Column-Wise Explanation

5.1 (Serial Number)

  1. Auto-generated row number.
  2. Helps with quick references.

5.2 Server Name

  1. Logical or physical name of the server.
  2. Often named for easy identification (e.g., Bhagirathi, Tapti).

5.3 Static IP

  1. Public IP address assigned to the server.
  2. Used for external access and domain mapping.

5.4 Local IP

  1. Internal/private IP address within the network.
  2. Useful for LAN and internal server communication.

5.5 Ports Open

  1. Lists open ports on the server.
  2. Common ports include:
  3. 80 – HTTP
  4. 443 – HTTPS
  5. 8038 / 8012 – Application-specific services
  6. Helps verify firewall and network configuration.

5.6 Provider

  1. Hosting or service provider managing the server.
  2. Example: NXTGEN, Internal IT, Vendor name.

5.7 Provider Contacts

  1. Contact details of the service provider:
  2. Phone number
  3. Email address
  4. Used for escalation during server issues.

5.8 Usage Status

  1. Indicates current server usage:
  2. Active – Server is in use
  3. Inactive – Server is not currently in use
  4. Helps avoid accidental use of retired servers.

5.9 Edit

  1. Allows modification of existing server details.
  2. Used to update IPs, ports, provider info, or usage status.

6. Action Buttons

Add New Server

  1. Used to register a new server in EasyLib.
  2. Opens a form to enter:
  3. Server name
  4. IP details
  5. Ports
  6. Provider info
  7. Usage status

Search

  1. Enables quick filtering by:
  2. Server name
  3. IP address
  4. Provider
  5. Status

Entries Dropdown

  1. Controls the number of records shown per page.

7. Role in Server Health Check

The Server Details module supports server health monitoring by:

  1. Identifying which servers are currently active
  2. Ensuring correct IP and port configuration
  3. Providing immediate support contacts
  4. Supporting incident resolution and audits

8. Best Practices

  1. Keep IP and port details updated
  2. Mark unused servers as Inactive
  3. Verify open ports regularly for security
  4. Maintain updated provider contact information
  5. Review server list periodically

9. Common Use Cases

  1. Troubleshooting site downtime
  2. SSL or domain mapping issues
  3. Network or firewall validation
  4. Infrastructure audits
  5. Vendor coordination

10. Outcome

Using Server Details, administrators can:

  1. Maintain clear visibility of server infrastructure
  2. Improve response time during incidents
  3. Support secure and stable EasyLib operations

Global Table Maintenance

1. Introduction

The Global Table Maintenance module is used to manage and maintain master-level system tables that are shared across multiple EasyLib modules. These tables control system-wide configurations, reference values, and standard codes, ensuring data consistency and smooth application functioning.

2. Access Path

Database Systems Set Up ? Global Table Maintenance

3. Purpose of Global Table Maintenance

  1. Maintain centralized master data
  2. Ensure uniform values across the application
  3. Support system configuration and customization
  4. Avoid data duplication and inconsistency
  5. Enable controlled updates by administrators

4. What Are Global Tables

Global tables store common reference data used across EasyLib, such as:

  1. Status codes
  2. System flags
  3. Configuration parameters
  4. Standard values used in reports and validations

5. Functional Overview

5.1 Table Selection

  1. Select the required global/master table from the list.
  2. Each table represents a specific configuration category.

5.2 View Records

  1. Displays existing entries in the selected global table.
  2. Helps verify current system configurations.

5.3 Add / Edit Records

  1. Allows authorized users to:
  2. Add new reference values
  3. Modify existing values
  4. Changes reflect across all linked modules.

5.4 Activate / Deactivate Values

  1. Enables or disables specific master values without deleting them.
  2. Helps control usage without data loss.

6. Role in System Health & Stability

Global Table Maintenance supports system health by:

  1. Preventing invalid or inconsistent data
  2. Ensuring smooth module integration
  3. Supporting upgrades and feature enablement
  4. Maintaining standardized system behavior

7. Best Practices

  1. Restrict access to authorized administrators
  2. Document changes made to global tables
  3. Avoid frequent changes to critical tables
  4. Validate impact before modifying values

8. Outcome

Using Global Table Maintenance ensures:

  1. Data consistency
  2. Reliable system configuration
  3. Reduced errors across modules
  4. Stable EasyLib operations

Back Up Files Report

1. Introduction

The Back Up Files Report module provides visibility into database backup activities, helping administrators ensure data safety, recovery readiness, and compliance. This module plays a crucial role in server health monitoring and disaster recovery planning.

2. Access Path

Database Systems Reports ? Back Up Files Report

3. Purpose of Back Up Files Report

  1. Track database backup history
  2. Verify backup completion and frequency
  3. Identify missing or failed backups
  4. Support audits and compliance checks
  5. Ensure disaster recovery preparedness

4. Information Displayed in Back Up Files Report

4.1 Backup File Name

  1. Name of the backup file generated.
  2. Usually includes database name and date.

4.2 Database Name

  1. Identifies which database was backed up.

4.3 Backup Date & Time

  1. Shows when the backup was created.
  2. Helps verify backup schedules.

4.4 Backup Type

  1. Indicates type of backup:
  2. Full
  3. Incremental
  4. Differential (if applicable)

4.5 Backup Location

  1. Path or storage location where backup is stored.
  2. Helps in retrieval during restoration.

4.6 Backup Status

  1. Displays:
  2. Success – Backup completed successfully
  3. Failed – Backup process failed
  4. Critical for monitoring data safety.

5. Report Actions

Search & Filter

  1. Filter by:
  2. Database name
  3. Date range
  4. Backup status

Export

  1. Export backup reports for:
  2. Audit records
  3. Compliance documentation
  4. Management review

6. Role in Server Health Check

The Back Up Files Report contributes to server health by:

  1. Ensuring regular backups are taken
  2. Detecting backup failures early
  3. Supporting data recovery during server failures
  4. Maintaining compliance with IT policies

7. Best Practices

  1. Review backup reports daily or weekly
  2. Investigate failed backups immediately
  3. Maintain off-site or cloud backups
  4. Retain backups as per data retention policy
  5. Test backup restoration periodically

8. Outcome

Using the Back Up Files Report ensures:

  1. Data protection
  2. Business continuity
  3. Reduced risk of data loss
  4. Reliable disaster recovery planning