Portal Server search functionality throws exception when upgrading
Web Server from Java ES 4 to Java ES 5.
-
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).
-
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.
-
Use the wadm command to inform
the Web Server about the location of the library files.
-
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.
-
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>
-
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>
-
Deploy the modified configuration by typing the following
command:
deploy-config [--user=admin-user] config-name