Show Table of Contents
7.5. Test the Installation
Task Prerequisites
- The necessary network ports must be open. Refer to Section 7.6, “Network Ports Used By JBoss Enterprise Application Platform 6” and Section 7.7, “Configure Network Firewalls to Work with JBoss Enterprise Application Platform 6”.
Look for error messages in the log files.
After you start the server, view the log files inEAP_HOME/domain/log/orEAP_HOME/standalone/log/.Result:If the server started properly, there will be no errors, and you will see output similar to the following:
Example 7.1. Example of a successful start-up
10:20:37,007 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.0.0.GA (AS 7.1.2.Final-redhat-1) started in 17942ms - Started 134 of 214 services (79 services are passive or on-demand)
In a managed domain, you see a similar message for each locally-run server.Browse to the Management Console.
If the installation worked properly and your server is running, you should be able to access the Management Console by pointing your web browser at an address similar tohttp://YOUR_SERVER:9990/, replacing YOUR_SERVER with a valid value.Result:The front page of the Management Console appears.
Result:
The Management Console is a deployable service. If you are able to reach it after starting the server, your installation is working properly and is able to deploy services.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.