What's New in 3forge Enterprise¶
If you are coming from 3forge Classic (AmiOne), these are the material changes. Each links to its full treatment. See Upgrading from Classic for the migration facts and what state you can carry over from an existing install.
| Area | What changed |
|---|---|
| AmiCore container | The application is AmiCore, launched from ami/amicore; JVM options in amicore.vmoptions (Windows) or amicore_linux.vmoptions (Linux); new log naming. |
| Security defaults | No demo/demo123 default login; you supply the initial admin on first start; TLS on by default; a file-system sandbox; mandatory mutual TLS on secure listeners. |
| Component management | ami.components=... is gone; the component set lives in the watched file data/ami.components. Unlimited components per JVM, hot-reloaded. |
| Managed plugins | Plugins moved from lib/ jars to isolated, per-bundle classloaders in plugins/, referenced by alias. |
| Gateway | A new governed distribution layer presenting many Centers behind one interface. |
| Python / ODBC / Excel / C++ clients | First-class programmatic and BI connectivity into the data fabric. |
| AI surfaces | An in-browser assistant, an MCP server for external agents, and session.promptAi in AmiScript. |
| Operations Hub | An estate-wide control layer cataloging, monitoring, and licensing deployed instances. |
| Styles and charts | Themes and modes, StyleSets, ADA adherence, and a rebuilt charting engine. |
| Licensing | A standalone license server; Classic 3FKEY keys still work but must be regenerated. |
Before You Start¶
- AI is off by default on every surface. Nothing calls out to a model until you explicitly enable it, and each AI surface needs access to at least one model provider.
- The developer tooling is dev-gated and off by default. Each page lists the properties it requires.
- Most files under
data/are watched and hot-reloaded, so day-to-day changes rarely need a restart.