After migrating IBM® WebSphere® Portal Express®, additional tasks
may be needed depending on how you customized the source portal environment
and which components you used.
Updating data after migration
After you have migrated to and successfully tested
it, update your data
with the latest version data from your source environment.
Enabling automatic synchronization
Before starting with migration, you disabled the automatic
synchronization to avoid nodes getting out of sync. Now that you have
completed migration, it is safe to enable this feature again.
Migration consideration for Tivoli Access Manager integration
The IBM WebSphere Portal Express migration
process migrates the security configurations. However, there is no
provision for the automatic migration of any junction definitions
that exist for the previous version of WebSphere Portal Express in WebSEAL. You must
replace the old junction definitions with the new virtual host junction
definitions.
Virtual Portal post migration steps
If you configured WebSphere Portal Express to use virtual portal,
there are some additional steps needed to complete the migration.
Mashup Integration Post Migration steps
Mashup Integration
feature was removed in WebSphere Portal Express Version 8.0. This
step is an optional if you actively used this feature in previous
releases and you still want to continue using it in portal Version
8.0, you need to manually enable Mashup Integration after migration.
Blogs and wikis post migration steps
After migrating from WebSphere Portal Express Version 7.0 to Version
8.0, you must run a configuration task to update the presentation
templates used by blogs and wikis to apply the correct styling. You
must run this task for content in your blogs and wikis to render properly.
Updating custom theme Dojo references
The default Dojo context root in WebSphere Portal Express is /WpsContextRoot/portal_dojo. You can find the value of WpsContextRoot in wp_profile_root/ConfigEngine/properties/wkplc.properties.
Analytics post migration steps
If you use site analytics on
your migrated WebSphere Portal Express, you need to create
the analytics tag root label.
Portlets no longer available
Some portlets that used to be available on previous releases
of WebSphere Portal Express are no longer
including in .
These portlets are not migrated as part of the WebSphere Portal Express migration process.
Setting up Tag Center page
If your target environment does
not have a Tag Center page
run the following command to create one along with all the associated
portlets.
Removing Person Tag hidden pages
Remove Person Tag hidden pages from migrated environments
where Search for Portal Site was previously configured.