Configuration File
|
Purpose
|
standalone.xml
|
This standalone configuration file is the default
configuration that is used when you start your standalone server. It contains
all information about the server, including subsystems, networking, deployments, socket bindings, and other configurable details. It does
not provide the subsystems necessary for messaging or high availability.
|
standalone-ha.xml
|
This standalone configuration file includes all of the default
subsystems and adds the modcluster and jgroups subsystems for
high availability. It does not provide the subsystems necessary for
messaging.
|
standalone-full.xml
|
This standalone configuration file includes all of the default
subsystems and adds the messaging-activemq and iiop-openjdk subsystems. It does not provide the subsystems necessary
for high availability.
|
standalone-full-ha.xml
|
This standalone configuration file includes support for every
possible subsystem, including those
for messaging and high availability.
|
standalone-load-balancer.xml
|
This standalone configuration file includes the minimum
subsystems necessary to use the built-in mod_cluster front-end
load balancer to load balance other JBoss EAP
instances.
|
Step 1: Make one directory JBOSS1
Command >> mkdir JBOSS1
Screenshot 1:
Step 2: copy the jboss binaries to that JBOSS1 folder.
Command >> cp -pr jboss-eap-6.4.0.zip /JBOSS1
Screenshot 2:
Step 3: unzip the jboss-eap-6.4.0.zip binaries .
Command >> unzip jboss-eap-6.4.0.zip
Screenshot 3:
Step 4: change permission to that directory.
Command >> chmod -R 755 /JBOSS1
Screenshot 4:
Step 5: Before starting make sure java is installed on Linux machine.
Command >> java -version
Screenshot 5:
Step 6: We have to add a users.
Command >> ./add-user.sh
Screenshot 6:
What type of user do you wish to add?
a) Management User (mgmt-users.properties)
b) Application User (application-users.properties)
Where,
a)The ManagementRealm and is authorized to perform management operations using the web-based Management Console or command-line based Management CLI.
b)Adds a user to the ApplicationRealm, and provides no particular permissions. That realm is provided for use with applications.
Step 7: locate to /JBOSS/JBOSS1/jboss-eap-6.4/bin and run add-user.sh to add the users.
Command >> ./add-user.sh
Screenshot 7:
Where,
./add-user.sh >> Use to add user
Username >> Provide username for Managemnet User.
Password >> Provide password for Management User.
Added user 'jboss' to file >> List of .properties file where the 'jboss' user is added .
Step 8: After adding user we have to start jboss using ./standalone.sh file.
Locate to /JBOSS/JBOSS1/jboss-eap-6.4/bin and run ./standalone.sh
Command >> ./standalone.sh
Screenshot 8:
Where,
JBOSS_HOME: /JBOSS/JBOSS1/jboss-eap-6.4 >> says jboss home.
-verbose:gc >> gc.log location
-Xms1303m -Xmx1303m >> heap size from standalone.conf
-XX:MaxPermSize=256m >> Perm size from standalone.conf
http-/127.0.0.1:8080 >> The “public” interface binding is used for all application related network communication.
http://127.0.0.1:9990 >> The “management” interface is used for all components and services that are required by the management layer
Step 9: go to browser , use http://127.0.0.1:9990 for login .
Screenshot 9:
Step 10 : Deploy the Calendar.war file on jboss using file system.
Command >> cp -pr Calendar.war /JBOSS/JBOSS1/jboss-eap-6.4/standalone/deployments/
Screenshot 10:
where,
JBAS018210: Register web context: /Calendar >> Access the application using context root.
JBOSS Server- Application Deployment Methods - Click here
Step 11 : Go to browser , use URL http://127.0.0.1:8080/Calendar
Screenshot 11:
Step 12 : Bind JBOSS to a Available IP address
from http://127.0.0.1:8080 to http://192.168.216.134:8080 >> Application Public IP (IPV4)
&
http://127.0.0.1:9990 to http://192.168.216.134:9990/console >> JBOSS Management user console
Step 13 : To bind "Application Public IP" (IPV4)
locate to jboss bin , use below command.
Command >> ./standalone.sh -b=192.168.216.134
Where,
-b=XXX.XXX.XXX.XXX is use to bind Application “public” interface to a specific IP address.
Screenshot 13-1:
Screenshot 13-2:
Step 14 : To bind “management” interface to available IP addresses
locate to jboss bin , use below command.
Command >> ./standalone.sh -bmanagement=192.168.216.134
Where,
-bmanagement=XXX.XXX.XXX.XXX is use to bind “management” interface to a specific IP address.
Screenshot 14-1:
Step 15 : To bind jboss “public” and “management” interface together .
locate to jboss bin , use below command.
Command >> ./standalone.sh -b=192.168.216.134 -bmanagement=192.168.216.134
Screenshot 15-1:
Screenshot 15-2:
JBoss EAP 6.X Http Connector Settings
max-connections: The maximum number of connections that the server will accept and process at any given time.
If the max-connections attributes is not set on web subsystem connectors in standalone-(*).xml / domain.xml, default is computed as:
512 * Runtime.getRuntime().availableProcessors() //for default Java connector
(i.e The maximum number of simultaneous connection for JBoss server is based on the number of CPU cores and it is calculated as 512*(no of CPU core)).
32 * Runtime.getRuntime().availableProcessors() //for native APR connector addon
max-threads: The maximum number of request processing threads to be created by this Connector, which therefore determines the maximum number of simultaneous requests that can be handled.
Reference link :
https://access.redhat.com/documentation/6.4/pdf/installation_guide/Red_Hat_JBoss_EAP_6.4
https://access.redhat.com/documentation/en-us/
http://anonsvn.jboss.org/repos/jbossweb/tags
https://developer.jboss.org/thread/266415
https://access.redhat.com/solutions/25054
Thanks :-)
No comments:
Post a Comment