Performing post migration configuration: qp85 

---

Some configuration to restore settings and update places is needed after migration before the target environment is ready for general use.

To complete the migration after the import process is complete, perform the following steps.
1. Restore configuration settings.

After testing the system, you must reset some of the configuration settings back to a level normally used during production.
a. Remove the passwords in your WebSphere® Portal 6.1 environment. Edit the quickr_install_root/wp_profile/ConfigEngine/properties/wkplc.properties file and change the properties WasPassword and PortalAdminPwd to blank.
b. Restore the Total transaction lifetime timeout value. 

1. Log into the WebSphere Integrated Solutions Console as the WebSphere Application administrator. 
2. Click on Servers --> Application servers --> Runtime tab -->Transaction Service
3. Change the value of  "Total transaction lifetime timeout" back to its previous value (default value is 120). 
c. In the administrative console, restore static trace, log settings, and administrative statistics collection in the administrative console back to their original values.  These were optional steps which you may not have performed.
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 trace.log, restore the Maximum File Size to your previous value (default is 20 MB) and the Maximum Number of Historical Files to your initial value (default is 3). Then, 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 SystemOut.log, restore the Maximum Size to your previous value (default is 5 MB) and the Maximum Number of Historical Files to your previous value (default is 3).  Then, click OK to save.
6. Click Troubleshooting->Logs and Trace->WebSphere_Portal->Change Log Detail Level
7. On the Configuration tab, set trace to its previous value (default is *=info)
then click OK.
8. Click on Resources --> Resource Environment --> Resource environment providers > QuickrAdminConsole > Custom properties then set the value of statistics.task.active to your previous value (default is true).
9. If you changed the value in the previous step, 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.  
d. Restore the policy handler task to it's previous schedule. 

1. Using the same file from step xx yy for example: <temp_loc>/policyhandlertask.xml, comment out the weekly stanza use previously. 
2. Uncomment the stanza needed to reset the task.  Using the default settings as and example, you need to comment the daily stanza and reset

3. Open a command prompt and change to app_server_root/bin then run the following command:


2. Update links within place content.

Links within migrated content are not automatically updated to point to the Lotus® Quickr™ 8.5 server. An example of a link would be a link from a wiki page to a document in a library. Upon completion of the migration, these links continue to point to their original location. For example, if a wiki page points to a library document, the migrated wiki page links to the library document on the source server.

There are several ways to correct the links after the migration process has completed.

Rename the Lotus Quickr 8.5 server entry point to match the Lotus Quickr 8.1.1.1 server.

Reconfigure the web server for the 8.1.1.1 server to route requests to the Lotus Quickr 8.5 server.

Manually update the links.

a. Rename the server.

In a typical production environment, whether a standalone server or a cluster, there are one or more web servers through which the Lotus Quickr resources are accessed. After migration, to preserve any internal and external links, the web server serving the Lotus Quickr 8.5 server can be renamed to match the server used for the Lotus Quickr 8.1.1.1 system. If a web server was not being used with the Lotus Quickr 8.1.1.1, it is not enough to rename the server since the default http and https ports may not match. For example, the default http port for Lotus Quickr 8.1.1.1 was 10038. The default port for Lotus Quickr 8.5 is 10040. You can pre-determine the ports for the Lotus Quickr at install time or change the ports after installation. See the topic Configuring the Lotus Quickr ports for information on setting the ports for the Lotus Quickr 8.5 server. Do not perform this step until you are ready to take the Lotus Quickr 8.1.1.1 server off line.
If you are renaming a single server instance it is best to update the DNS such that both the original name and new name resolve to the same server. This ensures that any intra-server communication that relies on the original hostname continues to function. For example, there may be some DB2® dependencies on the hostname that was used at the time of the installation.

b. Reconfigure the 8.1.1.1 server.

Another option to preserve the links after migration is to upgrade the web server used for Lotus Quickr 8.1.1.1 to serve the migrated Lotus Quickr 8.5 environment. See the WebSphere Network Deployment library for information on migrating web server configurations. For setting up a web server with Lotus Quickr 8.5, see Configuring Web servers. This option should not be performed until you are ready to take the Lotus Quickr 8.1.1.1 server off line.

c. Manually update the links.

If one of the other options for preserving links is not applicable, then the link information must be updated manually.
In Lotus Quickr 8.1.1.1, all links were stored as fully qualified links. For example: <a href="http://quickr8111.yourco.com:10038/dm/atom/library/7ac59a00413512f5bfb3bf7858640c1a/document/e19f8d804135139fbfbabf7858640c1a/media?resolve=true" target="" title="">My RTE document.ort</a> Links to a local wiki page or library document were not distinguishable from links to external sources.
In Lotus Quickr 8.5, links to local Lotus Quickr content are now stored as relative links. For example: <a href="/dm/atom/library/7ac59a00413512f5bfb3bf7858640c1a/document/e19f8d804135139fbfbabf7858640c1a/media?resolve=true" target="" title="">My RTE document.ort</a>
Upon completion of the migration, these fully qualified links must be updated to point to the content on the Lotus Quickr 8.5 server.
Perform the following procedure to update the content links:

i. Access a place that needs updating. This must be done by a user with authority to edit the contents.
ii. Edit the content.
iii. Click on the icon to edit the html source.
iv. Locate the link information.
v. Strip the hostname and port information from the link. For example: http://quickr8111.yourco.com:10038
vi. Save the changes.

The following is an example of the resulting links:

3. Update the status of the migrated places.

The status of a place (for example, place size or lock status) does not migrate with the place content. Upon completion of the migration, the migrated places will not reflect accurate status until the next policy task runs. You can optionally request that the policy task run immediately. See Scheduling the policy handler taskfor more information on working with the policy task.

4. Enabling search on the migrated content:

a. Turn on JCR text search and syndication. Edit the wp_profile_root/PortalServer/jcr/lib/com/ibm/icm/icm.properties file and change jcr.textsearch.enabled to true.
b. Stop the server.
c. Delete the index directory:
wp_profile_root/PortalServer/jcr/search/1

d. Start the server.
e. Update data in a place, for example edit a wiki page or document. This starts index generation.
f. Wait for index generation to complete. The time to completion depends on two factors:
• The amount of data that must be indexed. This is determined by number of places and amount of content in those places. The more data that must be indexed, the longer index generation takes.
• The pending updates checker. By default, every 30 minutes Lotus Quickr checks for pending updates to the index. (This interval is configurable.) The check must occur to start index generation.

g. Make sure that the index was created. Navigate to the index directory:

wp_profile_root/PortalServer/jcr/search/1

Note: This is the default location for the search index. You can use the icm.properties file to alter where the search index is located.
If there is no clusterlock_l.tlf file, the indexing process is complete.

5. If you run Lotus Quickr in a clustered environment, you need to create a cluster from the target server. Consult the appropriate installation instructions for your operating system in the list of related links.

Parent topic: Post migration configuration: qp85
Previous topic: Running the IBM WebSphere Portal import command: qp85
Next topic: Verifying Lotus Quickr migration: qp85


Related information
Creating a new cluster from a single server node on Windows: qp85
Creating a new cluster from a single server node on Linux: qp85
Creating a new cluster from a single server node on AIX: qp85