Firebug - Improve your website performance

To improve the performance of our website we can use Firebug. It is Mozilla plugin which clearly says what is broken, what can be fixed to improve our website performance. It is pretty cool feature enabled for analyzing our website. It clearly says what elements in the page can be cached, broken links, hints to improve the performance by analyzing our website.


Try this tool you will like it :)


Steps to use it is available in google code base.
http://code.google.com/speed/page-speed/docs/using.html#Running

Solution for unique values for the 'webAppRootKey'

Exception while server startup - Choose unique values for the 'webAppRootKey' context-param in your web.xml files

Solution:

This exception is used to be raised when multiple application is  installed in the server. It is better practice to include  webAppRootKey parameter in your web.xml to uniquely identify the application.

Example:

 < context-param >

< param-name >webAppRootKey< /param-name >

< param-value > Unique ID < /param-value >

< / context-param >

RichFaces - Freeze the Datatable Header - ExtendedDataTable

RichFaces is a component library for easily integrating AJAX capabilities into business applications. Richfaces 3.3.1 release has provided a feature to freeze the datatable header. This feature enable user to see the header constantly while scrolling the navigation bar. This feature is feature is provided in the component called rich:extendedDataTable. By using extendedDataTable we can also able to sort and filter the data. 




Please refer official website for its demo - Live Demo Richfaces

WAS 7.0 - Workspace Migration Tool

Websphere Application Server 7.0 - Workspace Migration Tool

To migrate the workspace from existing WAS version to next version please use the Websphere workspace migration tool for initial steps. Migration tool will update some of the essential changes in classpath file.

For initial migration please follow the below steps:

1. Install WAS 7.0
2. Setup the datasource and JMS queue using admin console
3. Import the project from source control.
4. Websphere automatically launch workspace migration tool
5. Select the project and follow the steps. This leads to automatic update of .classpath to suits the WAS 7.0 configuration.
6. After this process upgrade the required jar files like Spring 2.5.4, JSF 1.2, Richfaces 3.3.1

WAS Migration from 6.1 to 7.0 - Steps

Websphere Application Server Migration from 6.1 to 7.0

I faced lot of issues while migrating our application from Application Server 6.1 to websphere Application Server 7.0. Our Application is build on Spring 2.5.4, JSF 1.1, Richfaces, JPA. I was finally able to fix the issues and make the application up and running in WAS 7.0.

Basically we need to do is Jar file need to be used appropriately to migrate from 6.1 to 7.0.
WAS 7.0 support JSF 1.2 in default. So if you are pointing to 1.1 jar please remove it.

Following are core steps taken to migrate
1. Use Websphere 7.0 runtime server configuration and JRE.

2. Use ojdbc6.jar instead of ojdbc14.jar

3. Remove JSF 1.2 from lib and use the default JSF 1.2 from WAS 7.0

4. Upgrade Fecelets for JSF 1.2 (facelets-1.1.15-jsf1.2)

5. Upgrade Richfaces to

        > richfaces-ui-3.3.1.GA.jar

        > richfaces-impl-3.3.1.GA.jar

        > richfaces-api-3.3.1.GA.jar
6. Add all the spring 2.5.6 dependent jars in your workspace including jar files  given in step 7

7. Add following Jar files

        > spring-agent.jar

        > spring-aspects.jar

If you are coming across below exception please follow above steps to resolve it. Basically issue is in jar file conflict in your working environment. Once dependency jars are fixed you are good go.


org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.context.annotation.internalPersistenceAnnotationProcessor': Initialization of bean failed; nested exception is java.lang.NullPointerException

WAS - Datasource connection failed

Solution For - Websphere Application Server - Datasource test connection operation failed
The test connection operation failed for data source opstar on server server1 at node LHX00CND84324PVNode02 with the following exception: java.sql.SQLException: invalid arguments in callDSRA0010E: SQL State = null, Error Code = 17,433. View JVM logs for further details.

Solution::
1. Go to websphere admin console
2. Under Security >> Secure administration, applications, and infrastructure >> JAAS >> J2C authentication data
3. Click New
4. Enter alias name
5. Enter Data base user id and password for connecting to database.
6. Click OK.

WAS - Thin drive ClassNotFoundException

Websphere Application Server  - Thin drive ClassNotFoundException - Solution

The test connection operation failed for data source opstar on server server1 at node LHX00CND84324PVNode02 with the following exception: java.lang.ClassNotFoundException: DSRA8000E: No jar or zip files found in /ojdbc14.jar

    Solution: While creating the JDBC Provider give complete class path for the thin drive (ojdbc14.jar) jar file explicitly.

Note that for WAS 6.1 we need to use ojdbc14.jar where as for WAS 7.0 we need to use ojdbc6.jar