Conference azur::mcc

If you buy an AM from an outside vendor, it usually comes with an
installation procedure that does things like enroll the AM,
load the dictionary, etc.  If all you received was an AM executable,
then you are probably missing some files.  In this case, you will have
to refer to the toolkit documentation (not the director documentation)
for how to set up an access module.

>    mail/messaging requirements, on a different system, using a local MIR.

The style of MIR is a red herring.  The AM does not care what kind of
namespace you are using.

-- Erik

    Let's forget about MIRs and DNS and all that for now.  If I understand
    what I *think* I understand about your situation, DNS/local MIR is NOT
    a problem you should worry about.   

    From your developer friend you should have gotten:  
    	1) the actual AM .exe
    	2) the dictionary load files (.com files containing DAP commands)
    	3) any icon bitmaps for the AM global entity (i.e. object class)

    This *entire* process is explained in Chapter 1 of the DECmcc Developer's Toolkit
    Reference Manual.  There is a figure on P 1-3 that shows the entire
    development process including enrollment & dictionary loading.

    You need to :
    	1. Add the new entity's dictionary information to the dictionary
    	2. Enroll the AM
    	3. Move your icon bitmap files (if any) to MCC_ICONS:
    	4. Try it out.



Step 1: Add the new entity's dictionary information to the dictionary

    The developer needs to also give you the translated output his/her MSL
    for the AM.   This will be in the form of a .COM file (THESE ARE NOT DCL
    FILES!) that contains the MCC Dictionary commands needed to described
    the new object class.

    There should be TWO of thes files:  one for the SERVICE Interface and
    one for the MANAGEMENT Interface.  E.g. the dictionary load files for
    Translan AM are "MCC_TRANSLAN_AM_SVC_IF.COM" and
    "MCC_TRANSLAN_AM_MGT_IF.COM". 

    To update the dictionary with your new object you need to use the
    Dictionary Administrator Program (DAP).   Do it like this:
    $ manage/tool/dictionary
    DAP> load class <class_name> from <name of svc interface .com file>
    DAP> load class MCC SUBCLASS <class_name_AM> from <name of mgmt interface .com file>
    DAP> EXIT

    for example, the Translan AM would go like this:

    	$ mana/tool/dic
    	DAP> load class TRANSLAN from MCC_TRANSLAN_SVC_IF.COM
    	DAP> load class MCC SUBCLASS TRANSLAN_AM from MCC_TRANSLAN_MGT_IF.COM
    	DAP> EXIT
    	$

    Note that the Dictionary Administrator program will automatically
    update the parse tables when you exit, so you may have to wait a while
    before you see the "$" prompt again


Step 2: Enroll the AM

    Now that the dictionary has your entity definitions, it knows all about
    your new managed objects.   Now you need to enroll your AM code to the
    director so that MCC can use the AM routines.

    you can either move your AM .exe file to SYS$SHARE: 
    	e.g. $ COPY MY_AM.EXE SYS$SHARE:*.*
    or simply define a logical to point to the AM code
    	e.g. define MY_AM disk$foo:[foobar.test.sources]my_am.exe

    Once you've done either of those, you just enroll it from MCC:
    	MCC> enroll my_am

    Once that's done, you should be able to use the AM from either the FCL
    or the iconic map.


Step 3: Move your icon bitmap files (if any) to MCC_ICONS:

    E.g. 
    	$ copy mcc_my_am_foo_icon.dat mcc_icons:*.*
    	$ copy mcc_my_am_bar_icon.dat mcc_icons:*.*


Step 4: Try it out.

    First try some commands from FCL.  

    Then try the Iconic Map. 

    See what happens.

    Report back here.



/doug

    Doug,
    	Great stuff!  I was successful converting to the local MIR, per
    usual, it was quite simple once I got things going...  I did notice
    that the TSAM wouldn't convert, and I still have some problems with the
    TSAM stuff, but I'll attack that later.
    	I'll be going to the Customer site later this morning to test your
    procedure...  Thanks for taking the time to steer a dimrod... 8^).  One
    thing about DECmcc, it sure knocks you down a few pegs, eh?
    
    /Mic