• Browse Blogs
  • My Blog
  • My Updates

+Tags Get help with tags?

  • View as cloud  | list

+ Bookmarks

+ Blog Authors  

Caveat with AdminP Direct Deposit

Chad Scott |   | Comments (2)  |  Visits (888)
New to 8.x is a feature that allows AdminP requests to be created directly in the admin4.nsf of the server that will process the request. From Administration Help:
The Administration Process can deposit requests directly into the Administration Requests database (ADMIN4.NSF) -- The Administration Process can now deposit administration requests directly into a target server's Administration Requests database (ADMIN4.NSF) instead of depositing the request into a local copy of ADMIN4.NSF.
The direct deposit feature also applies on the client side. In particular, an 8.x client will attempt to deposit the Change HTTP Password in Domino Directory request in the administration server's admin4.nsf following a password change when synchronization is configured. In complex environments, regional clients and servers may not have a direct path to the administration server, causing the client to fail when attempting to create the request. In this case, you can use the ADMINP_DONT_ATTEMPT_DIRECT_DEPOSIT=1 parameter to instruct the client to bypass the direct deposit route and create the synchronization request in the home server's admin4.nsf. Replication will then carry the request to the administration server, allowing the process to complete successfully.
No RatingsRatings 0

Comments (2)

photo
1 Dennis van Remortel commented   Permalink No RatingsRatings 0

excelent tip! Thanks

photo
2 Chad Scott commented   Permalink No RatingsRatings 0

I've been talking with the AdminP developer, and we're not sure why this seems to be working. I used it with a customer and saw the results documented in this posting, but I'm wondering if anyone else has had different results.

Add a Comment Add a Comment

Previous |  Main  | Next
Skip to main content link. Accesskey S
IBM Lotus Connections Help Tools About