Frequently Asked Questions

FAQs

Welcome to the Infobelt Omni Archive Manager (OAM) Knowledge Hub, your comprehensive resource for enterprise data archiving, cloud-native architecture, and compliance management. Here you will find direct answers regarding our platform’s AI-powered capabilities, application connectors, security frameworks, and global service level commitments.

Section 1:

Infobelt Omni Archive Manager Solution & Platform Overview

Q. What is Infobelt Omni Archive Manager (OAM) and what does it do?

Infobelt Omni Archive Manager (OAM) is an enterprise-grade data archiving and long-term retention platform. It helps organizations safely decommission legacy applications, eliminate database bloat, and maintain strict regulatory compliance across all structured and unstructured data.

Key features include:

Automated Data Ingestion: Securely extracts and compresses structured data (ERP, CRM, financial systems) and unstructured content (PDFs, emails, images) into a centralized, tamper-evident repository.
Active Archiving: Provides near-line, transparent data retrieval for end users directly from within source applications like SAP or Oracle.
Automated Retention Engine: Enforces record-level retention rules and legal holds to ensure compliance with global regulations like GDPR, SOX, HGB, and GoBD.
Intelligent Search & Reporting: Features a no-code drag-and-drop query builder and generative AI-powered natural language search for rapid data retrieval.

Q. Which file formats and software applications does Infobelt OAM support?

Infobelt OAM features native out-of-the-box support for more than 200 data sources, encompassing major enterprise systems, relational databases, and file formats.Supported systems and formats include:

Enterprise Software & ERPs: Native integration with SAP S/4HANA, SAP ECC, SAP R/3 (across FI, MM, SD, HR, CO, PP, QM, and PM modules), Salesforce, Workday HCM, and Microsoft Dynamics 365.
Databases: Supports any JDBC/ODBC-compliant database, including Oracle, Microsoft SQL Server, IBM DB2, PostgreSQL, MySQL, Sybase, and Cosmos DB.
Unstructured Documents: Standard office files (DOCX, XLSX, PPTX), PDFs (including archive-standard PDF/A), images (TIFF, JPEG, PNG), and markup files (XML, JSON, HTML).
Email & Collaboration Platforms: Microsoft Exchange, Office 365, Microsoft Teams, Google Workspace, and standard email archives (PST, EML, MBOX).

Q. How do users access and query the archived data in Infobelt OAM?

Users can access the platform flexibly through a fully responsive web application, programmatic APIs, or direct deep-link integrations within existing corporate tools.

The five primary access methods are:

Web Browser Portal: A secure, responsive interface accessible from any modern desktop or mobile browser via Single Sign-On (SSO) with zero client-side installation.
Native Active Archiving Links: Deep-link retrieval built right into source transactions (such as SAP Fiori or SAP GUI), allowing users to view archived records transparently without realizing the data moved.
GenAI Natural Language Search: An AI assistant that lets business users type conversational questions (e.g., “Show 2022 invoices from Supplier X over €50,000”) to generate instant ad hoc reports.
Developer-Friendly REST APIs: Full OpenAPI (Swagger) documented REST endpoints for custom reporting and seamless downstream IT integrations.
Automated Scheduled Delivery: Programmatic report generation that securely pushes data directly to user emails or designated SFTP locations.

Q. Does Infobelt provide pre-built archiving accelerators?

Yes, Infobelt OAM includes a robust library of pre-configured implementation accelerators designed to minimize deployment risk, reduce data mapping time, and accelerate time-to-value.

These turnkey accelerators include:

SAP Module Blueprints: Pre-mapped archiving templates for core SAP objects (including FI-GL, FI-AR, MM-MATBEL, and SD-VBAK) with validation scripts.
Compliance Rule Blueprints: Out-of-the-box retention schedules mapped directly to global regulatory frameworks.
Standard Reporting Dashboards: Immediate access to business essentials like AP aging trends, compliance health, and comprehensive audit history extracts.
Automated Data Quality Checkers: Rules for completeness, referential integrity, and format verification applied instantly during data ingestion.

Section 2:

AI Capabilities & Data Governance

Q. How does Infobelt OAM use Artificial Intelligence (AI) and Machine Learning (ML)?

Infobelt OAM embeds AI and machine learning directly into its ingestion, search, and compliance pipelines to automate complex data management tasks.

The platform leverages AI and ML in four core areas:

Generative AI Natural Language Querying: Integrates with private Large Language Models (LLMs) to allow business users to search archives using natural, conversational language instead of complex SQL or database queries.
Automated Document Classification: Uses NLP and computer vision to automatically read, categorize, and tag unstructured files (like PDFs, scans, and emails) upon ingestion, assigning the correct retention rules without manual intervention.
Intelligent Ingestion & Anomaly Detection: Employs ML models to analyze historical data structures, flagging outliers, schema drift, structural anomalies, or corrupt files during the migration process.
Smart De-duplication: Automatically identifies and merges duplicate records, overlapping tables, and identical attachments across disparate legacy systems to maximize archive compression.

Q. Does Infobelt OAM support automated data profiling and structural validation?

Yes, the platform features a comprehensive, built-in automated data profiling and validation framework. This ensures that all data transferred into the archive remains complete, accurate, and trustworthy.

Key data profiling capabilities include:

Automated Source Profiling: Evaluates source database schemas before extraction to map primary/foreign key relationships, count null values, and determine data distributions.
Referential Integrity Enforcement: Validates that orphaned records are prevented and that interdependent database records are archived together as complete, cohesive business objects.
Business Logic Checks: Compares ingested data against pre-defined rules, confirming metrics like total document counts, hash balances, and mandatory field requirements match the source exactly.

Q. How does Infobelt OAM guarantee data integrity and chain of custody?

Infobelt OAM maintains a strict, unalterable chain of custody using automated cryptographic verification and immutable logging. This ensures your archived data is legally defensible and tamper-evident.

The system enforces data integrity through:

Cryptographic Checksums: Generates secure SHA-256 or SHA-512 hashes at the exact moment of data extraction. These are re-verified post-transfer and during long-term storage to detect any data corruption.
Immutable Audit Trails: Records every single platform action—including data ingestions, user searches, document views, compliance holds, and purge actions—in a secure, read-only audit log that cannot be modified or deleted by any user or administrator.
Background Consistency Audits: Periodically runs background sweeps to re-calculate document hashes across the entire archive, immediately alerting administrators if any integrity anomalies occur.

Q: How does the platform handle regulatory compliance, GDPR, and data retention?

Infobelt OAM features an automated, record-level compliance and retention engine designed to meet strict international standards, including GDPR, SOX, HGB, and GoBD.

Compliance automation features include:

Granular Retention Rules: Allows compliance teams to map retention periods based on specific date triggers, jurisdictional requirements, or business event types.
Defensible Destruction Workflows: When a data retention period expires, the platform executes a multi-stage approval workflow. No data is purged without explicit, multi-signature sign-off from authorized compliance officers.
Legal Holds: Enables administrators to instantly freeze specific records or entire datasets during litigation or active audits, overriding standard expiration dates and preventing accidental deletion.
GDPR Compliance (Right to Be Forgotten): Supports rapid, targeted data redaction or erasure capabilities, allowing organizations to cleanly purge specific consumer records across massive archived datasets to fulfill subject access requests (SARs).

Section 3:

Integration, Connectors, & Customizability

Q: How does Infobelt OAM integrate with existing enterprise software systems?

Infobelt OAM is built on an open, API-first architecture, allowing it to integrate seamlessly with standard corporate infrastructure via RESTful APIs and standard protocol gateways.

Integration methods include:

Out-of-the-Box (OOTB) Connectors: Features pre-built API and database connectors for over 200 commercial enterprise systems.
Standard Integration Protocols: Connects natively to systems using JDBC, ODBC, SFTP, FTPS, HTTPS, and AS2.
Application Services: Deeply integrates with common document repositories and messaging environments, including Microsoft SharePoint, OpenText, Documentum, Microsoft Exchange, and cloud object stores (AWS S3, Azure Blob).
Custom Extensibility: Includes a built-in development toolkit that allows your IT team or Infobelt engineers to quickly build bespoke connections to proprietary, home-grown legacy applications.

Q: Can Infobelt OAM be customized or extended to meet unique business requirements?

Yes. While the platform is a standard product, it is built to be highly extensible through configuration, a flexible microservices framework, and open API endpoints.

Customization options include:

Custom API Endpoints: Developers can build custom downstream applications or client portals using the platform’s comprehensive, OpenAPI-compliant REST APIs.
Flexible Metadata & Schemas: Administrators can define custom metadata schemas, custom archiving templates, and bespoke search forms without writing code.
Custom Plug-ins & Transformation Scripts: Supports custom Python or Java micro-scripts within the ingestion pipeline to handle complex, specialized data transformation or masking rules.
White-Labeling & Branding: The user interface can be branded with your organization’s logos, color schemes, and custom localized terminology.

Q: Does the platform support third-party components or plugins?

Yes, Infobelt OAM safely incorporates enterprise-grade, open-source modules and commercial libraries into its core microservices.

Third-party support includes:

Embedded Enterprise Tooling: Utilizes trusted open-source processing frameworks (such as Apache Spark for big data handling, Apache Tika for document content extraction, and Elasticsearch for rapid indexing).
Continuous Security Patching: All third-party libraries and dependencies are fully managed, monitored, and updated as part of Infobelt’s standard product release and patching cycles to ensure maximum security.
No Client-Side Add-ons Required: The browser interface requires no third-party silverlight, flash, or Java browser plugins, keeping the client footprint completely clean and secure.

Q: How does Infobelt OAM handle data transformation during archiving?

The platform includes an integrated, high-performance ETL (Extract, Transform, Load) engine capable of handling complex structural changes as data moves into the archive.

Key data transformation capabilities include:

Schema Evolution Support: Safely maps, merges, or rationalizes old legacy database structures into standardized archive tables.
Data Masking & Redaction: Can automatically tokenize, mask, or entirely redact sensitive records (like PII, credit card data, or SSNs) at the point of ingestion based on security policies.
Format Standardization: Converts obsolete or proprietary document formats into long-term, ISO-standard preservation formats like PDF/A, XML, or JSON.

Section 4:

Technical Architecture & Hosting Models

Q: What is the underlying technical architecture of Infobelt OAM?

Infobelt OAM is built on a modern, cloud-native microservices architecture designed for extreme scalability, fault tolerance, and high performance.

The platform’s technology stack includes:

Core Frameworks: Developing using Java (Spring Boot) and Python for backend microservices, ensuring cross-platform compatibility and high processing speeds.
Containerization & Orchestration: Built completely on Docker containers and orchestrated using Kubernetes (K8s) for automated scaling, self-healing, and seamless zero-downtime updates.
User Interface: A modern, single-page web application built with HTML5, CSS3, and JavaScript, requiring zero browser plugins or client-side installations.
Database & Storage Layers: Combines high-performance relational databases (like PostgreSQL) for metadata tracking, specialized document indexes (like Elasticsearch) for instant searching, and multi-tier object storage for the actual compressed data files.

Q: What deployment and hosting models does Infobelt OAM support?

Infobelt OAM offers complete deployment flexibility, supporting on-premises, private cloud, or fully managed cloud-native environments.

Available deployment options include:

Fully Managed SaaS Tenant: Hosted as a secure, dedicated private SaaS instance within Infobelt’s enterprise cloud environment, fully managed by Infobelt engineers.
Public Cloud (Hyperscalers): Deployed inside your organization’s corporate cloud tenants on Amazon Web Services (AWS), Microsoft Azure, or Google Cloud Platform (GCP).
Private Cloud / Virtual Environments: Supported on enterprise virtualization layers such as VMware vSphere and Red Hat OpenShift.
On-Premises Bare Metal: Can be deployed directly onto physical enterprise servers running standard Linux operating systems (including Red Hat Enterprise Linux and Ubuntu Server).

Q: Does Infobelt OAM support multi-tenancy and how is data isolated?

Yes, the platform natively supports a robust multi-tenant architecture that ensures strict logical and physical isolation between different business entities, departments, or corporate subsidiaries.

Data isolation mechanisms include:

Logical Tenant Separation: Separate encryption keys, distinct user access permissions, and independent database schemas ensure tenants can never see or access each other’s configuration or data.
Physical Deployment Isolation: For SaaS or private cloud environments, Infobelt can deploy dedicated, single-tenant infrastructure stacks (including isolated compute, isolated storage buckets, and isolated networks) to eliminate any risk of “noisy neighbors” or cross-tenant data leaks.
Independent Retention & Configurations: Each tenant can manage its own unique retention schedules, metadata schemas, search forms, and compliance workflows independently.

Q: How does the platform scale to handle massive volumes of enterprise data?

Thanks to its Kubernetes-driven microservices architecture, Infobelt OAM scales horizontally and dynamically to ingest and manage petabyte-scale archives without performance degradation.

Scaling features include:

Horizontal Auto-Scaling: The platform automatically spins up additional microservice containers (such as ingestion workers or extraction nodes) to handle peak workloads and tears them down when complete.
Distributed Processing Engines: Integrates with big data frameworks like Apache Spark to process, compress, and validate massive database extracts in parallel.
Tiered Storage Architecture: Moves older, infrequently accessed archives from high-performance block storage to cost-effective cold object storage (like AWS Glacier or Azure Archive) automatically, optimizing costs as data grows.

Section 5:

Security, Performance, & SLA Commitments

Q: What are the standard uptime SLAs and availability guarantees for Infobelt OAM?

Infobelt OAM guarantees a 99.9% platform availability service level agreement (SLA) for all cloud-hosted instances, measured on a monthly basis.

Our availability commitments include:

24/7 Monitoring: Automated platform health, infrastructure, and application monitoring tools continuously track performance and uptime.
Exclusions: Standard SLA calculations exclude pre-approved, scheduled maintenance windows, which are typically conducted during low-impact weekend hours.
Service Credits: Financial service credits are programmatically applied to the next billing cycle if the platform falls below the 99.9% uptime threshold in any given month.

Q: How does Infobelt handle critical system incidents and support tickets?

Infobelt operates a structured, multi-tier technical support framework with strict response time SLAs based on incident severity.

Our incident management response times are:

Priority 1 (P1) – Critical (System Down): 1-hour initial response SLA. Handled by a 24/7/365 on-call engineering rotation until resolved.
Priority 2 (P2) – Major (Core Function Impaired): 4-business-hour response SLA. Workarounds or hotfixes are prioritized during normal business hours.
Priority 3 (P3) – Minor (General Issues/Questions): Next-business-day response SLA. Resolved via standard support channels or scheduled patches.

Q: Where is the Infobelt support team located and what are their hours?

Infobelt provides global support coverage with regional teams situated to provide seamless, time-zone aligned assistance.

Our support footprint includes:

Support Hubs: Headquartered in Charlotte, North Carolina (Eastern Time, USA), with dedicated support engineering teams based in Europe and India.
European Support Hours: Standard business coverage is fully aligned with European time zones, operating from 08:00 to 18:00 CET/CEST, Monday through Friday.
Critical Coverage: P1 critical incidents bypass standard hours, offering global 24/7 support availability via an on-call pager system.
Dedicated Accounts: Enterprise customers are assigned a named Technical Account Manager (TAM) and a Customer Success Manager (CSM) to ensure a single, consistent point of contact.

Q: What are Infobelt’s Disaster Recovery (DR) and business continuity metrics?

Infobelt features a comprehensive disaster recovery architecture designed to prevent data loss and ensure rapid system restoration in the event of an infrastructure failure.

Our target DR metrics include:

Recovery Point Objective (RPO): Maximum of 4 hours. This ensures that, even in a catastrophic data center failure, no more than 4 hours of transactional or ingested data would ever be lost.
Recovery Time Objective (RTO): Maximum of 8 hours. The platform is engineered to be fully recovered, online, and accessible to users within 8 hours of a declared disaster.
Multi-Region Redundancy: Achieved through continuous database replication and automated configuration backups copied to geographically isolated secondary data centers or cloud zones.

Q: How frequently does Infobelt issue platform updates, patches, and security hotfixes?

Infobelt maintains software integrity and protection through a regular, predictable update cycle and automated security deployments.

Our patching cadence comprises:

Security Hotfixes: Deployed immediately upon discovery, verification, and testing of any critical vulnerability, operating entirely outside of standard release cycles.
Maintenance & Patch Releases: Issued on a monthly or quarterly basis to deliver minor feature updates, performance optimizations, and cumulative bug fixes.
Major Version Upgrades: Released 1–2 times per year, introducing significant platform capabilities and architectural improvements.
Zero-Downtime Maintenance: Leverages Kubernetes rolling updates to apply patches to active environments seamlessly, avoiding operational disruptions.

Infobelt Solutions FAQs