Multiple Notes Named Networks and Address Books

pts.
Tags:
Lotus Domino
Microsoft Exchange
Good Day, I currently manage 9 domino servers in 1 NNN. This domain contains 1000 corp users and 6000 stores. I'd like to configure multiple notes named networks and seperate the stores from our corp users but i'm finding very little info about how I would go about doing this. 1 question is how do I manage multiple address books? Create a new addbook for stores and add it to Directory Assistance? I think i've got the replication/connection issues .. but in seeing so little info about this.. it makes me nervous.. is this a good idea? Is it worth the effort? Any reading material on this would be greatly appreciated, as well as any experience w/ this process. i'm always looking for experienced people to bounce my ideas off of. I don't think platform should play in to this too much, but we are a mixed environment .. windows/iseries/redhat.. on 6.5.2fp1 and others. thanks for any feedback. Richard

Answer Wiki

Thanks. We'll let you know when a new response is added.

You ask if this is a good idea and worth the effort, but you didn’t say WHY you wanted to separate the stores from the corp users. What is it you’re trying to accomplish? Also, do the stores need to be separated from each other, or just from the corp?

Discuss This Question: 5  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Richgoe
    I'd like to seperate the groups to assist w/ manangement/administration. to Deligate sub-administrators if you will. Also, to reduce the amount of communication that is being sent to our stores from people who don't need to send to them. For organization.. to me, it just seems like the right thing to do - to seperate these address books. I'd simply to to create a NNN named CORP and a NNN named STORE - which I can do.. but it's the seperating the addbooks that scares me. How will people access these seperate addbooks? Can I say only some people can use the store addbook and others can't..
    0 pointsBadges:
    report
  • Stiletto
    I'm not trying to talk you out of this, because there may be some very good reasons for it. I'll just address a couple of your points/questions. Delegating administration duties can be done from the Security tab of the Server document. This doesn't require a separate NNN. >Can I say only some people can use the store addbook and >others can't.. Of course. The address book is a separate db with its own ACL. Of course, administering the list could have alot of administrative overhead. Are the users already separated onto different servers? Do you have applications that both NNN would need to access?
    3,830 pointsBadges:
    report
  • Richgoe
    You mention NNN as if it's a means of separating users and stores. The NNN is a means of telling servers how to connect, especially for mail routing; for users, the impact is only when opening databases. The following is from Domino Admin Help... "A Notes named network (NNN) is a group of servers that can connect to each other directly through a common LAN protocol and network pathway -- for example, servers running on TCP/IP in one location. Servers on the same NNN route mail to each another automatically, whereas you need a Connection document to route mail between servers on different NNNs. "Lotus Domino expects a continuous connection between servers that are in the same NNN, and serious delays in routing can occur if a server must dial up a remote LAN because the remote server is inadvertently placed within the NNN. Also bear in mind that the Notes Network field for each port can contain only one NNN name, and no two NNN names can be the same. "NNNs affect Notes users when they use the Open Database dialog box. When a user selects Other to display a list of servers, the servers displayed are those on the NNN of the user's home server for the port on which the Notes workstation communicates with the home server. Also, when users click on a database link or document link, if a server in their home server's NNN has a replica of that database, they can connect to the replica." The Domino Directory contains all registered "users" in the domain as well as information about the domain; you do not want to go messing around with removing users or stores from it. I suppose you could create directories or directory catalogs containing subsets of the directory information. You might look at the directory catalog and cataloger process.
    0 pointsBadges:
    report
  • Richgoe
    You mention NNN as if it's a means of separating users and stores. The NNN is a means of telling servers how to connect, especially for mail routing; for users, the impact is only when opening databases. So than.. what is the point. if it's only mail routing and connections, then why not put all servers in the same NNN? Then mail would route w/o a connection doc and that would be that. Who cares what happens when a user hits ctrl-o. IMO, they should never have to do that anyways.
    0 pointsBadges:
    report
  • Rapple
    Richgoe, from the information given, you have already had two really good answers from Stileto & TedNYC. I read your response to the first question to be that you think that 1) There is an administration problem. By inference you feel that are doing to much in the centre and would like some help. 2) You think that the corporate users (head office??) and the stores (branch offices or separate companies??) should not be able by default to talk to each other. Clearly without knowing a lot more about your environment it's difficult to advise but for 1) is this the case? If so, what administration is causing you the most pain and how do you do it? For 2) While you may think that this is sensible what does the business i.e. your customers (users) think? Is it really your decision? I say this because you also mentioned in your response that if you separated the address books how would the two sides talk to each other if they needed to which suggests that you haven't yet got all the requirements. I would think that some simple business analysis with some key users would be appropriate before going any further. Splitting up directories is not a simple process and has a number of pitfalls. It may be that you do need to do this in which case you may also need to create multiple Notes domains. But consider, is this just for mail? If you have application databases their security will make life even harder for you. Be really sure that this is something that you need to do because it will take a lot of effort to do this at low risk. There are many simple things that you can do to spread adminstration load and they don't involve the fundamental things that you seem to be looking at. I would urge you to look at these first. To put this in perspective I used to run an 8 server setup with 1 Notes domain, 1 Notes Named network (TCPIP), There were three groups of servers effectively managed by three administrators and the directory administration was handled by HR and a Helpdesk, this was achieved simply through the standard Roles available to the directory. We had partner companies using databases on one of the servers. We had one address book for our domain and 3 extra address books for other Notes domains of our sister companies. Client addressing wasn't an issue, the address books were chained in the client settings and the local address book was searched first. Broadcast messages were handled by clear naming conventions on the group distribution lists and follow ups on abusers! Distribution lists themselves were handled by user departments. We adapted the Standard directory by adding a specific view to be used as a telephone directory (to our needs) which could be sorted by department, location etc and then added a couple of buttons to that view only that allowed a user to create a mail to multiple selections from that view. (Most developers could do this with half a day including testing.) That did for most people for emails to dynamic gropus and gets round the distn. list maintenance issue. However for those that wanted to maintain a list, a simple cut and paste from the address list of a mail generated in this way maintained the distribution list! The conventions were all part of the four page email guide that users received when they started to use the service. I have always found that a lot of issues stem from the users not getting (or thinking they don't need) training in techniques for efficient use of their desktop tools. Such guides can be well worth the creation effort. Most of this is easily achievable without doing a lot to Vanilla Notes or Domino. Good luck whatever you decide!
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following