Jboss deployment document,

Jboss deployment document,
1 Introduction 1.1 Writing Purpose

This document is written to better standardize Jboss software installation and promote installation standardization.

2. Install JDK 2.1 On JBOSS

Select the JDK version:

Install:

Chmod 755 jdk-1_5_0_22-linux-amd64.bin

/Jdk-1_5_0_22-linux-amd64.bin

Configure the environment: Modify the/etc/profile file and add:

JAVA_HOME =/opt/jdk1.5.0 _ 22

PATH = $ JAVA_HOME/bin: $ PATH

CLASSPATH =.: $ JAVA_HOME/lib/tools. jar: $ JAVA_HOME/lib/dt. jar

Export PATH JAVA_HOME CLASSPATH

(Note: The Java_home directory configuration depends on the actual installation location and needs to be modified)

2.2 install Jboss

1. Create Jboss users and groups

Groupadd jboss

Useradd-g jboss

Passwd jboss

2. Unzip the installation media and decompress it to the app deployment path. You must plan the installation in advance.

Unzip jboss-eap-4.3.0.GA_CP10_patched.zip

3. Java environment variable check

Java-version

(Note: The JDK version information installed in 2.1 is displayed as normal. Otherwise, you must adjust the environment variable JAVA_HOME)

4. Authorize *. sh permission in the bin directory

/Home/jboss/jboss-eap-4.3.0.GA_CP08/bin

[Jboss @ reserved-app bin] $ ls-l *. sh

[Jboss @ reserved-app bin] $ chmod 755 *. sh

2.3 configure Jboss

[Jboss @ reserved-app bin] $ pwd

/Home/jboss/jboss-eap-4.3.0.GA_CP08/bin

[Autopri @ ccslUAT bin] $

Cp run. conf/zddj/jboss-eap-4.3.0.GA_CP10_patched/server/abc8180

[Jboss @ reserved-app bin] $ pwd

/Home/jboss/jboss-eap-4.3.0.GA_CP08/bin

Nohup sh run. sh-c abc8180-B 0.0.0.0>/dev/null &

3. Adjust VM parameters based on actual needs. The following content is the content of the run. conf file (the yellow background is the content to be adjusted ):

# Caic config. 2009-11-02am

# JAVA_OPTS = "-server-Xms2248m-Xmx2248m-XX: MaxPermSize = 512 m-Xss128k-XX: + UseParNewGC-XX: + UseTLAB-XX: + CMSIncrementalMode-XX: + CMSIncrementalPacing-XX: Tenant = 0-XX: Tenant = 10-XX: MaxTenuringThreshold = 0-XX: Tenant vorratio = 16-XX: Tenant = 60-XX: + DisableExplicitGC"

JAVA_OPTS = "-server-Xms1024m-Xmx1024m-XX: PermSize = 256 m-XX: MaxPermSize = 512 m-Djava. awt. headless = true-Dsun. rmi. dgc. client. gcInterval = 3600000-Dsun. rmi. dgc. server. gcInterval = 3600000-Dsun. lang. classLoader. allowArraySyntax = true"

4. modify the port bonding name, the Instance name abc8180/conf/jboss-service.xml file (yellow background for the content to be adjusted), ServerName to correspond to the sample-bindings.xml, The sample-bindings.xml file default ServerName has ports-default, ports-01, ports-02, ports-03, the jboss-service.xml configuration file is commented by default, you need to open the comment after modification.

<! -- ===================================================== ======================================= -->

<! -Service Binding

-->

<! -- ===================================================== ======================================= -->

<! -- Automatically activated when generatting the clustering environment -->

<! -- @ TESTSUITE_CLUSTER_CONFIG @ -->

<! --

| Binding service manager for port/host mapping. This is a sample

| Config that demonstrates a JBoss instances with a server name 'ports-01'

| Loading its bindings from an XML file using the ServicesStoreFactory

| Implementation returned by the XMLServicesStoreFactory.

|

| ServerName: The unique name assigned to a JBoss server instance

| Lookup purposes. This allows a single ServicesStore to handle mulitiple

| JBoss servers.

|

| StoreURL: The URL string passed to org. jboss. services. binding. ServicesStore

| During initialization that specifies how to connect to the bindings store.

| StoreFactory: The org. jboss. services. binding. ServicesStoreFactory interface

| Implementation to create to obtain the ServicesStore instance.

-->

<Mbean code = "org. jboss. services. binding. ServiceBindingManager"

Name = "jboss. system: service = ServiceBindingManager">

<Attribute name = "ServerName"> ports-01 </attribute>

<Attribute name = "StoreURL" >$ {jboss. home. url}/docs/examples/binding-manager/sample-bindings.xml </attribute>

<Attribute name = "StoreFactoryClassName">

Org. jboss. services. binding. XMLServicesStoreFactory

</Attribute>

</Mbean>

The ports-01 In the sample-bindings.xml must be the same as the yellow background name, and the two configuration files ServerName one-to-one correspondence.

5. Modify the web port. modify the content of the abc8180/deploy/jboss-web.deployer/server. xml file (the yellow background is the content to be adjusted). The default port is 8080.

<Connector port = "8180" address = "$ {jboss. bind. address }"

MaxThreads = "250" maxHttpHeaderSize = "8192"

EmptySessionPath = "true" protocol = "HTTP/1.1"

EnableLookups = "false" redirectPort = "8443" acceptCount = "100"

ConnectionTimeout = "20000" disableUploadTimeout = "true"/>

5. Start Jboss

Nohup sh run. sh-c abc8180-B 0.0.0.0>/dev/null &

6. Check whether startup is enabled

Ps-ef | grep java

2.4 Jboss monitoring

The monitoring account configuration is in the file:

In the Abc8180/conf/props/directory, the file is *-users. properties; modify the content in the file or remove the comment. Access address: http: // ip: port. The port here is the port configured in Step 2.3. The normal display page is:

JBoss Online Resources

• JBoss Documentation
• JBoss Customer Support Portal
• JBoss JIRA
• JBoss Forums

JBoss Management

• Tomcat status (full) (XML)
• JMX Console
• JBoss Web Console

Click one of the three links and a logon box appears. You must enter the user name and password. the user name and password are the username and password you Just configured in the property file.

3 jboss o & M 3.1 restart

Generally, on a linux server, log on to the target server by using ssh client tools such as the Connection Tool putty, and execute the following command in the command line: ps-ef | grep java shows the re-running jboss instance (the name corresponding to the-c parameter is the server instance name) and the relevant process number.

3.1.1 stop a process

Kill-9 process no.

3.1.2 restart

Generally, restart and clear the temporary cache directory work, data, and tmp under the JBOSS server instance. Then, find the relevant script (if any) and start it.