ApexReporter Studio

What, why & how

What it is

ApexReporter Studio is a visual, drag-and-drop, band-based report designer and runtime for Oracle Database — the same design language as Oracle Reports Builder (report/page headers and footers, group headers and footers, a detail band) rebuilt as a modern browser application. You design a report once against a live Oracle query and publish it to PDF, Excel, Word, PowerPoint, CSV, or HTML, on demand or on a schedule.

It ships as two cooperating processes: a browser-based designer (the application you interact with) and a self-hosted server that talks directly to your Oracle database and renders the final output. Everything runs on infrastructure you control — nothing about your report data or your database credentials passes through a third party.

Why it exists

Organizations that built their operational reporting on Oracle Reports and Oracle Forms are past due for a modernization plan — vendor direction has moved away from those tools, and the alternative most teams reach for is a general-purpose BI product that doesn't understand Oracle Reports Builder concepts (bands, PL/SQL lifecycle triggers, format masks, bind-variable parameters) and doesn't integrate cleanly with an existing Oracle APEX estate. ApexReporter Studio is purpose-built to close that gap: a familiar band-based design surface for teams who already think in Oracle Reports terms, native Oracle connectivity with no separate client install, and first-class Oracle APEX invocation built in from day one.

How it works

At a high level:

1. The designer (your browser) is where you connect to Oracle, write or generate a query, and lay out a report visually.
2. Saved reports, users, schedules, and version history are tracked by the server in a small embedded metadata database — no separate database server to install or license for the tool itself.
3. When you preview, export, or a scheduled job fires, the server runs your query against Oracle directly (in thin mode — no Oracle Instant Client required) and renders the result into the requested output format.
4. Reports can be triggered interactively from the designer, on a cron schedule with automated delivery, or invoked remotely — including directly from an Oracle APEX page.

How it compares

Three tools sit in the same general space — designing a formatted, data-driven document and getting it out to users — but they solve that problem in genuinely different ways. This is a straight technical comparison, not a marketing claim: pick the row that matches what you actually need.

Platform & requirements

Installation

ApexReporter Studio installs the same way on Windows and Linux: unpack it anywhere on disk, run the provided launch script, and it bootstraps its own configuration, installs its dependencies, and starts.

Windows

1. Install Node.js 22.5.0 or later (LTS installer from nodejs.org, or winget install OpenJS.NodeJS.LTS).
2. Extract ApexReporter Studio to an install folder of your choice.
3. Open PowerShell in that folder and run .\start.ps1.
4. On first run this creates the configuration file from its template, installs dependencies, and launches the designer in your default browser once it's reachable.

Linux

1. Install Node.js 22.5.0 or later — via your distribution's NodeSource repository is recommended over an older distro-bundled version.
2. Extract ApexReporter Studio to an install directory.
3. Make the scripts executable once: chmod +x start.sh stop.sh
4. Run ./start.sh. Behavior mirrors Windows: configuration bootstrap, dependency install, then launch. Add NO_BROWSER=1 on a headless server.

Production deployment

For a persistent, production installation, ApexReporter Studio packages into a standalone runtime: a single compiled Node.js process that serves both the API and the compiled designer application from one port — no separate dev server. Run it under a process manager so it survives reboots and crashes:

Put a reverse proxy (nginx, IIS, or Oracle ORDS/HTTP Server) in front to terminate HTTPS — the application itself speaks plain HTTP and expects TLS to be handled at that layer.

Verifying the install

A healthy installation, checked in order:

1. GET /api/health returns a JSON status — confirms the server process is up.
2. The designer loads in a browser and shows the login screen.
3. Signing in with the administrator account loads the designer shell — toolbar, palette, canvas, properties panel.
4. The built-in demo connection returns rows for a sample query — confirms the full client-to-database path works without needing a real Oracle instance.
5. A report can be designed, saved, previewed, and exported to PDF.

Configuration

Every deployment-level setting lives in one plain-text file, config.ini, at the root of the install — the single place to look, read at startup. Restart the application after editing it.

Administrator password

On a brand-new install, the value in [admin] password becomes the initial administrator password (leave it blank and one is generated and shown once in the startup console). On an existing install, changing this value and restarting resets only that one account's password — every report, connection, schedule, and other user account is left completely untouched.

Connecting to Oracle

Connection profiles are managed inside the designer itself (Connections panel), not in a config file. Each profile stores a display name, an EZConnect string or TNS alias, and credentials — passwords are encrypted at rest using the key configured in [security]. A built-in DEMO connection with sample data is always available and needs no configuration.

Licensing & plans

ApexReporter Studio is licensed by activation key, applied once in config.ini (or updated later from inside the running application, without a restart, from the About panel). The application will not start without a valid key.

Each activation key licenses one installation — a single physical or virtual machine — not a number of seats. Every Basic, Pro, or Enterprise plan's monthly and yearly price is per machine, up to that plan's user limit; running the same key on a second machine isn't supported. A key can optionally be hardware-locked to that one machine's fingerprint (see [license] hardware_key in Configuration) so it can't simply be copied to another server.

Three plans — Basic, Pro, and Enterprise — cover every user on the installation (designers, viewers, and administrators alike count toward a plan's user limit; there's no separate unlimited-viewer tier). Every plan, including Trial, includes all four report styles (Tabular, Group Above, Group Left, Summary Only) and the Crosstab element — none of that is plan-gated. Basic is a single-connection, single-user plan covering PL/SQL functions and procedures, up to 30 reports. Pro adds multiple database connections, up to 5 users, version history, triggers, report page setup, single-report import/export, and up to 100 reports. Enterprise lifts every limit — unlimited users and reports — and adds report scheduling, custom fonts, and bulk export/import of all reports at once. Custom DB Host, Alternate DB Engines (PostgreSQL/MySQL), the JasperReports XML export, and the two migration importers are separate one-time plug-in purchases available on any plan — see Plug-ins & migration. See the pricing section on the main site for the full feature comparison and current rates.

Want to try the designer itself first? A live hosted demo — no install, no signup — is always available at apex-reporter.com/studio.

A plan or seat-count change made from the About panel takes effect immediately across the running application — no downtime, no reinstall.

Navigation & interface

The designer is a single-page application laid out in four regions:

Most toolbar actions and panels are visible to every signed-in user; creating, editing, and deleting reports, connections, schedules, and other authoring actions require the Administrator, Designer, or Developer role — see Administration.

Core components

Bands

A report is built from bands, the same structure as Oracle Reports Builder: Report Header, Page Header, any number of Group Headers, a Detail band, any number of Group Footers, Page Footer, and Report Footer. Groups can be nested, and a page break can be forced on any group boundary.

Elements

Sixteen element types can be placed on any band:

Subreports nest recursively, with parent-to-child parameter mapping, so a master/detail layout is built the same way you'd expect from Oracle Reports Builder.

Report styles

The report wizard scaffolds a starting layout in one of four styles, and any of them can be freely edited afterward on the canvas like any other report:

Charts

The Chart element supports sixteen chart types — line, bar, column, area, combo, pie, donut, radar, scatter, bubble, gauge, funnel, waterfall, heatmap, treemap, and candlestick — rendered pixel-identically whether you're looking at the canvas, an HTML preview, or a generated PDF, and embedded as native, editable chart objects (not images) in PowerPoint exports for the chart types PowerPoint itself supports natively.

Crosstab

The Crosstab element pivots query rows into a row-header × column-header grid with an aggregated measure at each intersection (sum, count, average, min, or max) — the same shape as a spreadsheet pivot table, laid out and styled directly on the report canvas and rendered consistently across HTML, PDF, and every export format.

Parameters, variables & formulas

• Parameters — user-supplied input bound to a query's bind variables (text, date picker, checkbox, radio, list of values, or multi-select controls), used to filter what a report returns at run time.
• Variables — running calculations (sum, count, average, min, max, or a custom formula) that reset at the report, page, or group level, e.g. a group subtotal or a grand total.
• Formulas — named, reusable per-row expressions defined once and dragged onto a band exactly like a query column, e.g. an "Annual Salary" formula computed from a monthly salary field.

Data source & connections

A report's data source is a SQL query (or a stored procedure/ref cursor), run against an Oracle connection profile using standard named-bind syntax. The Query panel offers a live preview against real data while you design, and an AI-assisted "Generate with AI" option that turns a plain-English description into a starting query.

Feature functionality

Publishing & export

Every report, on every plan, can be previewed instantly as HTML, or exported to PDF (with true pagination, page breaks, and repeating group headers/footers), designer-fidelity Excel, Word, and PowerPoint, CSV, or raw JSON. Custom fonts (.ttf/.otf) can be uploaded and embedded directly into PDF and HTML output on the Enterprise plan.

Scheduling & unattended delivery (Enterprise)

Any report can be scheduled on a standard cron expression, with automatic retry and a full run history per job. Scheduling changes take effect immediately — no restart required. Delivery targets are Email (SMTP) or FTP/SFTP, configured once for the whole deployment; a job simply chooses recipients or a remote path within that configured target. A "Run Now" action executes a job on demand outside its schedule, useful for testing.

PL/SQL triggers & Program Units

Reports support the same five lifecycle trigger points as Oracle Reports Builder — Before/After Parameter Form, Before/After Report, and Between Pages — each a plain PL/SQL block run against the report's own connection at the matching point in rendering, whether the report is previewed, exported, or run on a schedule. Program Units let you author, validate, and compile PL/SQL functions and procedures directly against your Oracle connection from within the designer.

REF CURSOR / stored-procedure data sources

A report's data source (or any named query) can be a call to a PL/SQL function that returns a SYS_REFCURSOR, or a procedure with its own REF CURSOR OUT parameter, instead of a literal SQL statement — for data-assembly logic too complex to express as one SELECT. Write the call exactly as you would in PL/SQL; ApexReporter wraps and binds it automatically.

Placeholder variables

A report-scoped variable can be set purely by PL/SQL rather than derived from row data — Oracle Reports Builder's own Placeholder column idiom. Give it a PL/SQL function-call expression and it's evaluated once per render, its value available to any Field element like any other variable.

Parameter validation

Any parameter can carry a PL/SQL boolean validation expression, checked before any data is fetched — reject bad input with a clear, custom message instead of producing a bad or empty report.

AI-assisted authoring

Where enabled, "Generate with AI" turns a plain-English description into dialect-aware SQL for the Query panel, and into a report expression for any bound field or formula — a starting point to refine, not a black box; the underlying SQL and expressions remain fully visible and editable.

Version history (Pro and Enterprise)

Every save creates a new version rather than overwriting the last one — nothing is ever silently lost. Past versions can be browsed and reverted at any time; reverting itself creates a new version, so the version you reverted from stays in history too.

Portability (Pro and Enterprise)

A report's full design can be exported to a single portable file for backup or for moving between installations, and imported back in. Pro covers one report at a time; Enterprise adds exporting or importing every report on the installation at once.

Security & access control

Session-based authentication with six built-in roles (Administrator, Designer, Developer, Publisher, Runtime User, Viewer), a full audit trail of every meaningful action, per-report access restriction by role, and connection passwords encrypted at rest. A separate trusted service-caller key allows headless callers — most notably Oracle APEX — to invoke reports without an interactive login.

Step-by-step walkthroughs

Concrete, do-this-then-that examples for the PL/SQL-facing and dashboard features above. Every example uses the built-in DEMO connection (Oracle's classic EMP/DEPT tables, no setup required) except where noted — Program Units, REF CURSOR data sources, Placeholders, and Parameter validation all compile/run real PL/SQL, so those need a genuine Oracle connection.

Program Units — a Function

1. Toolbar → Program Units → + New Program Unit, name it AMT_IN_WORDS_FN.
2. Kind: Function, return type VARCHAR2. Paste the full PL/SQL, header included:

   function AMT_IN_WORDS_FN(p_amount in number) return varchar2 is
   begin
     return to_char(to_date(trunc(p_amount), 'J'), 'JSP');
   end;

3. Pick a connection, click Validate/Compile — status flips to VALID, or shows real Oracle compiler errors to fix.
4. Use it in a query (SELECT e.*, AMT_IN_WORDS_FN(e.sal) AS SAL_WORDS FROM EMP e) or a Field's Expression box: {AMT_IN_WORDS_FN(SAL)}.

Before/After Report triggers

1. Toolbar → Triggers — five tabs matching Oracle Reports Builder's own lifecycle points: Before/After Parameter Form, Before/After Report, Between Pages.
2. Type plain PL/SQL, no BEGIN/END wrapper needed:

   -- Before Report
   LOG_RUN_PROC('Monthly Sales Report');

3. Save. An exception raised by a trigger aborts the render with that error, exactly like Reports Builder.

REF CURSOR data source

1. Toolbar → Data Source → Data source type → Function returning a REF CURSOR.
2. Type the call as real PL/SQL — no SELECT, no BEGIN/END:

   pkg.get_dept_summary(:P_DEPTNO)

   This runs as BEGIN :cursor := pkg.get_dept_summary(:P_DEPTNO); END; — the returned cursor becomes the report's rows.
3. For a procedure instead, include the literal :cursor placeholder yourself: pkg.get_dept_summary(:P_DEPTNO, :cursor).
4. Click Run Preview to test before saving.

Placeholder variables

1. Toolbar → Parameters & Variables → Variables → + Add Variable, name it TAX_RATE.
2. Calculation → Placeholder (PL/SQL-set). Reset On locks to REPORT automatically — the only scope Placeholders support.
3. Type a real PL/SQL function-call expression: pkg.get_current_tax_rate(:P_YEAR) — evaluated once per render as SELECT pkg.get_current_tax_rate(:P_YEAR) FROM DUAL.
4. Reference it anywhere like any other variable: a Field's Field Name TAX_RATE, or {TAX_RATE} in an expression.

Parameter validation

1. Toolbar → Parameters & Variables → Parameters → under the parameter, the Validation row takes a PL/SQL boolean: TO_NUMBER(:P_YEAR) BETWEEN 2000 AND 2099.
2. Optionally set a custom error message — otherwise a generic one is shown.
3. Cross-parameter checks work too (bind every submitted parameter by name), e.g. on a second parameter: TO_DATE(:P_END_DATE,'YYYY-MM-DD') >= TO_DATE(:P_START_DATE,'YYYY-MM-DD').
4. A failed validation rejects the whole render before anything is fetched — no partial/bad report is ever produced.

KPI Card

1. Add a named query (Toolbar → Data Source → + New Query), e.g. TOTAL_SALARY_QUERY: SELECT SUM(SAL) AS TOTAL FROM EMP.
2. Drag KPI Card from the Palette onto the Report Header or Footer. (Enterprise plan feature — an Administrator can grant it per-user under Administration → Users → Permissions.)
3. Properties panel: Data source → TOTAL_SALARY_QUERY; Aggregate → SUM; Measure field → SAL; Label → "Total Salary"; Number format → 999,999.00.
4. Add several KPI Cards, each with its own Data source, to build a real multi-metric dashboard on one report.

Dashboard reports (full-screen, auto-refresh)

1. Select the report itself → Report type → Dashboard.
2. Build the layout with several KPI Card/Chart/Crosstab elements, each pointed at its own named query.
3. Preview auto-fits the report to fill the available space (not a fixed paper size) and offers a Full Screen button for a true full-browser-viewport wallboard view.
4. For an actual kiosk deployment, link the report as HTML with ?refresh=<seconds> appended:

   http://your-server:4000/api/reports/<report-id>/render?format=html&apiKey=<key>&refresh=60

Oracle APEX integration

ApexReporter Studio runs as its own service alongside your Oracle APEX/ORDS mid-tier — there's no plug-in to install into APEX itself. An APEX page calls it over plain HTTPS, the same way it would call any external REST API, and the two systems can point at the same Oracle database without sharing an application server.

Three ways to invoke a report from APEX

Setup checklist (do these in order)

1. Register the JavaScript client first. Shared Components → User Interface → JavaScript → File URLs (application-level, so every page has it), and add the exact URL your own server serves it at, e.g.:

   http://reporter-host:4000/apexreporter-client.js or
                  
   https://apex-reporter.com/studio/apexreporter-client.js

   This must load as a real external <script src> — not pasted inline into "Execute when Page Loads" — so it exists before any button's Dynamic Action runs. Skipping or mistyping this step is the #1 cause of the ApexReporter is not defined error below.
2. Design and save the report in ApexReporter Studio; copy its report id from the Open dialog (a UUID, e.g. eabe5c46-ace5-49fc-9bb8-0e4dd8c8db07).
3. Make sure the report's query uses named binds that match a Parameter defined on the report (e.g. :P_DEPTNO in the SQL ↔ a Parameter named P_DEPTNO).
4. Set a service-caller API key ([security] report_api_key= in config.ini, or REPORT_API_KEY) — APEX-driven calls have no interactive session of their own, so this key is what authenticates them; every call gets 401 without it.
5. Set allowed origins (CORS) to your APEX host — [security] cors_origin=https://your-apex-host.example.com — since the browser is calling a different origin than the one serving the APEX page. Restart the server after changing this.

Example — running a report from a button click

Report saved with id eabe5c46-ace5-49fc-9bb8-0e4dd8c8db07, ApexReporter running at http://reporter-host:4000, a page item P1_DEPTNO already on the page. Dynamic Action on the button's Click event → Execute JavaScript Code:

ApexReporter.run({
  baseUrl: "http://reporter-host:4000",
  report: "eabe5c46-ace5-49fc-9bb8-0e4dd8c8db07",
  format: "pdf",
  parameters: { P_DEPTNO: $v("P1_DEPTNO") },
  target: "_blank",
  apiKey: "your-report-api-key"
});

$v("P1_DEPTNO") reads a page item's current value with no page submit required; any number of parameters can be passed as long as each one matches a Parameter defined on the report. format also accepts xlsx, csv, docx, pptx, html, or json; target accepts "_blank", "_self", or "download" to force a file download instead of navigating.

Example — embedding a live preview inline

Add a Static Content region containing <iframe id="reportPreviewFrame" style="width:100%; height:800px; border:0"></iframe>, then a Dynamic Action (page load, button click, or a page item's Change event for a live-filter feel):

ApexReporter.preview("#reportPreviewFrame", {
  baseUrl: "http://reporter-host:4000",
  report: "eabe5c46-ace5-49fc-9bb8-0e4dd8c8db07",
  parameters: { P_DEPTNO: $v("P1_DEPTNO") }
});

This always renders format=html and just points the iframe's src at the render URL. Since an iframe can't send a custom header, an API key here must be appended to the URL as &apiKey=... instead — build the URL with ApexReporter.buildUrl(baseUrl, report, "html", parameters) + "&apiKey=" + key, or keep this endpoint behind network-level access control (VPN/firewall) if you'd rather not expose the key in markup.

Example — plain link, zero JavaScript

An APEX button set to Action → Redirect to URL, using APEX's own &ITEM_NAME. substitution syntax, works with no script at all:

http://reporter-host:4000/api/reports/eabe5c46-ace5-49fc-9bb8-0e4dd8c8db07/render?format=pdf&apiKey=your-report-api-key&P_DEPTNO=&P1_DEPTNO.

APEX resolves &P1_DEPTNO. to that page item's current value before redirecting. Since the key is visible in the URL/browser history this way, prefer the JavaScript client above whenever the report is reachable from an untrusted network.

Plug-ins & migration

Five optional plug-ins ship with every installation, already installed but locked until activated. Each is a one-time, per-installation purchase — $1,249, lifetime license — independent of your Basic/Pro/Enterprise plan, and it never expires.

Activating a plug-in

1. Open Administration → Plug-ins from the toolbar. Every plug-in is listed as "Installed" but "Not activated" until a key is entered.
2. Paste the activation key issued for that plug-in and click Activate.
3. Once activated, the matching feature (an import/export toolbar button, or a connection's Host field) is enabled for the whole installation — it stays activated across restarts, not per-user, unless an Administrator has restricted a specific user's access to it (see Users & roles below).

Uninstalling a plug-in

An Administrator can revoke a previously-activated plug-in at any time from the same panel — click Uninstall. This clears the activation immediately across the whole installation; using it again later requires entering the activation key again.

Creating a migratable export from Oracle Reports Builder 12c

The importer needs the report's definition as XML, not the data output a running report produces. Two ways to get it:

Method 1: Using the Oracle Reports Builder (GUI)

This is the easiest method if you prefer a visual interface and only have a few files to convert.

1. Open Oracle Reports Builder 12c.
2. Click File in the top menu.
3. Select Open and choose your .rdf file.
4. Click File again.
5. Select Save As.
6. Click the File Type dropdown menu.
7. Select Reports XML (*.xml).
8. Click Save.

Method 2: Using the Command Line Utility (rwconverter)

This is the fastest method for batch conversions or automation scripts. Oracle provides the rwconverter executable inside your middleware home directory.

1. Open your command prompt (Windows Terminal or Linux Shell).
2. Navigate to your Oracle Forms/Reports binary directory where rwconverter is located. For example:

   Windows: C:\Oracle\Middleware\Oracle_Home\user_projects\domains\base_domain\developer_common\bin\
   Linux:   /u01/app/oracle/middleware/user_projects/domains/base_domain/developer_common/bin/

3. Run the conversion command using the syntax below:

   rwconverter userid=username/password@database source=input_file.rdf dest=output_file.xml stype=rdffile dtype=xmlfile batch=yes

Creating a migratable export from Jaspersoft Studio

.jrxml is Jaspersoft Studio's native, plain-text save format — every report you design in it already exists as a .jrxml file on disk, so there's no separate export step. Locate that file (or use File → Save if you haven't yet) and hand it to the importer as-is.

Importing into ApexReporter Studio

1. In the toolbar, click Import Oracle Reports Structure (XML) or Import JasperReports (JRXML) — enabled once the matching plug-in above is activated.
2. Choose the .xml or .jrxml file. The importer parses it and shows a summary — report style, parameter/group/column/summary counts, and how many bands it produced.
3. Review anything listed under "needs manual review" — text this specific importer couldn't confidently translate. For an Oracle Reports import, the original PL/SQL for any such item can be viewed inline via "Show original PL/SQL" before you decide how to reproduce it.
4. Click Import into Designer. The report opens in the designer exactly like any other — attach a real Data Source connection before previewing, since the SQL is imported but no connection is attached automatically.

Management

Report lifecycle

Reports are created from a blank canvas, from a guided wizard that scaffolds a layout from your chosen columns, or by migrating an existing Oracle Reports or JasperReports definition via the plug-ins above. Every save is versioned; folders and tags help organize a larger catalog, filterable in the Open dialog.

Connections

Connection profiles are created, tested, and managed from the Connections panel — name, EZConnect string or TNS alias, and credentials, with a one-click connection test before you rely on it in a report.

Scheduled jobs

The Scheduled Reports panel lists every job with its cron schedule, delivery target, enabled state, last run time, and last status, and lets you drill into a job's full run history — including retries and error detail on a failed attempt.

Fonts & plug-ins

Custom font families are uploaded and managed from the Fonts panel. The Oracle Reports and JasperReports migration importers are activated the same way — see Plug-ins & migration above for the full walkthrough.

Administration

Every administrative feature lives in one Administration window, opened from its own toolbar button, with a separate tab for each area below: Plug-ins, Users, Administration, Sessions, and Visitor Inbox. A Designer or Developer sees only the Plug-ins tab (the same access they always had to activate an import plug-in); the other four tabs are Administrator-only.

Users & roles

Administrators manage accounts and role assignments from the Users tab. Six roles are built in, but they work on two different levels: what you can do in the application, and which named audience a specific report is restricted to.

Platform access

Every route in the application checks a role against exactly one of two effective tiers — there is no functional difference within either group:

Per-report audience restriction

This is where having six distinct names actually matters: any report can be restricted to specific roles via its access-control setting, independent of the platform-access tiers above. An author could mark a sensitive report visible only to "Publisher," for example, even though Publisher, Runtime User, and Viewer all grant identical baseline access to the application otherwise — the six role names exist to give report authors meaningful audience labels for this restriction, not because the platform treats each of the six differently on its own. Leaving a report unrestricted (the default) makes it open to any signed-in user.

The built-in admin account is a permanent break-glass superuser: it always holds every role, can't be deactivated or given an expiry, and its password can only be changed by itself or via config.ini — so a deployment can never be accidentally locked out of its own administration.

Finding & duplicating users

The Users tab has a search box that filters the account list by username or display name as you type — useful once a deployment has more than a handful of accounts. Each row also has a Duplicate button: it pre-fills the New User form with the source account's exact role assignment, so you only need to enter a new username and password. Once the new account is created, every other privilege the source account has is copied over too — its per-user feature overrides, connection-count cap, and plug-in access (see Per-user permissions below) — giving you a genuine "same roles and privileges" clone rather than just a same-role account you'd still have to configure by hand.

Account expiry & lockout

Any account other than admin can be given an expiry date/time — past that point it can no longer log in, and an already-open session is closed immediately rather than waiting for it to expire naturally. After five consecutive failed login attempts, an account locks automatically and needs an Administrator to unlock it from the Users tab; the built-in admin account is permanently exempt from lockout.

Per-user permissions

Beyond role assignment, an Administrator can fine-tune exactly what one specific user can do — independent of, and layered on top of, the installation's plan/license. Click the permissions icon on any user's row to set:

• Feature overrides — force any individual feature (report import/export, version history, personal folders, scheduled reports, custom fonts, JasperReports XML export, and more) to Allow or Deny for that one user, regardless of what the plan otherwise includes. Left on "Inherit," the user simply follows the plan/license default like everyone else.
• Connection limit — override the plan's whole-install connection cap with a personal limit for one user, e.g. letting a power user like "scott" create more connections than the plan would otherwise allow, while capping a more limited account lower.
• Plug-in access — restrict a specific user to only certain activated plug-ins, e.g. allowing the JasperReports importer but not the Oracle Reports importer for one particular account, even though both are activated for everyone else on the installation.

Every override is enforced server-side, not just hidden in the interface — a denied user can't work around it by calling the underlying action directly.

Audit log

Every meaningful action — logins, and every create, update, or delete of a report, connection, user, or schedule — is written to a permanent audit trail, reviewable by an Administrator at any time.

Administration dashboard

The Administration tab surfaces user, report, connection, and schedule counts, connections broken down by type, scheduled-job health (success/failure/running over a trailing window), and the audit log — everything an administrator needs to check the health of a deployment at a glance.

Sessions

The Sessions tab lists everyone currently signed in to the installation — one row per user (not per browser tab, so someone logged in from two devices at once still shows as a single row with a session count), with their last login time and when their session expires. An Administrator can end any user's session with one click, signing them out of every device/browser at once immediately; their very next action anywhere is treated exactly like an expired login, no restart or wait required. Ending your own session works the same way, for signing yourself out remotely.

Visitor Inbox

The public marketing site's Contact Us form and "forgot password" request both land here, not in an external inbox — each submission can be marked Unread, Read, Important, Needs Action, or Resolved as an Administrator works through it, with an unread-count badge on the toolbar so nothing sits unnoticed.

Security & deployment

• Every action requires a signed-in session, or the dedicated trusted-service-caller key for headless integrations — there is no open-by-default mode.
• Connection passwords are encrypted at rest, never returned to the browser once saved.
• Session cookies are HTTP-only and same-site restricted.
• Put the application behind HTTPS via a reverse proxy in front of it — the application itself expects TLS to be terminated there.
• Restrict allowed browser origins (CORS) to the exact hosts that need to call it, rather than leaving it open.
• Review role assignments periodically — anyone with Designer, Developer, or Administrator access can create and test Oracle connections using whatever credentials they submit.
• Check the audit log periodically for unexpected activity.

Data persistence & backup

All application state — the metadata database, saved report versions, and uploaded assets — lives under one configured data directory. Point that directory at a persistent, backed-up volume in any real deployment; the Oracle databases you report against are, of course, backed up independently by your own database team.

Troubleshooting & FAQ

Can I try ApexReporter Studio before buying a plan?

Yes — a live hosted demo is available anytime at apex-reporter.com/studio, no install and no signup required. When you're ready for your own connections, users, and schedules, install it on your own server under a Basic, Pro, or Enterprise plan.

Is this a cloud service?

No — ApexReporter Studio is self-hosted. It installs on your own Windows or Linux server and connects directly to your Oracle instance; your report data and query results never leave your network.

Do we need Oracle Instant Client?

No. Standard username/password and EZConnect/TNS connections run in thin mode out of the box.

Can we migrate existing Oracle Reports or JasperReports definitions?

Yes, via the Oracle Reports Migrator and JasperReports Migrator plug-ins (one-time purchase per installation — see Plug-ins & migration). Once activated, each reads a report definition export and converts it into a starting report, flagging anything that needs manual review rather than guessing at business logic.

The application won't start

Check the startup console output first — it states plainly whether the issue is a missing/invalid license activation key, a port already in use, or an unmet Node.js version requirement, rather than failing silently.

A scheduled job keeps failing

Open the job's run history in the Scheduled Reports panel — every attempt (including retries) records its actual error, which is almost always a query error, an expired connection credential, or a misconfigured delivery target.

Support

For licensing questions, deployment assistance, or to report an issue, use the contact options on the main site's pricing section. Administrators can also find build/version information and support details from within the running application via the About panel.