Skip to content
Home > Getting Started > Coming from 3forge Classic

Upgrading from Classic

If you are familiar with 3forge Classic (AmiOne), this page collects the changes that matter when migrating an existing application to 3forge Enterprise. The golden rule:

Do not copy Classic properties files over wholesale

Start from Enterprise defaults and re-apply only the configuration you need. Classic property files carry assumptions that no longer hold in Enterprise (inline feed handlers, the ami.components property, lib/ plugins, and more). Copying them wholesale reintroduces deprecated patterns and drift against defaults.properties.

AmiCore Replaces AmiOne

In Enterprise the application is AmiCore, not AmiOne. This shows across the platform:

  • The launch directory is now ami/amicore instead of ami/amione.
  • JVM options are now defined in amicore.vmoptions on Windows and amicore_linux.vmoptions on Linux.

Log Naming

Naming conventions for several log files have changed:

Old (Classic) New (Enterprise)
AmiOne.log, AmiOne.log.001 AmiCore.log, AmiCore.001.log
AmiOne.amilog, AmiOne.amilog.001 AmiCore.stats, AmiCore.0001.stats
AmiMessages.log, AmiMessages.log.001 AmiMessages.log, AmiMessages.001.log
stderr.log, stdout.log AmiCore.stderr.log, AmiCore.stdout.log

Security

Enterprise is secure by default. The key differences from Classic:

  • No demo/demo123 default login. Windows prompts you to create the initial admin on first start; Linux refuses to start until you create data/access.txt yourself.
  • The Linux startup banner still prints Default Username: demo and Default Password: demo123. That pair does not exist in 3forge Enterprise and does not work; log in with the credentials you put in data/access.txt.
  • TLS on by default, with an active keystore in keys/ and HTTPS on 33333; secure listeners enforce mandatory mutual TLS.
  • File-system sandbox: components are confined to their working directory unless you list extra paths in ami.component.allowed.dirs.

Component Management

The ami.components=relay,center,web property is gone. The component set is now defined in the watched file data/ami.components (property ami.components.file), generated automatically on first boot and hot-reloaded at runtime. See Components.

Feed Handlers

Inline feed handler definitions (ami.relay.fh.*) are deprecated (they log a warning on startup). Convert each to a line in the watched file data/relay.feedhandlers, referring to plugins by alias, not class name. See Feed handlers.

Plugins

Plugins have moved from lib/ jars to a managed plugin system: bundles load from plugins/, each in its own isolated classloader (no more driver dependency clashes), and are referenced by short alias. See Managed Plugins.

Licensing

Enterprise uses different licensing from 3forge Classic. The f1license.txt file for standalone 3forge Enterprise instances is still available, but must be regenerated for an AmiCore application instead of AmiOne. See Licensing for instructions.

What You Can Copy from an Existing Install

Starting from Enterprise defaults, the following state can be copied from your original install:

  • data/cloud (layouts)
  • data/managed_schema.amisql (other config schema files may be copied as well)
  • relay.transforms and relay.routes
  • Table persist files in persist/
  • Web_resources

Everything else, re-apply deliberately against Enterprise defaults rather than copying property files.