Most of the Web Applications, where there is a feature for file upload, there is a requirement for doing virus scan of the uploaded file. When I checked around, there were not too many options in the FOSS area. 

Antivirus scanners are available in the FOSS area but integration with the web application is still a nightmare. Check the list of antivirus software here.

I did some googling around and eventually came up with the following integration options 

  1. Command Line Option - Use a command line virus scanner,use the Runtime class to execute a scan on a file and based on the output of the program, display to the user whether or not the file is clean.  Sligthly tricky and not a very clean program but still does the job. 
  2. Using OPSWAT Meta Scan - OPSWAT MetaScan is an advanced engine for launching scan requests and obtaining scan results from many antivirus applications, as well as for analyzing file types. Metascan enables IT to develop multi-scanning solutions leveraging built-in antivirus engines from AVG, CA, ESET, Norman, VirusBuster EDK, MicroWorld, and ClamWin. Additionally, Metascan includes an easy, scalable interface to integrate with almost any antivirus engine on the market. Clean and elegant solution, but need to write a check for the same
  3. Using ModSecurity - ModSecurity is a Web Application Firewall that can be configured with the Web Server. ModSecurity has a feature to for inspecting files on upload which can be combined with an antivirus scanner software. Again not something out of the box. You end up adding another product for integration
  4. Using ICAP Servers  - ICAP is a protocol designed to off-load specific Internet-based content to dedicated servers, thereby freeing up resources and standardizing the way in which features are implemented. Check out ICAP-Server for an Open Source implementation of ICAP server. One can run GreaseSpoon on top of an ICAP server. Greasespoon can intercept the HTTP traffic and allow the application to perform the virus scan. Again a convuluted way of achieving the same. SafeSquid is a another product in the market 
Hope it helps others. Also, if someone has found another product/integration technique, please do let me know.

Amazon has released the AWS Toolkit for Eclipse, which is a plug-in for the Eclipse Java IDE that makes it easier for developers to develop, deploy, and debug Java applications using Amazon Web Services. 

Just goes on to show the commitment on Amazon's part to provide tools to help develop application on EC2.

Read more here.
There are series of new articles available that detail how to use JiBX for converting Java to XML and vice versa. Very good for anyone who is starting to work with JiBX.

Check them out here.

Since, it is possible for a single WebSphere Portal HTTP request to use multiple database connections concurrently, the ratio of the data source connection pool size to the WebContainer Thread Pool needs to be tuned.

For the WebSphere Portal databases, the recommended ratio is 2:1.

For Workplace Web Content Management (JCR) database, the recommended ratio is 2.5:1.

For example, if the WebContainer thread pool maximum is 50, then each WebSphere Portal data source connection pool maximum should be 100 and the JCR data source connection pool maximum should be 125.

Verify that your database server is able to handle all incoming client connections from all WebSphere Portal cluster member(s).

Check out the Tech Note here.

Enterprises initiate large multi-year, multi-million programs that meant to overhaul the existing applications, provide more flexibility to business managers, and provide more features to the end customers and so on. As the statistics speak, 2 out of 3 IT programs are a failure.

Now, the question is who pays for the failures of these programs?

It is the end customer. People like you and me.

The enterprises will load these failure costs as part of the operational costs and in the end, all these get charged as the cost of the service provided by the enterprise.