Hi, I have the Portal 5.0.2 and WAS 5.0.2 with required Fixes applied. But w
hen I try and install Websphere Portal 5.0 Test Environment from the Portal 
Toolkit, it tells me that I need
- PQ76567, PQ78166, PQ81248 , WAS_CM.....
This is kinda crazy since I have installed all of these with WAS 5.0.2 Fixes
. I reconfirmed that these were installed and then even uninstalled these fi
xes and reapplied them. But the damn thing still keep asking for the fixes. 
Has anyone experienced this
? Btw, this is a local install of WSAD 5.1.

Thanks in advance,
Jac.

[ Post a follow-up to this message ]

ok finally figured out...I had installed the interim fixes to the Actual WAS
 Server and not to the WSAD runtime Server. But that brings up the question.
..the three fixes(PQ77008, PQ78370 and WAS_Plugin) - are these not to be in
stalled on either server. O
R are tehy to be skipped only in the WSAD runtime server? Guess i will find 
out huh?

Jac.

[ Post a follow-up to this message ]

Hi,

There are so many threads about installing the Portal toolkit test
environment, that this must be a real drama. I came across these steps in
this newsgroup, maybe this'll help you:

I was lucky enough to get the following instructions from an IBM
techie. You will need a couple of fixes that can be downloaded from the
Portal Zone and CD2 of the Portal Installation.

Even though it's installed and running, I'm still suffering intermitent
problems with the portal server crashing.

=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=

System Requirements/Setup
· Processor:     800MHz Pentium III - as a minimum; 1.4 Ghz Pentium 4
or higher recommended
· Memory:        1024 MB of physical memory or more per processor
· Disk Space:   2500 MB free space plus additional space for projects
· Windows 2000 w/sp2 and security patches; update to IE5.5 sp2 or
higher
· Acrobat and some sort Zip utility

Software Needed
· WebSphere Studio Application Developer v5.1 DISK1, DISK2, DISK3
· cd1-17:  WAS fixpack2, Enterprise fixpack2, and additional fixes
· WebSphere Portal Toolkit v5.0.2 MP (PortalToolkit502MP.exe from
Portal Zone; Feb 3)
· cd2:  WebSphere Portal v5.0
· WebSphere Portal fixpack 2: cdFixpack or Fixpack2.zip (from Portal
Update; Jan 29)

Installing WebSphere Studio Application Developer v5.1
___ 1. Install WebSphere Studio Application Developer v5.1 (WSAD) using
DISK1.
__ a) Start the WSAD installation by double clicking
<DISK1>\launchpad.exe.
__ b) In 'WebSphere Studio Installation Launchpad' click Install IBM
WebSphere Studio Application Developer.
__ c) Read the Welcome dialog and click Next.
__ d) Read the License Agreement, select I accept the terms in the
license agreement, and click Next.
__ e) Change the Directory Name field to C:\WSAD_51 and click Next.
__ f) Notice the grayed-out default features, add extra runtimes or
features of interest, then click Next.
__ g) Review the installation information and if it's correct, click
Next.  Otherwise go Back.
__ h) At 71%, the 'Insert Next Disk' dialog will ask for DISK2, browse
to <DISK2> and click OK.
__ i) Read the installation summary and click Finish.
__ j) Close the LaunchPad window.

___ 2. Launch WSAD to check that the installation was successful and
add a shortcut to it on the desktop.
__ a) To create the shortcut, click Start then navigate to Programs >
IBM WebSphere Studio > Application Developer 5.1 and then right click
on the menu and select Send To > Desktop.
__ b) Double click the Application Developer 5.1 shortcut on the
desktop.
__ c) In the WebSphere Studio dialog box, enter C:\workspace and then
click OK.
__ d) Once WSAD is started, notice the Welcome view, and then click the
X to close WSAD.
__ e) In the Confirm Exit dialog, check Always exit without prompt, and
then click OK.

___ 3. Update the WAS v5.0.2 runtime environment to enable local
debugging for WPv5.0.2.
__ a) Copy <cd1-17>\fixes to the C:\fixes directory.  Create the
c:\fixes directory if necessary.
__ b) In a command prompt, navigate to C:\fixes\win and set
 JAVA_HOME=C:\WSAD_51\runtimes\base_v5\ja
va.
__ c) In the command prompt, run updateWizard.bat.
__ d) Select a Language for the wizard to use.
__ e) Read the Welcome screen and click Next.
__ f) Verify that Specify product information is checked and then
browse to C:\WSAD_51\runtimes\base_v5 and click Next.
__ g) Select Install fixes (not Install fixpacks) and then click Next.
__ h) Verify/update the Fix directory to C:\fixes\win\efixes and then
click Next.
__ i) Select all the fixes in the list except for PQ77008, PQ78370, and
WAS_Plugin. and then click Next.
__ j) Review the fixes to be installed or refreshed and then click
Next.
__ k) Check that the Update Wizard reports that the fixes installed
successfully and then click Finish.

Installing the WebSphere Portal Toolkit v5.0.2 MP
___ 1. Extract PortalToolkit502MP.exe.
__ a) Navigate to and double click PortalToolkit502MP.exe.
__ b) Enter a location for the Toolkit to be extracted to, such as
C:\PortalToolkit502MP, and click Next.
__ c) Navigate to C:\PortalToolkit502MP and verify that the files have
been extracted.

___ 2. Installing the WebSphere Portal Toolkit v5.0.2 MP.
__ a) Start the Toolkit installer by double clicking
C:\PortalToolkit502MP\Install.bat.
__ b) Select a Language for the wizard to use.
__ c) Read the Welcome screen and click Next.
__ d) Read the License Agreement, select I accept the terms in the
license agreement, and click Next.
__ e) In the list of components to install, select Portal Toolkit
V5.0.2 and click Next.
__ f) Review the install location of the Portal Toolkit and click
Next.
__ g) Once the installation has completed successfully, click Finish.
__ h) Read the Portal Toolkit Version 5.0.2 Readme file and then close
it.

___ 3. Verifying the WebSphere Portal Toolkit v5.0.2 MP installation.
__ a) Double click the Application Developer 5.1 shortcut on the
desktop.
__ b) In the WebSphere Studio dialog box, verify C:\workspace and then
click OK.
__ c) Once WSAD is started, notice the Configuration Changes dialog.
Expand the detected changes and verify the Portal Toolkit (Windows)
(5.1.0) has been detected.  Click Finish.
__ d) An Install/Update dialog appears and asks to restart WSAD to
incorporate the changes, click Yes.
__ e) After the restart, WSAD should display a Welcome to Portal
Toolkit view.
__ f) To further verify the installation, open the Portlet Perspective.
This will also open the Links view.
__ g) Close WSAD.

Installing the WebSphere Portal Test Environment v5.0.2
___ 1. Install the WebSphere Portal Test Environment v5.0.
__ a) Start the Toolkit installer by double clicking
C:\PortalToolkit502MP\Install.bat.
__ b) Select a Language for the wizard to use.
__ c) Read the Welcome screen and click Next.
__ d) Read the License Agreement, select I accept the terms in the
license agreement, and click Next.
__ e) From the component list, select WebSphere Portal V5.0 for Test
Environment and click Next.
__ f) In the WebSphere Portal V5.0 installer field, enter the location
of WebSphere Portal cd2's wpsinstaller.jar.  Such as
X:\WPv50-cds\cd2\wps\wpsinstaller.jar.
__ g) Review the install location of the WebSphere Portal V5.0 for Test
Environment and click Next.
__ h) Once the installation has completed successfully, click Finish.
__ i) Read the Portal Toolkit Version 5.0.2 Readme file and then close
it.

___ 2. Verify the WebSphere Portal Test Environment v5.0 is available.
__ a) Double click the Application Developer 5.1 shortcut on the
desktop.
__ b) In the WebSphere Studio dialog box, verify C:\workspace and then
click OK.
__ c) Once WSAD is started, notice the Configuration Changes dialog.
Expand the detected changes and verify the Server Tools for WebSphere
Portal Version 5.0 Test Environment 5.1.0 has been detected.  Click
Finish.
__ d) An Install/Update dialog appears and asks to restart WSAD to
incorporate the changes, click Yes.
__ e) After the restart, WSAD should display the basic development
environment again.
__ f) To further verify the installation, try to create a new Server
and Server Configuration.  This should load the WebSphere Portal v5.0
Test Environment and display it as an option in Server types.
__ g) Click Cancel in the create a new server and server configuration
screen and then close WSAD.

___ 3. Update the WebSphere Portal v5.0 Test Environment to v5.0.2.
__ a) Navigate to and extract Fixpack2.zip.
__ b) Enter an extract to location, such as C:\Fixpack2, and click
Extract.
__ c) Navigate to C:\Fixpack2 and verify that the files have been
extracted.
__ d) Open a command prompt and navigate to C:\WSAD_51\PortalToolkit.
__ e) Run updatePortalTestEnv502 C:\Fixpack2.  It should take ~20
minutes for the update to complete.
__ f) Check results in the command prompt for
updatePortalTestEnv502.bat Ended. (Successful).

___ 4. Verifying the WebSphere Portal v5.0.2 Test Environment upgrade.

__ a) Double click the Application Developer 5.1 shortcut on the
desktop.
__ b) In the WebSphere Studio dialog box, verify C:\workspace and then
click OK.
__ c) Once WSAD is started, notice the Configuration Changes dialog.
Expand the detected changes and
__ d) In the Portlet Perspective, right-click and select New >
Project.
__ e) In the New Project dialog select Portlet Development.  Also
expand Porlet Development to reveal the project wizard that supports
JSR 168 portlets, but make sure Portlet Development is selected.
__ f) Select Portlet Application Project in the right pane of the
dialog and click Next.
__ g) To define the Portlet Project, enter MyFirst for the Project name
and click Finish.
__ h) After the wizard finishes creating the project, right-click on
MyFirst in the Project Navigator and select Run on Server.
__ i) In the Server selection dialog, select WebSphere Portal v5.0 Test
Environment under the Create a new server area.  Check the Set server
as project default (do not prompt) and click Finish.
__ j) The project will be published to the WebSphere Portal v5.0 Test
Environment server and the server will be started.  Server startup
information can be tracked in the Console view in the bottom center
area.
__ k) After some time, a browser should display a Debug page with the
MyFirst portlet on it.  This verifies that the Test Environment in
running properly.
__ l) The server could be stopped and restarted in Debug mode after
adding break points to the MyFirst portlet code to verify the Debug
environment is working properly as well.
__ m) Close the Web Browser view and stop the WebSphere Portal v5.0
Test Environment server.
__ n) Close WSAD.

The End

"jacobkur" <jacob_poly@hotmail.com> wrote in message
news:207028169.1080104247079.JavaMail.wasadmin@swg3ws006...
> ok finally figured out...I had installed the interim fixes to the Actual
WAS Server and not to the WSAD runtime Server. But that brings up the
question....the three fixes(PQ77008, PQ78370 and WAS_Plugin) - are these not
to be installed on either server. OR are tehy to be skipped only in the WSAD
runtime server? Guess i will find out huh?
>
> Jac.

[ Post a follow-up to this message ]

Thanks Pim,

I actually located an earlier thread of yours with these instructions and pr
inted them out. They have really helped me and I appreciate that you have sh
ared them on this forum. Makes life a lot easier in an IBM world....

Thanks,
Jac.

[ Post a follow-up to this message ]

Get them from this URL:-
http://www-1.ibm.com/support/docvie...tf-8&lang=en+en
Then this:-
WebSphere Portal 5.0 Fix Pack 2
http://www-1.ibm.com/support/docvie...tf-8&lang=en+en
I managed to get this all working with a local install of wsad 5.1. But when
 I tried to move from cloudbase to DB2 I have run into a lot of problems wit
h stuff missing.
Good Luck...

[ Post a follow-up to this message ]