Already loaded DLL needs to be changed and renamed. How to remove an existing DLL?

Question

Running Q1IM 6.1.2: I inherited an environment that uses DLL's to allow for script libraries to code against target systems API's and such. I have coded changes to an existing loaded DLL in 1IM. It will have a new DLL name and namespace. I didn't inherit the code for the already loaded and differently named DLL. So I need to be able to clean up by removing the old DLL. Does anyone know how to remove a DLL? The doc has information about how to Load a DLL but not the reverse. Thanks, Todd

Barry Jackson · Answer

Hi Todd, 
 
Was the (DLL) file added to the 1IM database using software loader? 
 
If it was you can remove it by simply deleting the entry from DialogFileInformation and DialogSoftwareRevision using ObjectBrowser. 
 
I'm not sure if this will delete the physical file from your install directories but if not you can just delete the DLL manually in the safe knowledge that 1IM won't automatically put it back. 
 
If the file wasn't loaded to the database then you should be able to just delete it from your install directories. 
 
HTH, Barry.

ToddFendt · Answer

Hi Barry, Yes, it was loaded with the loader. Thanks for the table names, that's what I was looking for. (And missing from the Quest Doc). Thanks for the help. I just wanted to be able to know with certainty that the old DLL was removed as it has most of the same methods within it. Thanks again.

Markus Weiss-Ehlers · Answer

It is documented how to edit the files in the One Identity Manager database. http://documents.software.dell.com/identity-manager/6.1.3/configuration-guide/files-for-software-update/editing-the-files 
 And i may want to add, that using the Designer is way easier than using the ObjectBrowser and having to know the tables.

ToddFendt · Answer

Hi all, I did figure this out. Since the Job Server service calls the stdioprocessor.exe & stdioprocessor32.exe the config information has to go there instead of in the vinetworkservice confgi file. As the error stated from MS the calling program has to have the config file information. So I took the same section of config file and planted it in the stdio config files (32 and non 32). The upgrade erased the customizations from these files so it broke during my upgrade. Problem solved. Thanks for reading..