[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

Title:*OLD* ALL-IN-1 (tm) Support Conference
Notice:Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:IOSG::PYE
Created:Thu Jan 30 1992
Last Modified:Tue Jan 23 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:4343
Total number of notes:18308

40.0. "Need advice: DDS Prime vs. performance" by SWAM2::RHODEWALT_BR (Open. Close. Repeat.) Tue Feb 18 1992 23:14

    
    Any experience out there making DDS the primary search directory? Any
    horror stories?
    
    My customer wants to do this because of the friendlier search features,
    but I'm not sure this would help. 
    
    The particulars:
    
       Standalone 4000-300 (a second, smaller machine to be added this year,
       clustered)
       VMS 5.4
       ALL-IN-1 2.4
    
       300+ total users, less than 100 at a time, captive in ALL-IN-1
    
    A document I have (David Hare, ALL-IN-1 V2.3 and DDS: An Implementation
    Guide, V1.1, 1990) says that "the use of DDS Prime can increase the
    ALL-IN-1 image activation time by 30%, while the use of DDS at all will
    reduce by approximately 5% the supportable number of ALL-IN-1
    subscribers."
    
    Bruce
    
    
T.RTitleUserPersonal
Name
DateLines
40.1memoriesAIMTEC::WICKS_AVote Bill'n'Opus for a weirder USAWed Feb 19 1992 01:2513
    Bruce,
    
    Apart from Sir David Hare's document which is of course near perfect
    the next best description I saw on this topic was Chapter 2 of the
    ALL-IN-1 version 2.3 release notes (volume 1) - of all places
    
    I don't have them on-line anymore though I did print them off for
    sentimental reasons.
    
    Regards,
    
    Andrew.D.Wicks (who was vaguely briefed on DDS)
                                                                 
40.2Release Notes (v2.3) on DDSIOSG::EDMONDSONOf making many books there is no end (Eccl.12:12)Wed Feb 19 1992 10:05489
Oh Andy, I didn't know you cared....

Here's that sentimental chapter (it's in .MEM format, so bold lettering will 
appear as a duplicate line - sorry).

ro

                              
                              Chapter 2

                 THE MESSAGE ROUTER DIRECTORY SERVICE



Your ALL-IN-1 Version 2.3 kit includes Message Router Version 3.1.
This version of Message Router includes the Message Router Directory
Service, which is known in ALL-IN-1 as the Mail directory.

    ________ _______ ___ ____ __________ _____         ________
The ALL-IN-1 Version 2.3 Mail Management Guide and the ALL-IN-1
_______ ___ ____________ _____
Version 2.3 Installation Guide give details of the Mail directory.
This chapter covers issues relating to planning the use of the Mail
directory, and to populating the Mail directory.  The Release Notes
chapters on installation, on software problems and restrictions, and
on documentation and Help problems also contain information about the
Mail directory.  It is important that you read all these sections
before you adopt or set up the Mail directory for use with ALL-IN-1.

Using the Mail directory enables you to search for addressees on the
basis of a wide range of attributes.  For example, if you are not sure
of a person's full name, you can search the directory for that person
by entering part of their name, or the department where they work.
You can also identify groups of users on the basis of attributes that
the users have in common.  When you use the Mail directory, you have
access to all the users in the network.  It is also possible to
include users who are external to your network (for example, X.400
network users).

You can use the Mail directory while you are addressing mail messages,
when you are arranging meetings, and when you are creating
distribution lists.  For details of the facilities that are provided
by the Message Router Directory Service, refer to the chapter on
                                ________ ____ __________ _____
addressing mail messages in the ALL-IN-1 Mail Management Guide.

The Message Router Directory Service is used by Message Router
gateways.  These include the Message Router X.400 Gateway, the Message
Router/S Gateway and the Message Router/P Gateway.  If any of these
gateways are part of your mail network, you can use the Mail directory
in ALL-IN-1 to address mail to users of other mail systems through the


                                 2-1

THE MESSAGE ROUTER DIRECTORY SERVICE
THE MESSAGE ROUTER DIRECTORY SERVICE


gateways.  Updates to the directory, either at the gateway or from
ALL-IN-1, are automatically available to all users of the directory.



2.1  Planning the Use of the Mail Directory
2.1  Planning the Use of the Mail Directory

The Message Router Directory Service is a single, distributed
application which is used not only by ALL-IN-1, but also by addressing
services for Message Router gateways.  It is therefore essential that
you plan its use as a whole, taking into consideration its use by all
products.

Implementation of the Message Router Directory Service within ALL-IN-1
is optional.  During installation, you can choose whether or not to
use the Mail directory.  If you choose to use it, you can choose
whether to use it as the primary (default) directory, or as a
secondary directory that users must explicitly request.  Once you have
installed ALL-IN-1, you can modify the way you use the Mail directory.
If you choose not to use the Mail directory when you first install
ALL-IN-1 Version 2.3, you can add it later.

When planning the use of the Message Router Directory Service within
ALL-IN-1, you need to make the following decisions about its use at
each node or cluster:

      o  Should it be used by ALL-IN-1?

      o  If it is to be used by ALL-IN-1, should it be the primary or
         secondary directory?

      o  Should the Message Router Directory Service node be a world
         search node or not?

In making these decisions, you need to consider the following:

      o  What other components, both on and off the node, will use the
         Message Router Directory Service?

      o  What are the resource requirements of the Message Router
         Directory Service in terms of:

          -  Disk requirements

          -  Central processing unit (CPU) usage

          -  Memory usage




                                 2-2

                                  THE MESSAGE ROUTER DIRECTORY SERVICE
                                  THE MESSAGE ROUTER DIRECTORY SERVICE


2.1.1  Should the Message Router Directory Service be used in
2.1.1  Should the Message Router Directory Service be used in
       ALL-IN-1?
       ALL-IN-1?

You cannot use the Message Router Directory Service unless it is
installed and running locally.  The costs associated with this include
the following:

      o  Disk space for the Message Router installation

      o  Memory and processor time to run the Message Router Directory
         Service

      o  Disk space to store the Message Router Directory Service
         database


Using the Message Router Directory Service with ALL-IN-1 increases the
size of the ALL-IN-1 image, and imposes a slight additional load on
memory.  This additional load is largely independent of the number of
users on your ALL-IN-1 system.

Since the implementation of the Message Router Directory Service
increases memory usage, systems that are short of memory are affected
more than those that have plenty of memory.

Once you have set up the Mail directory for use with ALL-IN-1, the
time taken for users to log in to ALL-IN-1 is increased slightly, as
is the time taken to use mail functions for the first time in an
ALL-IN-1 session.  The extent of this increase in performance times
depends on the number of users on the system.



2.1.2  Should the Mail Directory be the Primary or Secondary
2.1.2  Should the Mail Directory be the Primary or Secondary
       Directory?
       Directory?

We recommend that when you install ALL-IN-1 Version 2.3, you use the
Mail directory as the secondary directory (that is, with the value of
the logical name OA$DDS_PRIME as 1).

When an ALL-IN-1 user enters a name, or part of a name, in an address
field, ALL-IN-1 attempts to validate the addressee.  After checking
for nicknames, distribution lists, special addresses and remote
addresses, ALL-IN-1 checks the entry against the entries in whichever
directory is primary.  Since Mail directory searches are more complex
than searches of the ALL-IN-1 directory, there is a greater cost
associated with using the Mail directory as the default directory.

The Mail directory is intended to be used after local mechanisms have


                                 2-3

THE MESSAGE ROUTER DIRECTORY SERVICE
THE MESSAGE ROUTER DIRECTORY SERVICE


failed to supply addressing information.  Its intended use is
analogous to a telephone directory, which you use to look up a number
for the first time.  If you know that you are likely to use that
number again in the future, you make a note of it in a personal
directory, where it is easier to look up.  Similarly, ALL-IN-1 users
should take advantage of local addressing methods such as nicknames
and distribution lists once they have found a person's details in the
Mail directory.

If you use the Mail directory as the primary directory in ALL-IN-1,
the response time for processes that use the Mail directory is
increased.  Response times for processes that do not use the Mail
directory are affected less.

As a rough guideline, to maintain the same levels of performance of
ALL-IN-1 when the Mail directory is the primary directory on a
mid-range system, you may need to reduce the maximum number of active
users by around three or four.  If the Mail directory is used as the
secondary directory, the impact on performance is not as great, so the
reduction in the number of active users would be less.



2.1.3  Should the Node be a World Search Node?
2.1.3  Should the Node be a World Search Node?

At a world search node, the Message Router Directory Service permanent
database contains details not only of the users (subscribers) whose
master copies are maintained at the local node, but also copies of
subscriber entries from all the other nodes in the network.  This
means that a world search node needs more disk space than other nodes,
in order to hold all the subscriber objects.  It must also have
sufficient CPU and memory resources to service both local requests and
remote inquiry requests from nodes that are not world search nodes.

We recommend that Message Router gateways be installed on a world
search node.

At a world search node, the ALL-IN-1 Message Header Search mail
directory (SMD) option searches all Mail directory entries on the
network.  It thus produces the same results as the Search other mail
directories (SOM) option on a node that is not a world search node.
These results are produced more quickly on a world search node than on
a node that is not a world search node.

On a world search node, an inquiry to the Mail directory involves a
search only on that node, whereas on other nodes, both the local node
and a world search node may be involved.  Therefore, lookups are
faster on world search nodes.  On the other hand, updates to the Mail
directory have to be made on the local node and on all other world


                                 2-4

                                  THE MESSAGE ROUTER DIRECTORY SERVICE
                                  THE MESSAGE ROUTER DIRECTORY SERVICE


search nodes, so updates are more costly on networks that contain
several world search nodes.

On very large networks, update and inquiry rates may be very high, and
it is important to establish the correct balance between having too
many world search nodes, where inquiry times are relatively fast but
updates are costly, and too few world search nodes, where inquiries
are slower but updates less costly.



2.2  Populating the Mail Directory
2.2  Populating the Mail Directory

ALL-IN-1 does not adopt existing Message Router Directory Service
entries.  Therefore, if you already use the Message Router Directory
Service, and some people who are to use ALL-IN-1 Version 2.3 have
existing entries in the Message Router Directory Service, you must
ensure that the following conditions apply:

      o  There is only one Message Router Directory Service entry for
         each user.  It is essential to avoid multiple entries for the
         same user in the Message Router Directory Service, because
         the gateways that use this directory service may reject mail
         sent to or from users with more than one entry.

      o  The Message Router Directory Service entry for each user
         contains all the information that is necessary for the
         Message Router gateways that they use.




2.2.1  Avoiding Multiple Entries
2.2.1  Avoiding Multiple Entries

It can be difficult to identify multiple Mail directory entries for
the same person.  You should therefore avoid creating additional Mail
directory entries for existing users of the Message Router Directory
Service when you do either of the following:

      o  Perform an upgrade installation of ALL-IN-1 Version 2.3, and
         some of the users of your existing ALL-IN-1 system have
         entries in the Message Router Directory Service

      o  Create a new ALL-IN-1 account for a user who has an existing
         entry in the Message Router Directory Service






                                 2-5

THE MESSAGE ROUTER DIRECTORY SERVICE
THE MESSAGE ROUTER DIRECTORY SERVICE


Upgrade Installation of ALL-IN-1 Version 2.3
Upgrade Installation of ALL-IN-1 Version 2.3

To avoid creating duplicate entries for existing users of the Message
Router Directory Service, once you have installed ALL-IN-1 Version 2.3
and converted the user profile, and before you execute the script
OA$LIB:MAIL_DIR_CONVERT, do the following:

      1  Review the ALL-IN-1 users to identify those who have an
         existing entry in the Message Router Directory Service and
         those who have no such entry.  To do this, use the Message
         Router MBMAN utility to produce a listing of the Message
         Router Directory Service subscribers.  Refer to the
         documentation for your Message Router gateway for information
         about the MBMAN utility.  Compare this listing with an index
         of the ALL-IN-1 user profile.  You may have to do this
         comparison manually, but if the existing Message Router
         Directory Service entries contain a user-supplied unique
         identifier, you may be able to automate this comparison.

      2  For users who have no existing Message Router Directory
         Service entry, set the MDFLAG to Y.  To do this, use the
         following command from the ALL-IN-1 manager's ALL-IN-1
         account:

         <WRITE CHANGE PROFIL USER="user", MDFLAG="Y"

         Ensure that users who do have an existing entry in the
         Message Router Directory Service have their MDFLAG set to N.

      3  Edit the script MAIL_DIR_CONVERT and comment out or remove
         the four lines of the first FOR statement, which sets the
         MDFLAG for all users to Y.


You can now execute the amended script MAIL_DIR_CONVERT to create Mail
directory entries for all those users who do not already have them.

To adopt the existing entries of those users whose MDFLAG is set to N,
follow the procedure described in the section on adopting existing
Message Router Directory Service entries.


Creating New ALL-IN-1 Accounts
Creating New ALL-IN-1 Accounts

When you create a new ALL-IN-1 account, set the MDFLAG to N unless you
are sure that this user does not have an existing entry in the Message
Router Directory Service.  The easiest way to do this is to use an
account template which has the Mail directory field set to N.



                                 2-6

                                  THE MESSAGE ROUTER DIRECTORY SERVICE
                                  THE MESSAGE ROUTER DIRECTORY SERVICE


To adopt the existing Message Router Directory Service entries of new
ALL-IN-1 users, follow the procedure described in the following
section.



2.2.2  Adopting Existing Message Router Directory Service Entries
2.2.2  Adopting Existing Message Router Directory Service Entries

To adopt existing Message Router Directory Service entries, so that
all the necessary gateway information remains in the entries, do the
following for each user:

      1  If the existing entry is owned by a remote node, log in to
         that node, and use the Message Router MBMAN utility to move
         the entry to the node where the ALL-IN-1 account resides.  To
         do this, use the following MBMAN command:

         MBMAN>
         MBMAN> MOVE DDS SUBSCRIBER node/qualifiers

         where:

          -  node is the node where the ALL-IN-1 account resides

          -  qualifiers give details of the subscriber's given name
             and surname


         If you do not do this, you cannot modify the entry from
         ALL-IN-1.

      2  From the local system, use MBMAN to add the correct ALL-IN-1
         proxy to the Message Router Directory Service entry.  The
         proxy should take the form:

         OA$node$ALLIN1

         where node is the node or cluster where ALL-IN-1 resides.

         Use the following MBMAN commands:

         MBMAN>
         MBMAN> SELECT DDS SUBSCRIBER/qualifiers
         MBMAN>
         MBMAN> MODIFY DDS SUBSCRIBER/qualifiers/PROXY=OA$node$ALLIN1
         MBMAN>
         MBMAN> ADD DDS MODIFIED_OBJECT
         MBMAN>
         MBMAN> EXIT

         If necessary, use MBMAN to modify the entry so that the first
         address listed is that of the user's ALL-IN-1 account.

      3  From ALL-IN-1, get the Mail directory identifier of the


                                 2-7

THE MESSAGE ROUTER DIRECTORY SERVICE
THE MESSAGE ROUTER DIRECTORY SERVICE


         entry.  To do this, search the Mail directory for entries
         that are likely to refer to the ALL-IN-1 user.  For example,
         search on the user's surname (last name).  Once a listing of
         entries is displayed, move the cursor to the appropriate
         entry and enter the following command:

         <GET #DDSID = OA$SCROLL_ADDRESS:32:2

         The identifier is placed in the ALL-IN-1 temporary symbol
         #DDSID.

      4  From ALL-IN-1, add the Mail directory identifier to the
         user's ALL-IN-1 profile entry, and set the user's MDFLAG to
         Y.  To do this, enter the following command:

         <WRITE CHANGE PROFIL USER="user", MDFLAG="Y", DDSID=#DDSID

      5  Optionally, copy the ALL-IN-1 profile information into the
         existing Message Router Directory Service entry so that the
         fields that are common to both contain the same information.
         To do this, set the symbol #DDS_ACCOUNT to contain the
         appropriate ALL-IN-1 username, and execute the script
         OA$LIB:SUBSCRIBER_CHANGE.SCP.  Use the following commands to
         do this:

         <GET #DDS_ACCOUNT = "user"
         <DO SUBSCRIBER_CHANGE

         Alternatively, you can leave the fields to be modified
         automatically the next time the user's account profile is
         edited.  This happens when the user uses the Set personal
         details (SPD) option from the User Setup menu, or when the
         manager or the administrator edits the account.




2.2.3  Deleting Multiple Entries
2.2.3  Deleting Multiple Entries

After you have set up the Mail directory, if you suspect that it
contains multiple entries for any user, you should do the following:

      1  Examine the listing of subscribers to identify the multiple
         entries.

      2  For each user with multiple entries, list the contents of
         each entry to determine whether there are any differences
         between the entries



                                 2-8

                                  THE MESSAGE ROUTER DIRECTORY SERVICE
                                  THE MESSAGE ROUTER DIRECTORY SERVICE


      3  If there are differences between the entries, use the Message
         Router MBMAN utility to modify the original entry so that it
         contains the details from the entry created by ALL-IN-1

      4  If necessary, use MBMAN to modify the entry so that the first
         address listed is that of the user's ALL-IN-1 account

      5  Use the MBMAN utility to delete the entry created by ALL-IN-1

      6  From ALL-IN-1, follow the procedure described earlier to
         adopt the updated Message Router Directory Service entry



40.3We use it at national PowerLARVAE::SHOREThe wonderful thing about tiggers...Wed Feb 19 1992 15:1916
    I am working on a site, National Power UK, who use DDS prime. We did it 
    because of the increased functionality in the directory searching. 
    
    We have not done exact measurements on the impact, but no-one has noticed 
    any significant difference, and there have been no complaints from the 
    users. The system is run on lots of dual host 4000s, although there are 
    some 3100. We currently have approx. 2000 users and will expand to 4000 by 
    the end of this year.
    
    So although we were a little worried about taking the plunge we have not 
    experienced any negative effects. We have been running DDS prime for about 
    4 months.
    
    If you want any specific details you could mail me on ANGELA SHORE @UCG.
    
    Rgds, Angela
40.4DDS Prime - OK !UTROP1::STEENIS_MThu Mar 19 1992 15:1278
    
    
    Hi,
    
    I've succesfully implemented DDS as primary addressing mechanism 
    at a large ALL-IN-1 IOS site in Holland.
    
    We use DDS as primary addressing mechanism because of the 
    Multivendor (ICL OfficePower, Digital ALL-IN-1 and External X.400) 
    nature of this account.
    
    Ok, DDS will increase the size of the ALL-IN-1 Image, but ALL-IN-1 
    Image activation at our site is NOT a problem. Just make sure the 
    ALL-IN-1 Image is on a fast disk and the image is CONTIGUOUS 
    (COPY/CONT).
    
    Furtheron, our large ALL-IN-1 nodes, as well as MRX Gateways, are 
    being defined as DDS World Search nodes. In our case (currently 
    �2000 DDS subscriber entries) this doesn't give any performance 
    problems from a user point of view.
    
    The basis of our appoach to DDS is KIS : "KEEP IT SIMPLE" :
    
    - ALL-IN-1 (departemental) systems are LOCAL nodes and responsible 
      of handling their local subscribers 
    
    - Big ALL-IN-1 nodes (several hundreds of users) are next to that
      being defined as World Search nodes (for performance reasons)
    
    - MRX Gateway nodes (currently one for external X.400 and EDI and   
      one for Internal ALL-IN-1 - ICL OfficePower) are ALWAYS DDS   
      World search nodes
    
      The internal Gateway is also the node on which 'foreign' DDS
      subscriber entries are being registered (ICL and External).
    
      The external Gateway will be split of the ONE Customer Wide
      DDS environment shortly for security reasons.
    
    Use of the right tools (Customer built DDS - OfficePower synch 
    procedures using ALL-IN-1 and X.400 mail and the EMS Synchronizer) 
    and the implementation of an fully equipped EMS Server System 
    ---which was completed very succesfully in the previous three 
    weeks--- are our KEYS to this succesful environment.
    
    Our DDS database will grow to �6000 subscribers on �40 systems in 
    the near future. The combined X.400/MAILbus environment is our 
    basis for EDI and countrywide ALL-IN-1 IOS implementation. Also 
    DDS is the key to implement (lots of) departemental ALL-IN-1 
    systems within this account.
    
    			    MAIL is BIG BUSINESS !
    
    			   DDS PRIME IS GREAT FUN !
    
    
    ALL-IN-1 IOS and DDS
    
    The ONLY disadvantage is the current ALL-IN-1 IOS V2.4 behavior 
    regarding to DDS...
    To do World Searches you must use extra keying and forms. 
    
    ALL-IN-1 V3.0 IOS will improve this behavior, by letting the user 
    choose automatically to extend the search beyond the local and 
    cache database to a world search node.
    
    Question : Does anyone know if the V3.0 DDS implementation can be
    	       used with ALL-IN-1 V2.4 IOS easily ?
    	       Will this be supported ?
    
    For more info, just send me a mail message (same for answer on my 
    question...)
    
    
    Regards,
    
    Martin van Steenis
    Dutch Social Insurance Account Group