Linux Operational Basics Linux Environment installation configuration Jboss__linux

System Information

Operating system: CentOS 7
JDK Version: 1.8
JBoss version: JBoss EAP 6.2
JBoss each version download address: https://teddysun.com/260.html

Installation Preparation

Upload the JBoss installation file (first extract into directory) to the server, directory:

/usr/local/software

This directory holds the software installation package

Start installation

JDK Installation:

JBoss operation needs to depend on the installation configuration of JDK,JDK as detailed below: http://blog.csdn.net/u010028869/article/details/50173745

JBoss Installation:

JBoss is a green version, you do not need to install, decompression can be used, as with Tomcat, below move the JBoss directory to usr/local, which is the directory for all software installation.

① Execute Command:

#mv/usr/local/software/jboss-eap-6.2/usr/local/jboss6.2

②ok, install complete, configure the environment variable

# Vi/etc/profile

Then add the following content

jboss_home=/usr/local/jboss6.2

To start the JBoss service:

① It is best to obtain the permissions for the JBoss file before booting:

# Chmod-r 777/usr/local/jboss6.2

② then enters the JBoss Bin directory:

# Cd/usr/local/jboss6.2/bin

Enter the command./standalone.sh start JBoss in a single server instance mode

Enter the command./domain.sh starts JBoss with allowing control and management of multiple instances mode

③ Access test:

In the browser address bar, enter: http://127.0.0.1:8080, the Welcome interface, to prove the success of the launch.

Start at the next run mode

It is a disadvantage to open jboss directly in the./standalone.sh way, and when the command window is closed, the JBoss service will also be down. In this way, when the remote server operates JBoss, it is very painful. If you turn off the Remote terminal window, JBoss will also drop it.

So we need to let JBoss open in the background to run: into the bin directory, enter the nohup./standalone.sh command. The service runs in the background, and the service is still running even if the command window is closed. View JBoss Startup log information input: Tail-f nohup.out.

Stop Service

Start JBoss as a direct startup, and you can stop the JBoss service completely by pressing CTRL + C at the startup terminal window at shutdown

If you use the background to run, shutting down the server is more cumbersome, looking for a long time to find the way to close JBoss EAP 6.2:

Into the JBoss Bin directory, enter:

[ROOT@ADMINKP bin]#./jboss-cli.sh-c  : Shutdown {"outcome"
=> "Success"}

Or violent resolution: Kill-9 PID

LAN access

The direct input http://xxx.xx.xx.xxx:8080 is inaccessible, and if you want to have access to other machines within the LAN, you need to configure the following:

① Firewall shutting down the server

# Systemctl Stop Firewall

② must modify the JBoss configuration file as follows:

Vi/usr/local/jboss6.2/standalone/configuration/standalone.xml

Found it

<interface name= "Public" >

    <inet-address value= "${jboss.bind.address:127.0.0.1}"/>

</ Interface>

Change 127.0.0.1 to the IP address of the machine where JBoss resides, and save and exit.

About JBoss installation configuration to introduce these, hope to be able to help everyone.