JBoss Application Server 7 Configurations

JBoss Application Server 7 Configurations

Standalone Server Configurations

• standalone.xml (default)
• Java Enterprise Edition 6 full profile certified configuration which includes the technologies required by the Full Profile specification plus others including OSGi 

• standalone-ha.xml
• Java Enterprise Edition 6 certified full profile configuration with high availability
• standalone-osgi-only.xml
• OSGi only standalone server. No JEE6  capabilities
• standalone-xts.xml
• Standalone JEE6 full certified profile with support for transactional web services.

Domain Server Configurations

• domain.xml (default)
• Java Enterprise Edition 6 full profile certified configuration which includes the technologies required by the Full Profile specification plus others including OSGi
• domain-osgi-only.xml
• OSGi only server. No JEE6  capabilities

Important to note is that the domain and standalone modes determine how the servers are managed not what capabilities they provide.

Starting JBoss Application Server 7

To start AS 7 using the default full profile configuration in "standalone" mode, change directory to $JBOSS_HOME/bin.

./standalone.sh

To start the default full profile configuration using domain management capabilities,

./domain.sh

Starting JBoss Application Server 7 with an Alternate Configuration

If you choose to start your server with one of the other provided configurations, they can be accessed by passing the --server-config argument with the server-config file to be used. 

To use the full profile with clustering capabilities, use the following syntax from $JBOSS_HOME/bin:

./standalone.sh --server-config=standalone-ha.xml

Similarly to run OSGi only server in  domain mode:

./domain.sh --domain-config=domain-osgi-only.xml

 Alternatively, you can create your own selecting the additional subsystems you want to add, remove, or modify.

Test Your Installation

After executing one of the above commands, you should see output similar to what's shown below.

========================================================================

JBoss Bootstrap Environment

   JBOSS_HOME: /work/jboss-as-7.0.0.Final

  JAVA: /usr/jdk1.6/bin/java

  JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true

  -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000

  -Djboss.modules.system.pkgs=org.jboss.byteman

=========================================================================

16:32:05,050 INFO  [org.jboss.modules] JBoss Modules version 1.0.1.GA

16:32:05,379 INFO  [org.jboss.msc] JBoss MSC version 1.0.0.GA

16:32:05,421 INFO  [org.jboss.as] JBoss AS 7.0.0.Final "Lightning" starting

<snip>

16:32:07,578 INFO  [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.0.Final "Lightning" started in 2804ms - Started 91 of 146 services (55 services are passive or on-demand)

As with previous JBoss releases, you can point your browser to http://localhost:8080 or http://IP:Port (if using the default configured http port) which brings you to the Welcome Screen:

                           

From here you can access links to the AS 7 community documentation set, stay up-to-date on the latest project information, have a discussion in the user forum and access the newly designed web-based Administration Console.  Or, if you uncover an issue while using AS 7, report an issue to inform us (attached patches will be reviewed).  This landing page is recommended for convenient access to information about AS 7 but can easily be replaced with your own if desired.

Thanks!!

Getting Started with JBoss Application Server 7

JBoss Application Server 7 is the latest release in a series of JBoss application server offerings. JBoss Application Server 7, is a fast, powerful, implementation of the Java Enterprise Edition 6 specification. The state-of-the-art architecture built on the Modular Service Container enables services on-demand when your application requires them.   JBoss Application Server 7.0.0.Final release is a certified implementation of the Java Enterprise Edition 6 Web Profile specification. 

Installation

Simply extract your chosen download to the directory of your choice. You can install JBoss Application Server 7 on any operating system that supports the zip or tar formats. Refer to the Release Notes for additional information related to the release.

AS 7 - A Quick Tour

Now that you’ve downloaded JBoss Application Server 7, the next thing to discuss is the layout of the distribution and explore the server directory structure, key configuration files, log files, user deployments and so on. It’s worth familiarizing yourself with the layout so that you’ll be able to find your way around when it comes to deploying your own applications.

AS 7 Directory Structure

DIRECTORY	DESCRIPTION
bin	Start up scripts, start up configuration files and various command line utilities like Vault, add-user and Java diagnostic report   available for Unix and Windows environments
bin/client	Contains a client jar for use by non-maven based clients.
bundles	Location of OSGi bundles
docs/schema	XML schema definition files
domain	Configuration files, deployment content, and writable areas used by the domain mode processes run from this installation.
modules	AS 7 is based on a modular classloading architecture. The various modules used in the server are stored here.
standalone	Configuration files, deployment content, and writable areas used by the single standalone server run from this installation.
appclient	Configuration files, deployment content, and writable areas used by the application client container run from this installation.
welcome-content	Default Welcome Page content

Standalone Directory Structure

In "standalone" mode each JBoss Application Server 7 instance is an independent process (similar to previous JBoss AS versions; e.g.,  3, 4, 5, or 6). The configuration files, deployment content and writable areas used by the single standalone server run from a JBoss Application Server installation are found in the following subdirectories under the top level "standalone" directory:

DIRECTORY	DESCRIPTION
configuration	Configuration files for the standalone server that runs off of this installation. All configuration information for the running server is located here and is the single place for configuration modifications for the standalone server.
data	Persistent information written by the server to survive a restart of the server
deployments	End user deployment content can be placed in this directory for automatic detection and deployment of that content into the server's runtime.   NOTE: The server's management API is recommended for installing deployment content. File system based deployment scanning capabilities remain for developer convenience.
lib/ext	Location for installed library jars referenced by applications using the Extension-List mechanism
log	standalone server log files
tmp	location for temporary files written by the server
tmp/auth	Special location used to exchange authentication tokens with local clients so they can confirm that they are local to the running AS process.

Domain Directory Structure

A key feature of AS 7 is the managing multiple servers from a single control point.    A collection of multiple servers are referred to as a "domain". Domains can span multiple physical (or virtual) machines with all JBoss Application Server 7 instances on a given host under the control of a Host Controller process. The Host Controllers interact with the Domain Controller to control the lifecycle of the JBoss Application Server 7 instances running on that host and to assist the Domain Controller in managing them. The configuration files, deployment content and writeable areas used by domain mode processes run from a JBoss Application Server 7 installation are found in the following subdirectories under the top level "domain" directory:

DIRECTORY	DESCRIPTION
configuration	Configuration files for the domain and for the Host Controller and any servers running off of this installation. All configuration information for the servers managed wtihin the domain is located here and is the single place for configuration information.
content	an internal working area for the Host Controller that controls this installation. This is where it internally stores deployment content. This directory is not meant to be manipulated by end users.  Note that "domain" mode does not support deploying content based on scanning a file system.
lib/ext	Location for installed library jars referenced by applications using the Extension-List mechanism
log	Location where the Host Controller process writes its logs. The Process Controller, a small lightweight process that actually spawns the other Host Controller process and any Application Server processes also writes a log here.
servers	Writable area used by each Application Server instance that runs from this installation. Each Application Server instance will have its own subdirectory, created when the server is first started. In each server's subdirectory there will be the following subdirectories:  data -- information written by the server that needs to survive a restart of the server  log -- the server's log files  tmp -- location for temporary files written by the server
tmp	location for temporary files written by the server
tmp/auth	Special location used to exchange authentication tokens with local clients so they can confirm that they are local to the running AS process.

Thanks!!

Monnitor Datasource connections Information in JBOSS AS 7.0.1 using CLI

How to monitor DataSource statistics in Jboss 7 using CLI? 

We can monitor DataSource statistics in JBOSS 7 using cli console as below :
Connect to CLI Console :

$cd $JBOSS_HOME/bin
$ ./jboss-cli.sh --controller=[mgmt_IP]:9999 -c 
[standalone@mgmt_IP:9999 /] 

[standalone@IP:9999 /] /subsystem=datasources/data-source=MySQLDS/statistics=pool:read-resource(include-runtime=true)

{

    "outcome" => "success",

    "result" => {

        "ActiveCount" => "10",

        "AvailableCount" => "99",

        "AverageBlockingTime" => "0",

        "AverageCreationTime" => "11",

        "CreatedCount" => "140",

        "DestroyedCount" => "130",

        "MaxCreationTime" => "34",

        "MaxUsedCount" => "2",

        "MaxWaitTime" => "1",

        "TimedOut" => "80",

        "TotalBlockingTime" => "1",

        "TotalCreationTime" => "1541"

    }

}

To get some more detail about DataSource configuration details use below command:

[standalone@IP:9999 /] /subsystem=datasources/data-source=MySQLDS:read-resource(include-runtime=true)                

{

    "outcome" => "success",

    "result" => {

        "allocation-retry" => undefined,

        "allocation-retry-wait-millis" => undefined,

        "allow-multiple-users" => undefined,

        "background-validation" => false,

        "background-validation-millis" => undefined,

        "blocking-timeout-wait-millis" => undefined,

        "check-valid-connection-sql" => "select 1",

        "connection-properties" => undefined,

        "connection-url" => "jdbc:mysql://IP:PORT/DB",

        "datasource-class" => undefined,

        "driver-class" => "com.mysql.jdbc.Driver",

        "driver-name" => "mysql",

        "enabled" => true,

        "exception-sorter-class-name" => undefined,

        "exception-sorter-properties" => undefined,

        "flush-strategy" => undefined,

        "idle-timeout-minutes" => undefined,

        "jndi-name" => "java:/MySQLDS",

        "jta" => true,

        "max-pool-size" => 100,

        "min-pool-size" => 10,

        "new-connection-sql" => undefined,

        "password" => "Secret",

        "pool-prefill" => true,

        "pool-use-strict-min" => undefined,

        "prepared-statements-cache-size" => undefined,

        "query-timeout" => undefined,

        "reauth-plugin-class-name" => undefined,

        "reauth-plugin-properties" => undefined,

        "security-domain" => undefined,

        "set-tx-query-timeout" => false,

        "share-prepared-statements" => false,

        "spy" => false,

        "stale-connection-checker-class-name" => undefined,

        "stale-connection-checker-properties" => undefined,

        "track-statements" => "NOWARN",

        "transaction-isolation" => undefined,

        "url-delimiter" => undefined,

        "url-selector-strategy-class-name" => undefined,

        "use-ccm" => true,

        "use-fast-fail" => false,

        "use-java-context" => true,

        "use-try-lock" => undefined,

        "user-name" => "gnia",

        "valid-connection-checker-class-name" => undefined,

        "valid-connection-checker-properties" => undefined,

        "validate-on-match" => false,

        "statistics" => {

            "jdbc" => undefined,

            "pool" => undefined

        }

    }

}

Thanks!!