WildFly (Seva ya Maombi ya JBoss) Dhana za Msingi

Katika nakala zetu mbili zilizopita, tulikuwa tumepitia Usakinishaji wa WildFly na kisha kudhibiti seva kwa kutumia toleo la GUI la CLI. Leo, tutajadili kuhusu dhana za msingi au unaweza kusema maneno yaliyotumiwa ndani ya WildFly. Unaweza kupitia nakala zetu zilizochapishwa mwisho kwa.

WildFly – Usakinishaji Mpya Ulioboreshwa wa Seva ya Maombi ya JBoss
Dhibiti Seva ya WildFly (JBoss AS) Kwa Kutumia toleo la GUI la CLI

Wale ambao tayari wanafahamu Jboss AS, watafahamu mabadiliko makubwa yaliyoletwa kwa Jboss AS 7.* na hivyo basi WildFly. Mabadiliko yalikuwa muundo wa kawaida, inamaanisha kuwa itapakia madarasa yanayohitajika na programu badala ya kupakia madarasa yote.

Yafuatayo ni baadhi ya maneno ya kimsingi yanayotumika katika WildFly:

Njia za Kuanzisha

Wildfly wameanzisha njia mpya za kuanza. Ina njia mbili za uendeshaji zinazotumiwa ni kusimamia shughuli zote za seva.

Hali Iliyojitegemea
Hali ya Kikoa

Njia hizi zote mbili zinashughulikiwa na hati mbili tofauti zinazotolewa ndani ya \bin saraka ya usakinishaji wa WildFly.

 ll -m1 standalone.sh domain.sh

domain.sh
standalone.sh

Katika toleo la awali la Jboss AS 7.* yaani, Seva ya Maombi ya Jboss 3, 4, 5 au 6, mifano yote ya jboss inayo mchakato wake binafsi. Kila mfano utakuwa na kiweko chake cha msimamizi na kazi zingine za kudhibiti sawa.

Kwa njia inayofanana sana hali ya kujitegemea inafanya kazi. Tunaweza kuzindua seva inayojitegemea kwa kutumia hati ya \standalone.sh\ na kupitisha vigezo tofauti kulingana na mahitaji. Tunaweza kuzindua matukio mengi tunavyotaka (zote zinapaswa kuwa zimesanidiwa kuendeshwa kwenye bandari tofauti).

Tunaweza pia kuunda vikundi tofauti vya HA kama tulivyokuwa tukifanya na toleo la awali yaani 4, 5 au 6.

Nenda kwenye saraka ya $JBOSS_HOME/bin na uzindue hati ya standalone.sh kutoka kwa kituo kama inavyoonyeshwa hapa chini. Ikiwa hatutabainisha kigezo chochote, basi kwa chaguo-msingi kitajifunga kwenye anwani ya loopback na kutumia faili ya 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

Kumbuka : Unaweza kutumia -b [IP] chaguo kuanzisha seva na IP nyingine na kupakia matumizi mengine ya faili ya usanidi -c [jina la faili ya usanidi].

Hii ni dhana mpya ambayo inaletwa katika AS-7.* . Kwa kipengele hiki kipya katika WildFly-8, tunaweza kudhibiti matukio tofauti kutoka kwa sehemu moja. Hii inatusaidia sana kushuka hadi sehemu moja ya udhibiti badala ya kudhibiti seva nyingi zinazojitegemea.

Seva zote zinazodhibitiwa na Domain zinajulikana kama wanachama wa kikoa. Wanachama wote wa kikoa wanaweza kushiriki usanidi/uwekaji sawa. Hii ni rahisi sana na inasaidia kwa mazingira ya nguzo.

Katika hali ya Kikoa tunaweza kuunda kikundi cha seva na kisha tunaweza kuongeza idadi ya seva kwenye kikundi hicho. Kwa hili chochote tunachofanya kwenye Kikundi hiki cha Seva, kila kitu kitaigwa kwa kila seva katika Vikundi vya Seva.

Hamisha hadi saraka ya $JBOSS_HOME/bin na uzindue hati ya domain.sh kutoka kwa terminal kama inavyoonyeshwa hapa chini.

 ./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

Kitu kingine ambacho utaona tofauti kati ya idadi ya huduma ambazo zilianza kwa Standalone (183 nje 0f 232) na hali ya Kikoa (207 kati ya 255).

Tofauti nyingine muhimu zaidi kati ya Hali ya Kujitegemea na Njia ya Kikoa ni amri ya kuanza inayotumiwa katika hati ya kuanza. Katika hali ya pekee, mahali pa kuingilia ni \org.jboss.as.standalone ilhali katika hali ya kikoa mahali pa kuingilia ni \org.jboss.as.process-controller. Chini ni takwimu inayoonyesha uhusiano wa kimantiki kati ya michakato tofauti.

Katika hali ya kikoa, kwanza itaanza kidhibiti cha mchakato na italeta mchakato mpya unaoitwa Kidhibiti cha Jeshi. Mchakato huu wa Kidhibiti Seva kitawajibika kwa kushughulikia seva nyingi ndani ya vikundi tofauti vya seva. Jambo lingine ambalo linahitaji kuzingatiwa kuwa kila Seva itakuwa na mchakato wake wa JVM.

Ni hayo tu kwa sasa! Katika makala yetu ijayo tutaonyesha njia tofauti za kupeleka katika WildFly. Hadi, basi endelea kutazama na uunganishwe na Tecmint na usisahau kutoa maoni yako muhimu katika sehemu yetu ya maoni hapa chini.