naming services in multi-tiered environments

From: Beck, Joseph (jbeck@seic.com)
Date: Mon Jun 26 2006 - 14:44:46 EDT


Looking for best practices here.

In a production environment, we have web, app, and core tiers for the
various layers of our infrastructure.

For the web tier, there is probably not enough return to justify
implementing ldapclient (naming service).

In app and core tier, there is. I'd like to know how people architect
this when dealing with firewalls.

Our directory server sits in the core tier. Do I simply research which
ports/protocols are being used and poke holes?

Are there people out there doing this in the web tier as well and if so
do they place some sort of proxy in the app (middle) tier to service the
calls to the directory server(s) sitting in core? Or is there another
approach?

Appreciate the feedback,

Joe Beck Ciber Inc. - a consultant to SEI One Freedom Valley Drive |
Oaks, PA 19456 | p: 610.676.2258 | jbeck@seic.com
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers



This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:40:15 EDT