Troubleshooting
Problem
There are several instances when applications require specific versions of libraries which are different from the ones that are packaged with the server distribution. For example, LOG4J-1.2.14 is distributed with WebSphere Application Server Community Edition version 2.1.1.1. If an application requires a version later than the supplied version, WebSphere Application Server Community Edition provides several mechanisms to make these specific versions of the libraries available to applications at runtime. This technote explains several methods available to address the same problem.
[{"Product":{"code":"SS6JMN","label":"WebSphere Application Server Community Edition"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"General","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"2.1.1.2;2.1.1.1;2.1.0.1;2.1;2.0.0.3;2.0.0.2;2.0.0.1;2.0;1.1.0.2;1.1.0.1;1.1;1.0.1.2;1.0.1.1;1.0.1;1.0.0.1;1.0","Edition":"Entry;Enhanced;Elite","Line of Business":{"code":"LOB77","label":"Automation Platform"}}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21261287