Where Do You Start: Planning And Considerations - IBM BS029ML - WebSphere Portal Server Self Help Manual

Access control
User customization
Virtual portals
Markups
Global settings
Portal resources
Workplace Web Content Manager content and components
Document Manager content
Personalization rules
Credential vault slots
Note: For the rest of this section regarding migration, when referring to the WebSphere
Portal Server V5.0 or V5.1 that you are migrating from, the document will refer to this
server as your source server. When the document refers to your newly installed
WebSphere Portal Server V6.0, it will refer to it as the target server.
The migration process first collects the files it needs from the source WebSphere Portal
Server by using the Property Collector. Depending on what types of applications you have on
your source system, there may be a few files that will need to be moved manually. After the
Property Collector has been run, the next task is the export of the source server. This will
create a xmlaccess file containing the information related to the source configuration. At this
point in the migration, all the information from the source WebSphere Portal Server has been
collected and the rest of the migration focuses on the target server.
The WebSphere Portal Server migration code will then perform a series of filters and
translations to the XML file created based on the source servers configuration to create an
XML file that will then be used to create a layout of the target server. An example of
WebSphere Portal Server artifacts that will be filtered out from the source server are the old
WebSphere Portal Server administration portlets.
The last part of the core migration is importing the edited XML file into the target WebSphere
Portal Server. This will create the page layout and portlet preferences into the target
WebSphere Portal Server.

Where do you start: planning and considerations

There is much pre-migration work that needs to be done in order to start the migration. First,
you need to have a target server installed and configured to use the same type of database
(DB2) and configured to use the same type of LDAP (or other third-party authentication tool).
If, for example, the source WebSphere Portal Server is using IBM Tivoli Directory Server as
the user repository in the source portal, you will need to configure the target server to use the
same type of LDAP with the same user repository data. Note that this does not mean it needs
to point to the same instance, just to an instance with the same user repository information.
220
IBM WebSphere Portal V6 Self Help Guide