Conference rocks::dec_edi

    Mauricio,
    
    Firstly, OBB can cache its proxies which can then become stale. The
    only way I have confidence that what 'obbshpxy' displays is what is
    used is to force all existing servers to stop obbmstp '*'. This only
    needs to be done when amending proxies.
    
    Next, how is your proxy set up on the server, obbshpxy, ideally as most
    PC's have no real concept of users you should have the proxy on the
    server defined with user defined as '*' i.e. wildcarded.
    
    Next, try using the ObjectBroker system administrator on the PC to
    try to look at the server e.g.
    	obbmsho -A -n <server_node> 
    This should test the proxies but not involve any DEC/EDI code.
    
    Graham

    Hello Graham
    
    Thanks for your help. I'll try the commands, but I think the end result
    will be an OBB_INV_NOTAUTHORIZED error status. I even tried to add a
    "passall" proxy but didn't work. Is there any way to set a flag to
    trace the request and see the node name OBB agent thinks it's
    receiving?
    
    Thanks again
    
    Mauricio

ObjectBroker is just determined to use the full form of a name, 
e.h. jmekn.reo.dec.com in preference to jmekn. 

Even if you think it''s been set up correctly.

To see what OBB is up to on the server, edit file .obb_login

e.g. From root ...

# su - decedi
# cat .obb_login

OBB_TRACE_FLAGS=RTSO
export OBB_TRACE_FLAGS


You may then have to start tracing on Servers as described
in the manuals. ( #obbmset -A -d1 )


If you are failing at the first proxy a server
may not be started, in this case it's almost certainly short vs long form
name.

M

    Hello Graham and Thompson
    
    Here are the results of tests requested in .1:
    
    At the DEC/EDI Server:
    
    #obbshpxy
    
    Local user              Remote User             Remote Host
    decedi                  *                       rmaestrali
    decedi                  *                       ccevolo
    decedi                  *                       lhferreira
    decedi                  *                       cssfer0301
    
    At the Win95 Client OBB System Administrator Utility:
    
    #obbmsho -A -n cssfer0301
    OBB_INV_NOTAUTHORIZED (e), Client user is not authorized to access
    server. 
    
    

    Hello Thompson
    

>
>ObjectBroker is just determined to use the full form of a name, 
>e.h. jmekn.reo.dec.com in preference to jmekn. 
>
    The problem is that this customer DOES NOT use full form TCP/IP host
    names!! They don't even have DNS up and running!! The only use HOSTS
    file to translate TCP/IP addresses to host names. And they don't use
    full form, only a single host name. Do you see any way to get OBB to
    work given this scenario?
    
    I'll do the tests you suggest on .4 and post the results back here.
    
    Thanks for any help.
    
    

    Well, from an NT DOS box I can
    
    set OBB_TRACE_FLAGS="RTS"
    obbmsho -A -n<my_server_node> > t.out
    type t.out | more
    
    Unfortunately, It doesnt show the caller's hostname. Also setting
    OBB_TRACE_FLAGS to "A" generates more information, but again no
    hostname.
    
    Maybe others know of other majic OBB flags to get the right
    information.
    
    As we dont get past the proxy check on the server, we will never start
    a server and hence all the server side things MArk suggested wont get
    reached.
    
    Maybe the folks in the ObjectBroker conference might know better ways
    of figuring out what's going on.
    
    Graham

    
    Is it possible to run DEC/EDI V3.1A with OBB V2.7? Is it supported?
    It seems that we have mode troubleshooting mechanisms with V2.7.
    
    Maur�cio

Hi,

Yes it's supported.



Mark