Errors due to missing library files (due to removal and deprecation from V5.0 to V6.0)
 Technote (FAQ)
 
Problem
You are experiencing problems with applications that use shared libraries that were removed in WebSphere® Application Server V6.0. These libraries will not be present, so you must manually perform one of the three workarounds documented in this technote.
 
Cause
Certain JAR files, (for example: xss4j-dsig.jar and xss4j-enc.jar) are shipped with WebSphere® Application Server V6.0. If your applications were using these libraries in V5.0, the applications might not function properly after migration, and servers these applications are deployed on might not start properly. The following are a couple reasons why libraries would not be shipped with V6.0:
  • The libraries have been deprecated for two releases
  • Compliance with the J2EE 1.4 specification
 
Solution
You should select the workarounds that best suit their needs. However, it is highly recommended that if you use workaround 1 or 2 also perform workaround 3 to prevent this problem from reoccurring the next time you attempt to upgrade the Application Server.
  • Workaround 1: Create a shared library in V6.0
    Note: This is the recommended short term solution, since customers are aware that their applications correctly work with the old release shipped library files. However, customers must be aware that the libraries might not function properly. Customers selecting this option are encouraged to also perform workaround 3.
    1. Copy all the missing libraries to a user space on the machine. (A user space is any location that is accessible by both V5.0 and V6.0 WebSphere code, but does not reside in the directory tree for either)

    2. In the V6.0 migrated configuration, create a shared library that includes in the library path the missing libraries (use the copies in the user space, from step 1).

    3. If the customer's configuration directly references the missing libraries.

  • Workaround 2: Use the Application Server classloader
    Note: It is recommended that you do not use this workaround for Application Server libraries that were removed in V6.0, instead use workaround 1. This option can be used for third-party libraries that are compliant with Application Server V6.0. If you select this option, you are also encouraged to perform workaround 3.

    Copy all missing libraries into the following directory:

    install_root/lib

    Note: This will affect all profiles in that installation.

  • Workaround 3: Update your application to use supported or included features
    Note: This is the best solution, however it will take some time. If you cannot wait to upgrade, you can use this workaround in conjunction with workaround 1 or 2.

    You should investigate available replacement solutions that are supported with or included in the new version of the Application Server . Then you need to update the your application to use the replacement solution.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Migration
Operating system(s): AIX
Software version: 6.0
Software edition:
Reference #: 1245037
IBM Group: Software Group
Modified date: Nov 13, 2006