<<

. 23
( 87 .)



>>

WY009-06 WY009-BenNatan-v1.cls May 9, 2004 9:35




116 Chapter 6


2. Open a command prompt on your WebSphere Portal V5.0 machine
(sandbox5.rigorconsultants.com) and go to <wp5_root>\
migrate directory.
3. Enter WPmigrate export-apps.
4. Wait for the Build Successful message and then check the
MigrationReport.xml ¬le for any errors.
5. On WebSphere Portal V5.0 portal, verify that all your portlet
applications that you migrated are present under Portlets ➪ Manage
Applications ➪ Web Modules. Click Modify Parameters and see that
they are correct. Next go to Administration ➪ Access Resource
Permissions and under Resource Permissions click Portlet
Applications and then verify that the access control settings are
correct. Lastly, add them to a test page and perform a function test.

Migrating Places
In WebSphere Portal V5.0, the concept of a Place was eliminated. The mi-
gration tool converts them to a top-level page. Do the following tasks to
migrate them:
1. Ensure that in the mig_core.properties ¬le, you have set the
includePlaces property with the names of all your custom Places.
2. Open a command prompt on your WebSphere Portal V5.0 machine
(sandbox5.rigorconsultants.com) and go to <wp5_root>\
migrate directory.
3. Enter WPmigrate migrate-places -DdeployPages=false-
DdeployApps=false -Dcon¬gThemesSkins=false.
4. Wait for the Build Successful message and then check the
MigrationReport.xml ¬le for any errors.
5. On WebSphere Portal V5.0 portal, click on Administration ➪ Portal
User Interface ➪ Manage Pages. Then under Content Root, click on
My Portal and verify that your Places were migrated. Check the page
properties, including the properties under Advance Options to see if
they are correct.

Migrating Pages
1. Ensure that in the mig_core.properties ¬le, you have set the
includePages property with the names of all your custom Pages.
2. Open a command prompt on your WebSphere Portal V5.0 machine
(sandbox5.rigorconsultants.com) and go to <wp5_root>\
migrate directory.
P1: FCH/SPH P2: FCH/SPH QC: FCH/SPH T1: FCH
WY009-06 WY009-BenNatan-v1.cls May 9, 2004 9:35




Migrating to WebSphere Portal Version 5.0 117


3. Enter WPmigrate migrate-pages -Dcon¬gThemesSkins=false .
4. Wait for the Build Successful message and then check the
MigrationReport.xml ¬le for any errors.
5. On WebSphere Portal V5.0 portal, click on Administration ➪ Portal
User Interface ➪ Manage Pages. Then under Content Root, click on
My Portal and verify that your pages were migrated. Check the page
properties, including the properties under Advance options to see if
they are correct.

Migrating All User Customizations
This task migrates all skins referenced by themes.
1. Ensure that in the mig_core.properties ¬le, you have set the
includePages property with the names of all your custom Pages.
2. Open a command prompt on your WebSphere Portal V5.0 machine
(sandbox5.rigorconsultants.com) and go to <wp5_root>\
migrate directory.
3. Enter WPmigrate migrate-user-customization.
4. Wait for the Build Successful message and then check the
MigrationReport.xml ¬le for any errors.
5. On WebSphere Portal V5.0 portal, click on Administration ➪ Portal
User Interface ➪ Manage Pages. Then under Content Root, click on
My Portal and verify that all your customization were migrated.

Migrating Credential Vault Slots and Segments
1. Open a command prompt on your WebSphere Portal V5.0 machine
(sandbox5.rigorconsultants.com) and go to <wps_root>\
migrate directory.
2. Enter WPmigrate migratecredential-slots-segments.
3. Wait for the Build Successful message and then check the
MigrationReport.xml ¬le for any errors.
4. On WebSphere Portal V5.0 portal, click on Administration ➪
Credential Vault ➪ Manage Vault Segments and verify that the
segments have been migrated. Then click
Administration ➪ Credential Vault ➪ Manage Vault Slots and verify
that your vault slots were migrated.

Migrating Credential Vault data
After you have migrated the credential vault slots and segments, you have
to migrate the actual data. You do this by exporting the data from the tables
P1: FCH/SPH P2: FCH/SPH QC: FCH/SPH T1: FCH
WY009-06 WY009-BenNatan-v1.cls May 9, 2004 9:35




118 Chapter 6


VAULT DATA and VAULT RESOURCES found on your WPS V4.0 database
(sandbox3.rigorconsultants.com) and importing them to your
WP V5.0 database on sandbox6.rigorconsultants.com. The tables on
the VP V5.0 database gave the same names: VAULT DATA and
VAULT RESOURCES.
Verify the migration by clicking Access ➪ Credential Vault ➪ Manage Sys-
tem Vault Slots and reviewing the data for accuracy and completeness.


Migrating Everything at One Time
If you are feeling very con¬dent (and lucky), you can do a complete migra-
tion with one command by following the steps given below:
1. Open a command prompt on your WebSphere Portal V5.0 machine
(sandbox5.rigorconsultants.com) and go to <wp5_root>\
migrate directory.
2. Enter WPmigrate migrate-all.
3. Wait for the Build Successful message and then check the
MigrationReport.xml ¬le for any errors.
4. On WebSphere Portal V5.0 portal, verify the migration by reviewing
all your pages, portlets, credential vault slots/segments, and all the
access controls for your users, groups, and resources.


XML Con¬guration Interface
Another tool you can use for migration and batch changes is the XML
Con¬guration Interface. This tool enables you to export a part of or entire
con¬guration and then re-create it on another portal. You can also use XML
Con¬guration tool to help back up or restore complete portal con¬gura-
tion, copy parts of a con¬gurations, install additional resources, or perform
reproducible administration tasks.
The XML Con¬guration can be used to perform a complete re-creation
of a portal. It cannot deal with War ¬les, cannot be used for WPCP, and is
not suitable for large volumes of data. Backup and restoration should be
performed by regular database and ¬le backup tools.
XML Con¬g is invoked by typing xmlaccess on the command line. It can
be invoked on the actual portal server or on any client. To invoke it on a
remote client you need to have a Java engine and the tool.jar ¬le that is
found in <wp_root>/bin directory.
As can be seen in Figure 6-2, the XML Con¬g tool takes an input ¬le
consisting of XML tags (1), sends it by HTTP from the client (2) to the WP
P1: FCH/SPH P2: FCH/SPH QC: FCH/SPH T1: FCH
WY009-06 WY009-BenNatan-v1.cls May 9, 2004 9:35




Migrating to WebSphere Portal Version 5.0 119




Figure 6-2 How the XML Con¬guration Interface utility works.

servlet (3), which passes the data to the XML Con¬g engine (4). The XML
Con¬g engine stores and retrieves data speci¬c to the con¬guration actions
from the Portal con¬g database (5). The output is sent back to the client via
HTTP as XML tags (6), which can then be used as input.
The XML Con¬guration Interface handles two types of requests: Export
and Update. Export results in complete or partial portal con¬guration into
XML. Update causes the portal con¬guration to be modi¬ed based on the
XML script values.
The syntax for the command is as follows:
xmlaccess-in inputfile-user user-pwd password-url URL-out
output_file

where -in is the input ¬le, -user is the authorized portal user id,
-password is the password, -url is the portal URL for processing the
command (such as http://www.rigorconsultants.com/wps/
config), and -out is the output ¬le.
P1: FCH/SPH P2: FCH/SPH QC: FCH/SPH T1: FCH
WY009-06 WY009-BenNatan-v1.cls May 9, 2004 9:35




120 Chapter 6


The user must be a super user with manager role on XML ACCESS and
administrator role on portal. The usernames and passwords are sent unen-
crypted, so send them over the intranet or use VPN.
The XML Con¬guration interface models your portal as XML tags with
the de¬ned hierarchical structure shown in Table 6-5. (This table can also
be found in the Portal infocenter.)

Table 6-5 Description of XML Access Tags
XML DESCRIPTION
portal Main element of every XML request

global-settings Global portal settings

services-settings Global portal settings for portal services

virtual-resource Virtual resources that have associated access control
settings

user Users de¬ned in the portal user management system

group Groups de¬ned in the portal user management system

markup Markups that can be supported by portal pages

client Client devices (browsers) that the portal knows about

event-handler De¬nitions of event handlers that can react to events in
the portal

skin Visual appearance settings that can be applied to user
interface elements

theme General visual settings that can be applied to the user
interface

web-app Web modules containing portlets

servlet Servlets that are de¬ned in the Web module

portlet-app Portlet applications that are de¬ned in the Web module

portlet Portlets that are de¬ned in the portlet application

content-node Elements of the portal content tree (pages or labels)

component Layout components of pages

portletinstance Occurrences of a portlet on a page with customized
settings

credential-segment Segments for storing credentials in the credential vault

credential-slot Slots in a credential segment that hold a credential

url-mapping-context User de¬ned URLs that map to pages in the portal
P1: FCH/SPH P2: FCH/SPH QC: FCH/SPH T1: FCH
WY009-06 WY009-BenNatan-v1.cls May 9, 2004 9:35




Migrating to WebSphere Portal Version 5.0 121


Obviously, the XML ¬les generated can be quite complex and cryptic,
especially with a detailed portal.


XML Input File
The XML Con¬guration Interface requests are de¬ned in an input ¬le with
the following structure:
<?xml version="1.0" encoding="UTF-8"?>
<request
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="PortalConfig_1.2.xsd"
type="export | update">
<portal . . . >
definition of configuration parts to be exported or updated
</portal>
<status . . . >
success or failure indication for the processing
</status>
</request>

You must always use the schema reference with no namespace to the
schema “PortalConfig_1.2.xsd.”
Actions are carried based on the value of the request type parameter. You
have two types of requests: update or export. Update performs a modi¬ca-

<<

. 23
( 87 .)



>>