Skip to main content

Fishbowl Server Administration

When Fishbowl Server is installed, the Fishbowl Server Administration app is installed with it. This app is used to create and connect databases, adjust server settings, manage licensing, and perform restore/maintenance tasks.

Source: Fishbowl Advanced - Server Administration

Related page: Connecting

Before Making Changes

If the Fishbowl Server service is running, you can view settings but cannot apply many changes.

Stop the server first using one of these methods:

  • Right-click the Fishbowl Server system tray icon and choose Stop
  • Open the tray app and click Stop

How to Open Server Administration

You can launch Fishbowl Server Administration from:

  • Windows Start menu -> Fishbowl -> Fishbowl Server Administration
  • C:\Program Files\Fishbowl\server\bin\Fishbowl Server Administration.exe
  • System tray icon -> Options (or Tools -> Options)

Installation and Log Locations on RDP

The Fishbowl installation on the RDP server is located at:

  • C:\Program Files\Fishbowl

The logs directory is located at:

  • C:\Program Files\Fishbowl\logs

API Request Logs (fbserver)

The fbserver log file in the logs directory contains API request activity and request-related operational details.

Use this file when troubleshooting:

  • API connectivity issues
  • Unexpected request/response behavior
  • Time-window correlation for integration failures

Operational guidance:

  • Review entries around the incident timestamp first
  • Capture relevant snippets for incident notes (without exposing secrets)
  • Retain original log context when escalating issues

Tabs and Core Operations

Database Tab

Use this tab to create or connect databases and perform maintenance operations.

Common right-click actions include:

  • Show Version: confirms installed Fishbowl release
  • Backup Database: creates a backup before upgrades or risky changes
  • Rebuild Database: clones business setup data while excluding training-period inventory/orders
  • Database Maintenance: runs diagnostics and reports detected issues
  • Optimize Database: improves query/performance characteristics
  • Drop Database: permanently deletes a selected database
  • Run Support Queries: executes Fishbowl Support-provided queries (active support contract required)
  • Send Copy to Fishbowl: sends database/log copy and issue context for troubleshooting

Rebuild Database

Use this when a sandbox/training database has valid master data (parts, users, customers) but should not keep training transactions.

Workflow:

  1. Stop Fishbowl Server
  2. Go to Database tab
  3. Right-click the source database
  4. Select Rebuild Database
  5. Confirm the new database name (date-based default can be edited)
  6. Wait for the rebuild to complete

Result: a new database entry appears, containing copied setup data without the training-period inventory/order history.

Server Tab

This tab controls connectivity, security, and runtime behavior.

Key settings:

  • Port: primary client-to-server connection port
  • Legacy Port: older local-network socket option (useful for compatibility or multiple-server setups)
  • Secure Connection: enable encryption via JKS certificate (self-signed or CA-issued)
  • Broadcast Server Location: allows discovery from the client login window
  • Single session enforcement: optionally prevent one user from logging in on multiple computers
  • Server memory: adjust allocation per workload guidance
  • Auto Updates: configure update behavior

Read-only Database User

Fishbowl includes a built-in read-only database account for reporting tools and direct-data consumers.

Best practices:

  • Set a custom password instead of relying on defaults
  • Rotate credentials and update all downstream reporting/integration tools
  • Disable the account if not required

Important behavior noted by Fishbowl: existing installations keep current/default credentials until explicitly changed.

DBeaver Access on RDP

There is a DBeaver Community instance installed on the RDP server for database access and troubleshooting.

Configured database connection:

  • Name: Fishbowl DB
  • Host: local to the server (localhost)

Read-only credentials for this connection are stored in LastPass:

  • Vault entry name: Fishbowl - Scottsdale

Security notes:

  • Do not place database credentials in documentation or tickets
  • Use read-only access for investigation/reporting whenever possible
  • If credential changes are made, update dependent tools and docs references

License Tab

Use this tab to enter or change the Fishbowl license key.

Restore Tab

Use this tab to restore database backups and adjust related MySQL restore settings.

Admin Checklist

  • Confirm maintenance window and notify client users
  • Stop Fishbowl Server before applying structural changes
  • Run backup before upgrades, rebuilds, or support queries
  • Document server port/certificate/read-only user changes
  • Validate client connectivity after changes
  • Validate reporting and external integrations after credential or restore operations