Table of contents

JBoss vs Weblogic vs Websphere

Enterprise architects and other IT decision makers are often faced with important decisions to make regarding the best application server / web server platform for IT. The market leaders are Websphere, Weblogic and JBoss. Here is a brief overview and comparison of each.

JBoss

JBoss is Red Hat's application server platform and comes in both open source and paid subscription versions. JBoss is the only option of the three if open source is an important consideration. The free version of JBoss called JBoss Community benefits from the open source community and has strong support in the ISV community with related technology like RichFaces. The paid license version called JBoss Enterprise supports mission critical functionality and has certified platforms. If your team is considering certain java frameworks from RedHat such as Seam, jBPM or RichFaces, JBoss should be your choice. JBoss also has strong support for Hibernate.

Weblogic

Weblogic is Oracle's application server acquired in the BEA acquisition. Weblogic has a long history very strong support for high end architecture features such as clustering and scalability. Weblogic has formed the delivered underlying application server architecture to many Oracle applications such as PeopleSoft although this is now changing with Oracle Fusion Middleware. Oracle has begun to rebrand Weblogic more of as a basis for application grids, a testament to its strong scalability and clustering functionality whereas Fusion Middleware is Oracle's plug and play architecture. Weblogic has the best integration with other Oracle products such as Fusion Middleware, Oracle database and Oracle applications.

Websphere

Websphere is IBM's application server. IBM offers a free WebSphere Application Server Community Edition along with an paid license Enterprise Edition. In many ways Websphere is a family of products ranging from SOA embedded server appliances to E-Commerce editions. IBM treats Websphere as a product platform supporting many product lines. Therefore Websphere is a nice choice if your needs fit a product line such as you are building an custom eCommerce website. Websphere also supports very high end architecture features such as clustering and high scalability.

Pricing Considerations

In general the choices above are listed in order of licensing cost from the lowest with JBoss to Websphere at the high end. To be fair, Websphere has more features than JBoss for the higher price. If your specific implementation need these additional features and you would have to build them, the higher end products are a good choice. Whereas if you just need a basic application server the lowest cost option can do the trick.

changing mac address in linux/fedora

lately i have shifted to new location so is my machine. new location new net connection but the configuration process was different. previously I used connection with static IP but this time i have got to use dynamic IP assigned by DHCP. DHCP server identifies my PC using my MAC address. Up to this point I was fine but the problem was I could not use the physical address of my NIC rather I have to use the one provided by the connection provider. So i had to change the MAC address and this was the problem as I did not know how to change the MAC address in Linux. The technician come along, advised me that i would not be able to use this connection in Linux platform. This sounded real ridiculous. After doing little googling and skimming through ref book, I found the solution. The solution is not that difficult.

use ifconfig utility:

MAC address can be changed very easily using ifconfig.Before issuing command, be root user.Then issue the following command on the terminal:

#/sbin/ifconfig eth0 down hw ether address

here it is assumed that ifconfig is in the /sbin directory.

eth0 is the name of the interface/NIC which address is to be changed.

down means the NIC is to be shutdown before changing address.

hw ether means hardware address class is ether(which indicates ethernet).

address is the address which will used as the new mac.

After the successful execution of the command. start the NIC again using the command:

#/sbin/ifconfig eth0 up

and that is all I needed.

jBoss : SSL configuration

<?xml version="1.0" encoding="UTF-8"?>

<server>
    <!-- The server socket factory mbean to be used as attribute to socket invoker -->
    <!-- which uses the JaasSecurityDomain -->
    <mbean code="org.jboss.remoting.security.domain.DomainServerSocketFactoryService"
           name="jboss.remoting:service=ServerSocketFactory,type=SecurityDomainAdvanced"
           display-name="SecurityDomain Server Socket Factory">
        <attribute name="SecurityDomain">java:/jaas/SSLAdvanced</attribute>
        <depends>jboss.security:service=JaasSecurityDomain,domain=SSLAdvanced</depends>
    </mbean>

    <mbean code="org.jboss.security.plugins.JaasSecurityDomain"
           name="jboss.security:service=JaasSecurityDomain,domain=SSLAdvanced">
        <!-- This must correlate with the java:/jaas/SSL above -->
        <constructor>
            <arg type="java.lang.String" value="SSLAdvanced"/>
        </constructor>
        <!-- The location of the keystore resource: loads from the classloaders conf/ is the first classloader -->
        <attribute name="KeyStoreURL">localhost.keystore</attribute>
        <attribute name="KeyStorePass">opensource</attribute>
    </mbean>

    <!-- The Connector is the core component of the remoting server service. -->
    <!-- It binds the remoting invoker (transport protocol, callback configuration, -->
    <!-- data marshalling, etc.) with the invocation handlers.  -->
    <mbean code="org.jboss.remoting.transport.Connector"
           name="jboss.remoting:type=Connector,transport=socket3843,handler=ejb3"
           display-name="Socket transport Connector">

        <attribute name="Configuration">
            <config>
                <invoker transport="sslsocket">
                    <attribute name="dataType" isParam="true">invocation</attribute>
                    <attribute name="marshaller" isParam="true">
                        org.jboss.invocation.unified.marshall.InvocationMarshaller
                    </attribute>
                    <attribute name="unmarshaller" isParam="true">
                        org.jboss.invocation.unified.marshall.InvocationUnMarshaller
                    </attribute>
                    <!-- The following is for setting the server socket factory.  If want ssl support -->
                    <!-- use a server socket factory that supports ssl.  The only requirement is that -->
                    <!-- the server socket factory value must be an ObjectName, meaning the -->
                    <!-- server socket factory implementation must be a MBean and also -->
                    <!-- MUST implement the org.jboss.remoting.security.ServerSocketFactoryMBean interface. -->
                    <attribute name="serverSocketFactory">
                        jboss.remoting:service=ServerSocketFactory,type=SecurityDomainAdvanced
                    </attribute>
                    <attribute name="serverBindAddress">${jboss.bind.address}</attribute>
                    <attribute name="serverBindPort">3843</attribute>
                </invoker>
                <handlers>
                    <handler subsystem="AOP">org.jboss.aspects.remoting.AOPRemotingInvocationHandler</handler>
                </handlers>
            </config>
        </attribute>
        <depends>jboss.remoting:service=ServerSocketFactory,type=SecurityDomainAdvanced</depends>

    </mbean>

</server>

Setting Up SSL on Tomcat In 3 Easy Steps

http://techtracer.com/2007/09/12/setting-up-ssl-on-tomcat-in-3-easy-steps/