Migration is supported between equivalent
offerings. For example, you can migrate
from WebSphere
Portal Enable Version 7.0 to WebSphere Portal Enable , but not from WebSphere
Portal Express Version 7.0 to WebSphere Portal Extend .
- Prerequisites
WebSphere Portal detailed system requirements
The following table summarizes supported
migration paths:
Table 1. Offerings and supported migration paths | Offering |
WebSphere Portal Express |
WebSphere Portal (Enable, Extend) |
Web Content Manager |
| WebSphere Portal Express
Version 6.1.x on WebSphere® Application
Server Version 6.1 |
Supported |
Not Supported |
Not Supported |
| WebSphere Portal Server V6.1.x (Enable,
Extend)
on WebSphere Application
Server Version
6.1 |
Not Supported |
Supported |
Not Supported |
| Web Content Manager V6.1 on WebSphere Application
Server Version 6.1 |
Not Supported |
Not
Supported |
Supported |
| WebSphere Portal Server V6.1.x (Enable, Extend)
on WebSphere Application
Server Version
7.0 |
Not Supported |
Supported |
Not Supported |
| Web Content Manager V6.1 on WebSphere Application
Server Version 7.0 |
Not Supported |
Not
Supported |
Supported |
| WebSphere Portal Express® Version
7.x |
Supported |
Not Supported |
Not Supported |
| WebSphere Portal Server Version
7.x |
Not Supported |
Supported |
Not Supported |
| Web Content Manager Version 7.x |
Not Supported |
Not
Supported |
Supported |
You may also migrate from a Server install to the
Enable or
Extend versions of
IBM® WebSphere Portal Express.
Important: Migration is supported only from the
two latest
fix pack levels for any listed offering. For example, if you are using WebSphere Portal Express Version 6.1.0.1, and
the two latest available fix packs are 6.1.0.4 and 6.1.0.5, you must
apply one of those fix packs before you can migrate to WebSphere Portal Express .
If you
are not sure which earlier version is installed, run the
following command on the earlier portal server:
When you migrate to
,
WebSphere Portal Express automatically
migrates the following applications and configuration data so that
the new portal looks and behaves the same way as the earlier portal:
- Security configuration
- Access control
- Portal behavior
- Portlet applications
- Customized portal resources, such
as themes and skins, pages,
and portlets
- Personalized content
- Virtual portals
Note: You cannot upgrade the source portal with a fixpack
after migration
if you intend to re-migrate the JCR. For example, if your source
portal is running Version 6.1.0.4 and you migrate the portal to , you cannot then
upgrade the source portal to Version 6.1.0.5 and migrate the JCR again.
This is not supported.