Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
netmonitor questions
raoliver
Can anyone describe the differences in the user/group checking when netmonitor=no (recommendation for bug 33811 and article 49028) and when netmonitor=yes. Describe in terms of LDAP (active directory, mixed mode) on windows, TeamSite 5.5.2 service pack 1.
Does netmonitor=no try to cache users/groups in TeamSite and netmonitor=yes not cache? or is it the reverse?
If LDAP is users and/or groups are updated will both settings see the update or will one require a reboot to see them?
Find more posts tagged with
Comments
Bryan_K
Check out this post. We were wondering this exact same thing. I was able to get an answer from IWOV.
http://devnet.interwoven.com/forums/cgi-bin/showflat.pl?Cat=&Board=PRODUCTS_TEAMSITE&Number=3712&page=0&view=collapsed&sb=5&o=0&part=2&vc=1
raoliver
Thanks. I did get this information from Interwoven on what netmonitor does:
----------------
Netmonitor is a new implementation of the code that maintains user-group
relationships in TeamSite 5.5.2. If netmonitor is disabled, then server uses
teamsite 5.0 implementation of this functionality. TeamSite server sends
requests to domain controllers for all configured domains in the domain list
and collects the group information for each user in the TeamSite roles
files. This is done when you start TeamSite, when you run iwreset and every
10 minutes.
With Teamsite 5.5, if netmonitor is enabled, server will update group-user
list asynchronously (server runs
separate thread for each domain it cares about). The primary reason for
introduction of netmonitor is to collect the user and group relationship for
instantaneous startup time and iwreset propagation time. In TeamSite 5.0
this is done synchronously meaning until the query for first domain is over
the new one will not be made and after collecting all the information the
TeamSite is started.
Simple rule: if server startup time is acceptable without netmonitor (less
than a minute ?), then netmonitor is not required.
Whenever granting access to a shared workarea or a shared branch the latest
user-group list generated by netmonitor or group updater (5.0) is used .
This is the same list that is last recorded in the iwtrace.log.
----------
I theorize that bug 33811 (that IW won't share the deatils of) is in the new netmonitor code, which is why 49028 recommends turning it off (with no information on why you are turning it off or what impact it might have).
Edited by raoliver on 11/07/02 07:18 AM (server time).
Bryan_K
Couldnt have said it better myself. Hopefully SP2 will correct this issue.