JBoss7.1.1 installation Configuration

JBoss7.1.1 installation Configuration

1. Download and install

First of all, pay attention to installing the jdk environment. The author installs a newer version of jdk 1.7.

1. http://www.jboss.org/jbossas/downloads, download Certified Java EE6 Full Profile version.

2. Unzip the jboss-as-7.1.1.Final.tar.gz to/usr/local/jboss

Tar zxvf jboss-as-7.1.1.Final.tar.gz
Cp-r jboss-as-7.1.1.Final/usr/local/jboss

4. Start JBoss
Cd/usr/local/jboss
./Bin/standalone. sh # note that the new jboss version no longer uses run. sh in the bin directory

 
 

  
  
15:48:06, 958 information [org. jboss. modules] JBoss Modules version 1.1.1.GA

  
  
15:48:07, 287 INFO [org. jboss. msc] JBoss MSC version 1.0.2.GA

  
  
15:48:07, 363 INFO [org. jboss. as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting

  
  
15:48:09, 285 INFO [org. jboss. as. server] JBAS015888: Creating http management service using socket-binding (management-http)

  
  
15:48:09, 295 INFO [org. xnio] XNIO Version 3.0.3.GA

  
  
15:48:09, 318 INFO [org. xnio. nio] xnio nio Implementation Version 3.0.3.GA

  
  
15:48:09, 326 INFO [org. jboss. remoting] JBoss Remoting version 3.2.3.GA

  
  
15:48:09, 402 INFO [org. jboss. as. logging] JBAS011502: Removing bootstrap log handlers

  
  
15:48:09, 459 INFO [org. jboss. as. configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem

  
  
15:48:09, 538 INFO [org. jboss. as. connector. subsystems. datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org. h2.Driver (version 1.3)

  
  
15:48:09, 596 INFO [org. jboss. as. clustering. infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.

  
  
15:48:09, 815 INFO [org. jboss. as. webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension

  
  
15:48:09, 823 INFO [org. jboss. as. security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem

  
  
15:48:09, 871 INFO [org. jboss. as. osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem

  
  
15:48:09, 881 INFO [org. jboss. as. naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem

  
  
15:48:09, 981 INFO [org. jboss. as. security] (MSC service thread 1-1) JBAS013100: Current PicketBox version = 4.0.7.Final

  
  
15:48:10, 063 INFO [org. jboss. as. naming] (MSC service thread 1-1) JBAS011802: Starting Naming Service

  
  
15:48:10, 168 INFO [org. jboss. as. connector] (MSC service thread 1-2) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)

  
  
15:48:10, 524 INFO [org. jboss. as. mail. extension] (MSC service thread 1-2) JBAS015400: Bound mail session [java: jboss/mail/Default]

  
  
15:48:10, 810 INFO [org. jboss. ws. common. management. AbstractServerConfig] (MSC service thread 1-1) JBoss Web Services-Stack CXF Server 4.0.2.GA

  
  
15:48:11, 004 INFO [org. apache. coyote. http11.Http11Protocol] (MSC service thread 1-2) Starting Coyote HTTP/1.1 on http -- 0.0.0.0-8080

  
  
15:48:11, 826 INFO [org. jboss. as. server. deployment. principal] (MSC service thread 1-2) JBAS015012: Started FileSystemDeploymentService for directory/usr/local/jboss/standalone/deployments

  
  
15:48:11, 862 INFO [org. jboss. as. remoting] (MSC service thread 1-2) JBAS017100: Listening on/127.0.0.1: 9999

  
  
15:48:11, 896 INFO [org. jboss. as. remoting] (MSC service thread 1-2) JBAS017100: Listening on/0.0.0.0: 4447

  
  
15:48:11, 987 INFO [org. jboss. as. connector. subsystems. datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java: jboss/datasources/ExampleDS]

  
  
15:48:12, 122 INFO [org. jboss. as] (Controller Boot Thread) JBAS015951: Admin console listening on http: // 127.0.0.1: 9990

  
  
15:48:12, 122 INFO [org. jboss. as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 5775 ms-Started 133 of 208 services (74 services are passive or on-demand)
 
 

5. Access http: // 127.0.0.1: 8080/. Note that the bound address is 127.0.0.1 by default. The Internet address cannot be accessed at this time. If you need an Internet address to start, standalone/configuration/standalone needs to be modified. change the public address in the xml file to 127.0.0.1 to 0.0.0.0, and restart it.

 
 

  
  
<interface name="public">

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

  
  


  
  
</interface>
 
 

The Welcometo AS 7 access interface is displayed, indicating that jboss is successfully started.

6. Stop JBoss. In the command line console of the Server, you only need to press Ctrl + C to stop the Server.

In this case, the jboss service will not run in the background. If you need to run it in the background, modify bin/standalone. sh.
Or run nohup./standalone. sh & to start jboss.
Here we can create a new startup script run. sh
Vi run. sh

 
 

  
  
#!/bin/sh

  
  
nohup ./standalone.sh &
 
 

New management user

When you access the Web server, a new user is prompted. You can execute a add-user.sh on the server side to add administrator users.

/Add-user.sh

What type of user do you wish to add?

A) Management User (mgmt-users.properties)
B) Application User (application-users.properties)

():

Press ENTER

Enter the details of the new user to add. Realm (ManagementRealm): // press Enter, select the default

Username: // enter the administrator Username

Password:

Re-enter Password:

After the Administrator is added, access http: // your IP address: 9990/console

After the basic configuration is completed, the deployment optimization will continue.