WildFly (JBoss Application Server) Basic Concepts

A cikin labaran mu biyu na ƙarshe, mun wuce ta WildFly Installation sannan kuma sarrafa sabar ta amfani da sigar GUI na CLI. A yau, za mu tattauna game da mahimman ra'ayoyi ko za ku iya faɗi kalmomin da aka yi amfani da su a cikin WildFly. Kuna iya shiga cikin labaran mu na ƙarshe da aka buga a.

WildFly – Sabon Ingantacciyar Shigar Sabar Sabar Aikace-aikacen JBoss
Sarrafa WildFly (JBoss AS) Server Ta amfani da sigar GUI na CLI

Wadanda suka riga sun saba da Jboss AS, za su san babban canjin da aka gabatar wa Jboss AS 7.* kuma saboda haka WildFly. Canjin shine ƙirar ƙirar ƙira, yana nufin zai loda azuzuwan da ake buƙata ta aikace-aikacen maimakon loda duk azuzuwan.

A ƙasa akwai wasu mahimman kalmomin da aka yi amfani da su a cikin WildFly:

Hanyoyin farawa

Wildfly sun gabatar da sabbin hanyoyin farawa. Yana da nau'ikan ayyuka guda biyu da ake amfani da su suna sarrafa duk ayyukan uwar garken.

Yanayin tsaye
Yanayin yanki

Duk waɗannan hanyoyin biyu ana sarrafa su ta hanyar rubutun daban-daban guda biyu da aka bayar a cikin kundin tsarin shigar da WildFly.

 ll -m1 standalone.sh domain.sh

domain.sh
standalone.sh

A cikin sigar da ta gabata ta Jboss AS 7.* watau Jboss Application Server 3, 4, 5 ko 6, duk misalan jboss masu gudana suna da tsarinsu na kowane mutum. Kowane misali zai sami nasa na'ura wasan bidiyo na admin da sauran ayyuka don sarrafa iri ɗaya.

Hakazalika yanayin keɓantacce yana aiki. Za mu iya ƙaddamar da uwar garken tsaye ta amfani da rubutun \standalone.sh\ da wucewa daban-daban kamar yadda ake buƙata. Za mu iya ƙaddamar da lokuta da yawa kamar yadda muke so (duk ya kamata a tsara su don gudanar da su a tashoshin jiragen ruwa daban-daban).

Hakanan zamu iya samar da gungu na HA daban-daban kamar yadda muke yi tare da sigar farko watau 4, 5 ko 6.

Matsar zuwa $JBOSS_HOME/bin directory kuma ƙaddamar da rubutun standalone.sh daga tasha kamar yadda aka nuna a ƙasa. Idan ba mu ƙididdige kowane siga ba, to ta tsohuwa za a ɗaure zuwa adireshin madauki kuma a yi amfani da fayil na standalone.xml.

 ./standalone.sh

tecmint-VGN-Z13GN bin # ./standalone.sh
=========================================================================

  JBoss Bootstrap Environment

  JBOSS_HOME: "/data/wildfly-8.0.0.Final"

  JAVA: java

  JAVA_OPTS:  -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true

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

13:25:22,168 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final
13:25:22,717 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.0.Final
13:25:22,818 INFO  [org.jboss.as] (MSC service thread 1-3) JBAS015899: WildFly 8.0.0.Final "WildFly" starting
13:25:24,287 INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
13:25:24,310 INFO  [org.xnio] (MSC service thread 1-1) XNIO version 3.2.0.Final
13:25:24,332 INFO  [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.2.0.Final
13:25:24,486 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 33) JBAS010280: Activating Infinispan subsystem.
13:25:24,491 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 28) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
13:25:24,514 INFO  [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.0.Final
13:25:24,573 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 39) JBAS012615: Activated the following JSF Implementations: [main]
13:25:24,575 INFO  [org.jboss.as.connector.logging] (MSC service thread 1-3) JBAS010408: Starting JCA Subsystem (IronJacamar 1.1.3.Final)
13:25:24,587 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) JBAS010417: Started Driver service with driver-name = h2
13:25:24,622 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 41) JBAS011800: Activating Naming Subsystem
13:25:24,691 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 46) JBAS013171: Activating Security Subsystem
13:25:24,707 INFO  [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service
13:25:24,708 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-3) JBAS015400: Bound mail session [java:jboss/mail/Default]
13:25:24,737 INFO  [org.jboss.as.security] (MSC service thread 1-1) JBAS013170: Current PicketBox version=4.0.20.Final
13:25:24,754 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 50) JBAS015537: Activating WebServices Extension
13:25:24,800 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017502: Undertow 1.0.0.Final starting
13:25:24,800 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 49) JBAS017502: Undertow 1.0.0.Final starting

Lura: Kuna iya amfani da zaɓin -b [IP] don fara uwar garken tare da wasu IP kuma don loda wasu fayilolin saiti amfani -c [sunan fayil ɗin saiti].

Wannan sabon ra'ayi ne wanda aka gabatar a cikin AS-7.* . Tare da wannan sabon fasalin a cikin WildFly-8, zamu iya sarrafa lokuta daban-daban daga aya guda. Wannan yana taimaka mana da gaske mu ragu zuwa wurin sarrafawa ɗaya maimakon sarrafa sabar masu zaman kansu da yawa.

Duk sabar da Domain ke sarrafawa an san su da membobin yanki. Duk membobi na yanki na iya raba daidaitawa/ turawa iri ɗaya. Wannan yana da amfani da gaske kuma yana taimakawa ga mahalli mai tari.

A cikin yanayin yanki muna iya ƙirƙirar ƙungiyar uwar garken sannan kuma zamu iya ƙara adadin sabar zuwa wannan rukunin. Da wannan duk abin da muke yi akan wannan Rukunin Sabar, komai zai yi kwafi ga kowane uwar garken a cikin Rukunin Sabar.

Matsar zuwa $JBOSS_HOME/bin directory kuma ƙaddamar da rubutun domain.sh daga tasha kamar yadda aka nuna a ƙasa.

 ./domain.sh

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

  JBoss Bootstrap Environment

 JBOSS_HOME: "/data/wildfly-8.0.0.Final"

  JAVA: java

  JAVA_OPTS: -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true

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

13:30:33,939 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final
13:30:34,077 INFO  [org.jboss.as.process.Host Controller.status] (main) JBAS012017: Starting process 'Host Controller'
[Host Controller] 13:30:34,772 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final
[Host Controller] 13:30:34,943 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.0.Final
[Host Controller] 13:30:34,999 INFO  [org.jboss.as] (MSC service thread 1-4) JBAS015899: WildFly 8.0.0.Final "WildFly" starting
[Host Controller] 13:30:35,689 INFO  [org.xnio] (MSC service thread 1-1) XNIO version 3.2.0.Final
[Host Controller] 13:30:35,692 INFO  [org.jboss.as] (Controller Boot Thread) JBAS010902: Creating http management service using network interface (management) port (9990) securePort (-1)
[Host Controller] 13:30:35,701 INFO  [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.2.0.Final
[Host Controller] 13:30:35,747 INFO  [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.0.Final
[Host Controller] 13:30:35,817 INFO  [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on 127.0.0.1:9999
^C13:30:36,415 INFO  [org.jboss.as.process] (Shutdown thread) JBAS012016: Shutting down process controller
13:30:36,416 INFO  [org.jboss.as.process.Host Controller.status] (Shutdown thread) JBAS012018: Stopping process 'Host Controller'
[Host Controller] 13:30:36,456 INFO  [org.jboss.as] (MSC service thread 1-2) JBAS015950: WildFly 8.0.0.Final "WildFly" stopped in 19ms
[Host Controller] 
13:30:36,476 INFO  [org.jboss.as.process.Host Controller.status] (reaper for Host Controller) JBAS012010: Process 'Host Controller' finished with an exit status of 130
13:30:36,476 INFO  [org.jboss.as.process] (Shutdown thread) JBAS012015: All processes finished; exiting

Wani abu da za ku lura da bambanci tsakanin adadin ayyukan da aka fara a Standalone (183 daga 0f 232) da Yanayin yanki (207 daga 255).

Wani muhimmin bambanci tsakanin Standalone da Domain Mode shine umarnin farawa da aka yi amfani da shi a rubutun farawa. A tsaye, wurin shigarwa shine \org.jboss.as.standalone yayin da a yanayin shigar yanki shine \org.jboss.as.process-controller. A ƙasa akwai adadi da ke nuna alaƙar ma'ana tsakanin matakai daban-daban.

A cikin yanayin yanki, da farko zai fara sarrafawa mai sarrafawa kuma yana haifar da sabon tsari da ake kira Mai sarrafa Mai watsa shiri. Wannan tsarin Mai Gudanar da Mai watsa shiri zai kasance da alhakin sarrafa sabar da yawa tsakanin ƙungiyoyin uwar garken daban-daban. Wani batu da ya kamata a lura cewa kowane Sabar zai sami nasa tsarin JVM.

Shi ke nan a yanzu! A cikin labarinmu mai zuwa za mu nuna hanyoyi daban-daban na yin turawa a cikin WildFly. Har sai, sannan ku ci gaba da sauraron ku kuma ku haɗa zuwa Tecmint kuma kar ku manta da bayar da ra'ayoyin ku masu mahimmanci a cikin sashin sharhinmu na ƙasa.