Upgrade WebSphere Portal Version 6.1 to 6.1.5?

WebSphere Portal Version 6.1 provides a complete portal solution that enables organizations to quickly implement new business designs that are engaging, flexible and high performance. WebSphere Portal Version 6.1.5 builds upon the solid foundation of WebSphere Portal Version 6.1 with new features that further improve the portal user experience.

Upgrade benefits

• Deliver exceptional Web experiences - Take advantage of new, nimble Web 2.0 technologies and philosophies that put new business models in reach.

• Extend your business assets - Create and deploy custom-branded, market-driven solutions comprised of existing and net-new business assets, and re-purpose and reuse as appropriate.

• Grow as you go - "Snap on" business-specific capabilities that speed time to value and allow you to pursue new market opportunities – all while reducing the of cost of deploying portals.

• Run your business efficiently - Built on WebSphere software so that enterprise-class applications, processes and transactions can reside on a proven, reliable, scalable and high-performance foundation.

Click here to View more...

IBM WebSphere Portal 6.1.5

Upgrades and migrations

Version 6.1 and 6.1.5 of WebSphere Portal include a number of features to help you make the most of your portal investment.

Valuable features in Version 6.1

Flexible access

• To existing enterprise data and applications

• To external news feeds or Web data

Live text tagging

• Allows access to relevant supporting information with a single click, without leaving the page you are viewing

Portal Representation State Transfer (REST) services

• Allows incorporation of composite mashup applications, including service feeds from other Web applications

A site wizard

• Allows you to create and deploy independent virtual portals

A one-click site management application

• Featuring rollback and versioning capabilities to simplify moving portals from staging to production

Expanded site layout support

• Enables you to incorporate existing static HTML, built with familiar HTML and PHP development tools

• Opens up the portal to additional content sources

Support for the latest portlet open standards

• Java™ Specification Request (JSR) 286

• Web Services for Remote Portlets (WSRP) 2.0

A Web application integrator

• Enables you to easily embed existing Web applications into your portals

Enhanced usability features

• Drag-and-drop customizations

• Semantic tags that enable smart mark-ups and dynamic menus

New portlet development and deployment capabilities

• Templates

• A Theme Customizer portlet

• WebSphere Portlet Factory software

New features in Version 6.1.5

Page Builder

• Simplifies page creation, making it easy for business users to create pages and add content to pages

Portal "Lite" Mode

• Helps improve cost-of-ownership by dramatically reducing portal start-up time

Integrated Site Analytics support

• Helps to optimize portal applications via integration with popular 3rd party solutions

WebDAV support

• Expands development ease-of-use by enabling direct editing of portal pages using tools such as Dreamweaver®

Template Page capability

• Speeds page creation by allowing portal pages to act as templates when creating other new portal pages

Mashup Integration support

• Provides rendering/creation of Mashups directly in portal as a portal page

Click here to View more...

Session management in servlets

Procedure

1. Get the HttpSession object.

   To obtain a session, use the getSession() method of the javax.servlet.http.HttpServletRequest object in the Java Servlet 2.3 API.

   When you first obtain the HttpSession object, the Session Management facility uses one of three ways to establish tracking of the session: cookies, URL rewriting, or Secure Sockets Layer (SSL) information.

   Assume the Session Management facility uses cookies. In such a case, the Session Management facility creates a unique session ID and typically sends it back to the browser as a cookie. Each subsequent request from this user (at the same browser) passes the cookie containing the session ID, and the Session Management facility uses this ID to find the user's existing HttpSession object.

   In Step 1 of the code sample, the Boolean(create) is set to true so that the HttpSession object is created if it does not already exist. (With the Servlet 2.3 API, the javax.servlet.http.HttpServletRequest.getSession() method with no boolean defaults to true and creates a session if one does not already exist for this user.)

2. Store and retrieve user-defined data in the session.

   After a session is established, you can add and retrieve user-defined data to the session. The HttpSession object has methods similar to those in java.util.Dictionary for adding, retrieving, and removing arbitrary Java objects.

   In Step 2 of the code sample, the servlet reads an integer object from the HttpSession, increments it, and writes it back. You can use any name to identify values in the HttpSession object. The code sample uses the name sessiontest.counter.

   Because the HttpSession object is shared among servlets that the user might access, consider adopting a site-wide naming convention to avoid conflicts.

3. (Optional) Output an HTML response page containing data from the HttpSession object.
4. Provide feedback to the user that an action has taken place during the session. You may want to pass HTML code to the client browser indicating that an action has occurred. For example, in step 3 of the code sample, the servlet generates a Web page that is returned to the user and displays the value of the sessiontest.counter each time the user visits that Web page during the session.
5. (Optional) Notify Listeners. Objects stored in a session that implement the javax.servlet.http.HttpSessionBindingListener interface are notified when the session is preparing to end and become invalidated. This notice enables you to perform post-session processing, including permanently saving the data changes made during the session to a database.
6. End the session. You can end a session:
   • Automatically with the Session Management facility if a session is inactive for a specified time. The administrators provide a way to specify the amount of time after which to invalidate a session.
   • By coding the servlet to call the invalidate() method on the session object.

import java.io.*;
import java.util.*;
import javax.servlet.*;
import javax.servlet.http.*;


public class SessionSample extends HttpServlet {
public void doGet (HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException {


// Step 1: Get the Session object

boolean create = true;
HttpSession session = request.getSession(create);

// Step 2: Get the session data value


Integer ival = (Integer)
session.getAttribute ("sessiontest.counter");
if (ival == null) ival = new Integer (1);
else ival = new Integer (ival.intValue () + 1);
session.setAttribute ("sessiontest.counter", ival);

// Step 3: Output the page

response.setContentType("text/html");
PrintWriter out = response.getWriter();
out.println("<html>");
out.println("<head><title>Session Tracking Test</title></head>");
out.println("<body>");
out.println("<h1>Session Tracking Test</h1>");
out.println ("You have hit this page " + ival + " times" + "<br>");
out.println ("Your " + request.getHeader("Cookie"));
out.println("</body></html>");
}
}


Click here to View more...

Sachin - The God

After completing 17,000 runs in the 50-over format of the game, Sachin Tendulkar scored his 45th ODI century off just 81 balls during the fifth One-Day International against Australia in Rajiv Gandhi Stadium, Hyderabad.

Earlier, Tendulkar finally touched the magical 17,000-run mark in One-Day International cricket, when he completed the formality of scoring seven runs needed to reach another milestone in his glittering career.

Sanath Jayasuriya is second on the list with 13,377 runs while Aussie captain Ricky Ponting has a lot of catching up to do.

The moment Tendulkar attained that mark the packed vociferous Rajiv Gandhi Stadium crowd jumped out of their seats and erupted in jubilation.

Tendulkar's wait to reach the 17,000-run mark in One-dayers continued in Mohali as he missed the milestone by just seven runs after getting dismissed for 40 on a dubious decision in the fourth ODI against Australia.

The 36-year-old scored the requisite seven runs to put another feather in his cap, which is already full of feathers but still managing to have some more. The Indian batting legend has 45 One-day hundreds and 91 ODI fifties under his belt.

The diminutive Mumbaikar, who made his ODI debut Pakistan in 1989, is already way ahead of his contemporaries when it comes to accumulating runs.

Rated as the world's best batsman after Australian legend Sir Donald Bradman, Tendulkar has an awe-inspiring Test record. In the whopping 159 matches that he has played thus far, Tendulkar has scored 12,773 runs at an average of 54.58.

The veteran batsman has scored 42 hundreds and 53 half centuries in the longer format of the game.

One-day cricket's leading run-scorers

Sachin Tendulkar (IND) 17,000
Sanath Jayasuriya (SRI) 13,377
Ricky Ponting (AUS) 12,286
Inzamam-ul Haq (PAK) 11,739
Sourav Ganguly (IND) 11,363
Rahul Dravid (IND) 10,765
Brian Lara (WIS) 10,405
Jacques Kallis (RSA) 10,328

The break-up of Tendulkar's run tally against various opponents:

2995 runs in 66 matches vs Australia
1335 runs in 36 matches vs England
1750 runs in 42 matches vs New Zealand
2389 runs in 67 matches vs Pakistan
1655 runs in 52 matches vs South Africa
2749 runs in 74 matches vs Sri Lanka
1571 runs in 38 matches vs West Indies
1377 runs in 34 matches vs Zimbabwe
354 runs in 10 matches vs Bangladesh
57 runs in 1 match vs Bermuda
4 runs in 1 match vs Ireland
647 runs in 10 matches vs Kenya
152 runs in 1 match vs Namibia
52 runs in 1 match vs Netherlands
81 runs in 2 matches vs UAE.


Click here to View more...