6432106 

Sun Java System Portal Server search throws exception after Web Server upgrade.

Portal Server search functionality throws exception when upgrading Web Server from Java ES 4 to Java ES 5.  

Workaround

Move the existing libdb-3.3.so and libdb_java-3.3.so library files to an appropriate location, somewhere outside the Web Server's private directories. Once the Portal Server libraries are in a suitable location, that path must be specified for the <libdb-3.3.so path>:<libdb_java-3.3.so path> in the following commands.

On Solaris platform, perform the following steps: 

1. Copy the libdb-3.3.so and libdb_java-3.3.so files from Web Server 6.1 lib directory to an appropriate location.

   ---

   Note –

   For HP-UX, the files are libdb-3.3.sl and libdb_java-3.3.sl. For windows, the files are libdb-3.3.dll and libdb_java-3.3.dll.

   ---

   ---

   Caution –

   Do not copy the library files to Web Server 7.0 private directories (For example, lib directory).

   ---

2. Create a directory (mkdir) by name /portal_libraries. Copy the library files libdb-3.3.so and libdb_java-3.3.so to /portal_libraries.

3. Use the wadm command to inform the Web Server about the location of the library files.

4. Get the current native library path setting by typing the following administration CLI command:

   get-jvm-prop -user=admin --config=hostname native-library-path-prefix

   Save the output.

5. Append the copied libdb-3.3.so and libdb_java-3.3.so path to the existing native library path by typing the following administration CLI command.

   set-jvm-prop --config=hostname native-library-path-prefix=<existing native library-path>:</portal-libraries-path>

   where, portal-libraries-path is the location of where you copied the libdb-3.3.so and libdb_java-3.3.so files in Step 1.

   If you do not get any results or output for the get-jvm-prop command, at the command prompt, set the native-library-path-prefix:

   native-library-path-prefix=</portal-libraries-path>

6. ---

   Note –

   For Windows platform, use ';' as the separator for native-library-path-prefix parameter as follows:

   native-library-path-prefix=<existing native libarary path>;<portal-libraries-path>

   For non-Windows platform, use the ':' as the separator for native-library-path-prefix parameter as follows:

   native-library-path-prefix=<existing native libarary path>:<portal-libraries-path>

   ---

7. Deploy the modified configuration by typing the following command:

   deploy-config [--user=admin-user] config-name

6504178 

Migration logs reports a bogus "root is not a valid user" message on Java ES 5.

While migrating from Java ES 4 to Java ES 5 on UNIX platforms, the migration log file reports WARNING: "root is not a valid user". This is incorrect as the "root" user is valid on that host.

6453037 

A lot of warnings/info messages displayed at Web Server startup on the standard output instead of routing these messages to the log file.