Environment
Novell Identity Manager 3.6
Situation
The purpose of this document is to provide the build numbers seen in a driver startup trace set to level 3 and above for the shipping IDM 3.6 and above product. This document does not currently include User Application information.
Resolution
IDM 3.6 FCS | |
Component | |
IDM Engine | Version: 3.6.0.4294 |
Active Directory driver | Version: 3.5.3 Build: 20080229_143300 |
Avaya PBX driver | Version: 3.5.2 Build: 20080710_0831 |
Delimited Text driver | Version: 3.5.4 Build: 20080710_082352 |
eDirectory driver | Version: 3.6.0.4294 |
GroupWise driver | Version: 3.5.1 Build: 20070626_2242 |
JDBC driver | Version: 3.5.2 Build: 20080710_0850 |
JMS driver | Version: 3.5.3 Build: 20080710_0850 |
LDAP driver | Version: 3.5.5 Build: 20080710_083657 |
Lotus Notes Driver | Version: 3.5.2 Build: 20080710_083658 |
PeopleSoft driver v5.2 | Version: 5.2.0 Build: 20080710_083658 |
Remedy ARS driver | Version: Build: |
SAP HR driver | Version: 3.5.3 Build: 20080710_085536 |
SAP User Management driver | Version: 3.5.1 Build: 20080710_085536 |
Scripting driver | Version: 3.6.0 Build: 20080523_1417 |
SOAP driver | Version: 3.5.3 Build: 20080710_082352 |
WorkOrder driver | Version: 3.5.2 Build: 20080710_0908 |
Entitlements Service driver | Version: 3.5.0 Build: 20080710_0908 |
ID Provider driver | Version: 3.6.0 |
Bi directional core driver | Version: 3.6.0 Build: 20080530_1424 |
Fan out core driver | Version: 3.6.0 Build: 080619 |
Additional Information
When capturing an IDM trace level 3 and above, it is possible to see in the XDS sections of the trace what is the engine build and what is the version and build information of a driver.
Here is an example of a document coming from the engine with its version within the <product> XML tag:
[10/01/08 03:52:15.779]:Delimited Text ST:
<nds dtdversion="3.5" ndsversion="8.x">
<source>
<product version="3.6.0.4294">DirXML</product>
<contact>Novell, Inc.</contact>
</source>
Here is an example of a document coming from a driver shim as a response to the __driver_identification_class__ query, with its version within the <product> XML tag:
[10/01/08 03:52:16.491]:Delimited Text ST:SubscriptionShim.execute() returned:
[10/01/08 03:52:17.129]:Delimited Text ST:
<nds dtdversion="2.0">
<source>
<product build="20080710_082352" instance="Delimited Text" version="3.5.4">Identity Manager Driver for Delimited Text</product>
</source>
<output>
<instance class-name="__driver_identification_class__">
<attr attr-name="driver-id">
<value type="string">TEXT</value>
</attr>
<attr attr-name="driver-version">
<value type="string">3.5.4</value>
</attr>
<attr attr-name="min-activation-version">
<value type="int">2</value>
</attr>
</instance>
</output>
</nds>
Here is an example of a document coming from the engine with its version within the <product> XML tag:
[10/01/08 03:52:15.779]:Delimited Text ST:
<nds dtdversion="3.5" ndsversion="8.x">
<source>
<product version="3.6.0.4294">DirXML</product>
<contact>Novell, Inc.</contact>
</source>
Here is an example of a document coming from a driver shim as a response to the __driver_identification_class__ query, with its version within the <product> XML tag:
[10/01/08 03:52:16.491]:Delimited Text ST:SubscriptionShim.execute() returned:
[10/01/08 03:52:17.129]:Delimited Text ST:
<nds dtdversion="2.0">
<source>
<product build="20080710_082352" instance="Delimited Text" version="3.5.4">Identity Manager Driver for Delimited Text</product>
</source>
<output>
<instance class-name="__driver_identification_class__">
<attr attr-name="driver-id">
<value type="string">TEXT</value>
</attr>
<attr attr-name="driver-version">
<value type="string">3.5.4</value>
</attr>
<attr attr-name="min-activation-version">
<value type="int">2</value>
</attr>
</instance>
</output>
</nds>