Some manual configuration is required on the IBM® Lotus® Quickr™ 8.5 environment before migration.
To prepare the Lotus Quickr 8.5 system for the import migration, perform the following steps:
1. Copy and activate required database library files as noted below.
Limitation: The WebSphere® Application Server UserManagement component (VMM) requires access to the following database libraries to use the VMM database functions such as Property Extension and database user registry.
1. DB2 Type 4 driver: db2jcc.jar;db2jcc_license_cu.jar
2. Oracle: ojdbc14.jar
Depending on the driver that you are using, copy the required files into the app_server_root/lib directory. Then stop and restart the server1 and WebSphere_Portal servers to load the library files.
2. Configure the passwords in your Lotus Quickr 8.5 environment.
Edit the wp_profile_root/ConfigEngine/properties/wkplc.properties file and update WasPassword and PortalAdminPwd with your passwords. These should be removed after running the import process.
3. Clear the tranlogs and temp directories before connecting to the new JCR and customization database by running a ConfigEngine task from
wp_profile_root/ConfigEngine. This will prevent any errors with xa transactions during startup.
ConfigEngine.bat/sh delete-was-temporary-8500
4. Update the log size and number of roll over logs for trace.log and SystemOut.log. The changes need to be static for the various server re-starts that occur during migration.
1. Log into the WebSphere Integrated Solutions Console as the WebSphere Application administrator.
2. Click Troubleshooting->Logs and Trace->WebSphere_Portal->Diagnostic Trace Service.
3. On the Configuration tab which changes the static setting for the trace.log file, first note the current values, then set the Maximum File Size to 20 MB and the Maximum Number of Historical Files to 10. Click OK to save.
4. Click Troubleshooting->Logs and Trace >WebSphere_Portal->JVM logs
5. On the Configuration tab which changes the static setting for the SystemOut.log file, first note the current values, then set the Maximum Size to 20 MB and the and the Maximum Number of Historical Files to 10. Click OK to save.
5. Change the trace settings in your Lotus Quickr 8.5 Environment. This is an optional but recommended step that improves problem determination with migration errors. Specifically, this trace adds start and stop time stamps for each place that migrates. The time stamps enable correlating migration events with other events in the SystemOut.log file. The added trace has a small impact on performance and on the size of the log. The trace needs to be static so that the trace is collected during the various server re-starts that occur during migration.
1. Log into the WebSphere Integrated Solutions Console as the WebSphere Application administrator.
2. Click Troubleshooting->Logs and Trace->WebSphere_Portal->Change Log Detail Level
3. On the Configuration tab, set trace to:
*=info: com.ibm.wps.ai.io.deserialization.migration.MigrationServiceImpl=all
4. Click OK.
6. Change the Generic JVM arguments used by the Portal Server to work around a memory leak in a Java API. For more information on the leak see
IBM Java service
. This workaround prevents intermittent server start failures.
1. Log into the WebSphere Integrated Solutions Console as the WebSphere Application administrator
2. Click on Servers -> Applications servers -> WebSphere_Portal -> Java and Process Management -> Process Definition -> Java Virtual Machine
3. Under the Configuration tab, append
" -Dcom.ibm.zipfile.closeinputstreams=true" to the Generic JVM arguments value. Make sure to have a blank space prior to the new argument.
4. Click OK.
7. Prevent two scheduled tasks from running during the migration import process, to improve migration performance and avoid scheduled task failures. The tasks are the administrative statistics collection and the policy handler. The statistics collection can be turned off during migration. The policy handler cannot be turned off and must be rescheduled instead.
1. Log into the WebSphere Integrated Solutions Console as the WebSphere Application administrator.
2. Click on Resources --> Resource Environment --> Resource environment providers --
QuickrAdminConsole --> Custom properties
3. Set the value of statistics.task.active to false which disables this task. The default value is true.
4. Restart the QuickrNextAdmin application. Click on Applications --> Enterprise Applications and search for the QuickrNextAdmin application. Click the check box for this application, followed by Stop then Start to pick up the new value.
5. Schedule the policy handler task to run on a day that migration does not run. By default, this background task runs at 10:30 p.m. daily. If you have already changed the default, take note of the current setting.
6. Make a local copy of the xml file defined in Scheduling the policy handler task. For example: <temp_loc>/policyhandlertask.xml
7. Uncomment and modify the daily stanza so that the task runs on a different day. For example, if you are running the import on Sunday, the stanza could be set to a day later in the week such as Monday.
<!-- Runs weekly at 11 pm each Monday. Specify a number from 1 to 7,
where 1 is equivalent to Monday and 7 is equivalent to Sunday. -->
<task action="create" name="com.ibm.portal.ai.task.AITask_PolicyHandler">
<dayOfWeek>1</dayOfWeek>
<startTime>23:00</startTime>
</task>
8. Open a command prompt and change to app_server_root/bin then run the following command:
xmlaccess.bat/sh -in policyhandlertask.xml -user <portaladminid> -password <portaladmin pwd>
-url http://<hostname>:10040/lotus/config -out <temp_loc>out.xml
8. Increase the value of "total transaction lifetime timeout". To prevent migration failures of large places and the xmlaccess import process, you must increase one of the Transaction Service settings.
1. Log into the WebSphere Integrated Solutions Console as the WebSphere Application administrator.
2. Click on Servers -> Applications servers -> WebSphere_Portal -> Container Settings -> Container Services -> Transaction Service
3. Note the existing value for "Total transaction lifetime timeout" then increase it to 1200 and save. This needs to be reset after migration completes.
Parent topic:
Preparing the target environment: qp85
Previous topic:
Verifying Lotus Quickr: qp85
Next topic:
Preparing the source environment: qp85