Extreme Portal

As we all know that whenever you put a portlet on a page that doesn't require authentication, portal don't create any session for this.
The administrator can change this setting with the public.session parameter in NavigatorService.properties.

Read here for more info

When you installed WebSphere Portal 6.1 in the Admin Installation mode, new virtual portals only contain a home page, but are missing the Administration section.
you can customize the XML Access Script that is used for creating or re-initializing virtual portals.

You can find an excellent article here, Read Here

Hi all,
with this article, you can upgrade from any version to desired version of IBM Portal and WAS...
here we start...

The starting point
Checking WAS version: - WebSphere Application Server's Administration Console, WAS reported that it was version 6.0.2.9.
Checking Portal version: - <portal-root>*/wps.properties it reported WPS to be at version 6.0.0.

Important NOTE:

When I write  <portal-root>, I mean the root WebSphere Portal installation directory. In my system that would be C:\program files\IBM\WebSphere\Portal\.

When I write <was-root>,  I mean the root WebSphere Application Server installation directory. In my system that would be C:\program files\IBM\WebSphere\Appserver\.

Take a backup of your WAS and Portal folder before going to next step. Just for a safer side.

For Linux, you will have to download the appropriate fix pack for WAS and Portal. The procedure will be same only the command will change as per the Operating System.

Overview of what needs doing

First we will upgrade WAS to version 6.0.2.17.
Then we will upgrade WPS to version 6.0.1

Information and download resources

Here are the sites that held both the downloads and the information that made it possible to upgrade my installation:

-->  6.0.2.17: WebSphere Application Server V6.0.2 Fix Pack 17 for Windows platforms
--> Readme for IBM WebSphere Application Server V6.0.2.17
--> 6.0.1: WebSphere Portal version 6.0 refresh pack 1.

What you need to download

First WAS-upgrade:
We will start out here:
6.0.2.17: WebSphere Application Server V6.0.2 Fix Pack 17 for Windows platforms

(the same way you can also find for Linux platform)
Of course, you will need to read it all; your server and environment might not be like mine.

Scroll down to the table below the text that says "Download package". Here you need to download the file that's described with this text: "32-bit x86 AMD/Intel AppServer".
The file name is 6.0.2-WS-WAS-WinX32-FP00000017.zip

Secondly moving on to WPS:
Go here to download the needed WPS file:
6.0.1: WebSphere Portal version 6.0 refresh pack 1.

What you need is a file named 6.0.1-WP-Multi-RP001.zip.

You also will need the PortalUpdateInstaller for V6: WebSphere Portal Update Installer.

You need the one for version 6. Scroll down till you find the text "PortalUpdateInstaller for V6"; that's the one. File name is PortalUpdateInstaller.zip.

WAS upgrade Starts here:-

The upgrade ran for about 10-15 minutes.

. Make sure that WAS is not running.

. Unzip 6.0.2-WS-WAS-WinX32-FP00000017.zip to . This will overwrite some files in <was-root>/updateinstaller.

. Open a command Prompt and switch directory to  <was-root>/bin

. Run: setupcmdline.bat

. Switch directory to /updateinstaller

. Run this command: update -silent

Leave the Command Prompt open as it is. You may feel that command has completed but it won. Please read the next 5 lines.

Now we will need to wait till the upgrade is done.
Have a look at  <was-root>/logs/update/tmp. While the upgrade is running, there will be temporary log files here.
When the upgrade has completed successfully, there will be a log at
<was-root>//logs/update/6.0.2-WS-WAS-WinX32-FP00000017.install

In order to check if you upgraded successfully, you can start WAS, log on to the Administrative console. On the first page you will see what version WAS is running at. Here's what mine is reporting:

Leave WAS running. We will be needing it shortly.

WPS upgrade Starts here:-

The upgrade process ran for about 1 and half hour.

. Open <portal-root>/config/wpconfig.properties for editing.

. Find the password entries for waspassword= and portaladminpwd= and insert the current passwords for both.

. Save it.

. Create a new subdirectory called updateinstaller inside <portal-root>.

. Now unzip the WebSphere Portal Update Installer (PortalUpdateInstaller.zip) into the <portal-root>/ updateinstaller directory.

. Inside the <portal-root>/updateinstaller directory create a new subdirectory called fixpacks.

. Unzip the refresh pack (6.0.1-WP-Multi-RP001.zip) in
<portal-root>/updateinstaller/fixpacks.
You will now have a .jar file there called WP_PTF_601.jar.

. Find the Profiles directory. On my system that is
C:\ibm\WebSphere\profiles\wp_profile\properties. Note that this is a directory different from where WebSphere and WebSphere Portal are installed.

. Edit the file called soap.client.props.
Find com.ibm.SOAP.requestTimeout= and make sure that the property is set to 6000.

. Save it.

. Open a browser to the WAS Administrative Console.
1. Click Servers > Application Servers > WebSphere_Portal > Web container settings > Web container transport chains.
2. Increase the timeout values for each entry listed in the web container transport chains section. Click HTTP Inbound Channel and make the following changes:
* Read timeout value to 180
* Write timeout value to 180
3. Save your changes. 

. Now stop WAS. 

. Open a command Prompt and switch directory to <portal-root>/bin
Run: setupcmdline.bat
in the same Command Prompt window switch to <portal-root>/updateinstaller
Run the command updateportalwizard 

. A graphical updateinstaller launches. select the obvious defaults. Basically its just the defaults all the way