Editing JBoss

==Introduction==

===Wildfly===
On 20 November 2014, JBoss Application Server was renamed WildFly. The JBoss Community and other Red Hat JBoss products like JBoss Enterprise Application Platform were not renamed. WildFly or simply JBoss, is an application server authored by JBoss, now developed by Red Hat. WildFly is written in Java, and implements the Java Platform, Enterprise Edition (Java EE) specification. It runs on multiple platforms. WildFly is free and open-source software.

===JBoss 7===
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. There two modes: standalone and domain, which is a group of servers.

====Overview of implemented Standards====
see https://docs.jboss.org/author/display/AS7/Getting+Started+Guide

====Extensions====
An extension is a module that extends the core capabilities of the server. The JBoss Application Server 7 core is very simple and lightweight; most of the capabilities people associate with an application server are provided via extensions. An extension is packaged as a module in the modules folder. The user indicates that they want a particular extension to be available by including an <extension/> element naming its module [[JBoss#JBoss_7_2|configuration file]].

===JBoss < 7===

The following components are part of the JBoss application server:
* Hibernate?
* Tomcat

==Installation==

===Home PC New===
see [[HomePCNew#JBoss_7|here]]

===HP EBS Laptop New===
see [[EONISLaptopHPNew#JBoss|here]]

===Raspberry PI===
see [[RaspberryPi3B#Wildfly_19.1|here]]

===VServer Server4You===
see [[Server4You#JBoss|here]]

===HP EBS Laptop===
see [[EONISLaptopHP#JBoss|here]]
* download JBoss Enterprise Application Platform 6 EAP
* create admin user 'UweHeuer' and 'Halloo0@1' with batch script
* deploy mysql connector
* create Data Sources with Web-Admin interface
* deploy uweheuer.war and enable
* add to '''standalone.xml''' for uweheuer application
 <connector name="ajp" protocol="AJP/1.3" scheme="http" socket-binding="ajp" enabled="true"/>
 ...
 <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] %C.%M %L: %s%E%n"/>
 ...
 <logger category="uweheuer" use-parent-handlers="false">
   <level name="INFO"/>
   <handlers>
     <handler name="FILE"/>
   </handlers>
 </logger>
* see also [[EONISLaptopHP#Magnolia|magnolia]]

====Create Service====
* created by https://community.jboss.org/thread/230109


====Shutdown====
* open the Windows Services dialogue and stop the services or
* in a cmd shell type:
 C:\Uwes\Programme\Java\JBoss\jboss-eap-6.1.0\jboss-eap-6.1\bin>jboss-cli.bat --connect command=:shutdown

==Configuration==

===JBoss 7===
* use <JBOSS_HOME>\bin\jboss-admin.bat or [http://localhost:9990/console Web Console]
* stored in <JBOSS_HOME>\standalone\configuration\standalone.xml
* for Axis2 see [[Axis#Installation|here]]

====Database Configuration====
Datasources are configured through the datasource subsystem. Declaring a new datasource consists of two separate steps: You would need to provide a JDBC driver and define a datasource that references the driver you installed. There is a datasource 'ExampleDS' coming together with the installation.

====Enabling Remote Access====
 <interface name="management">
   <inet-address value="${jboss.bind.address.management:0.0.0.0}"/>
 </interface>
 <interface name="public">
   <inet-address value="${jboss.bind.address:0.0.0.0}"/>
 </interface>

====Set Timeout for JBoss client====
e.g. for deployments set in jboss-cli.xml
 <connection-timeout>10000</connection-timeout>

====Enabling access.log====
 <access-log pattern="%h %l %u %t %r %s %b %{User-Agent}i %{JSESSIONID}c" prefix="access"/>
creates folder '''default-host''' below the log directory with a file named '''access'''<DATE>.

====Logging Configuration====
The overall server logging configuration is represented by the logging subsystem. It consists of three notable parts: handler configurations, logger and the root logger declarations (aka log categories). 

Output goes to:
* <code>.../standalone/log/server.log</code> contains also startup output
* [[EONISLaptopHPNew#JBoss|HP EBS Laptop New]]
* Z:\usr\share\jboss7\standalone\log\ at Home PC New
* [[Server4You#JBoss|Server4You]]
It is defined in [[JBoss#JBoss_7_2|standalone configuration file]], which can configured by the [http://localhost:9990/console/App.html#server/logging Admin console -> Profile -> Core -> Logging]. 

You may have noticed that there is a logging.properties file in the configuration directory. This logging configuration is used when the server boots up until the logging subsystem kicks in. If the logging subsystem is not included in your configuration, then this would act as the logging configuration for the entire server.

=====UweHeuer Logging=====
see [[uweheuer|uweheuer]]

====Apache configuration====

For connecting to Apache acting as proxy add to standalone.xml JBoss configuration file:

 <connector name="ajp" protocol="AJP/1.3" socket-binding="ajp" enabled="true"/>
 
 <socket-binding name="ajp" port="8009"/>

Apache Configuration on HomePC see [[HomePC#Apache|here]]

===JBoss < 7===
The JBoss Enterprise Application Platform ships with four different server configurations. Within the jboss-4.2.2.GA/server directory, you will find four subdirectories: minimal, default, production and all - one for each server configuration. Each of these configurations provide a different set of services. The default configuration is the one used if you don’t specify another one when starting up the server.
If you want to know which services are configured in each of these instances, look at the <code>jboss-service.xml</code> file in the <code>jboss-4.2.2.GA/server/<instance-name>/conf/</code> directory and also the configuration files in the <code>jboss-4.2.2.GA/server/<instance-name>/deploy</code> directory.
The directory server configuration you’re using, is effectively the server root while JBoss is running. It contains all the code and configuration information for the services provided by the particular server configuration. It’s where the log output goes, and it’s where you deploy your applications.

* in <JBOSS_HOME_423> and <JBOSS_HOME_422>\server\default\conf\jboss-service.xml from 1099 to 1499 because of exception at startup
* in <JBOSS_HOME_423>\bin\run.bat Zeile 66 JAVA_OPTS um -XX:+CMSPermGenSweepingEnabled -XX:MaxPermSize=128m ergänzt um die OutOfMemory Exception des PermGen aufzuschieben
* copy <JBOSS_HOME_423>\bin\run.bat to <JBOSS_HOME_423>\bin\run_debug.bat and decomment line 93 with debug options and suspend=n
* rename jboss-log4j.xml in jboss-log4j.xml.sik and copy jboss-log4j.xml from C:\Uwes\jboss\jboss-4.2.3.GA\server\default\conf to C:\Uwes\eclipse\workspace\seaminaction\opt\jboss-as-4.2.2.GA\server\default\conf
* change port in <JBOSS_HOME_422>\server\default\deploy\jboss-web.deployer\server.xml 8080 -> 8088
* for Axis2 see [[Axis#Installation|here]]

====Database configuration====

* mysql-connector-java-5.1.5-bin.jar nach <JBOSS_HOME>\server\default\lib kopiert
* The uweheuer data sources a configured via files e.g. mysql-ds.xml in the deploy directory <JBOSS_HOME>\server\default\deploy. The datasource is bound to the JNDI name e.g. java:/DefaultDS (s. [[JavaJEEJPA#persistence.xml|JPA configuration]]).

==Operation==

===CLI===
Command Line interface (examples see build file of [[Uweheuer|uweheuer]]):
* '''Operation requests''' is considered a raw low level way to manage things. Normally, for convenience and friendliness users would use 
* '''Commands''' instead

 /bin/jboss-cli.sh or jboss-cli.bat
 [disconnected /] connect 192.168.0.10:9990

Examples:
 [standalone@localhost:9999 /] /subsystem=logging/root-logger=ROOT:change-root-log-level(level=DEBUG)
 {"outcome" => "success"}

 [standalone@localhost:9999 /] /deployment=*:read-resource
Check Server State:
 [standalone@localhost:9990 /] :read-attribute(name=server-state)
Reload Configuration:
 [standalone@localhost:9990 /] :reload
Restart Server:
 [standalone@localhost:9990 /] :shutdown(restart=true)

===CLI Batch===
The batches are located in the bin directory:
 jboss-cli.bat or 
 jboss-cli.sh

====Disable Application====
 jboss-cli.bat --controller=192.168.178.202 --connect --user=admin --password=Halloo0@1 -c "undeploy uweheuer.war --keep-content"

====Enable Disabled Application====
 jboss-cli.bat --controller=192.168.178.202 --connect --user=admin --password=Halloo0@1 -c "deploy --name=uweheuer.war"

====Shutdown Server====
 ./jboss-cli.sh --connect --command=:shutdown

===Start the server===

====JBoss < 7====
* [[HomePCNew#JBoss_5|HomePCNew]]
* on Windows systems: <JBOSS_HOME>/bin/run.bat
* on Linux systems: <JBOSS_HOME>/bin/run.sh > /dev/null &

====JBoss 7====

=====Windows=====
* by cmd line: <JBOSS_HOME>\bin\MyStandalone.bat (s. also [[EONISLaptop#Dienste|Dienste]])
* by eclipse Window -> Show View -> Other -> Other -> Server -> Servers

=====Ubuntu=====
* on HomePC: /etc/init.d/jboss7 start

===Start the server for debugging===
====HP EBS laptop installation====
* open server tab
* select server 'Red Hat JBoss EAP 6.1+' -> right click-> debug
* select 'set the server adapter to 'started' without launching a new server'
* select server 'Red Hat JBoss EAP 6.1+' -> right click-> restart in debug

===Stop the server===

====JBoss < 7====
* Windows: <JBOSS_HOME>/bin/MyShutdown.bat 
* Linux-Standard is <JBOSS_HOME>/bin/shutdown.sh --server=localhost
* on HOME PC because of service installation: manual start or stop in terminal with sudo /etc/init.d/jboss [start|stop]

====JBoss 7====

=====Windows=====
* if started in cmd shell just press CTRl+C

=====Ubuuntu=====
* on HomePC: /etc/init.d/jboss7 stop

=====HomePC New=====

===Deployment of Applications===

====JBoss < 7====
#copy the ear file to <JBOSS_HOME>/server/<CONFIGURATION>/ directory
#it will be expanded to <JBOSS_HOME>/server/<CONFIGURATION>/tmp/deploy/...


====JBoss 7====

* copy war file to <JBOSS_DIR>\standalone\deployments or
* deployement via [[#CLI|CLI]] (see [[Uweheuer|uweheuer]] generantion)
* copy extracted war file to <JBOSS_DIR>\standalone\deployments and create empty file <WAR_FILENAME>'''.dodeploy'''

===Start the Hypersonic (HSQL) Database Manager===
* start [http://localhost:8080/jmx-console/ JBoss JMX Console]
* follow link '''database=localDB,service=Hypersonic''' 
* search startDatabaseManager() and press Invoke 
* new client start after some seconds

==JBoss applications==

===EJB Trail Tutorial===
#download EJB3Trail.ear from http://www.jboss.com/docs/trailblazer and copied to deploy directory

===TestWebApplication===
#jsf

===TestEJBApplication===
#EJBs

===ticket2rock===
* download from http://www.ejb3buch.de/
* ant
* copy /build/ticket2rock.ear to <JBOSS_HOME_DEPLOY_DIR>
* läuft nicht unter 4.2.3

===Seam In Action Example===
* C:\Uwes\eclipse\workspace\seaminaction>ant quickstart
* C:\Uwes\eclipse\workspace\seaminaction>ant -f stages/projects-part3/open18/build.xml explode
* runs as open18

===Seam Registration Example===
* cd C:\Uwes\eclipse\workspace\jboss-seam-2.0.2.SP1\examples\registration
* ant
** copies C:\Uwes\eclipse\workspace\jboss-seam-2.0.2.SP1\examples\registration\dist\jboss-seam-registration.ear to <JBOSS_HOME_DEPLOY_DIR>
* runs

===Seam Messages Example===
* cd C:\Uwes\eclipse\workspace\jboss-seam-2.0.2.SP1\examples\messages
* ant
** copies C:\Uwes\eclipse\workspace\jboss-seam-2.0.2.SP1\examples\messages\dist\jboss-seam-messages.ear to <JBOSS_HOME_DEPLOY_DIR>
* runs

===Seam Booking Example===
* cd C:\Uwes\eclipse\workspace\jboss-seam-2.0.2.SP1\examples\booking
* ant
** copies C:\Uwes\eclipse\workspace\jboss-seam-2.0.2.SP1\examples\booking\dist\jboss-seam-booking.ear to <JBOSS_HOME_DEPLOY_DIR>
* runs

===Seam Todo List Example===
* cd C:\Uwes\eclipse\workspace\jboss-seam-2.0.2.SP1\examples\todo
* ant
** copies C:\Uwes\eclipse\workspace\jboss-seam-2.0.2.SP1\examples\todo\dist\jboss-seam-todo.ear to <JBOSS_HOME_DEPLOY_DIR>
* runs

===Seam Numberguess Example===
* cd C:\Uwes\eclipse\workspace\jboss-seam-2.0.2.SP1\examples\numberguess
* ant
** copies C:\Uwes\eclipse\workspace\jboss-seam-2.0.2.SP1\examples\numberguess\dist\jboss-seam-numberguess.ear to <JBOSS_HOME_DEPLOY_DIR>
* runs

==State==
* Version 5 installed but uweheuer doesn't work => deinstalled
* Version 4.2.2 installed but WebTestApplication doesn't work => deinstalled
* Version 4.2.3: Seam Examples, WebTestApplication, TestEJBApplication, uweheuer work, ticket2rock does not
*