The following table lists the known issues in Migration.
Table 17 Known Issues in Migration
Problem ID |
Description |
||||
---|---|---|---|---|---|
4790457 |
Can't change the document root of migrated server from 4.1. Workaround: Edit the migrated instance's obj.conf and server.xml manually. These files are located under <code><SERVER_ROOT>/<HTTPS-INSTANCE>/config directory. In obj.conf change the line:
to
In server.xml under the relevant VSCLASS change the line:
to
|
||||
6213097 |
ktsearch.jar is not getting migrated correctly on Sun Java Enterprise System 3 (JES3). Workaround: Manually edit the server.xml file of the migrated instance to point to the correct path. For Linux: /opt/sun/private/share/lib/ktsearch.jar For Solaris Sparc: /usr/share/lib/ktsearch.jar |
||||
5007081 |
Web-apps file status ignored during migration from 6.0 to 6.1 Web-apps status defined at the file level in the server.xml file is not getting migrated. If a user has switched off the status of the web-apps file to suppress them, upon migration these web-apps are exposed. Workaround: Edit the server.xml file of the migrated instance and turn off status for each web-app. |
||||
4988156 |
Installation of SP_2 patch on existing install (update) If you wish to upgrade the Sun Java System Web Server 6.1 that is installed as a part of Sun Java Enterprise System (JES), to the latest Service Pack, you will have to download and apply the relevant patches. For more details refer to the JES 3 Migration and Upgrade Guide. |