one daytalk hbraun_oct2011

25
Heiko Braun, October 2011

Upload: hbraun

Post on 19-May-2015

1.149 views

Category:

Technology


1 download

TRANSCRIPT

Page 1: One daytalk hbraun_oct2011

Heiko Braun October 2011

Back to the future

AS 7 Key Featuresbull Fast and Lightweight

bull Unified user focused configurationndash No more intermixing of internal wiring and config

bull Modular ndash Only APIs no AS implementation exposure

ndash True isolation (users can finally use their own XML parsers)

bull Multiple consistent management interfacesndash CLI Java API HTTP API Console

bull Supports domain (multi-node) management

3

Performance Improvements

Kernel Architecture

bull Small and efficientndash 216K JARndash Tiny memory overhead

bull Highly concurrent amp scalable state machinebull Multiple startup modes

ndash Active Passive On-Demand

bull Async start amp stopndashConcurrent Service bootstrap

5

Modular Classloadingbull Small lightweight and efficient

ndash O(1) Dep resolutionndash Concurrent class loading ndash 207k JAR

bull ldquoPurerdquo modular class loadingndash Dependency declarations instead of visibility hierarchyndash Modules only see what they import (includes JDK classes)

6

Modular Classloading

7

bull Modules delegate to one another as peers (no parents)

bull A graph not a treebull Much like multi-module

projects are configured in an IDE

bull JDK classes are modules toobull All module ldquoseerdquo java

Subsystemsbull THE extensibility point for AS7

bull Defines management operations to represent all available configuration and runtime actions

bull Defines services as needed to carry out runtime behavior

bull Installs deployment processors as needed

8

Boot Time Results

9

Memory Comparison

10

Management amp Configuration

Simplified Configurationbull End user configuration centralized in a few files

ndashNo longer scattered all over the distributionbull Configuration files focused on end user configuration

ndashNo internal service wiring detailsbull Config changes made via management tools

persisted back to the config file

12

User-focused

13

Management APIbull Central Detyped Management API

ndash All management operations operate withon DMR(Detyped Management Representation)

bull Auto-converts like dynamic languagesbull Self describing

ndashOperationsndashAttributesndashMetrics

14

Management Protocol

15

[standalonelocalhost9999 ] subsystem=webconnector=httpread-resource outcome =gt success result =gt enable-lookups =gt false enabled =gt true max-post-size =gt 2097152 max-save-post-size =gt 4096 protocol =gt HTTP11 redirect-port =gt 8443 scheme =gt http secure =gt false socket-binding =gt http ssl =gt undefined virtual-server =gt undefined

Protocol Explained

16

[standalonelocalhost9999 ] subsystem=webconnector=httpread-resource outcome =gt success result =gt enable-lookups =gt false enabled =gt true max-post-size =gt 2097152 max-save-post-size =gt 4096 protocol =gt HTTP11 redirect-port =gt 8443 scheme =gt http secure =gt false socket-binding =gt http ssl =gt undefined virtual-server =gt undefined

Address

Operation

Payload

Management Infrastructurebull Several entry-points

ndashJava APIndashHTTP Protocol

bull ToolingndashCommand Line InterfacendashWeb Management Interface

bull CustomizationndashEasily integrate with other environments (scripting)

17

18

Operational Modes

Two Operational Modesbull Standalone

ndash Traditional JBoss single JVM serverndash Management facilities IN-VMndash No lifecycle management (only shutdown)

bull Domainndash Multi-JVM multi-server modelndash Management coordinated by Domain Controller Processndash Multiple server instances (JVMs) per Hostndash Full lifecycle managed by Process Controller

20

Domain topology

21

Management Choices

bull Basically do you want to take advantage of our multi-server management featuresndashYes run in Domain ModendashNo run in Standalone Mode

bull Either way you still get simplified configuration and a robust management API

22

Grow with your needs

ldquoStart small grow bigrdquo

bull Engineering requirements changendashProject requirementsndashDevelopment teams amp sizendashSystem Capacity

bull AS 7 can stayndashWeb Profile EE ProfilendashServer Managed DomainndashSingle Instance ClusterndashCloud

24

QampA

bull AS 7 space on jbossorgndashhttpcommunityjbossorgenjbossasdev

jboss_as7_developmentbull Mail list

ndashjboss-as7-devlistsjbossorgbull IRC

ndashjboss-as7 on freenodebull JIRA

ndashhttpsissuesjbossorgbrowseAS71

25

Page 2: One daytalk hbraun_oct2011

Back to the future

AS 7 Key Featuresbull Fast and Lightweight

bull Unified user focused configurationndash No more intermixing of internal wiring and config

bull Modular ndash Only APIs no AS implementation exposure

ndash True isolation (users can finally use their own XML parsers)

bull Multiple consistent management interfacesndash CLI Java API HTTP API Console

bull Supports domain (multi-node) management

3

Performance Improvements

Kernel Architecture

bull Small and efficientndash 216K JARndash Tiny memory overhead

bull Highly concurrent amp scalable state machinebull Multiple startup modes

ndash Active Passive On-Demand

bull Async start amp stopndashConcurrent Service bootstrap

5

Modular Classloadingbull Small lightweight and efficient

ndash O(1) Dep resolutionndash Concurrent class loading ndash 207k JAR

bull ldquoPurerdquo modular class loadingndash Dependency declarations instead of visibility hierarchyndash Modules only see what they import (includes JDK classes)

6

Modular Classloading

7

bull Modules delegate to one another as peers (no parents)

bull A graph not a treebull Much like multi-module

projects are configured in an IDE

bull JDK classes are modules toobull All module ldquoseerdquo java

Subsystemsbull THE extensibility point for AS7

bull Defines management operations to represent all available configuration and runtime actions

bull Defines services as needed to carry out runtime behavior

bull Installs deployment processors as needed

8

Boot Time Results

9

Memory Comparison

10

Management amp Configuration

Simplified Configurationbull End user configuration centralized in a few files

ndashNo longer scattered all over the distributionbull Configuration files focused on end user configuration

ndashNo internal service wiring detailsbull Config changes made via management tools

persisted back to the config file

12

User-focused

13

Management APIbull Central Detyped Management API

ndash All management operations operate withon DMR(Detyped Management Representation)

bull Auto-converts like dynamic languagesbull Self describing

ndashOperationsndashAttributesndashMetrics

14

Management Protocol

15

[standalonelocalhost9999 ] subsystem=webconnector=httpread-resource outcome =gt success result =gt enable-lookups =gt false enabled =gt true max-post-size =gt 2097152 max-save-post-size =gt 4096 protocol =gt HTTP11 redirect-port =gt 8443 scheme =gt http secure =gt false socket-binding =gt http ssl =gt undefined virtual-server =gt undefined

Protocol Explained

16

[standalonelocalhost9999 ] subsystem=webconnector=httpread-resource outcome =gt success result =gt enable-lookups =gt false enabled =gt true max-post-size =gt 2097152 max-save-post-size =gt 4096 protocol =gt HTTP11 redirect-port =gt 8443 scheme =gt http secure =gt false socket-binding =gt http ssl =gt undefined virtual-server =gt undefined

Address

Operation

Payload

Management Infrastructurebull Several entry-points

ndashJava APIndashHTTP Protocol

bull ToolingndashCommand Line InterfacendashWeb Management Interface

bull CustomizationndashEasily integrate with other environments (scripting)

17

18

Operational Modes

Two Operational Modesbull Standalone

ndash Traditional JBoss single JVM serverndash Management facilities IN-VMndash No lifecycle management (only shutdown)

bull Domainndash Multi-JVM multi-server modelndash Management coordinated by Domain Controller Processndash Multiple server instances (JVMs) per Hostndash Full lifecycle managed by Process Controller

20

Domain topology

21

Management Choices

bull Basically do you want to take advantage of our multi-server management featuresndashYes run in Domain ModendashNo run in Standalone Mode

bull Either way you still get simplified configuration and a robust management API

22

Grow with your needs

ldquoStart small grow bigrdquo

bull Engineering requirements changendashProject requirementsndashDevelopment teams amp sizendashSystem Capacity

bull AS 7 can stayndashWeb Profile EE ProfilendashServer Managed DomainndashSingle Instance ClusterndashCloud

24

QampA

bull AS 7 space on jbossorgndashhttpcommunityjbossorgenjbossasdev

jboss_as7_developmentbull Mail list

ndashjboss-as7-devlistsjbossorgbull IRC

ndashjboss-as7 on freenodebull JIRA

ndashhttpsissuesjbossorgbrowseAS71

25

Page 3: One daytalk hbraun_oct2011

AS 7 Key Featuresbull Fast and Lightweight

bull Unified user focused configurationndash No more intermixing of internal wiring and config

bull Modular ndash Only APIs no AS implementation exposure

ndash True isolation (users can finally use their own XML parsers)

bull Multiple consistent management interfacesndash CLI Java API HTTP API Console

bull Supports domain (multi-node) management

3

Performance Improvements

Kernel Architecture

bull Small and efficientndash 216K JARndash Tiny memory overhead

bull Highly concurrent amp scalable state machinebull Multiple startup modes

ndash Active Passive On-Demand

bull Async start amp stopndashConcurrent Service bootstrap

5

Modular Classloadingbull Small lightweight and efficient

ndash O(1) Dep resolutionndash Concurrent class loading ndash 207k JAR

bull ldquoPurerdquo modular class loadingndash Dependency declarations instead of visibility hierarchyndash Modules only see what they import (includes JDK classes)

6

Modular Classloading

7

bull Modules delegate to one another as peers (no parents)

bull A graph not a treebull Much like multi-module

projects are configured in an IDE

bull JDK classes are modules toobull All module ldquoseerdquo java

Subsystemsbull THE extensibility point for AS7

bull Defines management operations to represent all available configuration and runtime actions

bull Defines services as needed to carry out runtime behavior

bull Installs deployment processors as needed

8

Boot Time Results

9

Memory Comparison

10

Management amp Configuration

Simplified Configurationbull End user configuration centralized in a few files

ndashNo longer scattered all over the distributionbull Configuration files focused on end user configuration

ndashNo internal service wiring detailsbull Config changes made via management tools

persisted back to the config file

12

User-focused

13

Management APIbull Central Detyped Management API

ndash All management operations operate withon DMR(Detyped Management Representation)

bull Auto-converts like dynamic languagesbull Self describing

ndashOperationsndashAttributesndashMetrics

14

Management Protocol

15

[standalonelocalhost9999 ] subsystem=webconnector=httpread-resource outcome =gt success result =gt enable-lookups =gt false enabled =gt true max-post-size =gt 2097152 max-save-post-size =gt 4096 protocol =gt HTTP11 redirect-port =gt 8443 scheme =gt http secure =gt false socket-binding =gt http ssl =gt undefined virtual-server =gt undefined

Protocol Explained

16

[standalonelocalhost9999 ] subsystem=webconnector=httpread-resource outcome =gt success result =gt enable-lookups =gt false enabled =gt true max-post-size =gt 2097152 max-save-post-size =gt 4096 protocol =gt HTTP11 redirect-port =gt 8443 scheme =gt http secure =gt false socket-binding =gt http ssl =gt undefined virtual-server =gt undefined

Address

Operation

Payload

Management Infrastructurebull Several entry-points

ndashJava APIndashHTTP Protocol

bull ToolingndashCommand Line InterfacendashWeb Management Interface

bull CustomizationndashEasily integrate with other environments (scripting)

17

18

Operational Modes

Two Operational Modesbull Standalone

ndash Traditional JBoss single JVM serverndash Management facilities IN-VMndash No lifecycle management (only shutdown)

bull Domainndash Multi-JVM multi-server modelndash Management coordinated by Domain Controller Processndash Multiple server instances (JVMs) per Hostndash Full lifecycle managed by Process Controller

20

Domain topology

21

Management Choices

bull Basically do you want to take advantage of our multi-server management featuresndashYes run in Domain ModendashNo run in Standalone Mode

bull Either way you still get simplified configuration and a robust management API

22

Grow with your needs

ldquoStart small grow bigrdquo

bull Engineering requirements changendashProject requirementsndashDevelopment teams amp sizendashSystem Capacity

bull AS 7 can stayndashWeb Profile EE ProfilendashServer Managed DomainndashSingle Instance ClusterndashCloud

24

QampA

bull AS 7 space on jbossorgndashhttpcommunityjbossorgenjbossasdev

jboss_as7_developmentbull Mail list

ndashjboss-as7-devlistsjbossorgbull IRC

ndashjboss-as7 on freenodebull JIRA

ndashhttpsissuesjbossorgbrowseAS71

25

Page 4: One daytalk hbraun_oct2011

Performance Improvements

Kernel Architecture

bull Small and efficientndash 216K JARndash Tiny memory overhead

bull Highly concurrent amp scalable state machinebull Multiple startup modes

ndash Active Passive On-Demand

bull Async start amp stopndashConcurrent Service bootstrap

5

Modular Classloadingbull Small lightweight and efficient

ndash O(1) Dep resolutionndash Concurrent class loading ndash 207k JAR

bull ldquoPurerdquo modular class loadingndash Dependency declarations instead of visibility hierarchyndash Modules only see what they import (includes JDK classes)

6

Modular Classloading

7

bull Modules delegate to one another as peers (no parents)

bull A graph not a treebull Much like multi-module

projects are configured in an IDE

bull JDK classes are modules toobull All module ldquoseerdquo java

Subsystemsbull THE extensibility point for AS7

bull Defines management operations to represent all available configuration and runtime actions

bull Defines services as needed to carry out runtime behavior

bull Installs deployment processors as needed

8

Boot Time Results

9

Memory Comparison

10

Management amp Configuration

Simplified Configurationbull End user configuration centralized in a few files

ndashNo longer scattered all over the distributionbull Configuration files focused on end user configuration

ndashNo internal service wiring detailsbull Config changes made via management tools

persisted back to the config file

12

User-focused

13

Management APIbull Central Detyped Management API

ndash All management operations operate withon DMR(Detyped Management Representation)

bull Auto-converts like dynamic languagesbull Self describing

ndashOperationsndashAttributesndashMetrics

14

Management Protocol

15

[standalonelocalhost9999 ] subsystem=webconnector=httpread-resource outcome =gt success result =gt enable-lookups =gt false enabled =gt true max-post-size =gt 2097152 max-save-post-size =gt 4096 protocol =gt HTTP11 redirect-port =gt 8443 scheme =gt http secure =gt false socket-binding =gt http ssl =gt undefined virtual-server =gt undefined

Protocol Explained

16

[standalonelocalhost9999 ] subsystem=webconnector=httpread-resource outcome =gt success result =gt enable-lookups =gt false enabled =gt true max-post-size =gt 2097152 max-save-post-size =gt 4096 protocol =gt HTTP11 redirect-port =gt 8443 scheme =gt http secure =gt false socket-binding =gt http ssl =gt undefined virtual-server =gt undefined

Address

Operation

Payload

Management Infrastructurebull Several entry-points

ndashJava APIndashHTTP Protocol

bull ToolingndashCommand Line InterfacendashWeb Management Interface

bull CustomizationndashEasily integrate with other environments (scripting)

17

18

Operational Modes

Two Operational Modesbull Standalone

ndash Traditional JBoss single JVM serverndash Management facilities IN-VMndash No lifecycle management (only shutdown)

bull Domainndash Multi-JVM multi-server modelndash Management coordinated by Domain Controller Processndash Multiple server instances (JVMs) per Hostndash Full lifecycle managed by Process Controller

20

Domain topology

21

Management Choices

bull Basically do you want to take advantage of our multi-server management featuresndashYes run in Domain ModendashNo run in Standalone Mode

bull Either way you still get simplified configuration and a robust management API

22

Grow with your needs

ldquoStart small grow bigrdquo

bull Engineering requirements changendashProject requirementsndashDevelopment teams amp sizendashSystem Capacity

bull AS 7 can stayndashWeb Profile EE ProfilendashServer Managed DomainndashSingle Instance ClusterndashCloud

24

QampA

bull AS 7 space on jbossorgndashhttpcommunityjbossorgenjbossasdev

jboss_as7_developmentbull Mail list

ndashjboss-as7-devlistsjbossorgbull IRC

ndashjboss-as7 on freenodebull JIRA

ndashhttpsissuesjbossorgbrowseAS71

25

Page 5: One daytalk hbraun_oct2011

Kernel Architecture

bull Small and efficientndash 216K JARndash Tiny memory overhead

bull Highly concurrent amp scalable state machinebull Multiple startup modes

ndash Active Passive On-Demand

bull Async start amp stopndashConcurrent Service bootstrap

5

Modular Classloadingbull Small lightweight and efficient

ndash O(1) Dep resolutionndash Concurrent class loading ndash 207k JAR

bull ldquoPurerdquo modular class loadingndash Dependency declarations instead of visibility hierarchyndash Modules only see what they import (includes JDK classes)

6

Modular Classloading

7

bull Modules delegate to one another as peers (no parents)

bull A graph not a treebull Much like multi-module

projects are configured in an IDE

bull JDK classes are modules toobull All module ldquoseerdquo java

Subsystemsbull THE extensibility point for AS7

bull Defines management operations to represent all available configuration and runtime actions

bull Defines services as needed to carry out runtime behavior

bull Installs deployment processors as needed

8

Boot Time Results

9

Memory Comparison

10

Management amp Configuration

Simplified Configurationbull End user configuration centralized in a few files

ndashNo longer scattered all over the distributionbull Configuration files focused on end user configuration

ndashNo internal service wiring detailsbull Config changes made via management tools

persisted back to the config file

12

User-focused

13

Management APIbull Central Detyped Management API

ndash All management operations operate withon DMR(Detyped Management Representation)

bull Auto-converts like dynamic languagesbull Self describing

ndashOperationsndashAttributesndashMetrics

14

Management Protocol

15

[standalonelocalhost9999 ] subsystem=webconnector=httpread-resource outcome =gt success result =gt enable-lookups =gt false enabled =gt true max-post-size =gt 2097152 max-save-post-size =gt 4096 protocol =gt HTTP11 redirect-port =gt 8443 scheme =gt http secure =gt false socket-binding =gt http ssl =gt undefined virtual-server =gt undefined

Protocol Explained

16

[standalonelocalhost9999 ] subsystem=webconnector=httpread-resource outcome =gt success result =gt enable-lookups =gt false enabled =gt true max-post-size =gt 2097152 max-save-post-size =gt 4096 protocol =gt HTTP11 redirect-port =gt 8443 scheme =gt http secure =gt false socket-binding =gt http ssl =gt undefined virtual-server =gt undefined

Address

Operation

Payload

Management Infrastructurebull Several entry-points

ndashJava APIndashHTTP Protocol

bull ToolingndashCommand Line InterfacendashWeb Management Interface

bull CustomizationndashEasily integrate with other environments (scripting)

17

18

Operational Modes

Two Operational Modesbull Standalone

ndash Traditional JBoss single JVM serverndash Management facilities IN-VMndash No lifecycle management (only shutdown)

bull Domainndash Multi-JVM multi-server modelndash Management coordinated by Domain Controller Processndash Multiple server instances (JVMs) per Hostndash Full lifecycle managed by Process Controller

20

Domain topology

21

Management Choices

bull Basically do you want to take advantage of our multi-server management featuresndashYes run in Domain ModendashNo run in Standalone Mode

bull Either way you still get simplified configuration and a robust management API

22

Grow with your needs

ldquoStart small grow bigrdquo

bull Engineering requirements changendashProject requirementsndashDevelopment teams amp sizendashSystem Capacity

bull AS 7 can stayndashWeb Profile EE ProfilendashServer Managed DomainndashSingle Instance ClusterndashCloud

24

QampA

bull AS 7 space on jbossorgndashhttpcommunityjbossorgenjbossasdev

jboss_as7_developmentbull Mail list

ndashjboss-as7-devlistsjbossorgbull IRC

ndashjboss-as7 on freenodebull JIRA

ndashhttpsissuesjbossorgbrowseAS71

25

Page 6: One daytalk hbraun_oct2011

Modular Classloadingbull Small lightweight and efficient

ndash O(1) Dep resolutionndash Concurrent class loading ndash 207k JAR

bull ldquoPurerdquo modular class loadingndash Dependency declarations instead of visibility hierarchyndash Modules only see what they import (includes JDK classes)

6

Modular Classloading

7

bull Modules delegate to one another as peers (no parents)

bull A graph not a treebull Much like multi-module

projects are configured in an IDE

bull JDK classes are modules toobull All module ldquoseerdquo java

Subsystemsbull THE extensibility point for AS7

bull Defines management operations to represent all available configuration and runtime actions

bull Defines services as needed to carry out runtime behavior

bull Installs deployment processors as needed

8

Boot Time Results

9

Memory Comparison

10

Management amp Configuration

Simplified Configurationbull End user configuration centralized in a few files

ndashNo longer scattered all over the distributionbull Configuration files focused on end user configuration

ndashNo internal service wiring detailsbull Config changes made via management tools

persisted back to the config file

12

User-focused

13

Management APIbull Central Detyped Management API

ndash All management operations operate withon DMR(Detyped Management Representation)

bull Auto-converts like dynamic languagesbull Self describing

ndashOperationsndashAttributesndashMetrics

14

Management Protocol

15

[standalonelocalhost9999 ] subsystem=webconnector=httpread-resource outcome =gt success result =gt enable-lookups =gt false enabled =gt true max-post-size =gt 2097152 max-save-post-size =gt 4096 protocol =gt HTTP11 redirect-port =gt 8443 scheme =gt http secure =gt false socket-binding =gt http ssl =gt undefined virtual-server =gt undefined

Protocol Explained

16

[standalonelocalhost9999 ] subsystem=webconnector=httpread-resource outcome =gt success result =gt enable-lookups =gt false enabled =gt true max-post-size =gt 2097152 max-save-post-size =gt 4096 protocol =gt HTTP11 redirect-port =gt 8443 scheme =gt http secure =gt false socket-binding =gt http ssl =gt undefined virtual-server =gt undefined

Address

Operation

Payload

Management Infrastructurebull Several entry-points

ndashJava APIndashHTTP Protocol

bull ToolingndashCommand Line InterfacendashWeb Management Interface

bull CustomizationndashEasily integrate with other environments (scripting)

17

18

Operational Modes

Two Operational Modesbull Standalone

ndash Traditional JBoss single JVM serverndash Management facilities IN-VMndash No lifecycle management (only shutdown)

bull Domainndash Multi-JVM multi-server modelndash Management coordinated by Domain Controller Processndash Multiple server instances (JVMs) per Hostndash Full lifecycle managed by Process Controller

20

Domain topology

21

Management Choices

bull Basically do you want to take advantage of our multi-server management featuresndashYes run in Domain ModendashNo run in Standalone Mode

bull Either way you still get simplified configuration and a robust management API

22

Grow with your needs

ldquoStart small grow bigrdquo

bull Engineering requirements changendashProject requirementsndashDevelopment teams amp sizendashSystem Capacity

bull AS 7 can stayndashWeb Profile EE ProfilendashServer Managed DomainndashSingle Instance ClusterndashCloud

24

QampA

bull AS 7 space on jbossorgndashhttpcommunityjbossorgenjbossasdev

jboss_as7_developmentbull Mail list

ndashjboss-as7-devlistsjbossorgbull IRC

ndashjboss-as7 on freenodebull JIRA

ndashhttpsissuesjbossorgbrowseAS71

25

Page 7: One daytalk hbraun_oct2011

Modular Classloading

7

bull Modules delegate to one another as peers (no parents)

bull A graph not a treebull Much like multi-module

projects are configured in an IDE

bull JDK classes are modules toobull All module ldquoseerdquo java

Subsystemsbull THE extensibility point for AS7

bull Defines management operations to represent all available configuration and runtime actions

bull Defines services as needed to carry out runtime behavior

bull Installs deployment processors as needed

8

Boot Time Results

9

Memory Comparison

10

Management amp Configuration

Simplified Configurationbull End user configuration centralized in a few files

ndashNo longer scattered all over the distributionbull Configuration files focused on end user configuration

ndashNo internal service wiring detailsbull Config changes made via management tools

persisted back to the config file

12

User-focused

13

Management APIbull Central Detyped Management API

ndash All management operations operate withon DMR(Detyped Management Representation)

bull Auto-converts like dynamic languagesbull Self describing

ndashOperationsndashAttributesndashMetrics

14

Management Protocol

15

[standalonelocalhost9999 ] subsystem=webconnector=httpread-resource outcome =gt success result =gt enable-lookups =gt false enabled =gt true max-post-size =gt 2097152 max-save-post-size =gt 4096 protocol =gt HTTP11 redirect-port =gt 8443 scheme =gt http secure =gt false socket-binding =gt http ssl =gt undefined virtual-server =gt undefined

Protocol Explained

16

[standalonelocalhost9999 ] subsystem=webconnector=httpread-resource outcome =gt success result =gt enable-lookups =gt false enabled =gt true max-post-size =gt 2097152 max-save-post-size =gt 4096 protocol =gt HTTP11 redirect-port =gt 8443 scheme =gt http secure =gt false socket-binding =gt http ssl =gt undefined virtual-server =gt undefined

Address

Operation

Payload

Management Infrastructurebull Several entry-points

ndashJava APIndashHTTP Protocol

bull ToolingndashCommand Line InterfacendashWeb Management Interface

bull CustomizationndashEasily integrate with other environments (scripting)

17

18

Operational Modes

Two Operational Modesbull Standalone

ndash Traditional JBoss single JVM serverndash Management facilities IN-VMndash No lifecycle management (only shutdown)

bull Domainndash Multi-JVM multi-server modelndash Management coordinated by Domain Controller Processndash Multiple server instances (JVMs) per Hostndash Full lifecycle managed by Process Controller

20

Domain topology

21

Management Choices

bull Basically do you want to take advantage of our multi-server management featuresndashYes run in Domain ModendashNo run in Standalone Mode

bull Either way you still get simplified configuration and a robust management API

22

Grow with your needs

ldquoStart small grow bigrdquo

bull Engineering requirements changendashProject requirementsndashDevelopment teams amp sizendashSystem Capacity

bull AS 7 can stayndashWeb Profile EE ProfilendashServer Managed DomainndashSingle Instance ClusterndashCloud

24

QampA

bull AS 7 space on jbossorgndashhttpcommunityjbossorgenjbossasdev

jboss_as7_developmentbull Mail list

ndashjboss-as7-devlistsjbossorgbull IRC

ndashjboss-as7 on freenodebull JIRA

ndashhttpsissuesjbossorgbrowseAS71

25

Page 8: One daytalk hbraun_oct2011

Subsystemsbull THE extensibility point for AS7

bull Defines management operations to represent all available configuration and runtime actions

bull Defines services as needed to carry out runtime behavior

bull Installs deployment processors as needed

8

Boot Time Results

9

Memory Comparison

10

Management amp Configuration

Simplified Configurationbull End user configuration centralized in a few files

ndashNo longer scattered all over the distributionbull Configuration files focused on end user configuration

ndashNo internal service wiring detailsbull Config changes made via management tools

persisted back to the config file

12

User-focused

13

Management APIbull Central Detyped Management API

ndash All management operations operate withon DMR(Detyped Management Representation)

bull Auto-converts like dynamic languagesbull Self describing

ndashOperationsndashAttributesndashMetrics

14

Management Protocol

15

[standalonelocalhost9999 ] subsystem=webconnector=httpread-resource outcome =gt success result =gt enable-lookups =gt false enabled =gt true max-post-size =gt 2097152 max-save-post-size =gt 4096 protocol =gt HTTP11 redirect-port =gt 8443 scheme =gt http secure =gt false socket-binding =gt http ssl =gt undefined virtual-server =gt undefined

Protocol Explained

16

[standalonelocalhost9999 ] subsystem=webconnector=httpread-resource outcome =gt success result =gt enable-lookups =gt false enabled =gt true max-post-size =gt 2097152 max-save-post-size =gt 4096 protocol =gt HTTP11 redirect-port =gt 8443 scheme =gt http secure =gt false socket-binding =gt http ssl =gt undefined virtual-server =gt undefined

Address

Operation

Payload

Management Infrastructurebull Several entry-points

ndashJava APIndashHTTP Protocol

bull ToolingndashCommand Line InterfacendashWeb Management Interface

bull CustomizationndashEasily integrate with other environments (scripting)

17

18

Operational Modes

Two Operational Modesbull Standalone

ndash Traditional JBoss single JVM serverndash Management facilities IN-VMndash No lifecycle management (only shutdown)

bull Domainndash Multi-JVM multi-server modelndash Management coordinated by Domain Controller Processndash Multiple server instances (JVMs) per Hostndash Full lifecycle managed by Process Controller

20

Domain topology

21

Management Choices

bull Basically do you want to take advantage of our multi-server management featuresndashYes run in Domain ModendashNo run in Standalone Mode

bull Either way you still get simplified configuration and a robust management API

22

Grow with your needs

ldquoStart small grow bigrdquo

bull Engineering requirements changendashProject requirementsndashDevelopment teams amp sizendashSystem Capacity

bull AS 7 can stayndashWeb Profile EE ProfilendashServer Managed DomainndashSingle Instance ClusterndashCloud

24

QampA

bull AS 7 space on jbossorgndashhttpcommunityjbossorgenjbossasdev

jboss_as7_developmentbull Mail list

ndashjboss-as7-devlistsjbossorgbull IRC

ndashjboss-as7 on freenodebull JIRA

ndashhttpsissuesjbossorgbrowseAS71

25

Page 9: One daytalk hbraun_oct2011

Boot Time Results

9

Memory Comparison

10

Management amp Configuration

Simplified Configurationbull End user configuration centralized in a few files

ndashNo longer scattered all over the distributionbull Configuration files focused on end user configuration

ndashNo internal service wiring detailsbull Config changes made via management tools

persisted back to the config file

12

User-focused

13

Management APIbull Central Detyped Management API

ndash All management operations operate withon DMR(Detyped Management Representation)

bull Auto-converts like dynamic languagesbull Self describing

ndashOperationsndashAttributesndashMetrics

14

Management Protocol

15

[standalonelocalhost9999 ] subsystem=webconnector=httpread-resource outcome =gt success result =gt enable-lookups =gt false enabled =gt true max-post-size =gt 2097152 max-save-post-size =gt 4096 protocol =gt HTTP11 redirect-port =gt 8443 scheme =gt http secure =gt false socket-binding =gt http ssl =gt undefined virtual-server =gt undefined

Protocol Explained

16

[standalonelocalhost9999 ] subsystem=webconnector=httpread-resource outcome =gt success result =gt enable-lookups =gt false enabled =gt true max-post-size =gt 2097152 max-save-post-size =gt 4096 protocol =gt HTTP11 redirect-port =gt 8443 scheme =gt http secure =gt false socket-binding =gt http ssl =gt undefined virtual-server =gt undefined

Address

Operation

Payload

Management Infrastructurebull Several entry-points

ndashJava APIndashHTTP Protocol

bull ToolingndashCommand Line InterfacendashWeb Management Interface

bull CustomizationndashEasily integrate with other environments (scripting)

17

18

Operational Modes

Two Operational Modesbull Standalone

ndash Traditional JBoss single JVM serverndash Management facilities IN-VMndash No lifecycle management (only shutdown)

bull Domainndash Multi-JVM multi-server modelndash Management coordinated by Domain Controller Processndash Multiple server instances (JVMs) per Hostndash Full lifecycle managed by Process Controller

20

Domain topology

21

Management Choices

bull Basically do you want to take advantage of our multi-server management featuresndashYes run in Domain ModendashNo run in Standalone Mode

bull Either way you still get simplified configuration and a robust management API

22

Grow with your needs

ldquoStart small grow bigrdquo

bull Engineering requirements changendashProject requirementsndashDevelopment teams amp sizendashSystem Capacity

bull AS 7 can stayndashWeb Profile EE ProfilendashServer Managed DomainndashSingle Instance ClusterndashCloud

24

QampA

bull AS 7 space on jbossorgndashhttpcommunityjbossorgenjbossasdev

jboss_as7_developmentbull Mail list

ndashjboss-as7-devlistsjbossorgbull IRC

ndashjboss-as7 on freenodebull JIRA

ndashhttpsissuesjbossorgbrowseAS71

25

Page 10: One daytalk hbraun_oct2011

Memory Comparison

10

Management amp Configuration

Simplified Configurationbull End user configuration centralized in a few files

ndashNo longer scattered all over the distributionbull Configuration files focused on end user configuration

ndashNo internal service wiring detailsbull Config changes made via management tools

persisted back to the config file

12

User-focused

13

Management APIbull Central Detyped Management API

ndash All management operations operate withon DMR(Detyped Management Representation)

bull Auto-converts like dynamic languagesbull Self describing

ndashOperationsndashAttributesndashMetrics

14

Management Protocol

15

[standalonelocalhost9999 ] subsystem=webconnector=httpread-resource outcome =gt success result =gt enable-lookups =gt false enabled =gt true max-post-size =gt 2097152 max-save-post-size =gt 4096 protocol =gt HTTP11 redirect-port =gt 8443 scheme =gt http secure =gt false socket-binding =gt http ssl =gt undefined virtual-server =gt undefined

Protocol Explained

16

[standalonelocalhost9999 ] subsystem=webconnector=httpread-resource outcome =gt success result =gt enable-lookups =gt false enabled =gt true max-post-size =gt 2097152 max-save-post-size =gt 4096 protocol =gt HTTP11 redirect-port =gt 8443 scheme =gt http secure =gt false socket-binding =gt http ssl =gt undefined virtual-server =gt undefined

Address

Operation

Payload

Management Infrastructurebull Several entry-points

ndashJava APIndashHTTP Protocol

bull ToolingndashCommand Line InterfacendashWeb Management Interface

bull CustomizationndashEasily integrate with other environments (scripting)

17

18

Operational Modes

Two Operational Modesbull Standalone

ndash Traditional JBoss single JVM serverndash Management facilities IN-VMndash No lifecycle management (only shutdown)

bull Domainndash Multi-JVM multi-server modelndash Management coordinated by Domain Controller Processndash Multiple server instances (JVMs) per Hostndash Full lifecycle managed by Process Controller

20

Domain topology

21

Management Choices

bull Basically do you want to take advantage of our multi-server management featuresndashYes run in Domain ModendashNo run in Standalone Mode

bull Either way you still get simplified configuration and a robust management API

22

Grow with your needs

ldquoStart small grow bigrdquo

bull Engineering requirements changendashProject requirementsndashDevelopment teams amp sizendashSystem Capacity

bull AS 7 can stayndashWeb Profile EE ProfilendashServer Managed DomainndashSingle Instance ClusterndashCloud

24

QampA

bull AS 7 space on jbossorgndashhttpcommunityjbossorgenjbossasdev

jboss_as7_developmentbull Mail list

ndashjboss-as7-devlistsjbossorgbull IRC

ndashjboss-as7 on freenodebull JIRA

ndashhttpsissuesjbossorgbrowseAS71

25

Page 11: One daytalk hbraun_oct2011

Management amp Configuration

Simplified Configurationbull End user configuration centralized in a few files

ndashNo longer scattered all over the distributionbull Configuration files focused on end user configuration

ndashNo internal service wiring detailsbull Config changes made via management tools

persisted back to the config file

12

User-focused

13

Management APIbull Central Detyped Management API

ndash All management operations operate withon DMR(Detyped Management Representation)

bull Auto-converts like dynamic languagesbull Self describing

ndashOperationsndashAttributesndashMetrics

14

Management Protocol

15

[standalonelocalhost9999 ] subsystem=webconnector=httpread-resource outcome =gt success result =gt enable-lookups =gt false enabled =gt true max-post-size =gt 2097152 max-save-post-size =gt 4096 protocol =gt HTTP11 redirect-port =gt 8443 scheme =gt http secure =gt false socket-binding =gt http ssl =gt undefined virtual-server =gt undefined

Protocol Explained

16

[standalonelocalhost9999 ] subsystem=webconnector=httpread-resource outcome =gt success result =gt enable-lookups =gt false enabled =gt true max-post-size =gt 2097152 max-save-post-size =gt 4096 protocol =gt HTTP11 redirect-port =gt 8443 scheme =gt http secure =gt false socket-binding =gt http ssl =gt undefined virtual-server =gt undefined

Address

Operation

Payload

Management Infrastructurebull Several entry-points

ndashJava APIndashHTTP Protocol

bull ToolingndashCommand Line InterfacendashWeb Management Interface

bull CustomizationndashEasily integrate with other environments (scripting)

17

18

Operational Modes

Two Operational Modesbull Standalone

ndash Traditional JBoss single JVM serverndash Management facilities IN-VMndash No lifecycle management (only shutdown)

bull Domainndash Multi-JVM multi-server modelndash Management coordinated by Domain Controller Processndash Multiple server instances (JVMs) per Hostndash Full lifecycle managed by Process Controller

20

Domain topology

21

Management Choices

bull Basically do you want to take advantage of our multi-server management featuresndashYes run in Domain ModendashNo run in Standalone Mode

bull Either way you still get simplified configuration and a robust management API

22

Grow with your needs

ldquoStart small grow bigrdquo

bull Engineering requirements changendashProject requirementsndashDevelopment teams amp sizendashSystem Capacity

bull AS 7 can stayndashWeb Profile EE ProfilendashServer Managed DomainndashSingle Instance ClusterndashCloud

24

QampA

bull AS 7 space on jbossorgndashhttpcommunityjbossorgenjbossasdev

jboss_as7_developmentbull Mail list

ndashjboss-as7-devlistsjbossorgbull IRC

ndashjboss-as7 on freenodebull JIRA

ndashhttpsissuesjbossorgbrowseAS71

25

Page 12: One daytalk hbraun_oct2011

Simplified Configurationbull End user configuration centralized in a few files

ndashNo longer scattered all over the distributionbull Configuration files focused on end user configuration

ndashNo internal service wiring detailsbull Config changes made via management tools

persisted back to the config file

12

User-focused

13

Management APIbull Central Detyped Management API

ndash All management operations operate withon DMR(Detyped Management Representation)

bull Auto-converts like dynamic languagesbull Self describing

ndashOperationsndashAttributesndashMetrics

14

Management Protocol

15

[standalonelocalhost9999 ] subsystem=webconnector=httpread-resource outcome =gt success result =gt enable-lookups =gt false enabled =gt true max-post-size =gt 2097152 max-save-post-size =gt 4096 protocol =gt HTTP11 redirect-port =gt 8443 scheme =gt http secure =gt false socket-binding =gt http ssl =gt undefined virtual-server =gt undefined

Protocol Explained

16

[standalonelocalhost9999 ] subsystem=webconnector=httpread-resource outcome =gt success result =gt enable-lookups =gt false enabled =gt true max-post-size =gt 2097152 max-save-post-size =gt 4096 protocol =gt HTTP11 redirect-port =gt 8443 scheme =gt http secure =gt false socket-binding =gt http ssl =gt undefined virtual-server =gt undefined

Address

Operation

Payload

Management Infrastructurebull Several entry-points

ndashJava APIndashHTTP Protocol

bull ToolingndashCommand Line InterfacendashWeb Management Interface

bull CustomizationndashEasily integrate with other environments (scripting)

17

18

Operational Modes

Two Operational Modesbull Standalone

ndash Traditional JBoss single JVM serverndash Management facilities IN-VMndash No lifecycle management (only shutdown)

bull Domainndash Multi-JVM multi-server modelndash Management coordinated by Domain Controller Processndash Multiple server instances (JVMs) per Hostndash Full lifecycle managed by Process Controller

20

Domain topology

21

Management Choices

bull Basically do you want to take advantage of our multi-server management featuresndashYes run in Domain ModendashNo run in Standalone Mode

bull Either way you still get simplified configuration and a robust management API

22

Grow with your needs

ldquoStart small grow bigrdquo

bull Engineering requirements changendashProject requirementsndashDevelopment teams amp sizendashSystem Capacity

bull AS 7 can stayndashWeb Profile EE ProfilendashServer Managed DomainndashSingle Instance ClusterndashCloud

24

QampA

bull AS 7 space on jbossorgndashhttpcommunityjbossorgenjbossasdev

jboss_as7_developmentbull Mail list

ndashjboss-as7-devlistsjbossorgbull IRC

ndashjboss-as7 on freenodebull JIRA

ndashhttpsissuesjbossorgbrowseAS71

25

Page 13: One daytalk hbraun_oct2011

User-focused

13

Management APIbull Central Detyped Management API

ndash All management operations operate withon DMR(Detyped Management Representation)

bull Auto-converts like dynamic languagesbull Self describing

ndashOperationsndashAttributesndashMetrics

14

Management Protocol

15

[standalonelocalhost9999 ] subsystem=webconnector=httpread-resource outcome =gt success result =gt enable-lookups =gt false enabled =gt true max-post-size =gt 2097152 max-save-post-size =gt 4096 protocol =gt HTTP11 redirect-port =gt 8443 scheme =gt http secure =gt false socket-binding =gt http ssl =gt undefined virtual-server =gt undefined

Protocol Explained

16

[standalonelocalhost9999 ] subsystem=webconnector=httpread-resource outcome =gt success result =gt enable-lookups =gt false enabled =gt true max-post-size =gt 2097152 max-save-post-size =gt 4096 protocol =gt HTTP11 redirect-port =gt 8443 scheme =gt http secure =gt false socket-binding =gt http ssl =gt undefined virtual-server =gt undefined

Address

Operation

Payload

Management Infrastructurebull Several entry-points

ndashJava APIndashHTTP Protocol

bull ToolingndashCommand Line InterfacendashWeb Management Interface

bull CustomizationndashEasily integrate with other environments (scripting)

17

18

Operational Modes

Two Operational Modesbull Standalone

ndash Traditional JBoss single JVM serverndash Management facilities IN-VMndash No lifecycle management (only shutdown)

bull Domainndash Multi-JVM multi-server modelndash Management coordinated by Domain Controller Processndash Multiple server instances (JVMs) per Hostndash Full lifecycle managed by Process Controller

20

Domain topology

21

Management Choices

bull Basically do you want to take advantage of our multi-server management featuresndashYes run in Domain ModendashNo run in Standalone Mode

bull Either way you still get simplified configuration and a robust management API

22

Grow with your needs

ldquoStart small grow bigrdquo

bull Engineering requirements changendashProject requirementsndashDevelopment teams amp sizendashSystem Capacity

bull AS 7 can stayndashWeb Profile EE ProfilendashServer Managed DomainndashSingle Instance ClusterndashCloud

24

QampA

bull AS 7 space on jbossorgndashhttpcommunityjbossorgenjbossasdev

jboss_as7_developmentbull Mail list

ndashjboss-as7-devlistsjbossorgbull IRC

ndashjboss-as7 on freenodebull JIRA

ndashhttpsissuesjbossorgbrowseAS71

25

Page 14: One daytalk hbraun_oct2011

Management APIbull Central Detyped Management API

ndash All management operations operate withon DMR(Detyped Management Representation)

bull Auto-converts like dynamic languagesbull Self describing

ndashOperationsndashAttributesndashMetrics

14

Management Protocol

15

[standalonelocalhost9999 ] subsystem=webconnector=httpread-resource outcome =gt success result =gt enable-lookups =gt false enabled =gt true max-post-size =gt 2097152 max-save-post-size =gt 4096 protocol =gt HTTP11 redirect-port =gt 8443 scheme =gt http secure =gt false socket-binding =gt http ssl =gt undefined virtual-server =gt undefined

Protocol Explained

16

[standalonelocalhost9999 ] subsystem=webconnector=httpread-resource outcome =gt success result =gt enable-lookups =gt false enabled =gt true max-post-size =gt 2097152 max-save-post-size =gt 4096 protocol =gt HTTP11 redirect-port =gt 8443 scheme =gt http secure =gt false socket-binding =gt http ssl =gt undefined virtual-server =gt undefined

Address

Operation

Payload

Management Infrastructurebull Several entry-points

ndashJava APIndashHTTP Protocol

bull ToolingndashCommand Line InterfacendashWeb Management Interface

bull CustomizationndashEasily integrate with other environments (scripting)

17

18

Operational Modes

Two Operational Modesbull Standalone

ndash Traditional JBoss single JVM serverndash Management facilities IN-VMndash No lifecycle management (only shutdown)

bull Domainndash Multi-JVM multi-server modelndash Management coordinated by Domain Controller Processndash Multiple server instances (JVMs) per Hostndash Full lifecycle managed by Process Controller

20

Domain topology

21

Management Choices

bull Basically do you want to take advantage of our multi-server management featuresndashYes run in Domain ModendashNo run in Standalone Mode

bull Either way you still get simplified configuration and a robust management API

22

Grow with your needs

ldquoStart small grow bigrdquo

bull Engineering requirements changendashProject requirementsndashDevelopment teams amp sizendashSystem Capacity

bull AS 7 can stayndashWeb Profile EE ProfilendashServer Managed DomainndashSingle Instance ClusterndashCloud

24

QampA

bull AS 7 space on jbossorgndashhttpcommunityjbossorgenjbossasdev

jboss_as7_developmentbull Mail list

ndashjboss-as7-devlistsjbossorgbull IRC

ndashjboss-as7 on freenodebull JIRA

ndashhttpsissuesjbossorgbrowseAS71

25

Page 15: One daytalk hbraun_oct2011

Management Protocol

15

[standalonelocalhost9999 ] subsystem=webconnector=httpread-resource outcome =gt success result =gt enable-lookups =gt false enabled =gt true max-post-size =gt 2097152 max-save-post-size =gt 4096 protocol =gt HTTP11 redirect-port =gt 8443 scheme =gt http secure =gt false socket-binding =gt http ssl =gt undefined virtual-server =gt undefined

Protocol Explained

16

[standalonelocalhost9999 ] subsystem=webconnector=httpread-resource outcome =gt success result =gt enable-lookups =gt false enabled =gt true max-post-size =gt 2097152 max-save-post-size =gt 4096 protocol =gt HTTP11 redirect-port =gt 8443 scheme =gt http secure =gt false socket-binding =gt http ssl =gt undefined virtual-server =gt undefined

Address

Operation

Payload

Management Infrastructurebull Several entry-points

ndashJava APIndashHTTP Protocol

bull ToolingndashCommand Line InterfacendashWeb Management Interface

bull CustomizationndashEasily integrate with other environments (scripting)

17

18

Operational Modes

Two Operational Modesbull Standalone

ndash Traditional JBoss single JVM serverndash Management facilities IN-VMndash No lifecycle management (only shutdown)

bull Domainndash Multi-JVM multi-server modelndash Management coordinated by Domain Controller Processndash Multiple server instances (JVMs) per Hostndash Full lifecycle managed by Process Controller

20

Domain topology

21

Management Choices

bull Basically do you want to take advantage of our multi-server management featuresndashYes run in Domain ModendashNo run in Standalone Mode

bull Either way you still get simplified configuration and a robust management API

22

Grow with your needs

ldquoStart small grow bigrdquo

bull Engineering requirements changendashProject requirementsndashDevelopment teams amp sizendashSystem Capacity

bull AS 7 can stayndashWeb Profile EE ProfilendashServer Managed DomainndashSingle Instance ClusterndashCloud

24

QampA

bull AS 7 space on jbossorgndashhttpcommunityjbossorgenjbossasdev

jboss_as7_developmentbull Mail list

ndashjboss-as7-devlistsjbossorgbull IRC

ndashjboss-as7 on freenodebull JIRA

ndashhttpsissuesjbossorgbrowseAS71

25

Page 16: One daytalk hbraun_oct2011

Protocol Explained

16

[standalonelocalhost9999 ] subsystem=webconnector=httpread-resource outcome =gt success result =gt enable-lookups =gt false enabled =gt true max-post-size =gt 2097152 max-save-post-size =gt 4096 protocol =gt HTTP11 redirect-port =gt 8443 scheme =gt http secure =gt false socket-binding =gt http ssl =gt undefined virtual-server =gt undefined

Address

Operation

Payload

Management Infrastructurebull Several entry-points

ndashJava APIndashHTTP Protocol

bull ToolingndashCommand Line InterfacendashWeb Management Interface

bull CustomizationndashEasily integrate with other environments (scripting)

17

18

Operational Modes

Two Operational Modesbull Standalone

ndash Traditional JBoss single JVM serverndash Management facilities IN-VMndash No lifecycle management (only shutdown)

bull Domainndash Multi-JVM multi-server modelndash Management coordinated by Domain Controller Processndash Multiple server instances (JVMs) per Hostndash Full lifecycle managed by Process Controller

20

Domain topology

21

Management Choices

bull Basically do you want to take advantage of our multi-server management featuresndashYes run in Domain ModendashNo run in Standalone Mode

bull Either way you still get simplified configuration and a robust management API

22

Grow with your needs

ldquoStart small grow bigrdquo

bull Engineering requirements changendashProject requirementsndashDevelopment teams amp sizendashSystem Capacity

bull AS 7 can stayndashWeb Profile EE ProfilendashServer Managed DomainndashSingle Instance ClusterndashCloud

24

QampA

bull AS 7 space on jbossorgndashhttpcommunityjbossorgenjbossasdev

jboss_as7_developmentbull Mail list

ndashjboss-as7-devlistsjbossorgbull IRC

ndashjboss-as7 on freenodebull JIRA

ndashhttpsissuesjbossorgbrowseAS71

25

Page 17: One daytalk hbraun_oct2011

Management Infrastructurebull Several entry-points

ndashJava APIndashHTTP Protocol

bull ToolingndashCommand Line InterfacendashWeb Management Interface

bull CustomizationndashEasily integrate with other environments (scripting)

17

18

Operational Modes

Two Operational Modesbull Standalone

ndash Traditional JBoss single JVM serverndash Management facilities IN-VMndash No lifecycle management (only shutdown)

bull Domainndash Multi-JVM multi-server modelndash Management coordinated by Domain Controller Processndash Multiple server instances (JVMs) per Hostndash Full lifecycle managed by Process Controller

20

Domain topology

21

Management Choices

bull Basically do you want to take advantage of our multi-server management featuresndashYes run in Domain ModendashNo run in Standalone Mode

bull Either way you still get simplified configuration and a robust management API

22

Grow with your needs

ldquoStart small grow bigrdquo

bull Engineering requirements changendashProject requirementsndashDevelopment teams amp sizendashSystem Capacity

bull AS 7 can stayndashWeb Profile EE ProfilendashServer Managed DomainndashSingle Instance ClusterndashCloud

24

QampA

bull AS 7 space on jbossorgndashhttpcommunityjbossorgenjbossasdev

jboss_as7_developmentbull Mail list

ndashjboss-as7-devlistsjbossorgbull IRC

ndashjboss-as7 on freenodebull JIRA

ndashhttpsissuesjbossorgbrowseAS71

25

Page 18: One daytalk hbraun_oct2011

18

Operational Modes

Two Operational Modesbull Standalone

ndash Traditional JBoss single JVM serverndash Management facilities IN-VMndash No lifecycle management (only shutdown)

bull Domainndash Multi-JVM multi-server modelndash Management coordinated by Domain Controller Processndash Multiple server instances (JVMs) per Hostndash Full lifecycle managed by Process Controller

20

Domain topology

21

Management Choices

bull Basically do you want to take advantage of our multi-server management featuresndashYes run in Domain ModendashNo run in Standalone Mode

bull Either way you still get simplified configuration and a robust management API

22

Grow with your needs

ldquoStart small grow bigrdquo

bull Engineering requirements changendashProject requirementsndashDevelopment teams amp sizendashSystem Capacity

bull AS 7 can stayndashWeb Profile EE ProfilendashServer Managed DomainndashSingle Instance ClusterndashCloud

24

QampA

bull AS 7 space on jbossorgndashhttpcommunityjbossorgenjbossasdev

jboss_as7_developmentbull Mail list

ndashjboss-as7-devlistsjbossorgbull IRC

ndashjboss-as7 on freenodebull JIRA

ndashhttpsissuesjbossorgbrowseAS71

25

Page 19: One daytalk hbraun_oct2011

Operational Modes

Two Operational Modesbull Standalone

ndash Traditional JBoss single JVM serverndash Management facilities IN-VMndash No lifecycle management (only shutdown)

bull Domainndash Multi-JVM multi-server modelndash Management coordinated by Domain Controller Processndash Multiple server instances (JVMs) per Hostndash Full lifecycle managed by Process Controller

20

Domain topology

21

Management Choices

bull Basically do you want to take advantage of our multi-server management featuresndashYes run in Domain ModendashNo run in Standalone Mode

bull Either way you still get simplified configuration and a robust management API

22

Grow with your needs

ldquoStart small grow bigrdquo

bull Engineering requirements changendashProject requirementsndashDevelopment teams amp sizendashSystem Capacity

bull AS 7 can stayndashWeb Profile EE ProfilendashServer Managed DomainndashSingle Instance ClusterndashCloud

24

QampA

bull AS 7 space on jbossorgndashhttpcommunityjbossorgenjbossasdev

jboss_as7_developmentbull Mail list

ndashjboss-as7-devlistsjbossorgbull IRC

ndashjboss-as7 on freenodebull JIRA

ndashhttpsissuesjbossorgbrowseAS71

25

Page 20: One daytalk hbraun_oct2011

Two Operational Modesbull Standalone

ndash Traditional JBoss single JVM serverndash Management facilities IN-VMndash No lifecycle management (only shutdown)

bull Domainndash Multi-JVM multi-server modelndash Management coordinated by Domain Controller Processndash Multiple server instances (JVMs) per Hostndash Full lifecycle managed by Process Controller

20

Domain topology

21

Management Choices

bull Basically do you want to take advantage of our multi-server management featuresndashYes run in Domain ModendashNo run in Standalone Mode

bull Either way you still get simplified configuration and a robust management API

22

Grow with your needs

ldquoStart small grow bigrdquo

bull Engineering requirements changendashProject requirementsndashDevelopment teams amp sizendashSystem Capacity

bull AS 7 can stayndashWeb Profile EE ProfilendashServer Managed DomainndashSingle Instance ClusterndashCloud

24

QampA

bull AS 7 space on jbossorgndashhttpcommunityjbossorgenjbossasdev

jboss_as7_developmentbull Mail list

ndashjboss-as7-devlistsjbossorgbull IRC

ndashjboss-as7 on freenodebull JIRA

ndashhttpsissuesjbossorgbrowseAS71

25

Page 21: One daytalk hbraun_oct2011

Domain topology

21

Management Choices

bull Basically do you want to take advantage of our multi-server management featuresndashYes run in Domain ModendashNo run in Standalone Mode

bull Either way you still get simplified configuration and a robust management API

22

Grow with your needs

ldquoStart small grow bigrdquo

bull Engineering requirements changendashProject requirementsndashDevelopment teams amp sizendashSystem Capacity

bull AS 7 can stayndashWeb Profile EE ProfilendashServer Managed DomainndashSingle Instance ClusterndashCloud

24

QampA

bull AS 7 space on jbossorgndashhttpcommunityjbossorgenjbossasdev

jboss_as7_developmentbull Mail list

ndashjboss-as7-devlistsjbossorgbull IRC

ndashjboss-as7 on freenodebull JIRA

ndashhttpsissuesjbossorgbrowseAS71

25

Page 22: One daytalk hbraun_oct2011

Management Choices

bull Basically do you want to take advantage of our multi-server management featuresndashYes run in Domain ModendashNo run in Standalone Mode

bull Either way you still get simplified configuration and a robust management API

22

Grow with your needs

ldquoStart small grow bigrdquo

bull Engineering requirements changendashProject requirementsndashDevelopment teams amp sizendashSystem Capacity

bull AS 7 can stayndashWeb Profile EE ProfilendashServer Managed DomainndashSingle Instance ClusterndashCloud

24

QampA

bull AS 7 space on jbossorgndashhttpcommunityjbossorgenjbossasdev

jboss_as7_developmentbull Mail list

ndashjboss-as7-devlistsjbossorgbull IRC

ndashjboss-as7 on freenodebull JIRA

ndashhttpsissuesjbossorgbrowseAS71

25

Page 23: One daytalk hbraun_oct2011

Grow with your needs

ldquoStart small grow bigrdquo

bull Engineering requirements changendashProject requirementsndashDevelopment teams amp sizendashSystem Capacity

bull AS 7 can stayndashWeb Profile EE ProfilendashServer Managed DomainndashSingle Instance ClusterndashCloud

24

QampA

bull AS 7 space on jbossorgndashhttpcommunityjbossorgenjbossasdev

jboss_as7_developmentbull Mail list

ndashjboss-as7-devlistsjbossorgbull IRC

ndashjboss-as7 on freenodebull JIRA

ndashhttpsissuesjbossorgbrowseAS71

25

Page 24: One daytalk hbraun_oct2011

ldquoStart small grow bigrdquo

bull Engineering requirements changendashProject requirementsndashDevelopment teams amp sizendashSystem Capacity

bull AS 7 can stayndashWeb Profile EE ProfilendashServer Managed DomainndashSingle Instance ClusterndashCloud

24

QampA

bull AS 7 space on jbossorgndashhttpcommunityjbossorgenjbossasdev

jboss_as7_developmentbull Mail list

ndashjboss-as7-devlistsjbossorgbull IRC

ndashjboss-as7 on freenodebull JIRA

ndashhttpsissuesjbossorgbrowseAS71

25

Page 25: One daytalk hbraun_oct2011

QampA

bull AS 7 space on jbossorgndashhttpcommunityjbossorgenjbossasdev

jboss_as7_developmentbull Mail list

ndashjboss-as7-devlistsjbossorgbull IRC

ndashjboss-as7 on freenodebull JIRA

ndashhttpsissuesjbossorgbrowseAS71

25