Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
The DZone Refcard Getting Started With JBoss Enterprise Application Platform 7 is a real, compact guide to installing, starting, administering and deploying applications to JBoss EAP 7. Its steps remain useful for learning or maintaining a legacy system, but the Refcard’s Java 8-era assumptions are not a universal setup recipe in 2026: EAP 7 full support ended June 30, 2025. For a local experiment, use a compatible EAP 7 release and JDK in standalone mode; for new production work, evaluate EAP 8 or another currently supported platform.
What the DZone Refcard covers
DZone’s Refcard #097, written by Red Hat software engineer James Perkins, is aimed at Java EE-era developers and administrators getting started with JBoss Enterprise Application Platform 7. Its roadmap covers the platform, installation, directory structure, server startup, administration, application deployment, modules, troubleshooting and further links.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
JBoss in Action: Configuring the JBoss Application Server | $26.02 | Buy on Amazon |
| 2 |
|
JBoss AS 5 Development | $37.93 | Buy on Amazon |
| 3 |
|
Enterprise Application Servers CookBook - Part 2: JBoss EAP | $9.99 | Buy on Amazon |
| 4 |
|
Mastering JBoss Enterprise Application Platform 7 | $50.08 | Buy on Amazon |
| 5 |
|
JBoss A Complete Guide | $93.76 | Buy on Amazon |
That makes it a useful orientation, not a substitute for release-specific instructions. The Refcard’s original workflow specifies a Java 8-compliant JDK; supported Java versions vary by EAP release and update. Check Red Hat’s EAP 7 supported configurations against the precise EAP update, JVM vendor and operating system you intend to use.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteWhat EAP 7 is—and why the distinction matters
JBoss EAP is Red Hat’s enterprise application-server product in the WildFly lineage. EAP 7 provides a Java EE 7-era runtime and management features for hosting enterprise applications, including security, messaging, clustering and modular class loading. WildFly is the related upstream/community server; it is not simply another name for the EAP product.
#1 Best Overall
- New
- Mint Condition
- Dispatch same day for order received before 12 noon
- Guaranteed packaging
- No quibbles returns
Java EE later evolved into Jakarta EE, but that does not make an EAP 7 application automatically interchangeable with a modern Jakarta EE application. EAP 7’s APIs, configuration and application dependencies belong to their own generation. The Maven plugin goal used by an EAP quickstart may say wildfly:deploy because of the shared tooling lineage; it does not mean the target server is WildFly.
Is EAP 7 still appropriate in 2026?
Red Hat says EAP 7 full support ended on June 30, 2025. Continued supported use is tied to EAP 7.4 with Extended Lifecycle Support (ELS), subject to the applicable subscription and terms; Red Hat states ELS coverage is available until October 2027. See the EAP 7 ELS notice and Red Hat support policy. Confirm eligibility and coverage with Red Hat or your organization’s subscription administrator.
| Need | Practical direction |
|---|---|
| Learn the server locally | Use a ZIP installation and standalone mode with a compatible EAP/JDK combination. |
| Test a legacy application | Match its required EAP patch level, JDK, configuration and dependencies rather than choosing a version by habit. |
| Maintain a production EAP 7 system | Verify that it is EAP 7.4 and that the organization has the required ELS entitlement. |
| Start a new Red Hat-supported deployment | Evaluate EAP 8 and plan for application and configuration migration; it is not necessarily a zero-change replacement. |
| Explore EAP without installing locally | Red Hat’s getting-started page describes an OpenShift Developer Sandbox route and links to an EAP 7 Helm Chart experience. This does not teach local scripts, filesystem logs or standalone/domain internals. |
Choose an installation route
For a disposable local learning environment, the ZIP archive is the simplest route: it avoids operating-system service integration and makes it easier to keep the installation separate from system files. The graphical installer is an alternative when guided setup is preferable. RPM-based installation is more relevant to operating-system-integrated legacy deployments and deserves production-specific planning.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Red Hat’s EAP downloads page lists current access routes, including an installer, certified container images and the Developer Sandbox. Availability of a particular historical EAP 7 archive depends on account status, entitlement and portal availability; do not assume that an old EAP 7.0 or 7.1 archive is freely downloadable. Access to a development artifact, a subscription entitlement and production support are different things.
Check the prerequisites
- Obtain the EAP archive or installer through a route available to your account.
- Install a JDK compatible with the exact EAP version and update. The original Refcard names Java 8; EAP 7.4 can support other JDK versions at particular update levels and with particular vendors.
- Ensure your account can read and write the installation directory. Unix-like ZIP installation also requires an extraction utility such as
unzip. - On Windows, configure
JAVA_HOMEandPATHso the server scripts use the intended JDK.
Install from ZIP or installer
On a Unix-like system, extract the archive:
unzip jboss-eap-7.x.x.zipSet EAP_HOME to the extracted top-level directory. The version pattern above is illustrative: use the actual archive filename and keep its patch level identifiable. To use the graphical installer instead, run:
Rank #2
java -jar jboss-eap-7.x.x-installer.jarThe installer guides you through its configuration. The EAP 7.0 Getting Started Guide also points to separate installation instructions for the graphical installer and RPM packages.
Choose standalone or managed domain mode
Standalone mode runs and configures an individual server instance. It is the straightforward choice for a local tutorial, a single server or basic troubleshooting. Managed domain mode uses a domain controller and host controllers to manage multiple server instances centrally; it suits some existing enterprise topologies, but adds processes, configuration and networking to understand. Domain mode is not automatically equivalent to modern container orchestration.
Free tools Windows power users keep installed
One-click scans. No signup required.
| Mode | Where configuration lives | Best fit |
|---|---|---|
| Standalone | EAP_HOME/standalone/, including configuration/standalone.xml |
Learning, local development, a single instance and simple tests |
| Managed domain | EAP_HOME/domain/, including configuration/domain.xml and configuration/host.xml |
Existing environments that centrally manage multiple EAP instances |
In domain mode, domain.xml holds domain-wide configuration, while host.xml configures the host controller. For local work, start with standalone mode unless an application or environment specifically requires a managed domain.
Start, secure and stop a standalone server
Start the default standalone configuration with the script for your operating system:
# Unix-like systems
$EAP_HOME/bin/standalone.sh
:: Windows Server
EAP_HOMEbinstandalone.batTo select a different configuration, such as the full profile, pass it at startup:
$EAP_HOME/bin/standalone.sh --server-config=standalone-full.xmlFor a local-only development server, keep the default loopback binding. Binding to another address changes who can reach the server; do not expose a management interface publicly without appropriate network controls, authentication, TLS and role-based access. If another address is genuinely needed, the documented property form is:
$EAP_HOME/bin/standalone.sh -Djboss.bind.address=IP_ADDRESSAfter changing interfaces or ports, use the actual configured values when connecting to the application and management endpoints.
Add a management user
Run the user utility and choose a management user when prompted:
# Unix-like systems
$EAP_HOME/bin/add-user.sh
:: Windows
EAP_HOMEbinadd-user.bat- Select the management-user option.
- Enter a username and password; add groups only if your setup needs them.
- Confirm the details and answer
nowhen asked whether this user represents a remote server instance.
A management user is associated with ManagementRealm. An application user is associated with ApplicationRealm and does not automatically have administration rights. Avoid passing passwords as command-line arguments: credentials can be exposed through shell history or logs.
Connect to and stop the server
Launch the management CLI and connect to the running server:
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchRank #4
$EAP_HOME/bin/jboss-cli.sh --connectFor an interactive session, you can also start jboss-cli.sh and enter connect. To stop a server running in the foreground, press Ctrl+C. To stop an instance through the CLI, connect and enter:
shutdownThe web management console is another administration route. Treat it as a privileged interface: keep it on trusted networks and restrict access rather than making it public.
Know the important directories
In standalone mode, the active configuration, deployments and runtime files are grouped beneath standalone/. In managed domain mode, domain-wide configuration and host-specific server data are beneath domain/.
EAP_HOME/
├── bin/ # startup, user and CLI scripts
├── modules/ # modular runtime content
├── standalone/
│ ├── configuration/ # standalone.xml and user properties
│ ├── deployments/ # deployment scanner location, if enabled
│ ├── log/ # server logs
│ ├── data/ # runtime data
│ └── tmp/ # temporary files
└── domain/
├── configuration/
│ ├── domain.xml # domain-wide settings
│ └── host.xml # host-controller settings
└── servers/ # managed-server runtime data and logsThe deployment scanner can be convenient for simple experiments when enabled, but routine deployment through the management CLI or console is more controllable and scriptable than copying files into a directory.
Deploy a quickstart
A quickstart is a practical first test because it exercises the server and its management connection. Follow the quickstart’s own README.md and pom.xml for its exact requirements. The EAP 7.0 Getting Started Guide’s helloworld workflow is:
Best Value
- Start EAP in standalone mode:
$EAP_HOME/bin/standalone.sh. - From the quickstart directory, build and deploy it:
mvn clean install wildfly:deploy. - Open http://localhost:8080/jboss-helloworld. The documented EAP 7.0 quickstart displays a Hello World response.
The Maven goal and endpoint are specific to that quickstart workflow. Deployment can fail if the server is stopped, the management user is missing, the port or profile differs, Maven cannot resolve dependencies, or the application requires APIs or configuration incompatible with the selected server.
Administer with the CLI instead of ad hoc XML edits
The management CLI is available at $EAP_HOME/bin/jboss-cli.sh (or jboss-cli.bat on Windows). Once connected, help lists commands, and deploy --help explains deployment options. The CLI can deploy and undeploy applications, inspect and change configuration, control servers, run batches and perform management read/write operations; it also supports tab completion.
Red Hat’s EAP 7 documentation favors the management interfaces—the CLI, console or management API—for routine configuration changes. Those operations persist through the management model and may rewrite the XML files. If you edit XML directly, back up the configuration first and understand how management operations may subsequently change it.
Recommended Free Tools
Understand modules and class-loading errors
EAP does not load every server and application library from one undifferentiated class path. Its module system makes dependencies explicit. As a result, a missing class, ClassNotFoundException, NoClassDefFoundError, linkage error or conflicting API version can point to a dependency or visibility problem.
- Check the application’s Maven dependencies and the server profile before adding libraries. Some Java EE APIs are provided by the server and should not be bundled indiscriminately.
- Use a deployment descriptor such as
jboss-deployment-structure.xmlwhen the deployment needs an intentional dependency or exclusion from the server’s module system. - Use a separate server module for a library deliberately shared by multiple deployments, rather than copying arbitrary JARs into the EAP installation.
- Keep application-bundled libraries distinct from server-provided APIs, and check for duplicate or incompatible versions.
Module changes are not a universal cure: first identify the missing class or conflicting version and determine whether the dependency belongs in the application, is already provided by EAP, or is genuinely shared.
Troubleshoot by symptom
The server will not start
- Verify the JDK,
JAVA_HOMEand compatibility of the exact EAP update with that JVM. - Check file permissions, port conflicts and whether another EAP process is already running.
- Read the startup console output and
EAP_HOME/standalone/log/server.log; inspect recent configuration changes if startup began failing after an edit.
Management login or CLI connection fails
- Confirm that the account is a management user in
ManagementRealm, not only an application user. - Make sure the server has fully started and that the CLI is connecting to the intended host and management port.
- Check credentials and the user-properties files under the active standalone or domain configuration directory.
Deployment fails or the application is inaccessible
- Inspect the server log for the deployment error and check the quickstart’s
README.mdfor its required profile, credentials and Maven setup. - Check API compatibility, missing modules, dependency resolution and application prerequisites such as a datasource, messaging configuration or security realm.
- Confirm the deployment reached an OK state and that you are using its actual context root. If the server is bound to
127.0.0.1, another machine cannot reach it through that address. - Check whether the application port differs from 8080, and account for firewall or reverse-proxy rules.
Logs or configuration do not look as expected
The Refcard identifies server.log as the default standalone log; logs can also be inspected through management interfaces. Check the active server mode and configuration before assuming a file under standalone/ applies to a managed domain. If a manual edit seems to disappear, a management operation may have persisted a different model back to the XML. Back up the configuration before experimentation and use the CLI or console for deliberate changes.
Where to go next
For version-specific procedures, use the official EAP 7.0 Getting Started Guide alongside documentation matching the release actually installed. For a supported new Red Hat deployment, Red Hat’s current EAP getting-started resources link to EAP 8 documentation, installation guidance and migration material. If your application requires EAP 7, establish the precise update, JVM and support entitlement before treating an old Refcard command as production guidance.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
