Conference abbott::teamlinks_windows

The reason that comes to mind is that they are somehow
using Internet or MAPI as their primary. Could you confirm
that they're using V2.7 and the ALL-IN-1 is the primary?

Also, see if they customized the Unit1-Unit4 labels. It
would be under [DDS], UnitLabels. This shouldn't be a
problem, but it's not the default code path, so perhaps
something happens.

I'm not the expert on our directory services support,
Jerry

    On one of our systems we appear to have values in org
    unit 1 and org unit 2 and the value for the second 
    unit is not displaying.  I have ALL-IN-1 IOS as the
    primary mail file cabinet with TeamLinks 2.7-001.
    
    I also have no entries under [DDS] for the UnitLabels.
    
    Any other ideas,
    
    Beth
    

It sounds like I misunderstood. I thought that you
meant that the fields were not visible (the labels
and the value fields were hidden). But I think you're
saying that the fields are there on the form, but
don't contain any data?

Thanks,
Jerry

    Jerry,
    
    You are right the fields are there but the data is not when using
    X500.
    
    Beth
    

    Beth
    
    What exactly do you mean when you say you have added values for these
    fields in X.500? X.500 out-of-the-box has a single OU attribute than
    can take multiple values (whose ordering is unpredictable). This is a
    different concept to the DDS OU1 to OU4 attributes which portray OU
    values in a predictable order.
    
    If you have customised the X.500 schema to introduce OU1 to OU4 fields
    then you are ok. You can map the Teamlinks UNIT fields onto their
    appropriate counterparts in the directory.
    
    I should go back a step. Why do you want to see these individual
    values? If they represent a strict hierarchy, and you want to be able
    to search on them and display them in the correct order, then to get
    the interface to look just like DDS you will have to customise the
    X.500 schema and Teamlinks mapping as above.
    
    Beth, sorry, I keep saying "you" when I mean "the customer".
    
    Dick

    Dick,
    
    I need to get some more information from the customer since you have
    explained this.  On one of our nodes at the CSC we have multiple values
    for the OU field and only one is displaying.  
    
    If the customer has done the same thing then I understand why his
    is not displaying either.
    
    I will get back to this when I get more information from the customer.
    
    Beth Andres
    

        Hi Dick,
        
        It's time for me to jump in here.  We've duplicated what the
        customer is reporting in the US CSC.  Here's what DXIM shows:
        
            /C=US/O=DEC/OU=ALF/OU=VSG/CN="John Doe"
            /C=US/O=DEC/OU=ALF/OU=VSG/CN="Bob Smith"
            /C=US/O=DEC/OU=ALF/OU=VSG/CN=CALLQ-DSA
            /C=US/O=DEC/OU=ALF/OU=VSG/CN="O. A. Sysm"
            /C=US/O=DEC/OU=ALF/OU=VSG/CN="Beth Andres"
            /C=US/O=DEC/OU=ALF/OU=VSG/CN="Bill Smythe"
            /C=US/O=DEC/OU=ALF/OU=VSG/CN="CXP Captive"
            /C=US/O=DEC/OU=ALF/OU=VSG/CN="Dave Burden"
            /C=US/O=DEC/OU=ALF/OU=VSG/CN="Sam P Adams"
            /C=US/O=DEC/OU=ALF/OU=VSG/CN="Sharon Hess"
            /C=US/O=DEC/OU=ALF/OU=VSG/CN="Paul Morabito"
            /C=US/O=DEC/OU=ALF/OU=VSG/CN=ALL-IN-1-CALLQ
            /C=US/O=DEC/OU=ALF/OU=VSG/CN="Alice Braswell"
            /C=US/O=DEC/OU=ALF/OU=VSG/CN="Alyce Omoregie"
            /C=US/O=DEC/OU=ALF/OU=VSG/CN="Dave Zaniewski"
            /C=US/O=DEC/OU=ALF/OU=VSG/CN="ELAINE GOURICK"
            /C=US/O=DEC/OU=ALF/OU=VSG/CN="Jill Anne Heft"
            /C=US/O=DEC/OU=ALF/OU=VSG/CN="Debbie Giannetti"
            /C=US/O=DEC/OU=ALF/OU=VSG/CN="Desktop 1 Server"
        
        When I pull down on Services and choose Directory Services, I
        enter "S" in the Last Name field and then Lookup.  Smith, Smythe,
        Sysm and System Manager are returned with ALF in the Unit 1 field,
        but the Unit 2 field is blank.  It misses "Desktop 1 Server"
        completely and Unit 2 should have returned VSG in all cases.
        ALL-IN-1 returns VSG as the Organizational unit for 4 cases, but
        "O. A. Sysm" returns "KAOS or EX-OAD".
        
        Real inconsistency and an apparent TeamLinks miscue.
        
        Dave Zaniewski

    Hi Dave
    
    My turn to jump.
    
    >          /C=US/O=DEC/OU=ALF/OU=VSG/CN="Bill Smythe"
    
    Don't forget that the OU=ALF and OU=IOSG terms in this Distinguished
    Name just indicate where in the tree the entry resides. It is the
    presence of OU attribute values in the entry itself that is important.
    (But I think you already knew that).
    
    If the entry has a single OU attribute, but with multiple values ALF,
    VSG then (because of the limitations of the Teamlinks/CFC/AIDA
    interfaces) you will only see one of these values, although you could
    search on either.
    
    By default, the Unit1 field on the Directory Services form maps onto OU
    and Unit2 etc do not map onto anything, so Unit2 will inevitably show
    blank.
    
    If you have customised X.500 to make it look more like DDS (adding
    attributes OU1, OU2 ... like I mentioned earlier) then you are ok, you
    would map Unit -> the OU1 attribute, Unit2 -> the OU2 attribute etc.
    
    Dick
    

    Dick,
    
    If X500 is set up to look more like DDS with org unit 1 to org
    unit 4 then can the TeamLinks client just pick these values up
    and display them in the Unit 1 to Unit 4 fields on the Directory
    Services window.
    
    They don't really care what the unit Label says so modifying
    the entry in office.ini to get the label name changed is not
    a big deal to them.
    
    I am assuming the servers will just pass this information to
    the TL client.
    
    Thanks,
    
    Beth
    
    

    That's right. You can search on them and display them.
    
    But it's not quite a free lunch.
    
    Assume you have customised the X.500 schema with the following new
    attributes: OU0, OU1, OU2, OU3. I am assuming that the attribute OU
    will still be populated with all the values from Profil.
    
    Then you will need the following logical definitions on your AIDA
    system:
    
    def/sys/exec OA$AIDA_DDS_ORG_UNIT  "OU0;SW"
         (That's why I made the first one 0 :-)
    def/sys/exec OA$AIDA_DDS_ORG_UNIT1 "OU1;SW"
    def/sys/exec OA$AIDA_DDS_ORG_UNIT2 "OU2;SW"
    def/sys/exec OA$AIDA_DDS_ORG_UNIT3 "OU3;SW"
    
    If you don't want to allow partial matches on searches then leave out
    the Ws.
    
    Sorry about the trickery, but the TL/CFC/AIDA interface is very DDSic.
    There are some variations on the above that you could use, but if this
    is sufficient I'll leave it at that.
    
    Of course those attributes will have to be populated. This is a simple
    extension to the X.500 mapping policy script. Do you need more details?
    
    By the way I didn't realise you could customise the labels on the
    Directory Services window. Do you have a pointer to a description on
    how to do it?
    
    Cheers
    
    Dick

    Dick,
    
    I am going to give the customer the information you just provided
    me, thanks.
    
    
    The documentation on changing the pointers is on page 5-8 of
    the TeamLinks Client Administration Guide or if you have
    a copy of custom.wri from TeamLinks 2.5 the section is
    Customizing Directory Service Unit Labels.
    
    
    Beth
    

        Thanks for the new information Dick.  This AIDA thing just keeps
        growing more features every day 8-)
        
        Dave Zaniewski

    Dick,
    
    I am asking this because I know this will be the next question
    from my customer.  Is there any place these AIDA logicals are
    documented?
    
    Thanks,
    
    Beth
    

    http://www-iosg.reo.dec.com/awi/ALFFA/%22[IOSG]PUBLIC%22.TEAMLINKS
    
    Dick