WildFly (JBoss Application Server) Kunċetti Bażiċi

Fl-aħħar żewġ artikoli tagħna, konna għaddejna mill-Installazzjoni WildFly u mbagħad immaniġġjaw is-server bl-użu tal-verżjoni GUI ta 'CLI. Illum, ser niddiskutu dwar il-kunċetti bażiċi jew tista 'tgħid termini użati fi ħdan WildFly. Tista' tgħaddi l-aħħar artikli ppubblikati tagħna fuq.

WildFly – Installazzjoni Ġdida Mtejba ta' JBoss Application Server
Immaniġġja WildFly (JBoss AS) Server billi tuża l-verżjoni GUI tas-CLI

Dawk li diġà huma familjari ma 'Jboss AS, se jkunu konxji tal-bidla kbira introdotta għal Jboss AS 7.* u għalhekk WildFly. Il-bidla kienet id-disinn modulari, tfisser li se tagħbija l-klassijiet meħtieġa mill-applikazzjoni minflok it-tagħbija tal-klassijiet kollha.

Hawn taħt huma xi wħud mit-termini bażiċi użati f'WildFly:

Modi tal-Istartjar

Wildfly introduċew modi ġodda tal-istartjar. Għandu żewġ modi ta 'operazzjonijiet użati huma l-ġestjoni tal-operazzjonijiet kollha tas-server.

Modalità Standalone
Modalità tad-Dominju

Dawn iż-żewġ modi huma ttrattati miż-żewġ skripts differenti pprovduti fid-direttorju \bin tal-installazzjoni WildFly.

 ll -m1 standalone.sh domain.sh

domain.sh
standalone.sh

Fil-verżjoni preċedenti ta' Jboss AS 7.* jiġifieri Jboss Application Server 3, 4, 5 jew 6, l-istanza jboss kollha li qed taħdem għandha l-proċess individwali tagħhom. Kull istanza se jkollha l-admin console tagħha stess u funzjonijiet oħra biex tikkontrolla l-istess.

B'mod simili ħafna jaħdem il-modalità standalone. Nistgħu nniedu server waħdu billi nużaw script \standalone.sh\ u ngħaddu parametri differenti skont ir-rekwiżiti. Nistgħu nniedu każijiet kemm irridu (kollha kellha tkun ikkonfigurata biex titmexxa fuq portijiet differenti).

Nistgħu wkoll niffurmaw raggruppamenti HA differenti kif konna nagħmlu bil-verżjoni preċedenti jiġifieri 4, 5 jew 6.

Imxi fid-direttorju $JBOSS_HOME/bin u tniedi standalone.sh script mit-terminal kif muri hawn taħt. Jekk ma nispeċifikaw l-ebda parametru, allura awtomatikament se jintrabat mal-indirizz loopback u juża fajl 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

Nota: Tista' tuża l-għażla –b [IP] biex tibda server b'xi IP ieħor u biex tgħabbi xi fajl ta' konfigurazzjoni ieħor uża -c [isem tal-fajl tal-konfigurazzjoni].

Dan huwa kunċett ġdid li jiġi introdott f'AS-7.* . B'din il-karatteristika ġdida f'WildFly-8, nistgħu namministraw każijiet differenti minn punt wieħed. Dan tassew jgħinna niċkienu għal punt ta 'kontroll wieħed minflok ma namministraw servers awtonomi multipli.

Is-servers kollha ġestiti minn Domain huma magħrufa bħala membri tad-dominju. Il-membri kollha tad-dominju jistgħu jaqsmu l-istess konfigurazzjoni/skjeramenti. Dan huwa verament utli u utli għall-ambjent ta 'clustering.

Fil-mod ta 'Dominju nistgħu noħolqu grupp ta' servers u mbagħad nistgħu nżidu numru ta 'servers ma' dak il-grupp. B'dan dak kollu li nagħmlu fuq dan il-Grupp ta 'Server, kollox se jiġi replikat għal kull server fil-Gruppi ta' Server.

Imxi lejn $JBOSS_HOME/direttorju bin u tniedi domain.sh script mit-terminal kif muri hawn taħt.

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

Ħaġa oħra li tinnota d-differenza bejn in-numru ta 'servizzi li bdew b'mod Standalone (183 minn 0f 232) u l-mod ta' Dominju (207 minn 255).

Differenza oħra l-aktar importanti bejn Standalone u Domain Mode hija l-kmand tal-istartjar użat fl-iskript tal-istartjar. Fi waħdu, il-punt tad-dħul huwa \org.jboss.as.standalone filwaqt li fil-mod tad-dominju l-punt tad-dħul huwa \org.jboss.as.process-controller. Hawn taħt hija l-figura li turi relazzjoni loġika bejn proċessi differenti.

Fil-modalità tad-dominju, l-ewwel se tibda kontrollur tal-proċess u tbid proċess ġdid imsejjaħ Kontrollur Ospitanti. Dan il-proċess tal-Kontrollur Ospitanti se jkun responsabbli għall-immaniġġjar ta' servers multipli fi ħdan gruppi ta' servers differenti. Punt ieħor li jeħtieġ li jkun innota li kull Server se jkollu l-proċess JVM tiegħu stess.

Dak kollu għalissa! Fl-artiklu li jmiss tagħna ser nuru modi differenti kif nagħmlu l-iskjeramenti fil-WildFly. Sakemm, imbagħad ibqa' sintonizzat u konness ma' Tecmint u tinsiex tagħti l-feedback siewi tiegħek fit-taqsima tal-kummenti tagħna hawn taħt.