Anonymous_User

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2015-05-14
18:54
318 views
Renaming a Deployed UserApp Driver IDM4.5
Trying to assess the time and impact of renaming an IDM 4.5 UserApp
driver, before I fall back to rebuilding from scratch.
In a DEV environment the driver was called "UserApplication" while the
Production install was called "UserApp," and we have a bevy of GCV's
that refer to the UA Driver DN
I would like to rename the Production driver, to match DEV. The
Production environment has not gone live yet. The driver is in a fairly
green-field IDVault, so I don't have to worry about mass implications.
I see from 2009 that renaming the UserApp driver was trivial:
https://forums.netiq.com/showthread.php?10463-Rename-userapp-driver
Does this still hold water for IDM4.5? Stop the driver, rename it in
iManager, restart the driver.
What other modifications might there be? Modify the Driver DN in
Configupdate.sh?
Any other implications? We do have the Roles and Resources driver
running as well. Reconfigure the DN reference in its config, I assume.
Thanks for additional insights/process, in advance.
--
folboteur
------------------------------------------------------------------------
folboteur's Profile: https://forums.netiq.com/member.php?userid=3683
View this thread: https://forums.netiq.com/showthread.php?t=53488
2 Replies


Knowledge Partner
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2015-05-14
19:23
There's a GCV that refers to the driver itself; why not use that directly
so that, regardless of the object's name, your policies work?
dirxml.auto.driverdn (or something like that)
--
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
so that, regardless of the object's name, your policies work?
dirxml.auto.driverdn (or something like that)
--
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
Anonymous_User

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2015-05-14
20:14
This, ultimately, is a good suggestion on architecture... but short of
re-installing, and short of re-architecting code, renaming the driver
would be the quickest, effective fix. So, any thoughts on whether the
4.5 driver can be easily and quickly renamed, and what impacts it may
have?
--
folboteur
------------------------------------------------------------------------
folboteur's Profile: https://forums.netiq.com/member.php?userid=3683
View this thread: https://forums.netiq.com/showthread.php?t=53488