Conference pamsrc::objectbroker

    
    Can anyone answer this question from a student? He is pursuing it
    through the "real" support channels, but questions have to go through
    the campus CLSG rep, to DIGITAL, back to the rep, and then to Mike
    Yukish. If the answer isn't simple, please don't spend time on it...
    
    Thanks,
    
    JP
    
    
    
From:	US1RMC::"[email protected]" "Mike Yukish" 27-FEB-1997 15:06:31.20
To:	"John H. Parodi  13-Feb-1997 1614 -0500" <send::parodi>
CC:	
Subj:	Re: ObjectBroker and NT 4.0

John,

I have a question for you, about running the ObjectBroker demos. I seem to
be having endless troubles with the advertisement registry.

trying to run the Bank Example 3, I have the client on a Solaris box and
the server on an NT box. If I generate the *.obr file on the server, copy
it to the client, and use 'get obj ref from file' on the client, everything
works fine. If i use obbreg -O ... on the server, the server gets
registered fine. When I run obbmerge ... on the client, to get to the
advertisement registry, I get

elvis 11% obbmerge -s -n revenge advertisement
OBB_REG_NOREMOTE (e), The registry on system `revenge' is not reachable.

Same thing if I try to go the other way.

for the C++ example, the server creates *.obr files for a bunch of objects.
these are obbreg'd into the advertisement registry on the same computer.
The client, also on the same computer, then should get the objects from the
advertisement registry and do its magic. when i try to run this demo, the
client fails during the NamingService resolution code.

It appears the problem is with the registries. Isthere some kind of admin
stuff i am missing? the network tests work, client-server works when the
client gets passed via file the objref, but any action requiring access to
the advertisment registry fails.

help!



***********************************
Mike Yukish

[email protected]
http://elvis.arl.psu.edu/~may106/yuke.html
(814) 863-7143

Applied Research Lab
PO Box 30
State College, PA 16804

Unless he is running ObjectBroker V2.7-11, he probably running into
the known problem with starting server processes on Window NT 4.0.

The V2.7-11 release contains an update to work around changes 
made in Windows NT 4.0 concerning credential managers.

Try hand starting the Name Service server and the application
servers.

Paul Patrick

    
    He is running OBB V2.7-11 on the NT system and -10 on the Solaris
    system.
    
    Example 3 calls for hand starting the server using the server -c
    command, so he is running the server prior to the client trying to
    connect.
    
    JP

    > Example 3 calls for hand starting the server using the server -c
    > command, so he is running the server prior to the client trying to
    > connect.
    
    He will have to hand start the name server too.
    

    
    He claims to have started everything. Still no joy -- any help
    appreciated.
    
    JP
    
Subj:	Re: Have you hand-started the Name Server?

At 2:06 PM 3/6/97, John H. Parodi wrote:
>Mike, if you know what and where the name server .exe is, just start it
>up in a separate window using the executable's name. At least that's how
>we do it when demonstrating the example code at trade shows and such.
>

I started it on the WinNT. obbmerge still does not work.

I now have objectBroker installed on two WinNT boxes and a solaris box.

On one box (revenge) I have the proxies set up:

remote user: jdm111
remote host: jdm
local user: jdm111

on the other I have:
remote user: jdm111
remote host: revenge
local user: jdm111

On both machines I have manually started obbnamsrv.exe
On both machines, I can use the implementation Manager to see the other's
implementations. I can ping from one to the other. On both, ObjectBroker
was installed in c:\win32app\obroker\... Both run v2.7-11

I can't merge the advertisement registries from one to the other. I have
tried using the command line and the GUI.

A different person has done the installation on each computer, so i
wouldn't expect a systemic error from that. None of the three computers can
merge with the others. This is really exasperating, we had no troubles with
Orbix seeing the other computers, or starting the server process. we can't
do either with ObjectBroker.


***********************************
Mike Yukish

[email protected]
http://elvis.arl.psu.edu/~may106/yuke.html
(814) 863-7143

Applied Research Lab
PO Box 30
State College, PA 16804

.
.
.

John,

another question (sorry)

>
>As far as auto-start in general, OBB certainly has it. My (limited)
>understanding was that if you had 2.7-11 running everywhere, this
>would work as expected.

The problem is I don't know how it is expected to work. There are no demos
or explicit instructions anywhere! This would seem to be an important
feature that would get due attention.  My guess was (on winNT):

1. Use quickstart on the foo.idl file, generate client and server
executables, foo.iml file
2. edit the foo.iml file so activation type is 'program', activation string
is "C:\\....\\fooServer.exe"
3. Make registration file using obbcomp -a foo.reg foo.udl foo.iml
4. register using  obbreg -I foo.reg
5. Run the client. For quickstart, the object reference for the server is
already embedded into the code.
6. This would, in my perfect world, auto-start the server. It doesn't work.

Is this how it is supposed to be done?

***********************************
Mike Yukish