New JBoss Application Servers are comes with a new name known as wildfly. The first version of wildfly release is wildfly 8. In wildfly the module arrangement has a little bit change as compared with jboss as 7. Below image shows the module arrangement in wildfly server.
Below shows its the corresponding folder structure of the above
The system root level is used to separate modules associated with the distribution base from add-ons and other modules that you can add to customize your distribution. Because of the new module file system, the older JBoss Tools plugin will not be able to configure WildFly as Server. For this purpose we suggest the following environemt:
- JBoss Tools 4.1.1
- Eclipse Kepler 4.3.1
Wildfly architecture
Take a look through the following diagram which shows the technologies(with version) fitted in wildfly server
Wildfly Operation Modes
WildFly has two modes of operation: Standalone and Domain. In Standalone mode, a single instance of WildFly server is started. WildFly Domain mode allows you to control and configure multiple instances.Standalone WildFly instance can be started as:./bin/standalone.sh or standalone.bat. It displays a message like:
Key Features of Wildfly
Lets see what are the key features of WildFly 8:
- Java EE 7 support – At this point all user facing APIs have been implemented, more on this in a subsequent blog.
- Fast Startup - Server started in about 5 seconds.
- Small Footprint by minimizing GC pauses and starting/stopping service on demand.
- Modular Design by loading classes on demand using JBoss Modules. OSGi 4.2 support is available out-of-the-box.
- Unified Configuration and Management available from polished user-friendly web console, Java and HTTP APIs, and CLI. Only three ports are exposed in beta 1 (8080 for applications and 9990 for management, and the third port 9999 will be deprecated) by multiplexing protocols.
No comments:
Post a Comment