WebSphere & TAM embedded PD.jar

echnote (FAQ)



## Question

What versions of TAM’s PD.jar are compatible with various versions of WAS

## Cause



IBM WebSphere upgrade causes an incorrect version of PD.jar to be installed.

Answer



IBM WebSphere® Application Server includes the ISAM (TAM) PD.jar file in its distribution.

This can be problematic or confusing when the Policy Server is at a different version.

In general there is quite a bit of flexibility in using various PD.jar files with WebSphere. The main issue
is what version of the PD.jar will work with what versions of TAM’s Policy Server and Authorization Server.
Other considerations include WPM, JACC and WebSphere 8. WAS 8 introduced some changes
that required changes to the PD.jar. Therefore it is more restricted to certain versions of the PD.jar.
WAS 8 requires a TAM PD.jar level of 6.1.0.7 or 6.1.1.3 as a minimum. JACC is also included in WAS
and depends on the PD.jar. WPM is not included with WAS but also depends on the PD.jar.

In general it is recommended that the PD.jar be at the same level as the TAM server. Since this is
not always possible the following tables will help serve as a guideline in determining which version to use .

The following chart shows key WAS releases and the versions of the PD.jar included.






































WebSphere Application Server ND

ISAM / Tivoli Access Manager PD.jar

7.0 Fix pack 29

6.1.0.7

8.0

6.1.0.5

8.0 Fix Pack 01

6.1.0.7

8.5

6.1.0.7

8.5 Fix Pack 02

6.1.0.7


The following chart show key WAS releases and the TAM server versions supported

Product Versions that PD.jar functions against.






















PD.jar

WebSphere Application Server ND
Version

ISAM/TAM
Policy Server

TAM Local Mode DB

6.1.0.5

6.1 / 7.x

6.1 / 6.1.1

6.1 / 6.1.1

6.1.0.7

7.x / 8.x

6.1 / 6.1.1 / 7.0

6.1 / 6.1.1

Back ground information:

The PD.jar file allow java runtimes to deploy a set of classes to an appropriate resource.
Jar files are compressed so you can download a complete application with one download.

The PD.jar file had a manifest file located in the path of the META-INF/MANIFEST.MF
The MANIFEST.MF can be extracted by any standard zip software including “jar” for Windows.

On Unix/Linux the PD.jar version can be viewed by using the zcat command as below:-
For this document I am going to use the zcat command ( from Unix/linux) and available from cygwin for Windows,, i.e zcat PD.jar



To continue this example the above PD.jar was available but after an upgrade of WAS you can see that an older version of
PD.jar was inserted and therefore our customer should contact IBM WebSphere for the latest version so it can be inserted
into the WebSphere installation/ upgrade mechanism.



Note: The PD.jar the can not be downloaded independent of a patch.

All of the above PD.jar need to be upgraded to the latest version of TAM PD.jar to obtain the latest resolved issues:
They can be downloaded from IBM’s Fix Central :-
www. ibm .com/support/ fixcentral /

For WAS installation please contact your local WebSphere Support for to obtain the latest level using WebSphere installation mechanism