Step-by-step Migration Guide for IBM WebSphere Portal version 8 from 61x

Whether you are migrating an IBM® WebSphere® Portal or Workplace Web Content Management™ 6.1.x server to version 8, these guides are designed to aid you through the process.

Content

The paper describes the steps and best practices for migrating an existing standalone WebSphere Portal 6.1.x environment to a standalone WebSphere Portal V8 and should be followed by the majority of customers, even those in a Web Content Management environment.

The foundation for this document is the initial release of the V8 Information Center with additional information based on the outcome and experiences of our pre-release testing. With this document, we provide a more comprehensive guide and highlight some of the common pitfalls and mistakes when migrating.

*Special note - if you are using this guide on an operating system that is different than the example documented, some allowances must be made to convert commands and screens shown to your environment. This might include changing executable script commands from batch files (.bat) to shell scripts (.sh) or vice versa, or when using command-line utilities in place of graphical interfaces that might be shown.

Download the white paper now via http://www-01.ibm.com/support/docview.wss?uid=swg27036349

Portal v7002 fixpack installation fails with "Target `check-portal-level-CF' does not exist in this project

When installing the Portal v7002 fixpack on a binary Portal installation after installing any cumulative fix, the 7002 fixpack installation may fail with "Target `check-portal-level-CF' does not exist in this
project"

Symptom

In the console output at the time of the failure, you see the following exception:
=============================
Result: StdErr: BUILD FAILED
Result: StdErr: Target `check-portal-level-CF' does not exist in this project. It is used from target `action-validate-portal-version-for-multProfile-CF'.
Result: StdErr:
Result: StdErr: Total time: 4 seconds
Log: ExecCmd::launch returns 1
Task 2 out of 630; End Uninstalling fix ' PM49013', component 'wp.ptf.config'.
Task 3 out of 630; Begin Completing fix ' PM49013' subTmpDir to be cleaned up: /tmp/ptfs
The directory does not exist, or is not a directory, continue to run: /tmp/ptfs
Fix pack installation has failed. Consult
/usr/WebSphere7/PortalServer/version/log/20120217_085936_PM49013_uninsta
ll.log for error details.
chmod -R 550 /usr/WebSphere7/PortalServer done!
UpdateInstaller.puiReturnCode is 9
End of [ ./updatePortal.sh ]
=============================

A similar error can be seen in the ConfigTrace.log as well.

Cause

This issue occurs when the user has done the following:

- Installed Portal as a binary installation

- Upgraded Portal to v7001 + any CF

- Created a profile (or migrated)

- Updated the wps.properties with the new profile information

- Attempted to upgrade to v7002

The first step for any fixpack installation is to remove all fixes and cumulative fixes. The CF uninstall fails in this case and that is why the fixpack fails.

The CF uninstall fails because of a defect in the Portal Update Installer that prevents any fix or CF from uninstalling cleanly when it was originally installed on a binary install. This will be fixed in a later version of the Portal Update Installer.

Resolving the problem

If you encounter this exception, you must take the following steps to resolve it:

1. Edit the PortalServer/wps.properties file
2. Remove the ProfileName and ProfilePath parameters from it.
3. Manually uninstall the cumulative fix(es) you have applied
4. If the following file still exists after the CF uninstall, manually remove it:

PortalServer/installer/wp.config/config/includes/preconfig_cumulative_fix.xml

5. Edit the PortalServer/wps.properties file again and add ProfileName and ProfilePath back to the file.
6. Reattempt the 7002 fixpack installation.

Source :  http://www-01.ibm.com/support/docview.wss?uid=swg21585265