This article details about the recommended configuration settings for IBM WebSphere Portal Document Manager migration tool. Ensure that the WebSphere Portal Server is configured correctly before progressing ahead with the migration from IBM Portal Document Manager to Lotus Web Content Management.
1. Enable trace.log for all the servers (=info: com.ibm.pdm2wcm.=finest
2. Ensure you have installed language packs on the server machines if the content to be migrated has DBCS characters.
3. Configure the servers to log DBCS characters properly. This can be done from the WAS admin console by changing the JVM setting
a. In the administrative console, click Servers>
Application servers and select the server you want to enable for DBCS Transformation Format.
b. Go to Server Infrastructure, click Java and Process Management >
Process Definition >
Java Virtual Machine. Add -Dfile.encoding=UTF-8
in Generic JVM Arguments. Click OK.
c. Restart server.
Note : If there are any existing settings in 'Java Virtual Machine', Do not remove them. Add this new setting in there, and separate them with a space.
See Developing J2EE Global Applications Character Encoding
Additional Recommendations & Settings
Some of the additional settings are as below -
1. While viewing reports in Excel/OpenOffice, make sure u select UTF -8 character set
2. If any text (java regular expression) is added to Start or Exclude file located in the 'param' folder of 'Solutions' directory, ensure that the file is saved in 'Unicode' encoding.
To do this, first open the file with a text editor eg. Notepad on Windows, then select 'Unicode' for Encoding and click 'Save'.
This is to support unicode characters also in the Start and Exclude files.
3. Portlets render properly in Internet Explorer 7 and Firefox 3
4. The migration should be run by a user who is an administrator on both the PDM and Quickr/WCM machines
5. Check free disk space on server before performing Local migration
To investigate memory issue, enable the following -
1. Enable Heap Dumps.
a. Place IBM_HeapDump.jsp here -> \IBM\WebSphere\wp_profile\installedApps\dub01\wcm.ear\ilwwcm.war
b. Place this link into browser htt:/wps/wcm/IBM_HeapDump.jsp and enter.
2. Enable Verbose Garbage Collection. Log is saved in the file native_stderr.log
For AIX®, Microsoft® Windows®, or Linux®:
a. In the Administrative Console, expand Servers.
b. Click on Application Servers
c. Click on the server that you would like to work with, for example, server1
d. On the Configuration tab, under Server Infrastructure, expand Java and Process Management, and click Process Definition
e. Under the Additional Properties section, click Java Virtual Machine.
f. Check the Verbose Garbage Collection check box. Apply and Save the changes.
g. Restart the Application Server for the changes to take effect