AS7 Console performance improvements

I did take a look at the components that serve the console files again and removed some really sloppy parts and tweaked the HTTP cache behavior a little bit. With some really interesting results.

This is what the average page loading time looked like, when client did access the console for the first time:



This is what looks like after the improvements:



It get's even better, when a client does access the console subsequently:



How can it be explained?

Well the most notable improvement is probably the replacement of the sloppy IO parts. Hence the drastic page loading times from ~4sec to ~1sec. Furthermore the addition of an HTTP "Expires" header allows the browser to successfully cache the results, which drastically decreases the page loading size from ~750kb ~10kb. All tests have been run on a LAN connection.

Managing JBoss7: Console Beta9 released

We just updated to 1.0.0.Beta9:
===================

- suport for standalone
- i18n
- deployments
- authentication

- datasources
- jms configurations
- messaging
- web subsystem

- server groups
- server configurations

- system properties
- jvm options
- socket bindings


The given functionality has small glitches here and there but most of it has been reported and is being worked on. In terms real tasks, this is still outstanding:

- transaction subsystem
- security
- webservices
- threads
- logging

But we expect this to be ready for 7.0.CR1.

Give it try & let us know what you think.
Tell us what works and what doesn't.

How do I access the console?
==================

http://localhost:9990/console



How do I enable authentication?
====================

Simply create a security realm configuration.
This needs to be done in "domain/configuration/host.xml" for domain mode:

<management>
       <security-realms>
           <security-realm name="ManagementRealm">
               <authentication>
                   <users>
                       <user username="admin">
                           <password>
                               password
                           </password>
                       </user>
                   </users>
               </authentication>
           </security-realm>
       </security-realms>
   </management>
   <management-interfaces>
       <native-interface interface="public" port="9999"/>
       <http-interface interface="public" 
            port="9990" security-realm="ManagementRealm"/>
   </management-interfaces>

Or "standalone/configuration/standalone.xml":

<management>
       <security-realms>
           <security-realm name="ManagementRealm">
               <authentication>
                   <users>
                       <user username="admin">
                           <password>password</password>
                       </user>
                   </users>
               </authentication>
           </security-realm>
       </security-realms>
   </management>

   <management-interfaces>
      <native-interface interface="default" port="9999"/>
      <http-interface interface="default" 
              port="9990" security-realm="ManagementRealm"/>
   </management-interfaces>

How do I switch between standalone and domain administration?
========================================

Just boot AS7 in either one of these modes and reload the console web application.

WebKit Remote Debugging

Interesting, remotely connect the web inspector to a web kit instance:
http://www.webkit.org/blog/1620/webkit-remote-debugging/

Managing JBoss7: Messaging Provider Settings

This should give you an idea how the HornetQ configuration is going to look like:

Messaging Provider




Queues & Topics

Managing JBoss7: Datasource Configurations

We've begun working on datasource configurations within the web management interface. While it still requires some finishing touches, here's how regular and XA datasource configurations look like:

Managing JBoss7: Staging Applications

Your colleagues are all stressed out, because the new build of your b2b app needs to be put on a staging server for your external partner to verify the recent API changes. How to get this setup and running without interfering with the existing production system? It's fairly simple. I'll show you ...

Step1: Create a dedicated server group for your staging servers

Step2: Prepare a staging server-configuration

A custom server-group separates our staging environment from the production servers.

... with a specific port offset

You need to remember this, in order to connect to the server instances later on.

Launch a server instance

So we can connect to it.

Deploy your application

In this case a simple web application.

... to the staging server-group

Domain deployments are always associated with server-groups.

Verify it has been deployed successfully

Grab a coffee and relax

Fairly simple, no?

Managing JBoss 7: UX updates

The current JBoss 7 development stream contains an updated version of the console that will be shipped with Beta3. We've removed the clutter on the left hand side and do now provide a cleaner separation between navigation and functional elements. The LHS is now only used for navigational purposes and the any functional element (i.e. add, delete resources) has been moved to the toolstrips on the right hand side. Along with this change we've turned the stacked navigation sections (used to display only one at a time) into a more tree like structure, that shows all available options at one glance.

In our opinion this make it much easier to find relevant management options within the UI. Let us know what you think. Screenshots attached.

Server Configuration



Data Source Management