Bug 133709

In Spitfire, we will provide documentation for this.  After Spitfire, we want to install it.

Reopening this defect so we can fix it in Seafang.

Steve Shaw has the files in the install image, and I've provided Paul Thomas with a brief description and the files that need to be installed.  Re-assigning to Paul Thomas.

Paul Thomas: On Linux/Solaris/AIX, the installer does not have a Utilities option; the tools and utilities for the various drivers are all automatically installed by the driver packages (RPMs, etc.). The only options are Metadirectory Server, Connected System Server, Web-based Administrative Server, or Custom. Should the tool only be available via a Custom install? Should we install it by default for a Metadirectory, Connected System, or Web-based Admin install?
Richard Matheson: It's not a tool that is specific to a driver.  
Richard Matheson: So it wouldn't be wrapped up in a driver RPM
Richard Matheson: I would assume we don't do a utilities install on Linux... because there hasn't been a reason.
Richard Matheson: Now there's a reason.
Richard Matheson: The whole point of doing this in Java was to make it available on platforms other than Win32.
Paul Thomas: But if I add a Utilities option, I think the user would expect all of the other tools/utilities to be controlled by that option also (like on Windows/NetWare). That would require repackaging a lot of stuff and is not feasible right now.
Richard Matheson: So what do you do with this?  It doesn't really fit in the metadirectory, connected system or Web install.
Paul Thomas: Do you see an issue with always installing the audit tool?  If so, I would recommend we just add it to the choices under the Custom install.
Richard Matheson: Where would it get installed?
Paul Thomas: That's a good question.
Paul Thomas: I'll have to figure out a good location...perhaps an idm-tools directory somewhere logical...but if you had to choose between always installing it or making it a Custom option only, which would you pick?  As I said, I don't believe adding a Utilities option is feasible at this point.
Richard Matheson: At this point I wonder if the best thing is to have it have a stand-alone install and leave it on the CD.
Richard Matheson: 1. It's a client based, not server based, utility; 2. It doesn't need to be installed everywhere, and may not need to be installed at all.
Paul Thomas: I think I agree with you. Whose decision is this to make?
Richard Matheson: PM & CCB.
Richard Matheson: Deven MacDonald is the relevant PM for this.
Paul Thomas: Will you present this issue to him/them and ask for a decision? I think you can explain it better than I.
Richard Matheson: Groovy
Richard Matheson: Assign the defect back to me.

Since this defect has a fixed in milestone assigned, I'm changing the status from "New" to "Assigned".

So, CCBers, what is the decision here?  Leave it in the utilities directory and provide it a stand-alone install?  Leave it there with simple file copy instructions?  It's pretty lightweight stuff.  There is a .jar for each utility, a windows batch and Linux command file for each, plus they are dependent on forms_rt.jar and ldap.jar.

On Windows we would like the installation to install it as part of the utilities install option.  On Linux, Solaris, AIX, the files will exist on the .iso, and the documentation will need to explain how to make it go.

If possible, we would like that for Windows all reg settings, etc. be handled by the IDM install.

Reassigning to Paul Thomas.

*** Bug 198805 has been marked as a duplicate of this bug. ***

The IDM installer for Windows now installs the contents of nt\dirxml\utilities\idm_lat in the .iso image to C:\Novell\NDS\DirXMLUtilities\idm_lat.

I'm reassigning this bug to documentation to document the use of the IDM License Auditing Tool and the IDM Association Disabler Tool. On all platforms besides Windows, these tools need to be copied from the CD to a writable directory. The tools create files in the current directory and will fail if they cannot do so.

Please refer all questions regarding these tools to Richard Matheson.

Sarah, will you please assign this bug to the appropriate writer. Thanks.

This defect had a fixed in milestone assigned, but the status was NEW.  I changed to status to ASSIGNED.

I have created the first draft of the IDM LAT documentation, which Richard Matheson is reviewing now. That process is being managed under Bug #198809, so I don't need this bug to track it.

However, when I attempted to install IDM LAT on Windows using the Utilities option in the Install, I didn't get the IDM LAT app files. Rather, the following files were copied to C:\Novell\NDS\DirXMLUtilities (no idm_lat folder was created):

SampleInputTransform.xml
SampleSubCommandTransform.xml
SampleSubEventTransform.xml

I went out ot the image and was able to copy the IDM LAT files manually, so they are in the image, but the install didn't appear to work properly. I believe I was using the 1/12/07 Seafang build image.

Reassigning to Paul Thomas. Please contant me if you have any questions about my experience.

Paul-  Anything left for you on this>

I installed the 20070117 build of IDM onto a fresh install of Windows Server 2003 (R2 Standard Edition) with eDirectory 8.8.2. I selected only Utiltities, then only Application Components, then C:\Novell\NDS\DirXMLUtilities, and then only License Auditing Tool. After the install, the C:\Novell\NDS\DirXMLUtilities directory had been created and contained the idm_lat directory and its contents (in addition to the Sample*.xml files mentioned in comment #12 which are always installed if Application Components is selected).

Regressed with IDM3.5 build 20070123 and verified that the idm_lat directory is created and contains idmlat, idmlat.bat, AuditMain.jar, etc., and that the Sample*.xml files are created under the DirXMLUtilities directory.

Marking Seafang customer relevant bugs for public view.