one daytalk hbraun_oct2011
TRANSCRIPT
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
QampA
bull AS 7 space on jbossorgndashhttpcommunityjbossorgenjbossasdev
jboss_as7_developmentbull Mail list
ndashjboss-as7-devlistsjbossorgbull IRC
ndashjboss-as7 on freenodebull JIRA
ndashhttpsissuesjbossorgbrowseAS71
25