- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-27-2017 08:21 AM
I'm currently planning out my mid server setup. I'm hoping someone can recommend some best practices for mid server installs.
Currently we'll be using it for ldap use only. No discovery, etc, but that may come next year. We're a Windows environment. How many Windows servers are typically rolled out and howm any instances of mid servers on each Windows server is recommended. Are the sizing specs for Windows memory, hard drive space, etc realistic in the documentation or do they need to be bigger?
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-28-2017 08:48 AM
If your LDAP server is behind your firewall, then the MID server is a requirement.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-27-2017 08:24 AM
For LDAP, you don't need much. The sizing requirements are sufficient as documented. You can get started with one MID server. You may want to consider 2 for fault tolerance, allowing you to do maintenance on one server vs. another.
As you look in to Discovery, you will have other requirements to consider like location of the data centers to discover, number of subnets, connectivity, load balancing the MID severs, etc. You can consider those as you grow, but for now, they are not a concern.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-27-2017 08:36 AM
Thanks for the reply Chuck. I'm looking through the docs right now for fault tolerance. It recommends not using a cluster for ldap. Can 2 still be setup for fault tolerance in a non cluster environment? I'm probably missing some info here that I still need to read through. Also, how about for my dev, test, environments. Is it recommended to just use the same mid servers? Just point all instances to the same mid servers?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-27-2017 08:39 AM
It's been a while since I set up LDAP via MID server so I'm not able to answer your question on fault tolerance. I'll defer to another SME.
As for dev, test, etc. Best practice would be to have your SN dev instance point a non-prod LDAP server so you can test, make crazy data, etc. without risk of production issues. When you've got it figured out, you can move it to UAT/Test, which ideally would talk to another non-prod LDAP server, but could be the same as dev. Finally, when you get it to prod, you talk to the production LDAP server.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-27-2017 10:06 AM
Yes, that makes sense. Thanks. If one does have a MID server is best practice to have ldap going through it? Seems like there's a couple of options.